June 2, 2005 at 11:42 am
I am getting the following messages:
----
The process is running and is waiting for a response from one of the backend connections.
-----
Category:COMMAND
Source: Failed Command
Number:
Message: {CALL sp_MSupd_ITEM_200522 (NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,2005-06-02 11:59:59.000,1,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,2005-06-02 08:19:41.000,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,82010,2005-06-01 00:00:00.000,'301180292',0,0x0006100000000000)} {CALL sp_MSupd_ITEM_200522 (NULL,NULL,NULL,NULL,NULL,NULL,NULL,'301180111',2005
----
Source: ODBC SQL Server Driver Number: S1T00 Message: Timeout expired
----
This is what I have done:
1. Stopped and started SQL Server
2. Rebooted server
3. Verified that MDAC is at latest level
4. Increased query timeouts on the distribution agent and restarted the agent
I am still getting timeouts with the same frequency. What should I try next?
😎
June 3, 2005 at 1:35 pm
We see this at times when the msrepl_transaction table gets too large, log reader is bringing over a large transaction, or many distribution tasks are running at the same time. Create a new distribution profile where CommitBatchSize = 1 and CommitBatchThreshold = 1. Set your distribution to use this profile and restart it. You can then switch it back to the default profile when it completes.
Hope this works for you,
Michelle
June 3, 2005 at 1:58 pm
Michelle - thanks! i did try this also. but it didn't make a dent. i think i've narrowed it down to a hardware issue with my SAN.
tell me if you think this tracks ...
while the timeouts were happening the Disk Queue length was thru the roof. i took the tables with the most updates pending out of replication. i was then able to restart replication without any timeouts. i created another publication with my most active tables, took a snapshot, started the distribution agent again, and taaa daaa! no more timeouts. although ... from the sounds of it, it seems like your solution should have worked, but it didn't ... what gives, if it isn't a disk issue? any ideas? bottom line is that it's fixed now ... *knocking on wood*
😎
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply