January 17, 2012 at 7:00 am
Hi list,
I have configured a Transactional Replication for one of our Databases. The replication configuration process occurred without any errors. The problem is when I run the replication, the initial snapshot...I get the error below (got the error on the log file viewer) from "SQL Server Agent -> Jobs" at Management Studio:
2012-01-17 14:40:48.173 Copyright (c) 2008 Microsoft Corporation
2012-01-17 14:40:48.173 Microsoft SQL Server Replication Agent: logread
2012-01-17 14:40:48.173
2012-01-17 14:40:48.173 The timestamps prepended to the output lines are expressed in terms of UTC time.
2012-01-17 14:40:48.173 User-specified agent parameter values:
-Publisher 03SQL0
-PublisherDB PROTHEUS10_TESTE
-Distributor 03sql0
-DistributorSecurityMode 1
-Continuous
-XJOBID 0x4D09D7D16381224695A1764B7323DD8D
-XJOBNAME 03SQL0-PROTHEUS10_TESTE-3
-XSTEPID 2
-XSUBSYSTEM LogReader
-XSERVER 03SQL0
-XCMDLINE 0
-XCancelEventHandle 00000B20
-XParentProcessHandle 00000B58
2012-01-17 14:40:48.318 Status: 0, code: 20015, text: 'Login failed for user 'MSIGA'.'.
2012-01-17 14:40:48.318 Login failed for user 'MSIGA'.
This MSIGA user has all permissions possible inside both SQL Server machines, including 'sa'.
What could be wrong?
Thanks
Mario
January 17, 2012 at 9:54 pm
Are you using a separate distribution server? Can you check the the login has access on that machine?
Also, look through the SQL error logs to confirm which machine is actually experiencing the login error. That will help to narrow things down.
January 17, 2012 at 10:10 pm
mariobehring (1/17/2012)
...2012-01-17 14:40:48.318 Status: 0, code: 20015, text: 'Login failed for user 'MSIGA'.'.
2012-01-17 14:40:48.318 Login failed for user 'MSIGA'.
This MSIGA user has all permissions possible inside both SQL Server machines, including 'sa'.
What could be wrong?
Thanks
Mario
I guess password has been changed/expired.
January 19, 2012 at 7:37 am
Hi,
The distributor resides on the same server as the publisher. The log message seems to be referring to the server where the replica will be stored.
There are no issues like password change or something...the MSIGA password is the same on both SQL Servers.
Mario
January 19, 2012 at 8:38 am
First try to check the error logs on all servers involved and get the login failure message from there. That should give you more info on what database and what ID was involved in the login failure. Check the error number, severity and state to find the exact cause of the failure.
Also you should start a profiler trace and capture login failures and in 'Errors and Warnings' select 'User Error Messages'
The 'user error messages' will tell you exactly which database it was trying to connect. I have seen situations where the login does not have authority to connect to the DEFAULT database of the login which typically is MASTER.
Blog
http://saveadba.blogspot.com/
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply