Event 3351, SQL database login for 'DB_Config' on instance failed. Additional error information from SQL server is mentioned below. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

category-database
event id-3351
source-sharepoint foundation
SQL database login for 'DB_Config' on instance 'DB\instance' failed. Additional error information from SQL Server is included below:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I have been getting this error every hour on only 1 application server of the 2.
My farm consists of 2 app servers, 2 wfes & 2 sql nodes.
My public site is working fine. Authentication is NTLM.
SharePoint VSS Writer is disabled.None of my appPool accounts are running under local system.
I have read many forums/blogs, but couldnt find a solution for this.
Any help would be appreciated!

Hi,
As I understand, you found event id 3351 in event log. Please collect more information as below：
Check if the error also occurs on other servers in your farm.
Check if backup job is scheduled at the time when the event id occurs.
Please run Config Wizard or psconfig.exe -cmd secureresources on all servers and test the issue again.
Regards,
Rebecca Tu
TechNet Community Support

Similar Messages

SQL database login for 'SharePoint_Config_2010' on instance 'DB server' failed. Additional error information from SQL Server is included below.

we formatted Database server and restored all the databases from the backup. but the sharepoint site is giving below error when i access the home page.
we have 3 application servers in that two are working fine, but only one server getting the below error.
SQL database login for 'SharePoint_Config_2010' on instance 'db server' failed. Additional error information from SQL Server is included below.
Login failed for user 'domain\user'.
could you help what is the issue?

Hi,
According to your post, my understanding is that you failed to access sharepoint site with one application server.
It was due to the MOM/SCOM Agent that has a SharePoint management pack installed, the agents Windows Service runs as ‘Local System’ and thus causes this.
The workaround is to either kill the SCOM agent service, or set it to run as a dedicated service account.
In addtion, I recommend to add the logon account of the SharePoint Timer service as a user of the SharePoint_Config database. Give role membership to the account db_owner.
You also need to add the SharePoint accounts back into sql server.
There are some similar articles for you to take a look at:
http://blog.blksthl.com/2012/04/26/login-for-sharepoint_config-login-failed-for-user-domaincomputername-scom-agent/
http://msdn.microsoft.com/en-us/library/jj551781(v=nav.70).aspx
http://sharepoint.stackexchange.com/questions/51623/moved-sql-databases-for-sharepoint-2010-and-now-have-a-3351-error
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.Invalid object name 'Webs'.

SP 2013 Server + Dec 2013 CU. Upgrading from SharePoint 2010.
We have a web application that is distributed over 7-8 content databases from SharePoint 2010. All but one database are upgradable. However, one database gives:
Invalid object name 'Webs'.
while running Test-SPContentDatabase or Mount-SPContentDatabase.
EventViewer has the following reporting 5586 event Id:
Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.Invalid object name 'Webs'.
After searching a bit, these links do not help:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/fd020a41-51e6-4a89-9d16-38bff9201241/invalid-object-name-webs?forum=sharepointadmin
we are trying PowerShell only.
http://blog.thefullcircle.com/2013/06/mount-spcontentdatabase-and-test-spcontentdatabase-fail-with-either-invalid-object-name-sites-or-webs/
In our case, these are content databases. This is validated from Central Admin.
http://sharepointjotter.blogspot.com/2012/08/sharepoint-2010-exception-invalid.html
Our's is SharePoint 2013
http://zimmergren.net/technical/findbestcontentdatabaseforsitecreation-problem-after-upgrading-to-sharepoint-2013-solution
Does not seem like the same exact problem.
Any additional input?
Thanks, Soumya | MCITP, SharePoint 2010

Hi,
“All but one database are upgradable. However, one database gives:
Invalid object name 'Webs'.”
Did the sentence you mean only one database not upgrade to SharePoint 2013 and given the error?
One or more of the following might be the cause:
Insufficient SQL Server database permissions
SQL Server database is full
Incorrect MDAC version
SQL Server database not found
Incorrect version of SQL Server
SQL Server collation is not supported
Database is read-only
To resolve the issue, you can refer to the following article which contains the causes and resolutions.
http://technet.microsoft.com/en-us/library/ee513056(v=office.14).aspx
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Event ID:      5586
Task Category: Database
Level:         Error
Keywords:
User:          DOMAIN\SA account
Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.
The target principal name is incorrect. Cannot generate SSPI context.
This is the error, if often find in my WFE's. I googled for the error and granted DB owner roles for the service account as specified in TechNet, but no luck.
Even same error logs generated on SharePoint logs.
SqlError: 'The target principal name is incorrect. Cannot generate SSPI context.'
Source: '.Net SqlClient Data Provider' Number: 0 State: 0 Class: 11 Procedure: 'GenClientContext' LineNumber: 0 Server: 'servername\SHAREPOINT,4101'
f2cbcc9c-ac65-7084-fcab-4d2943cdfdea
Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.
The target principal name is incorrect. Cannot generate SSPI context.
f2cbcc9c-ac65-7084-fcab-4d2943cdfdea
System.Data.SqlClient.SqlException (0x80131904): The target principal name is incorrect.
Cannot generate SSPI context.     at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions
userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnecti...
f2cbcc9c-ac65-7084-fcab-4d2943cdfdea
Thanks.
Badri

For SharePoint to recognize the SQL server name we provide its name and instance while installing SharePoint. When we are using SQL alias to connect to SQL, we need to configure the same alias on SharePoint server so that SharePoint recognize alias over
the network.
Having SharePoint connect to a SQL Alias instead of the NetBIOS name is always a good idea. The main benefit is, if you ever have to switch the SQL Server or connect to a SQL Cluster VIP address, you just change the Alias to point to the SQL Cluster name
on the SharePoint Server and restart the SharePoint Timer Service and you are good to go.
Please check this blog.
http://blogs.msdn.com/b/priyo/archive/2013/09/13/sql-alias-for-sharepoint.aspx
http://technet.microsoft.com/en-us/library/hh292622(v=office.15).aspx
Thank You, Pallav S. Srivastav ----- If this helped you resolve your issue, please mark it Answered.

Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' between sql server 2005 32 bit and sql server 2012 64 bit

Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.S

Hello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Exception Message: The form cannot connect to the data source. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

When opening a form in SharePoint 12013 that was created from Infopath 2013, I get the following error.
You do not have permissions to access a database that contains data required for this form to function correctly.
An entry has been added to the Windows event log of the server.
Log ID:5566
When I go to the log files on the SharePoint server. I see the following error.
Exception Message: The form cannot connect to the data source. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
I am guessing this has something to do with the UDCX connection and the database.
Can anyone help me get this fixed?

Hi Jim,
Please check the following kb article when it occurs 5566errro with the UDCX conection file, try the method of using the Secure Store Service to store alternate credentials for the data connection method, or the method of stating the credentials
in the UDC file explicitly.
Also check if it could help with setting sql server as "SQL Server and Windows Authentication mode".
http://support.microsoft.com/kb/981684
Thanks
Daniel Yang
TechNet Community Support

BizTalk Powershell Provider Mount remote BizTalk drive: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

I've been dabbling in the Powershell BizTalk Provider Extensions for some automation of deployment and such. So far it's pretty cool on a local machine, but the real benefits to me would be to do it remotely. Does anyone have any experience in the with the
following issue?
My BizTalk Server and SQL Servers are on separate machines which I think is the issue, but I don't know how to resolve. I've tried to provided credentials to the New-PSDrive command, but get the following errors:
The provider does not support the use of credentials. Perform the operation again without specifying credentials.
I'm trying to manage a remote BizTalk instance. The machine running the script has biztalk fully configured and can connect
to the Target Server just fine. The issue comes when I try to mount the "BizTalk:" drive
Enter-pssession -computername myServer -configurationname microsoft.powershell32
$InitializeDefaultBTSDrive = $false;
Remove-PSSnapin -Name BizTalkfactory.PowerShell.Extensions;
Add-PSSnapin -Name BizTalkfactory.PowerShell.Extensions;
New-PSDrive -Name BizTalk -PSProvider BizTalk -Root "BizTalk:\" -Instance mySqlServer -Database BizTalkMgmtDb -Scope Global
When it get to the New-PSDrive I get the following error:
New-PSDrive : Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
+ CategoryInfo : InvalidArgument: (BizTalk:PSDriveInfo) [New-PSDrive], BtsException
+ FullyQualifiedErrorId : 0,Microsoft.PowerShell.Commands.NewPSDriveCommand
Has anyone experienced this and solved? The same error occurs when use Invoke-Command as well.

It seems that the PowerShell provider is not Microsoft Support, it is community supported through the CodePlex site -
http://psbiztalk.codeplex.com
Right, I posted there as well, but there is not much movement on the site. I was hoping to find if this larger community may have had some experience with the provider.

SqlException was caught: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Hi,
I have deployed an On-Premise SharePoint solution with event receiver to update external SQLDB. I'm using Visual Studio 2013 to create a SharePoint 2013 project on the same machine where SharePoint 2013 server is running. I was able to create
new items, but unable to update/delete. My event were fired accordingly however got choked on sqlConnectionlOpen() when attempting to update/delete with the following exception:
SqlException was caught: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Why would SharePoint uses SharePoint web application account my admin created to create and assumes NT AUTHORITY\ANONYMOUS LOGON account for update\delete? Any idea how to fix?
Appreciate your help.

I'm new to SharePoint development. I'm not familiar with SharePoint object model. Do I need to use it for working with external data? I used SPSecurity.RunWithElevatedPrivileges
block like you have suggested and is now working fine for both update/delete =)
My project is to develop a SharePoint site to work off external SQL DB. I tried BCS approach to work with external data but that didn't allow workflow/task feature.
Besides, there is no delete event where I can manually sync with external data when an item gets deleted when using SharePoint 2013 Designer. So using event receiver with SharePoint solution in VS2013 is the solution. Now that I am able to
propagate changes to external data store on item events, the new challenge is how do I over come SharePoint deployment conflict resolution (default? enforcement?) as each publish automatically deletes existing items in my lists and recreate? In another word,
I'm trying to replicate SharePoint list to external data store each transaction to keep them sync. Any thought would be greatly appreciated.

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. when open external list

Hi
i created a external list based on a external content type in shaepoint designer
but i got this error in event viewer when i open this list
Could not open connection using 'data source=xxxx;initial catalog=xxx;integrated security=SSPI;pooling=True;persist security info=false' in App Domain '/LM/W3SVC/1756231635/ROOT-1-130330475307091531'. The full exception text is: Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
I created bcs service with Users Identity and my web application using claims based authentication
and sql server in seperate server under a domain.
all servers are in same domain
adil

Most likely you are running into double-hope issue.
Read following article and implement the workaround that works for you.
http://www.spdoctor.net/Pages/message.aspx?name=login-failed-for-user-bdc
I am assuming your are using NTLM in your farm. If you are using Kerberos then check the following article.
http://blogs.technet.com/b/harmeetw/archive/2011/08/28/getting-login-failed-for-user-nt-authority-anonymous-logon-when-browsing-external-list-on-a-claims-kerberos-web-application.aspx
Amit

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Trying to get an admin type report working from the server. Works fine when I run it from BIDS since I have all the associated permissions. The report connects to multiple databases on different servers. The servers have links between them,
that is not the issues. I think I would have to change the security settings on the report server itself.
I read the similar posts, but didnt see any mention of verifying the security settings on Report Server itself, in IIS. In my case the web site that the Report Server app is under, has "Allow Anonymous" checked, but not on the app. So
I think that as I hit the url, my credentials are not being carried through. When I browse the report locally on the server, i get
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Im using integrated windows security for my data sources.

Actually, I think its an issue of Kereros authentication not being enabled for some of the servers that are being referenced in the datasets of the report.
http://blogs.msdn.com/b/sql_protocols/archive/2005/10/12/479871.aspx

Integrated Security results in Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON' after code deployment

Sometimes, when we deploy new code to the server, we're getting the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
we're using windows authentication and in our connectionstring use integrated security.
Only after restarting the server, the application can connect to the DB again. restarting IIS or recycling the application pool doesn't help.
Our application pool is configured using ApplicationPoolIdentity and we would like to keep it as such.
Any idea what we can do to prevent this error from occurring almost every time we deploy code?
Thanks

Hi amisol,
Thanks for your post here.
For your issue is related with asp.net security ,i suggest that you can post your issue to the link below:
http://forums.asp.net/25.aspx/1?Security
Best Regards,
Kevin Shen.

Using Distributed Views: Login Failed for user "NT AUTHORITY\ANONYMOUS LOGON...

Hi,
I have SCCM 2012 Configured in the following way:
CAS and SQL Database server on separate servers. Provider and Reporting Point installed on SQL server. SQL runs under domain account. SPN has been registered.
Child Primary with SQL server installed on the site server. SQL runs under local system.
I have configured Distributed Views for Hardware Inventory.
In the rcmctrl.log I see the following errors:
Here are the SPNs registered for the 3 servers involved: CAS, CAS SQL box and child Primary box:
The error would indicate the the issue is Kerberos related and that SPN's may not be configured or misconfigured. Can annyone shed some light here.
Thanks
Simon
Simon Burbidge

I might add that the SQL database for the CAS is a named instance with dynamic port allocation turned off for "SQL Server Network Configuration" and a static port of 14001 has been set. For the SQL Native client setting, the port remains at 1433. The Child
primary SQL is using a default instance with dynamic port allocation enabled for the "SQL Server Network Configuration" with the SQL Native client setting at 1433.
I'm wondering what SPN the SQL client at the CAS is attempting to use when trying to connect to the child primary. The SQL logs on the child primary dont say.
Simon Burbidge

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON when creating linked server

I am setting up a linked server connection in SQL Server 2012 that is "be made using the Login's current security context." When I test connect from SSMS from my PC it fails with the above error. If I RDP to the server and test connect
it succeeds. The service is running under a domain account. Any help would greatly be appreciated.

You need to enable Kerberos for this. Check out the new
Microsoft® Kerberos Configuration Manager for SQL Server®
David
David http://blogs.msdn.com/b/dbrowne/

Linked Server : The old "Login failed for users "NT Authority\Anonymous Logon" issue

Two SQL Servers: SQL Server 2008 sp3 and SQL Server 2014We are transitioning from 2008 to 2014. We have need of some linked servers whilst this is ongoing.
We've used them before, and indeed I set them up quite easily or so I thought.
On the 2014 server, I can test the connection and everything ok. If I logon to the linked server instance (ie the 2008 server) on the 2014 server, and connect to 2014 server, and test, I get the Error: 18456 Login failed error message.
If I create a linked server on any instances of the 2008 server pointing to the 2014 server, no problems whatsoever going in that direction.
Note that I'm selecting "Be made using the login's current security context"
The 2008 sql server services is using a domain account as it's logon, whereas the 2014 server is using Managed Service Accounts.
I've checked the SPN's and they all seem to be set ok.
I then thought that perhaps there was an inconsistency with the Managed Service Account not being recognised (although does work when actually on the 2014 server). I then changed (using Sql Server config manager) the account being used for the MSSQLSvc
from the managed service account to the same account used by the 2008 sql server. This seems to have produced a certain degree of success. I can now test the connection from my local ssms and the 2008 server and these work ok for the most part.
I presumed I had a workaround and did further testing, however it doesn't always seem to run true. This could of course be due to me not taking the same steps to reproduce the original workaround.
This is effectively a transient condition as eventually we won't need the linked servers, however, they are needed for at least the next 2-3 months.
Could anyone help explain the nature of this problem and where I'm going wrong?
Regards
Ian

Hello,
In addition to what Ashwin has asked (though the anonymous error message kind of gives it away):
It does sound (I know you have you checked, but SPNs can be tricky devils) like an SPN issue or delegation issue
The first thing I would point you to is the Kerberos Checking Tool for SQL Server. It's pretty new but in my testing it's been very accurate. Download, run it, and check the output:
http://www.microsoft.com/en-us/download/details.aspx?id=39046
Secondly, I would point you to this entry (yes, made by me):
http://www.seangallardy.com/2014/05/using-kerberos-with-sql-server-part-1-double-hop/
The reason why it works when you login from the 2008 server or the 2014 server and go to either or is because you're not double-hopping. You're local to the server, there is no delegation involved.
Sean Gallardy | Blog
MCM 2008
MCSM:Data Platform Charter Member

Like Server error Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

Getting error when trying to test the link server from remote ... Please help

Hello,
You've supplied us with little information other than what little is in the title. I'll refer you to a post I wrote about this. Please read
through it and post back if it does not fix your issue. There are a few other resource links in the post to check out, but it's most likely related to a Kerberos/SPN issue.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

Event 3351, SQL database login for 'DB_Config' on instance failed. Additional error information from SQL server is mentioned below. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Similar Messages

Maybe you are looking for