Replication Timeout Issue

Greetings!

I am running into this error when running Replication:

The response message was received from 'https://replia.websitename.net/replia/replisapi.dll' and is being processed.

(f) The process could not connect to Distributor 'OURDATABASE-DB'.

(f) The process could not connect to Distributor 'OURDATABASE-DB'.

(f) Unable to complete login process due to delay in opening server connection

*******************************************************

01/11/2007 18:26:09 - Error during FINAL DB Replication. The process could not connect to Distributor 'OURDATABASE-DB'.

I am running Replication on a Windows XP Pro laptop, with 1 GB of RAM, 1.83 GHz CPU. Any ideas, suggestions and/or help would be appreciated!

Thanks!

Cristian E.

Please provide more information. What version of SQL server are you using? Are you using standard edition, enterprise, or express? Transactional or merge replication?

Gary

|||

Hello,

1. Is the Laptop computer your Subscriber or Publisher/Distributor?

2. If you do not do web sync, can you run sync through merge agent (replmerg.exe) from Console window command line using fully connected mode?

This posting is provided AS IS with no warranties, and confers no rights.

|||

I am using SQL Server 2005 Express version, Merge replication. I changed the History Verbose Level to a 2 and I got a different error:

(f) The response message was received from 'https://replia.websitename.net/replia/replisapi.dll' and is being processed.
(f) The process could not connect to Distributor 'ABCD-DB'.
(f) The process could not connect to Distributor 'ABCD-DB'.
(f) Named Pipes Provider: Could not open a connection to SQL Server [2].
(f) An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(f) Login timeout expired
(f) The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
*******************************************************
01/13/2007 09:31:39 - Error during FINAL DB Replication. The process could not connect to Distributor 'ABCD-DB'.

*******************************************************

I have already increased the timeout to 15-20 mins. Any other suggestions?

Thanks!

Cristian E.

|||

I am using SQL Server 2005 Express version, Merge replication. I changed the History Verbose Level to a 2 and I got a different error:

(f) The response message was received from 'https://replia.websitename.net/replia/replisapi.dll' and is being processed.
(f) The process could not connect to Distributor 'ABCD-DB'.
(f) The process could not connect to Distributor 'ABCD-DB'.
(f) Named Pipes Provider: Could not open a connection to SQL Server [2].
(f) An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(f) Login timeout expired
(f) The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
*******************************************************
01/13/2007 09:31:39 - Error during FINAL DB Replication. The process could not connect to Distributor 'ABCD-DB'.

*******************************************************

I have already increased the timeout to 15-20 mins.

The Laptop computer is the Publisher and it is running web synchronization (web services).

|||

Has it ever worked before?

Can you try this on your machine?

osql -S"ABCD-DB" -U"login"

See if you get the same error message for "Named Pipes Provider: Could not open a connection to SQL Server [2]. "

If you get the same message, then the problem is as simple as enable the protocols in your sql server setting.

I also noticed that the name "ABCD-DB" sounds more like a database name than a server name...

Regards,
Gary

sql