Talk about frustrating! Spending almost 10 hours to see it fail? Very frustrating.
Anyway, the article over here gave me enough information to apply a solution to my particular case. To give everyone an idea of my setup...
I have the following:
- a publisher at one location
- a subscriber at another (connection is via Internet, which is why it is so slow)
- the subscriber has an old MSDE installation for the (local) database, but was changed to SQL 2000 Personal way back to accommodate a larger database size, since MSDE has a 2GB limit.
Show/Hidden sql code
Will show a list of the servernames, as if you were to do a Show/Hidden sql code on your particular instance to pull back THAT particular server's name (keeping in mind, the server name may not be set or may be incorrect if you have actually changed the computer name after installing SQL)
According to the article mentioned above, the "srvid" should be "0" for the subscriber. To see if it is, run Show/Hidden sql code. If you get nothing or something else, then the instance you're working with is obviously NOT set to 0. If that's the case, drop the server that does show up OR the one that you want to be there, e.g. run Show/Hidden sql code, then add the correct one, e.g. Show/Hidden sql code.
After the above steps, run Show/Hidden sql code to hopefully show that your newly added server name IS, in fact, the one that you wish to use with merge replication.
References:
http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server-replication/4577/call-sp-MSmakegeneration
http://www.eggheadcafe.com/software/aspnet/29953789/2000-sp4-merge-agent-failure-the-process-could-not-make-a-generat.aspx
| Next > |
|---|








