Thank you for your post and sorry that you are experiencing this issue.

Is this problem occurring for all of the alerts or just this deadlock one?

Can you please check the following setting in the server properties for each monitored server on your Production Alert Repository and if required modify the Execution time-out to set it to 0 seconds.

Right click the computer in the Servers to show list and select Server Properties

In the Server Properties dialog for each sever and confirm that the Execution time-out Connection setting is set to 0 seconds. If it is not set to 0 seconds, can you please modify it so it becomes 0 seconds and then stop and restart the SQL Response Alert Repository.

Next monitor any new alerts and ensure that you are not getting the 'Alert is still being written to' in the alert details.

I found an article about Excluding paths from the Anti-Virus Protection on the Server. The acticle said the Documents and Settings file path needed to be excluded, we weren't doing that, I had it added and it's working like a champ.

"Thank you for your post and sorry that you are experiencing this issue.

Is this problem occurring for all of the alerts or just this deadlock one?

Can you please check the following setting in the server properties for each monitored server on your Production Alert Repository and if required modify the Execution time-out to set it to 0 seconds.

Right click the computer in the Servers to show list and select Server Properties

In the Server Properties dialog for each sever and confirm that the Execution time-out Connection setting is set to 0 seconds. If it is not set to 0 seconds, can you please modify it so it becomes 0 seconds and then stop and restart the SQL Response Alert Repository.

Next monitor any new alerts and ensure that you are not getting the 'Alert is still being written to' in the alert details."