Re: Replication error at subscriber's end
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Wed, 2 Aug 2006 08:21:56 -0400
It sounds like you have everything configured correctly. Can you enable
logging to determine exactly where it is failing?
In SQL 2005 the repldata folder is not automatically shared the way it is in
SQL 2000. You must share it yourself (create the share and give rights to
the SQL Server agent account on the subscriber rights to read and list files
and folders on the share folder and the files and folders underlying it).
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"NiTiN" <emailme.nitin@xxxxxxxxx> wrote in message
news:1154497619.365164.203720@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Good day,
I seem to be having issues with subscribing to a publication. The
actual error that I get on running the subscriber job is:
"The job failed. The Job was invoked by User sa. The last step to run
was step 1 (Run agent.)."
The agent process account is set to: "SQL Server Agent account", and
Distributor connection is set to: "SQL Server Authentication (sa)" (the
'sa' username & password of the Publisher/Distributor -- I also tried
with the 'sa' account of the Subscriber, but I still get the same
error).
The Management > SQL Server log shows the following:
----------
Date 8/2/2006 11:04:22 AM
Log SQL Server (Current - 8/2/2006 11:04:00 AM)
Source Logon
Message
Login failed for user 'sa'. [CLIENT: <local machine>]
----------
Also, I don't have a repldata share on the publisher/distributor. Isn't
that folder supposed to be automatically shared on configuring
publishing?
I'm running SQL Server Developer Edition 9.0.2047 (SP1) with Windows XP
on the publisher/distributor, and SQL Server Enterprise Edition
9.0.2047 (SP1) with Windows 2003 Server on the subscriber.
The publisher/distributor does have the subscription listed against the
publication, and there is connectivity as I'm able to connect remotely
and use transaction log shipping (log shipping not currently in use).
Regards,
N.I.T.I.N.
.
- References:
- Replication error at subscriber's end
- From: NiTiN
- Replication error at subscriber's end
- Prev by Date: Re: replication sequence
- Next by Date: Re: Replication error at subscriber's end
- Previous by thread: Re: Replication error at subscriber's end
- Next by thread: Re: Weird SQL Server 2000 behavior in Transaction Log Shipping
- Index(es):
Relevant Pages
|
