The SQL server is too busy to respond to the request in adequate time. There
are two approaches to solving this:
1. Reduce the load on the SQL server
2. Increase the timeout for the command.
I would suggest going down the path of (1) before attempting (2). Just
blindly increasing the timeout can mask a real problem.
The easiest way to reduce load on a production system is to turn off the
distributor's logging options (on by default). To do this, edit the ADF and
set the <LogBeforeDeliveryAttempts>, <LogNotificationText>, and
<LogStatusInfo> to false (these are all documented in Books Online). You
still get basic logging for status tracking purposes, but this removes a lot
of extra logging that puts load on the server.
You should also look at whether you have the right indexes on your event and
subscription classes so that your match rules execute efficiently. You can
add index creation statements right in the ADF - look at the
If you need to increase the timeout for the distributor commands, you need
to specify the <WorkItemTimeout> element in the ADF and set it to a value
larger than the default (15 minutes).
Hope this helps.
Learn more about SQL-NS:
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
"Balaji Ramachandran" <[email protected]> wrote
in message news:[email protected]
> When I have multiple notifications which were setup to run at a particular
> time, I am not getting some of the notifications and I am getting this
> following error in the event log.
> What should I do?
> How do I handle this kinds of errors?
> Event Type: Error
> Event Source: NotificationServices
> Event Category: None
> Event ID: 6078
> Date: 5/10/2005
> Time: 7:20:26 PM
> User: N/A
> Computer: BILLPAY-BALAJI
> An error occurred while logging the delivery attempt for this
> <Distributor Id>1</Distributor Id>
> <Distributor Name>SpiderDist1</Distributor Name>
> <Distributor Work Item Id>93</Distributor Work Item Id>
> <Notification Id>703</Notification Id>
> Source: .Net SqlClient Data Provider
> Number: -2
> State: 0
> Class: 10
> Message: Timeout expired. The timeout period elapsed prior to completion
> of the operation or the server is not responding.
> Procedure: ConnectionRead (WrapperRead()).
> Line Number: 0
> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding.
> DistributorName: SpiderDist1
> For more information, see Help and Support Center at