Hi Everyone,

I need help to reinitialize a subscriber subscription for merge
replication. So far, B server has been take offline, a new B2 server
was put in, and a DTS package moved all of the db in B to B2 . A has
been running alone on production. I have to get replication working
again. B2 now has a pull subscription that I try and 'reinitialize'
and 'start synchronizing' but I keep getting  "The subscription to
publication 'XXXXXXXXX' has expired or does not exist."

When I check Replication Monitor/Publishers, I see two entries:

XXX_merge__pub:db_name                Type:Merge
XXX_working_merge_pub:db_name    Type:Merge


On A, There are 2 entries for each of these in the Snapshot Agents
folder, but there is nothing in the Agents folders with names: Log
Reader, Queue Reader, Distribution, Merge.

The Miscellaneous Agents has 5 entries. However, the 'Replication
Agents checkup' agent shows:
Executed as user: NT AUTHORITY\SYSTEM. The agent is suspect. No
response within last 10 minutes. [SQLSTATE 01000] (Message 20554).
The step succeeded.

On the subscriber (B2 server) all I see is a pull subscription called

serverA:db_name:XXX_working_merge_pub

It is assigned to the right database, type=pull, but status= FAILED.
The job history shows that it connects to both A and B2 but I get:

Category:NULL
Source:  Merge Process
Number:  -2147200985
Message: The subscription to publication 'eccs_working_merge_pub' has
expired or does not exist.

Is it still possible to re-enable this merge replication? Why can't I
see a merge agent?

Clustered Index Not Working
Select distinct problems
CASE in WHERE clause
DESPERATE - Need help getting a SQL stored procedure output parameter to my .NET app
Cast/Convert Query help