The process could not enumerate changes at the Subscriber.

The error "The process could not enumerate changes at the Subscriber", can mean a lot of things. But if you look on the details of this error on your enterprise manager you will notice that it says something like this:

General netowork error. Check your network documentation.

Yes, there is probably a network connection problem on the other end or the subscriber server is offline.

General Network error - cannot connect to subscriber db

Today Jan 18, 2007, I found out the the SQL Server Distributor, cannot connect to the subscriber machine probably for a day or two. The following error message log from the distributor machine tells us that there is a communication failure between the distributor and the subsriber.

Because of these communication problem, between the servers data are not transmitted to FCPHIL.

Communication link failure
(Source: SUBSCRIBERDB-XXX (Data source); Error number: 0)
---------------------------------------------------------------------------------------------------------------

The process could not connect to Subscriber 'SUBSCRIBERDB-XXX'.
(Source: SUBSCRIBERDB-XXX (Agent); Error number: 20084)
---------------------------------------------------------------------------------------------------------------
SQL Server does not exist or access denied.
(Source: SUBSCRIBERDB-XXX (Data source); Error number: 17)
---------------------------------------------------------------------------------------------------------------


The process could not enumerate changes at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
---------------------------------------------------------------------------------------------------------------
General network error. Check your network documentation.
(Source: SUBSCRIBERDB-XXX (Data source); Error number: 11)
---------------------------------------------------------------------------------------------------------------
The process was successfully stopped.
(Source: Merge Replication Provider (Agent); Error number: -2147199469)
---------------------------------------------------------------------------------------------------------------

SQL Server Replication Re Design

I changed the design of the replication. Before this changed the setup was, both, backup terminal server, Cargo Database, the Distribution database for the replication are on one machine.

This setup is not recommended. The ideal setup should be that each services must be housed on a separate machine, this way, if work is needed on each server, other services can continue their function normally.

Turned off Replication

Today Nov. 27, replication of data to FCPHIL Server will be temporarily disable, to allow remote users to work on remit2. Cargo data is temporarily moved to another server. We will temporarily dedicate this server as the distributor and as a Backup Terminal Server.

Remit 2 -Terminal Server slow

One reason why users encounter slow perfomance on the remit2 terminal server is because, it is transferring cargo data in manila. Hopefully next year we can be able to add a new server dedicated to this task. This server is also the Distributor for data transfer.

Replication Problem

Main problem with replication on our setup is the reliability of internet connection. Most of the time, data in the U.S are not replicated on the server in FCPhil because their internet connection is down. We have a dedicated server here in the U.S that process the replication, this server often cannot to connect to the server in FCPhil.