July 4, 2003 at 3:17 am
Hello..
I have two SQL Server 2000 (version: 8.00.760) that is running on win2000 Servers (sp3).
Both SQL servers are located behind a firewall.
Problem
I can set up a replication (transactional or merge) and the snapshot goes thru.
The replication works fine for a couple of hours, or days, than it suddenly goes down with the error "Could not connect to subscriber XXXXXX" or "The process could not query row metadata at the 'Subscriber'."
Then I start the agent again and I get the same error after a while...
Please assist...
Server1 is behind a Cisco Pix 515e ver 6.2.2
Server2 is behind a Clavister ver 8.2 (software)
The VPN type is 3DES
I had a "ping-loop" going for a couple of days and no packet was lost.
The key exchange works fine between the two servers.
Jonas
Jonas
July 4, 2003 at 10:14 am
quote:
The process could not query row metadata at the 'Subscriber'.
First of all I don't think this has anything to do with the Firewalls and/or VPN connection. I've seen this error lot's of times and usually if you restart the agent it will work (if it's not in your case then let me know). As I said it's only a temp error and the reason tfor this I suspect is that the merge metadata tables are locked through some user activity at the time, the agent tries to query them.
The other error
quote:
Could not connect to Subscriber
this can be caused by a slow/unreliable network or a heavily used subscriber not responding in time. You might try to change the connection timeout for the agent.
[font="Verdana"]Markus Bohse[/font]
July 13, 2003 at 11:45 pm
quote:
quote:
The process could not query row metadata at the 'Subscriber'.First of all I don't think this has anything to do with the Firewalls and/or VPN connection. I've seen this error lot's of times and usually if you restart the agent it will work (if it's not in your case then let me know). As I said it's only a temp error and the reason tfor this I suspect is that the merge metadata tables are locked through some user activity at the time, the agent tries to query them.
The other error
quote:
Could not connect to Subscriberthis can be caused by a slow/unreliable network or a heavily used subscriber not responding in time. You might try to change the connection timeout for the agent.
Hello Markus, thanks for looking at the problem.
I have restarted the agent several times but the problem is still there. It can go days or hours before it falis. The agent stops but I don't get any notification in the replication monitor.
Jonas
Jonas
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply