SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Login Failed issue with Replication Job


Login Failed issue with Replication Job

Author
Message
SQLisAwE5OmE
SQLisAwE5OmE
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1068 Visits: 3068
I was assigned to look at a login failed issue, which is related to a replication job. I don't have much experience with replication and I am not really sure what exactly the job is trying to do. Currently the job has been disabled, but I have the job step and an error message from the job history. Can someone help me out as to where I should start with this for troubleshooting.

I have kind of modified the names where it shows serverName and databaseName, etc.

The job step is as below.

StepName = Run agent

“-Publisher ‘PublisherName’ -PublisherDB [PublisherDBName] -Publication [PublicationName] -Distributor [DistributorName] -SubscriptionType 1 -Subscriber [SubscriberName] -SubscriberSecurityMode 1 -SubscriberDB [SubscriberDBName] -Continuous”

Job Hisorty(1 of the failed error messege)
Date 6/26/2013 10:21:05 AM
Log Job History (‘Job Name’)

Step ID 1
Server ‘ServerName’
Job Name ‘JobName’
Step Name Run agent.
Duration 00:00:09
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
-Continuous
-XJOBID 0x5D5E3BC3FDB66E44958B31B1EC9EF942
-XJOBNAME ‘JobName’
-XSTEPID 1
-XSUBSYSTEM Distribution
-XSERVER ‘ServerName’
-XCMDLINE 0
-XCancelEventHandle 000003FC
-XParentProcessHandle 00000578
2013-06-26 15:21:05.142 Startup Delay: 9417 (msecs)
2013-06-26 15:21:14.564 Connecting to Subscriber ‘SubscriberName’
2013-06-26 15:21:14.642 Agent message code 20052. The process could not access database ‘DatabaseName’ on server 'ServerName'.
2013-06-26 15:21:14.642 Category:NULL
Source: Microsoft SQL Native Client
Number: 4060
Message: Cannot open database "DatabaseName" requested by the login. The login failed.
2013-06-26 15:21:14.642 Category: NULL
Source: Microsoft SQL Native Client
Number: 18456
Message: Login failed for user 'LoginName'.<----I noticed that this login/user name is the service acct that SQL agent is running on.

Thanks in advance,
SueTons.

Regards,
SQLisAwe5oMe.
HanShi
HanShi
SSCarpal Tunnel
SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)

Group: General Forum Members
Points: 4446 Visits: 3672
SQLCrazyCertified (6/26/2013)2013-06-26 15:21:14.642 Agent message code 20052. The process could not access database ‘DatabaseName’ on server 'ServerName'.
2013-06-26 15:21:14.642 Category:NULL
Source: Microsoft SQL Native Client
Number: 4060
Message: Cannot open database "DatabaseName" requested by the login. The login failed.

According to the error it looks like the process is able to connect to the SQL instance, but not able to access the database. Check if the login account has enough permission to the database ‘DatabaseName’ on server 'ServerName'. Also check the SQL Server log on server 'ServerName' for additional logging about the failed login. These additional logging could be resolved to a cause with Aaron Bertrands log at http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
SQL!$@w$0ME
SQL!$@w$0ME
SSC Eights!
SSC Eights! (841 reputation)SSC Eights! (841 reputation)SSC Eights! (841 reputation)SSC Eights! (841 reputation)SSC Eights! (841 reputation)SSC Eights! (841 reputation)SSC Eights! (841 reputation)SSC Eights! (841 reputation)

Group: General Forum Members
Points: 841 Visits: 1244
Sounds like one of the accounts you are trying to connect to the
publisher/distributor/or subscriber is not defined. You will need to use an
account which is in the pal on the publisher and in the sysadmin or dbo_role
on the subscriber. It will need rights to read, and list files and folders
on the snapshot share.

Also check for dropped publication / subscriber databases, but replication jobs for those databases still running.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search