SCCM Console issue, SQL connectivity login failed for SCCM machine account

Hi ,
As part of resolving the corrupt SCCM 2012 R2 environment, we have uninstalled the site from the Standalone primary site and restored it from the last backup. The database is on remote server on SQL 2012 SP1. Only Site recovery is run.
Post the restoration on unable to launch the SCCM console, Error Could not connect to the site.
When I checked the logs in the log file SmsProv.log in the program filles\Microsoft Configuration manager\logs, the error is as below
*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspobjectquery.cpp(6260) : SQL Connection attempt timed out~ SQL Error: [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'XXXX\ABBC$'.~*~*
*~*~SQL Connection attempt timed out [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'XXXX\ABBC$'.~*~*
<*><*> CANT CONNECT TO SQL, RETURNING ERROR <*><*>
Regards
Leela

Duplicate post.
https://social.technet.microsoft.com/Forums/en-US/6b26502b-ac07-426c-abe4-6cfdaa45b33b/sccm-console-launch-fails-sql-connectivity-issue-with-sccm-machine-account?forum=configmanagergeneral
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Similar Messages

[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'

Hi,
We have exadata x3-2. I am seeing this error in alert log file frequently.
The db version: 11.2.0.3 On RAC on Linux 5.8 x86-64Bit
Errors in file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
The file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc
Contains many repeated lines like below
*** 2015-01-21 06:34:40.209
ERROR, tran=21.24.51311, session#=1, ose=0:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
Could any please help why is this happening.
Thanks

Hi,
You have customers who are running distributed transactions using a gateway which need to be rolled back. However, the gateway has not been correctly configured for distributed transactions. To roll back a transaction on the SQL*Server database a connection is made as the user defined in the parameter HS_FDS_RECOVERY_ACCOUNT in the gateway init<sid>.ora file but this user has not been created in the SQL*Server database with the password defined in HS_FDS_RECOVERY_PWD. This user also needs to own the transaction log table.
I assume you are using the Database Gateway for SQL*Server (DG4MSQL) as the Database Gateway for ODBC (DG4ODBC) doesn't support distributed transaction.
If you have access to My Oracle Support have a look at this note -
How to Setup DG4MSQL to Use Distributed Transactions (Doc ID 227011.1)
Otherwise, check the Gateway documentation.
Regards,
Mike

SQLException thrown by the physical connection: Login failed for user

Hi Experts,
I am creating a custom data source on Visual Administrator (2004s 7.01 SP3) for SQL 2008 with a named instance. Using Logon, System databases are getting connected. But Visual Administrator throws the below exception trace while attempting to connect to any custom created databases.
Please help me to resolve this.
Thanks in Advance,
Nikhil

java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during runtime changes of application "sap.com/JDBCConnector_QIDB.xml". [id = ConfigError]
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:705)
     at sun.reflect.GeneratedMethodAccessor647.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.rmi.RemoteException: Error occurred while making runtime changes with application sap.com/JDBCConnector_QIDB.xml; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 3640850:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "QIDB".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.application.RuntimeTransaction.finalActions(RuntimeTransaction.java:286)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:339)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:344)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)
     at sun.reflect.GeneratedMethodAccessor647.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'xxxx'.
     at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:193)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:168)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:134)
     at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:294)
     at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:316)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
     ... 40 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'xxxx'.
     at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
     at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(Unknown Source)
     at com.microsoft.sqlserver.jdbc.TDSParser.parse(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(Unknown Source)
     at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
     at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:163)
     ... 45 more
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:346)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)
     ... 28 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 3640850:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "QIDB".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.application.RuntimeTransaction.finalActions(RuntimeTransaction.java:286)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:339)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:344)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)
com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:316)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
     ... 40 more

Java.sql.SQLException: Login failed for user 'ccms'.

Windows Server 2003 R2 Enterprise x64 Edition service pack 1
SQL Server 2000 Enterprise edition 32 bit, SP4 : 2000.8.00.2039
jdbc driver: jtds
connection string: jdbc:jtdsqlserver://ZH-DATA-4:1434/[dbname];instance=[instance name]
the connectivity works fine...almost.
I have 2 identical sql servers one of which is linked to the other via a linked server config which for one particular query gives back the error I give in the subject of this thread:
java.sql.SQLException: Could not get the data of the row from the OLE DB provider 'SQLOLEDB'
if I run the exact same sql string in query analyser it runs with no problem.
if have similar queries also running from java which use the linked server and these do not give an error. I am at a loss as to explain why this is happening.
the query in question joins together a number of views which reference the linked server.
I have tried everything I can think of including recreating the views and linked server definition.
If all is OK in query analyser, how can it fail when called over jbdc (especially when all other db requests succeed) ?

refer below link
http://blog.soapplied.com/2013/06/websphere-distributed-transactions-with.html

SQL connection string failed for $ password

Hi Team,
I am not able to connect to SQL DB when password contains $ symbol. Please help me to open connection for this scenenrio.
$sqlconstr = "Data Source=Server1;Initial Catalog=DB;User ID=User;pwd='$$XXXXX0';"
$sqlconn = New-Object system.Data.SqlClient.SqlConnection
$sqlconn.connectionstring = $sqlconstr
$sqlconn.open()

Thanks I tried below string & it worked
$sqlconstr = 'Data Source=Server1;Initial Catalog=DB;User ID=User;pwd=$$XXXXX0;'

SCCM console launch fails , SQL connectivity issue with SCCM machine account

Hi ,
As part of resolving the corrupt SCCM 2012 R2 environment, we have uninstalled the site from the Standalone primary site and restored it from the last backup. The database is on remote server on SQL 2012 SP1. Only Site recovery is run.
Post the restoration on unable to launch the SCCM console, Error Could not connect to the site.
When I checked the logs in the log file SmsProv.log in the program filles\Microsoft Configuration manager\logs, the error is as below
*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspobjectquery.cpp(6260) : SQL Connection attempt timed out~ SQL Error: [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'XXXX\ABBC$'.~*~*
*~*~SQL Connection attempt timed out [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'XXXX\ABBC$'.~*~*
<*><*> CANT CONNECT TO SQL, RETURNING ERROR <*><*>
Regards
Leela

Hi Grath,
We ran a Site recovery, I checked the permissions on SQL server. Could not find the SCCM machine account in the SQL logins. Adding the SCCM machine account to the SQL logins solved the issue. As part of the recovery we only recovered the Site using the Site
backup. Have not touched the SQL server which is on a remote machine??
Anyways the login issue is resolved now.
Regards
Leela

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

Reports successfully execute but generate a login failed for user 'sa' err

I am running Crystal Reports Server XI R2. Classic ASP is used to generate embedded reports within our application. The crystal reports use ODBC to connect to a SQL Server 2005 database. The reports successfully generate in our Classic ASP application. However in SQL Server 2005, the following error messages are being generated each time a crystal report is ran:
- Login failed for user 'sa'.
- Error: 18456, Severity: 14, State: 8.
We know that we are passing the correct username/password to the crystal reports, becuase they execute successfully.
It appears that when the report is called, Crystal Reports appears to conect to SQL Server using a username/password that we didn't provide it at execution time, this fails and the SQL Server 'login failed for user' is generated. Then it runs the report using the username/password we provide and it successfully generates a report.
I have ran Profiler against the SQL Server Database and the 'Login failed for user 'sa' ' errors have a ApplicationName of either 'Seagate Crystal Reports' or 'Crystal Reports'. Therefore I know it is Crystal Reports generating these errors in SQL Server.
Does anyone have any ideas on how to stop these SQL Server 'Login failed for user 'sa' ' errors being generated?

What happens if you use Profiler when running the report using Crystal Report Designer?
If the report is ran through Crystal Report Designer, NO 'Login failed for user' error messages appear in profiler. Everything looks ok when ran in Designer.
Also, need to know what patch level you are on?
We are running Crystal Reports Server XI Release 2, Version: 11.5.8.8265
No additional patchs have been applied since Crystal Reports Server was installed.
We may try the SA account if one of the connections fail to log on with the credentials you provided. Verify the user you logged on with has rights to all tables.
The reports were running through our application using the SA account. The SA account has permissions to these tables. The reports do generate results and appear perfectly fine in the application. The issue is that when our application requests the report from Crystal Reports Server. Crystal Reports Server delivers the correct report to our application. However during the process to generate the report, 'login failed for user 'sa' ' errors are being generated in SQL Server 2005.
Also, I have tried creating a completely new SQL user called 'crystaluser'. I ran the report using Crystal Report Designer and used the crystaluser logon and saved the report. Then I ran the same report through our application. SQL Profiler will then display 'login failed for user 'crystaluser''.
Its seems as though Crystal Reports Server is first executing the report using the default SQL user saved with the report, but is either sending a blank password or no password at all. This generates the 'login failed for user' in SQL Server 2005. But it then uses the SQL username/password my application gives it and successfully generates the report. Of course this is only speculation.

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection

"[DBNETLIB] Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
After patches applied on patch Tuesday the database reports the above error.
All accounts are domain accounts and SQLServer uses Windows auth.
DCDIAG show no errors
All servers and DC have been restarted,
Message in db log confirms the connection is being denied due to trust.
Event log shows same rejection
Protocols enabled: named pipes, tcpip, memory
TESTS:
PortQry: "
TCP port 1433 (ms-sql-s service): LISTENING"
Connect with domain admin accounts works from multiple clients systems to DB.
Cannot connect with newly created domain admin account
Can connect if new admin account connect to server in terminal server session and uses UDL wizard or any other tool including isql.
New standard user also fails to connect.
NOTES:
I removed the SSL patch and the IE security update to see if that was an issue.
¯\_(ツ)_/¯

Has someone left the company or has an account of some nature been dropped/replaced?
Please click "Mark As Answer" if my post helped. Tony C.
Hi Tony,
Srry but No. We just installed the monthly updates.
I went back and found I had missed removing a patch. I missed the rollup for Windows Server 2003:
Event Type: Information
Event Source: NtServicePack
Event Category: None
Event ID: 4382
Date:  3/12/2015
Time:  12:26:04 PM
User:  NETTEST\admin
Computer: DATA1
Description:
Windows Server 2003 KB954920 was removed from your computer, and the previous Windows Server 2003 configuration was restored.
After I removed that is still didn't work but after about five minutes it started working.
I guess I ned to report that to MS after I research what might be changed to make the patch work.
Every time I get stuck and ask for help it seems to be just before I stumble on the solution.
Thanks for replying.
Well - maybe this will help someone else.
Thanks again for replying Tony
¯\_(ツ)_/¯

Cannot connect to SERVER. Login failed for user 'DOMAIN\user'. (Microsoft SQL Server, Error 18456) - SQL Server 2012 on Windows Server 2008 R2

I've seen multiple blogs and forums with similar problems and SQL 2012 or 2008. But no solutions that work for me.
I have installed SQL Server in mixed mode (SQL and Windows authentication). I can create new Login accounts in either mode. However, I cannot get an AD security group Login account to work. I am trying to add group 'DOMAIN\Domain Admins' or 'SERVER\Administrators'
as a Login so that any of the domain's administrator accounts can open SQL Server Management Studio and act as an 'sa' account on this server.
I have deleted the SQL account 'DOMAIN\Domain Admins'.
I have restarted SQL.
I have restarted the Win2K8r2 server.
I have launched SSMS as Administrator from the desktop of SERVER.
I have launched SSMS as another user (and used 'DOMAIN\user' to lauch it) from the desktop of SERVER.
I can create a login account named 'DOMAIN\user' (who happens to be a member of the 'DOMAIN\Domain Admins' group) and give this account 'sa' security, and when I do that, this account works as expected...
How do I add a security group as a Login account and give all members of that group the ability to be an 'sa' account?

Hi geoperkins,
Are you getting the following error message?
Error: 18456, Severity: 14, State: 11
Login failed for user <Domain\user>. Reason: Token-based server access validation failed with an infrastructure error.
If that is the case, the issue could be due to that the Windows login has no profile or that permissions could not be checked due to UAC. Please disable UAC firstly and check if it is successful to log in SQL Server.
Another reason could be that the domain controller could not be reached. You may need to resort to re-creating the login. Create a new group in AD, add users to the new group, then add the group to the local admin group and create login for the group in SQL
Server.
There is a connect item describing similar issue for your reference.
https://connect.microsoft.com/SQLServer/feedback/details/680705/cant-login-to-sql-using-windows-authentication-when-user-is-in-a-domain-security-group
For more details about above error, please review the following blog.
http://sqlblogcasts.com/blogs/simons/archive/2011/02/01/solution-login-failed-for-user-x-reason-token-based-server-access-validation-failed-and-error-18456.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Cannot connect to newly created SQL 2008 R2 instance. Login failed for user...

I'm not a SQL guy, just figuring my way around here...
I just created a new instance on an existing SQL server. The original instance works fine. On
Database Engine Configuration > Account Provisioning
I selected Windows authentication mode and added several users, myself among them.
Tried to log in with one my account and getting:
TITLE: Connect to Server
Cannot connect to SERVERNAME\INSTANCE.
ADDITIONAL INFORMATION:
Login failed for user 'domain\myusername'. (Microsoft SQL Server, Error: 18456)
Guidance/suggestions?
Thanks,
Scott

http://sqlserver-help.com/2014/07/08/help-how-to-find-cause-of-login-failed-for-user-error/
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

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

How to fix Login failed for user ''. (Microsoft SQL Server, Error: 18456)in windows 2008?

Hi All,
we are facing the Login fails issue .
how to resolve the bellow error , could you please suggested the possible ways .. ASAP
TITLE: Connect to Server
Cannot connect to ..
ADDITIONAL INFORMATION:
Login failed for user ' domain\name'. (Microsoft SQL Server, Error: 18456)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
BUTTONS:
OK
Log Name: Application
Source: MSSQLSERVER
Date: 10/6/2011 1:56:28 PM
Event ID: 18456
Task Category: Logon
Level: Information
Keywords: Classic,Audit Failure
User: domain\name
Computer:
Description:
Login failed for user ' domain\name'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
RAM

I was hitting myself in the head with this problem for a couple of minutes.... Everything was fine on the DC and Domain itself.. I added the Domain admins Group Principal for which I am part of... I was getting this error ... Long History... Short
(Right Click and Run as Administrator took care of this for me..) UAC was the cause of the problem.
Cannot connect to XX-DB-XX3.
===================================
Login failed for user 'XXXXS\XXas'. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
Server Name: XX-DB-XX3
Error Number: 18456
Severity: 14
State: 1
Line Number: 65536
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Error Msg: SQL login failed for HOSTNAME? Upgrade task?

Hi everybody,
Since some weeks we see an error message in all servers our SharePoint 2010 SP1 Farm, regulary every hour:
SQL database login for 'SharePoint_Config' on instance 'sqlsrv' failed.
Additional error information from SQL Server is included below.
Login failed for user 'OURDOMAIN\SERVERNAME$'.
The interesting part is that the
server tries to connect to the SharePoint Config database, not a dedicated account, which is normally used for every SharePoint service.
What circumstances can lead to an access of a server?
Unfortunately I get no details of the service or application which is trying to access. The event log just states "SharePoint Foundation (Microsoft-SharePoint Products-SharePoint
Foundation)" , Task Category "Database". The user who raises the error is "SYSTEM".
In the ULS log I can find the Stack Trace below which indicates to an upgrade task. But why is the SYSTEM user trying an update? Normally we do an upgrade by running the Upgrade Wizard with an dedicated account. And only the SharePoint Administration
windows service runs as Local System.
And I never heard or read something like: Give Local System (so the server) access to the SharePoint Config database?!
Thanks for your ideas :-)
Benjamin
System.Data.SqlClient.SqlException: Login failed for user 'DOMAIN\SERVERNAME$'.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SharePoint.Utilities.SqlSession.OpenConnection()
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, Boolean retryForDeadLock)
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command)
at Microsoft.SharePoint.Upgrade.SPDatabaseSequence.GetVersion(SPDatabase database, Guid id, Version defaultVersion, SqlSession session, SPDatabaseSequence sequence)
at Microsoft.SharePoint.Upgrade.SPDatabaseWssSequence.get_BuildVersion()
at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade()
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveCanUpgrade(Object o)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade()
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.ValidateBackwardsCompatibility()
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Initialize(SqlConnectionStringBuilder connectionString, Boolean enableCaching, Boolean checkCompatibility, Boolean bindRequestGuid)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Initialize(SqlConnectionStringBuilder connectionString, Boolean enableCaching, Boolean checkCompatibility)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.get_Local()
at Microsoft.SharePoint.Administration.SPFarm.FindLocal(SPFarm& farm, Boolean& isJoined)
at Microsoft.SharePoint.Administration.SPWebService.get_ContentService()
at Microsoft.SharePoint.PowerShell.SPCmdletSnapIn.get_Cmdlets()
at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.MergeCustomPSSnapIn(PSSnapInInfo mshsnapinInfo, CustomPSSnapIn customPSSnapIn)
at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.LoadCustomPSSnapIn(PSSnapInInfo mshsnapinInfo)
at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.LoadPSSnapIn(PSSnapInInfo mshsnapinInfo)
at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.LoadPSSnapIn(PSSnapInInfo mshsnapinInfo, PSSnapInException& warning)
at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.DoAddPSSnapIn(String name, PSSnapInException& warning)
at Microsoft.PowerShell.Commands.AddPSSnapinCommand.AddPSSnapIns(Collection`1 snapInList)
at Microsoft.PowerShell.Commands.AddPSSnapinCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
at System.Management.Automation.CommandProcessorBase.DoExecute()
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.StatementListNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.ifStatementNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.StatementListNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.ParseTreeNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
at System.Management.Automation.ScriptCommandProcessor.ExecuteWithCatch(ParseTreeNode ptn, Array inputToProcess)
at System.Management.Automation.ScriptCommandProcessor.RunClause(ParseTreeNode clause, Object dollarUnderbar, Object inputToProcess)
at System.Management.Automation.CommandProcessorBase.DoComplete()
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.StatementListNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.ParseTreeNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
at System.Management.Automation.ScriptCommandProcessor.ExecuteWithCatch(ParseTreeNode ptn, Array inputToProcess)
at System.Management.Automation.ScriptCommandProcessor.RunClause(ParseTreeNode clause, Object dollarUnderbar, Object inputToProcess)
at System.Management.Automation.CommandProcessorBase.DoComplete()
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

http://aanuwizard.com/2010/04/30/login-failed-for-user-domainservername/
It will need to add user ‘NT AUTHORITY\NETWORK SERVICE’
to your database to get rid of this problem.
An asp.net application is running under NT AUTHORITY\NETWORK SERVICE account.
http://stackoverflow.com/questions/2806438/login-failed-for-user-domain-machinename
NETWORK SERVICE and LocalSystem will authenticate themselves always as the correpsonding account locally (builtin\network service and builtin\system) but both will authenticate as the machine account remotely.
If you see a failure like Login failed for user 'DOMAIN\MACHINENAME$' it means that a process running as NETWORK SERVICE or as LocalSystem has accessed a remote resource, has authenticated itself as the machine account and was denied authorization.
Typical example would be an ASP application running in an app pool set to use NETWORK SERVICE credential and connecting to a remote SQL Server: the app pool will authenticate as the
machine running the app pool, and is this machine account that needs to be granted access.
When access is denied to a machine account, then access must be granted to the machine account. If the server refuses to login 'DOMAIN\MACHINE$', then you must grant login rights to 'DOMAIN\MACHINE$' not to NETWORK SERVICE. Granting access to NETWORK SERVICE
would allow a local process running as NETWORK SERVICE to connect, not a remote one, since the remote one will authenticate as, you guessed, DOMAIN\MACHINE$.
If you expect the asp application to connect to the remote SQL Server as a SQL login and you get exceptions about DOMAIN\MACHINE$ it means you use Integrated Security in the connection string. If this is unexpected, it means you screwed up the connection
strings you use.
If this helped you resolve your issue, please mark it Answered

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

SCCM Console issue, SQL connectivity login failed for SCCM machine account

Similar Messages

Maybe you are looking for