June 11, 2008 at 3:10 am
Sorry this is a repost
I orriginally posted in the sql 2000 replication thread thinking not reallising there was a seperate 2005 one.
Appologies if this is a really obvious question but as a recent graduate i have only been working with SQL server for a 6 months and this has got me pretty stumped.
I Tried to set up transactional replication with immediate updating subscribers between two servers
running 2005 sp2.
as soon as the initial snapshot had been applied to the subscribing database a big red cross appeared in the
replication monitor GUI
This turned out to be caused by the Queue Reader Agent Failing.
I have read around and tried several methods (in vain) to solve the problem including
sp_link_publication (or what ever it is called), Dropping and recreating the subscription and publication
and deleting the queue reader agent job in the sql server agent.
From my reading and limited knowledge i am not totaly sure the queue reader needs to be working for the replication
to be successful but it would be nice to get rid of the red X
Any advice on what to try next would be greatly appreciated
Also as this is my first (technically second) post Hi to everybody
The information below is extracted from the queue reader agents log output
2008-06-06 04:05:50.468 Connecting to OLE DB myPublicationServer at datasource: 'myPublicationServer', location: '', catalog: 'MyReplicatrdDB', providerstring: '' using provider 'SQLNCLI'
2008-06-06 04:05:50.500 The Queue Reader Agent has encountered the error 'Login failed for user 'sa'.' when connecting to 'MyReplicatedDB' on 'MyPublicationServer'. Ensure that the publication and subscription are defined properly and that both servers are running.
June 11, 2008 at 10:39 am
you should verify the credentials for the Queue reader Agent Job
* Noel
June 12, 2008 at 1:57 am
Please excuse my ignorance but how do i do this?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply