Has anyone come across the situation where after recreating a Transactional (push) subscription for replication, that is does not show up on the subscriber?
I recently had to delete a subscription, then delete a publication then restore a database. I was then required to recreate the publication... successful, then recreate the subscription... not so successful.
The publisher server, shows the publication, it shows the subscription sitting underneath it, replication monitor shows all the component, the job monitor on the distributor server shows the replication jobs... all of which show no errors.
But the following three three things are missing;
1. The subscription is no showing up on the subscriber under local subscriptions.
2. The subscription database, although created during the wizard, is not updating from the publisher.
3. Replication monitor will not show any response for the phase of "Distrbutor to Subscriber", when sending a trace token.
I am running MSSQL 2005 standard edition SP3 on Windows 2003, in a three server configuration;
Server 1 - Database engine (Publisher)
Server 2 - Database engine (Distributor)
Server 3 - Database engine & Reporting Services (Subscriber)
At a guess, with my limited knowledge, I am wondering if there is something in the distributor database that I need to look for/delete/clean up, given I have successfully since having this problem, created a publication and subscription to a different database, and restored the database to a test server and create a publication and subscription on the test servers in the same way I would in production.
My tests has me coming to the idea that, the servers/instances are find, just this particular database and replication have got themslves all out of shape and won't play the game.
Any help in this matter would be greatly appreciated.