I have two machines running SQL Express that I am attempting to use as proxies for a client application as the security admin has deemed that outside clients can not connect directly to the main DB servers.
When I have one of the SQL Express boxes subscribed to my SQL 2005 standard server, everything is happy, but when I attempt to add the second SQL Express box as a subscriber, everything seems to blow up.
OK, I'm setup as a merge with updates and no filter since I want all of the servers to get all of the data. I'm also on a non-standard port but have my aliases setup, and I don't have any connection issues. When I run the subscription wizard from the management studio, it comes back with "Success", but about 2 seconds later, I get errors on both subscribers from the replication monitor. Oh, I am aslo setup for push subscriptions and am setup to run continuously.
Here is the error message from the rep. monitor.
Error messages:
No subscription is on this publication or article. (Source: MSSQLServer, Error number: 14050)
Get help: http://help/14050
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001
What I find odd is that It only dies when I try to add a second subscriber, and then it kills both of them. Any help or ideas on where I should look would be most welcome.
Thanks!
Adding a 2nd subscrber makes my Merge replication blow up.
SQLBOY36
I should have clarified that I replaced the actual information with HOSTNAME for security purposes. I network group would be pretty upset with me if I posted actual host information.
Thanks again!
Vaylor Trucks
It looks like your subscription isn't set up properly. Is that the actual name of your subscriber machine: HOSTNAME
csi_hugh
Tibor Biro
Just to add some information....
Our SQL Server 2005 Standard server which is acting as publisher and distributor is located in chicago with our SQL Express machines in NY and London. I've narrowed the problem down to the Lodon machine, but everything is configured the same as the NY box. I also double checked and made sure the snapshot share was visable to both machines.
Here are the error messages in the error log.....
2006-08-25 16:03:48.51 spid53 Error: 14151, Severity: 18, State: 1.
2006-08-25 16:03:48.51 spid53 Replication-Replication Merge Subsystem: agent HOSTNAME\SQLEXPRE-16 failed. The subscription to publication 'REP_GRP' could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscr
2006-08-28 10:15:07.07 spid60 Error: 14151, Severity: 18, State: 1.
2006-08-28 10:15:07.07 spid60 Replication-Replication Merge Subsystem: agent HOSTNAME\SQLEXPRE-16 failed. No subscription is on this publication or article.
Any help is most welcome. Thanks again.