Critical SMS_Executive SQL Login failed for user 'NT AUTHORITY\SYSTEM'.

I am getting sql login errors on my sms executive log that i believe is stopping me from pxe booting. I have tried finding where to enter the credentials but i cannot find it.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
Starting SMS_EXECUTIVE... SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Microsoft System Center 2012 Configuration Manager v5.00 (Build 7958)
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
Copyright (C) 2011 Microsoft Corp. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Running as a Win32 service. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Process ID: 2368 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Worker thread ID: 2412 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Certificate (0x610450) is Exportable SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Initialize COM Security. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
InitializeCOMSecurity: RegOpenKeyEx for appid key Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: RegQueryInfoKey for appid key Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: RegQueryValueEx for AccessPermission Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: IsValidSecurityDescriptor() Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: MakeAbsoluteSD() Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: CoInitializeEx() Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity() Succeeded. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Installation directory: E:\Program Files\Microsoft Configuration Manager
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
This server: E076SCCM SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Site server: sccmserver.org SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Site code: 076 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Site type: 1 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
CSMSExecService::RegisterDBConnection: Register a DB connection...
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
Initializing the status message reporting system...
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
    The path to the "Status Manager" inbox is "E:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs".
SMS_EXECUTIVE 4/10/2014 3:13:13 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
    SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Registered this process as a source of "SMS Server" events.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Registered this process as a source of "SMS Client" events.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Registered this process as a source of "SMS Provider" events.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Status message reporting system initialized successfully.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_EXECUTIVE" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:47.950 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Certificate maintenance interval is every 1800 seconds
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_FOREST_DISCOVERY_MANAGER initialized, DLL = "\bin\x64\ADForestDisc.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Sun Apr 13 00:00:00 2014 Eastern
Daylight Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_FOREST_DISCOVERY_MANAGER" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.119 2014 ISTR0="2014 04 0 13 04 00 00 000" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adsgdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern
Daylight Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.120 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_SYSTEM_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adsysdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern Daylight
Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_SYSTEM_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.157 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_USER_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adusrdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern Daylight
Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_USER_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.158 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AI_KB_MANAGER initialized, DLL = "\bin\x64\aikbmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_ALERT_NOTIFICATION initialized, DLL = "\bin\x64\NotiCtrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AMT_PROXY_COMPONENT initialized, DLL = "\bin\x64\amtproxymgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CERTIFICATE_MANAGER initialized, DLL = "\bin\x64\CertMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CLIENT_CONFIG_MANAGER initialized, DLL = "\bin\x64\ccm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CLIENT_HEALTH initialized, DLL = "\bin\x64\chmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CLOUD_SERVICES_MANAGER initialized, DLL = "\bin\x64\CloudMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_COLLECTION_EVALUATOR initialized, DLL = "\bin\x64\colleval.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_COMPONENT_MONITOR initialized, DLL = "\bin\x64\compmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_COMPONENT_STATUS_SUMMARIZER initialized, DLL = "\bin\x64\compsumm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DATABASE_NOTIFICATION_MONITOR initialized, DLL = "\bin\x64\smsdbmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DESPOOLER initialized, DLL = "\bin\x64\despool.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DISCOVERY_DATA_MANAGER initialized, DLL = "\bin\x64\ddm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DISTRIBUTION_MANAGER initialized, DLL = "\bin\x64\distmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_ENDPOINT_PROTECTION_CONTROL_MANAGER initialized, DLL = "\bin\x64\EPCtrlMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_ENDPOINT_PROTECTION_MANAGER initialized, DLL = "\bin\x64\EPMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_EN_ADSERVICE_MONITOR initialized, DLL = "\bin\x64\adctrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_FALLBACK_STATUS_POINT initialized, DLL = "\bin\x64\fspmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_HIERARCHY_MANAGER initialized, DLL = "\bin\x64\hman.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INBOX_MANAGER initialized, DLL = "\bin\x64\inboxmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INBOX_MONITOR initialized, DLL = "\bin\x64\inboxmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INVENTORY_DATA_LOADER initialized, DLL = "\bin\x64\dataldr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INVENTORY_PROCESSOR initialized, DLL = "\bin\x64\invproc.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_LAN_SENDER initialized, DLL = "\bin\x64\sender.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_LICENSE_MANAGER initialized, DLL = "\bin\x64\licensemgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_MIGRATION_MANAGER initialized, DLL = "\bin\x64\migmctrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_MP_CONTROL_MANAGER initialized, DLL = "\bin\x64\mpcontrol.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_MP_FILE_DISPATCH_MANAGER initialized, DLL = "\bin\x64\mpfdm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_NETWORK_DISCOVERY initialized, DLL = "\bin\x64\netdisc.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", not scheduled to start again.
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
STATMSG: ID=1106 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_NETWORK_DISCOVERY" SYS=sccmserver.org SITE=076 P

First, if your site server is having problems logging into the DB, which it clearly is, you've got bigger issues than just PXE.
Have you verified the permissions in your SQL Server instance for the local System account (I'm assuming at this point that it is local to the site server)?
Jason | http://blog.configmgrftw.com

Similar Messages

  • Sql Server 2012 Login Failed for user "NT Authority\System"

    I have installed SQL Server on a new server. I have been getting the following error on each of the database in it.
    Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ABC'. [CLIENT: xxx.xxx.xxx.xxx]
    Here is some information on the instance:
    1) Default instance
    2) SQL Server, Sql Server Agent, Sql Server Reporting services are running / log on using a domain service account.
    3) Sql Server Browser is disabled.
    4) SQL Server VSS Writer is running / log on as Local Service.
    5) NT AUTHORITY\SYSTEM does exists in Login with just public server roles.
    I ran a trace on login failed and I get:
    ApplicationName: Microsoft Windows Script Host
    and it runs every 15 minutes.
    Help please?

    Hi,
    The error was thrown when the SCOM components connected to the backend SCOM databases.
     You can specify a domain account, grant it the sysadmin role and the error should be gone.
    Also, see the replies in your previous thread:
    http://social.technet.microsoft.com/Forums/en-US/23f6b6cb-ec41-4117-8613-26d24c948827/login-failed-for-user-username-reason-failed-to-open-the-explicitly-specified-database
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Receiving error message "Login failed for user 'NT AUTHORITY\SYSTEM'" every minute on server which is the mirror

    Hello,
    I have 2 SQL Server 2008 R2 machines that are configured with database mirroring (using certificates as authentication), there is no witness configured.  My issue is that the mirror server is receiving at least one of the below pared messages every
    second and filling up my sql error log quickly.
    SYSTEM is the service account user for the MSSQLSERVER service. 
    [298] SQLServer Error: 4060, Cannot open database "<databasename>" requested by the login. The login failed. [SQLSTATE 42000]
    [298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\SYSTEM'. [SQLSTATE 28000]
    The database has a status of: Affected database state is: Mirror, Synchronized/Restoring...
    When I checking the database mirror monitor, it shows that its mirroring ok and everything has green checkboxes.
    Is there a way to stop all these errors being logged, I'm assuming this isn't normal.
    Marcus

    Yes i have faced the same issues and tried everything and nothing was using this account, system was ended up with creating few GB's sql error log files everday.. and finally i had two options, 1 -- Rebuild the instance completely 2. Change the SQL Server
    Audit settings to Only successful logins and restart the instance.. ( May be your current sql server level Audit setting is set to Failed & Successful logins..
    Remeber my server was a DR so I have changed the SQL Server Audit settings to only Successful logins.. but production servers we will monitor both... :)
    Raju Rasagounder Sr MSSQL DBA

  • System.Data.SqlClient.SqlException: Cannot open database "MSCRM_CONFIG" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\SYSTEM

    Dear ALL 
    After successfully shifting the CRM from 2011 to 2013 i found a problem in Reporting section none of the report is working after some finding i conclude that MSCRM_FetchDataSource is not able to connect successfully 
    Through my report manager i tried to test the connection of MSCRM_FetchDataSource but i got the following error 
    System.Data.SqlClient.SqlException: Cannot open database "MSCRM_CONFIG" requested by the login. The login failed. Login failed for
    user 'NT AUTHORITY\SYSTEM'. 
    I already add the NT Authority \ System as a db_owner under my database user of MSCRM_CONFIG
    But still no success any one have any idea why it's happaning 
    Regards 
    RB

    I found a solution I hope my post will help other
    I gave the  db_owner to 'NT AUTHORITY\SYSTEM' and 'NT AUTHORITY\NETWORK' and assigned with both CRM and Config database
    It resolved my issue
    RB

  • 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

  • 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

  • Deployment issue - Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

    I am attempting to deploy a site from my development PC to my server. I have no issues running the site on the server using VS2010 Express Web in debug. All page queries are working within the debugger. The connection strings are identical between the PC
    and Server, except the host name.
    connectionString
    ="Data
    Source=SOCIALSERVER;Initial Catalog=Intake_be;Integrated Security=True"
    However, when using the site normally via IIS, the pages containing data access are failing with a permissions problem. The non-data access pages render normally.
    Login failed for user 'NT AUTHORITY\NETWORK SERVICE'
    Looking at the SQL2005 instance via SQL Management Studio, I see security folder with Logins under the Server. NTA\NS is listed as a user login. But, I also see similar folders under each
    of 3 databases. NTA\NS is not listed as a login specific to my target dB.
    My site is for internal (intranet) use only. There is no internet access into my IIS. This is my first deployment into production. I think I only need Windows Authentication but I lack the experience to make a good decision. My goal is to allow domain users
    to access pages that produce read only data. But, I also need controlled access to pages that can modify data. I used the native winform template for ASP.NET 4, which includes some roles based security.
    How do I grant permissions for internal users on the pages that access SQL data? How does that security model work with the native roles based security? i.e.
    add
    name="AspNetSqlMembershipProvider"type="System.Web.Security.SqlMembershipProvider"connectionStringName="ApplicationServices"...
    etc.
    Thanks for your time and patience on this Deployment 101 type issue.
    Kurt

    hi,
    You receive either of these error messages specifically when you use integrated security.
    To resolve you can use one of below.
    Method 1: Programmatically change the security context of the ASP.NET worker process to a user who has the correct SQL Server permissions.
    Method 2: Change the default configuration of ASP.NET so that the ASP.NET worker process starts and runs under the context of a user who has the correct permissions in SQL Server.
    Method 3: Grant the correct permissions in SQL Server so that the ASPNET account (or NetworkService account, for an application that runs on IIS 6.0) has the appropriate access to the required resources.(Go to the Computer Management >> Local User and
    Groups >> Groups >> Right Click and go to properties on IIS_IUSRS >> Add appropriate user.
    Thanx, Mark as answered if you are ok ..

  • Login failed for user 'NT AUTHORITY\ANONYMOUS

    Hi All
    I have already gone thru lot of links, So appreciate if i can have some solution
    I have 3 servers A, B and C . A and B are in same domain and C is in different domain. and I am sysadmin in all 3 servers and all have trusted connection with each other
    1. All have tcp and named pipe enable
    2. All 3 servers and all services including browser are up and running
    3. When i connect any sql server from any Server using SSMS i am able to connect and  (net_transport, auth_scheme = TCP , NTLM).
    Now i create linked server at server B to Server C (C domain is different than A and B).  When i login on Server B and try to run query on C its working fine. But after remote login to server A and connect sql server at B using SSMS when
    i expand linked server to c i cant see databases and query is giving error "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'"
    I also tried to connect to all 3 server in ssms using forced  named pipes but i am getting below error
    "provider named pipes provider error 40 - Could not open connection to sql server"
    My question :
    1. I have to use domain account to use linked server from server A to connect SQLserver B to server C, How this can be done is this related to Double hop ??
    2. Why i cant connect using forced Named pipe to any server using SSMS except local host
    Thanks Saurabh Sinha http://saurabhsinhainblogs.blogspot.in/ Please click the Mark as answer button and vote as helpful if this reply solves your problem

    Hello,
    First, it is possible to use Kerberos delegation across trusted domains.
    net_transport, auth_scheme = TCP , NTLM
    This means something isn't correctly setup as you're defaulting back to NTLM. This should read Kerberos if your SPNs were setup correctly and authenticated properly. Check the SPNs and service accounts.
    http://technet.microsoft.com/en-us/library/cc280744(v=SQL.105).aspx
    1. I have to use domain account to use linked server from server A to connect SQLserver B to server C, How this can be done is this related to Double hop ??
    To go across domains I'm not entirely sure on that part, but I can say it'd probably be easier if you did use a domain account as the service account.
    2. Why i cant connect using forced Named pipe to any server using SSMS except local host
    I'm not quite sure what you mean here. You can't connect through NP? Why the need for NP at all?
    Sean Gallardy | Blog |
    Twitter

  • 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

  • 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.

  • 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

  • BCS - Message from External System : 'Login failed for user 'NT AUTHORITY\IUSR'.'.

    Hello,
     I have create a an external content type .
     I Choose "Connect with user's Identity".
     I create a external list that uses the ExternalContentType.
     When I try open the external list from browser by User "TestUser" . I get the following error "Message from External System : 'Login failed for user 'NT AUTHORITY\IUSR'.'"
       My Question :
           I need to know why pass the credential "NT AUTHORITY\IUSR" to connect to the data base not the
            current log in"TestUser" ?  How Can I solve it ?
            Thanks
             Hema
    ASk

    Hi,
    did you configure Kerberos delegation?
    NTLM fails when you try to open external list from client computer, because SharePoint cannot pass user's identity - "Double Hop" issue.
    Take a look at confguring Kerberos for SharePoint 2010 white paper
    Download Configuring Kerberos Authentication for Microsoft SharePoint 2010 Products from Official Microsoft Download Center
    http://www.microsoft.com/en-us/download/details.aspx?id=23176
    Robi MCT Kompas Xnet d.o.o. Ljubljana | blog: http://xblogs.kompas-xnet.si | website: http://www.kompas-xnet.si
    Slovenia
    Please vote if you find reply useful or mark it as answer.
    Thank you

Maybe you are looking for