Replication Distribution agent fails with error 17

Question

Replication Distribution agent fails with error 17

dpantekoek

SSC Enthusiast

Points: 165
More actions
December 9, 2002 at 8:38 pm

#79959

I have four databases on my production server all replicating with transactional replication to a reporting server. Both Servers are using SQL 2000 enterprise SP2. Three of the databases replicate with no problem. The distribution agent on one of the databases is failing with Server unavailable or access denied code 17. I have dropped the subscriber database several times, and recreated the publication and reinitialized. The datebase will get populated with data, and transactions will replicate for about 20 minutes, then it dies.
Any Ideas?
Thanks

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Antares686 SSC Guru Points: 125444 More actions · Answer 1

First and foremost check the SQL Server Logs and Event Viewer logs, they sometimes have additional details. Next start profiler and watch the commands occurring for replication on both servers. Also, try dropping the publication and remove the publication from being replicated wih sp_removedbreplication [ @dbname = ] 'dbname' and add back from scratch on that DB. Also, any additional information may help, such as full text of error and details you find from my other susggestions.

dpantekoek SSC Enthusiast Points: 165 More actions · Answer 2

Thank you for taking the time to reply to my posting, I have looked at the SQL error logs, and the Event viewer logs and have come up with nothing. I have dropped the publication numerous times in the last 24 hours, but once the publication is completely rebuilt and the snapshot is done, the distribution agent will run a while and then post this error message:

SQL Server does not exist or access denied.

(Source: REPLICATION (Data source); Error number: 17)

I also noticed last night that a netbios access denied was occurring from applications using SQLOLE.

Thanks

Darin

Antares686 SSC Guru Points: 125444 More actions · Answer 3

How is your network connection to the other server defined in Client Network utility. Make sure to use TCP/IP to make the connection as has fewer overall issues.

Found this comment

quote:
This error could indicate that the user logged into the client machine does not have permission on the machince where SQL Server is installed. Can you successfully execute a net use
\\<SQLServermachine>\IPC$. If not then that might be the problem.

And also check this out

http://support.microsoft.com/default.aspx?scid=kb;en-us;300420

dpantekoek SSC Enthusiast Points: 165 More actions · Answer 4

Thanks again

Network connection worked fine.

I remove replication from both servers, replaced the databases, and re-replicated them. Still had the same problem. I gave up and called Microsoft support. Turns out that there was a trigger in the subscriber database that was attempting to write to the a database on the publication server. The trigger was attempting to access the database using an anonymous connection and was no longer able to do that. The resulting error code was much less than helpful, but Mr. Mason with Microsoft support did a great job in diagnosing the problem. We were able to get the distributor agent to write the actions to a text log file that shed much more light on the problem. He stated that often this error comes from a bad server alias in the client network connection utility, or often triggers in the subscriber database.

Thanks again for your help.

Darin