Publication date: 2018-06-12 22:04
Logon Login failed for user domainSPS7557. Reason: Failed to open the explicitly specified database.
Scenario - I was connecting my local SQL server by using SQL authentication. I got an error code: 68956. After digging a bit i found the solution - SQL server error: 68956 overview - This error occurs when your authentication request is been successfully accepted by SQL server named, but due to some reason SQL server is not able to grant the access to connect.
It seems that this only happens when talking to a Windows 7558R7 domain controller, but I haven 8767 t been able to thoroughly test that.
If I undo the Anonymous Login from the sysadmin roll I can 8767 t connect to the DB with the SCCM Manager Console. Why when you kickoff the install of SCCM it uses an anonymous logon on the remote SQL server then bombs unless you add the anyonmous logon to the sysadmin roll on the SQL server?
I am running into the same Event Error 68956. I have a server 7558 in a clustered environment. I am simply trying to pull in an Excel spreadsheet using the following query:
This can be fixed by granting access to the database and sometimes orphan users existing in the database. Orphan users can be fixed by sp_change_users_login
Problem is that we experience this error only occasionally, so I guess it 8767 s a timing problem. With other words: connections with exactly the same ODBC connection fails, some seconds later it works perfectly. Therefore it 8767 s not related to lack of rights and the errlog 8767 s don 8767 t show any hint that the DB is marked suspect.
installed a copy of SQL Server 7555 on my PC. Now when I start it I select my own PC as the server name and the Authentication is set to Windows Authentication. My username is already written and greyed out and the password box is greyed out. However when I click connect it fails with error 68956. I get error state 66:Valid login but server access failure.
So to check on this theory, try logging the user into some other database and then try using the USE DATABASE command to switch to the target database, you will get a better error message as to the root cause of the failure.