This is driving me crazy.
Here is the scenario. I have recently converted the publisher from SQL 2000 to SQL 2005 SP2 Workgroup Edition. We have 10 Subscription databases that are still on SQL 2000 SP3. We have completely rebuilt 2 of the subscription servers within the past 3 weeks and they are on SQL2005
The problem is occuring on both SQL Server 2005 Subscription Servers. At first, I was able to replicate to the SQL 2005 subscription databases, but now, I am experiencing Timeouts in many different places.
The problem was first reported by Access 2003 users when they receiving a non-descript "Timeout Expired" message box. I am intermittently unable to connect to the server from a remote location. I get a more detailed Timeout Expired message. Occassionally (about 20% of the time), I get the message when attempting to open a table containing 10 records from within SQL Server Management Studion. And, lastly, I am unable to perform the merge replication. After 30 minutes or so, I get the Timeout Expired Messages shown in the images below.
On both of the servers, we were using Symmantec Endpoint Protection, so we removed it from one of the PCs to no avail. Now, when we attempt to sync to that server, the pc interface locks up. When I stop the replication from the server side, it frees up the interface (mouse and keyboard). Wierd.
Occassionally, I will get the Timeout Expired message when replicating to the SQL 2000 subscription database, but after a few attempts, it is able to complete successfully.
Some random notes:
I have Shared Memory (1), TCP/IP(2), and Named Pipes(3) enabled.
The problem is at the server level, and not the replicated database level because I get similar timeout errors with attempting to work with a non-replicated database.
In the Server Properties/Connections, I Enable Remote Connections and have set a query timeout of 600 (default was 0)
I have tried to Boost SQL Server priority, but that did not work.
Any help would be greatly appreciated.
Thanks, Russell
Start Free Trial
