Sql login failed

Hi everybody.
I installed database 10g release 2 with enterprise manager on windows server 2003 machine.
But when I tried to login to the database throughout internet explorer using the following command:-
http://localhost:5560/isqlplus , but it is failed.
the messager which is appeared to me is:-
{The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings}
I knew isqlplus port from portlist.ini, so I completely sure that is the correct port.
but when I logged into em from internet explorer ,the em is called successfully.
I don't know why isqlplus was not called.
to notify that my database is already running
please could anyone gives me a helping hand?
bye.

[email protected] wrote:
Hi,
I really appreciate you.
I managed to connect to isqlplus throughout HP-UX 11i .
but the same problem I have with em on HP-UX 11i.
byeAnd so the pattern that has been established so far is that when you can't connect, it is because that component hasn't been started. Have you made sure the agent and dbconsole are started?

Similar Messages

  • SQL Login failed alert

    Hi,
         In my environment i get alert mail of severity 20 when a Windows Login fails. But I'm not getting the alert when a SQL login fails. Is there anything i have to enable or i have to script a job. Advice me other that trigger.

    To check what database was being used when the login failed, you will need to use default trace as mentioned in the link below:-
    http://www.eraofdata.com/the-sql-server-default-trace/
    Or simply run the below query, if you have default trace enabled:-
    SELECT  TE.name AS [EventName] ,
            v.subclass_name ,
            T.DatabaseName ,
            t.DatabaseID ,
            t.NTDomainName ,
            t.ApplicationName ,
            t.LoginName ,
            t.SPID ,
            t.StartTime ,
            t.SessionLoginName
    FROM    sys.fn_trace_gettable(CONVERT(VARCHAR(150), ( 
                    SELECT TOP 1
                    f.[value]
                    FROM    sys.fn_trace_getinfo(NULL) f
                    WHERE   f.property = 2)), DEFAULT) T
            JOIN sys.trace_events TE 
                    ON T.EaventClass = TE.trace_event_id
            JOIN sys.trace_subclass_values v 
                    ON v.trace_event_id = TE.trace_event_id
                    AND v.subclass_value = t.EventSubClass
    WHERE   te.name IN ( 'Audit Login Failed' )
    order by t.StartTime desc
    Also, you mentioned that 'Alert For Severity 20' is triggered when there is a failed login for windows. However, it's not the case. Alert for Severity 14 is triggered on failed logins as far as i have seen. 
    Severity Level 20: SQL Server Fatal Error in Current Process
    These messages indicate that a statement has encountered a problem. Because the problem has affected only the current process, it is unlikely that the database itself has been damaged.
    Reference:
    http://technet.microsoft.com/en-us/library/aa937483(v=sql.80).aspx
    http://sqlrows.blogspot.in/2011/10/note-to-self.html
    Please mark the answer as helpful if i have answered your query. Thanks and Regards, Kartar Rana

  • 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

  • SUP and SQL login failed

    Hi,
    Been racking my brain about this one, searched online (including here) but haven't found a solution yet. My scenario is: SCCM 2012 R2 and SQL 2012 (with databases CM_SCM and SUSDB, instance name is MSSQLSERVER) installed on the same server. SCCM will only
    be used to build servers using TS. I'm using SCCM as a SUP to do offline servicing of the wim files. This setup was working up to several weeks ago (don't know exactly when it stopped) and since, whenever I do a software update sync, I get
    'Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.. Source: CWSyncMgr::DoSync'.
    Checking the WCM.log I get the following error: 
    System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'DOMAIN\MACHINENAME$'.~~   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)~~   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetConfiguration()~~
      at Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load()~~   at Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args)~~   at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type
    type, Object[] args)~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetConfiguration()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.SetUpstreamServerSettings(Boolean SyncFromMicrosoftUpdate, Boolean ReplicaServer, String
    UpstreamWSUSServerName, Int32 UpstreamWSUSServerPortNumber, Boolean UseSSL, Boolean HostBinariesOnMU, Int32 ReportingLevel, Int32 MaximumAllowedComputers)~~ClientConnectionId:00000000-0000-0000-0000-000000000000
    If I then check the SQL Server log, I have (over and over again) the error:
    Login failed for user "DOMAIN\MACHINENAME$". Reason: Could not find a login matching the name provided. [CLIENT: <local machine>] - Error 18456, Severity: 14, State: 5
    According to http://sqlblog.com/blogs/aaron_bertrand/archive/2011/01/14/sql-server-v-next-denali-additional-states-for-error-18456.aspx , state 5 indicates (as the error msg mentions) that the login doesn't exist, however in the SQL server it does exist
    and is also present under both DBs\Security\Users.
    There was no SPN set for the service account I created when setting the server up (in this case sccmsql), I've now set it manually to MSSQLSvc/FQDN:1433, as mentioned in http://technet.microsoft.com/en-us/library/hh427336.aspx#BKMK_ManageSPNforDBSrv
    , but without any luck.
    Thanks in advance for reading this.
    Dan

    Dan,
    Remove the SUP role. Remove WSUS and delete the SUSDB. Reboot the site server and reinstall WSUS and SUP. It'll recreate all the required permissions as part of the install.
    Cheers
    Paul | sccmentor.wordpress.com

  • 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

  • Intermittant (not constant) SQL database ShareWebDb login failed events 3760 and 2424

    My Sharepoint 3.0 services that were bundled with SBS 2008 appear to be working fine. Companyweb, etc, all work w/o issue, so I don't want to take violent action, but these errors seem to be accellerating so I would love to know if there is a known
    solution.
    I typically receive the following (these are in reverse time order, latest at the top, just as they appear in the event log):
    Error Event ID: 3760 SQL Database 'ShareWebDb' on SQL Server instance 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error information from SQL Server is included below. Cannot open database "ShareWebDb" requested
    by the login. The login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
    one second earlier:Error Event ID: 2424 The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again. Context: Application 'Search', Catalog 'index file
    on the search server Search'
    Information Event ID: 18456 No description, here is the Details:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider
    Name="MSSQL$MICROSOFT##SSEE" />
    <EventID Qualifiers="49152">18456</EventID>
    <Level>0</Level>
    <Task>4</Task>
    <Keywords>0x90000000000000</Keywords>
    <TimeCreated
    SystemTime="2010-11-12T18:35:06.000Z" />
    <EventRecordID>491461</EventRecordID>
    <Channel>Application</Channel>
    <Computer>myserver.mydomain.local</Computer>
    <Security
    UserID="S-1-5-20" />
    </System>
    <EventData>
    <Data>NT AUTHORITY\NETWORK SERVICE</Data>
    <Data>[CLIENT: <named pipe>]</Data>
    <Binary>184800000E000000170000005000450054003300310030005C004D004900430052004F0053004F00460054002300230053005300450045000000070000006D00610073007400650072000000</Binary>
    </EventData>
    </Event>
    Two seconds earlier
    Information Event ID 17137 No description, here is the Details:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider
    Name="MSSQL$MICROSOFT##SSEE" />
    <EventID Qualifiers="16384">17137</EventID>
    <Level>4</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated
    SystemTime="2010-11-12T18:35:04.000Z" />
    <EventRecordID>491460</EventRecordID>
    <Channel>Application</Channel>
    <Computer>mysever.mydomain.local</Computer>
    <Security
    UserID="S-1-5-20" />
    </System>
    <EventData>
    <Data>ShareWebDb</Data>
    <Binary>F14200000A000000170000005000450054003300310030005C004D004900430052004F0053004F00460054002300230053005300450045000000070000006D00610073007400650072000000</Binary>
    </EventData>
    </Event>
    I get more 3760 errors than 2424's. However, the
    2424's do seem to usually correspond to a 3760 18456 17137 occurance and the
    3760 are always preceeded by 18456 17137. I was getting one or two sets a day, lately that has increased to 5 or 10.
    I've done a lot of
    web research on Sharepoint Errors 3760 and
    2424 and I see a number of people are experiencing the the same issue. Most of what I've come across for solutions do not apply, since errors are intermittent, not chronic and my public remote URL has already been added
    to BackConnectionHostNames as per:
    http://blogs.technet.com/b/sbs/archive/2009/08/05/sharepoint-services-3-search-event-errors-after-an-sbs-2008-update-rollup.aspx
    I installed the SQL Server Management Studio Express so I could try to track down the permissions on this database. I see the SQL server instance, MYSERVER\Microsoft##ssee, and it shows as running, but when I try to connect to it I get the following
    error: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote
    connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)" I'm assuming that is because I don't have access permission for that internal database.
    I don't see any errors in the event log related to failed logins or any errors at all from the SQL server, but there are the time matching informational entries right before the error events and lots of other 17137's and 2803's from MSSQL$Microsoft##ssee

    Thank you Kevin, that does seem to match my symptoms and I have made the change suggested. Just incase that page becomes unreachable by others, here is the part of the page that applies to this:
    Issue:
    =========
    Receive event error 3760 and 6398 on SBS 2008
    Cause:
    ==========
    Issue was caused by incorrect Auto Close option for ShareWebDb database
    Solution:
    ==========
    1. On the SBS 2008 server, click Start -> All Programs -> Microsoft SQL Server 2005, right click SQL Server Management Studio Express and choose run as administrator.
    NOTE: You must run it as administrator to perform steps below.
    2. In the Server Name box, type \\.\pipe\MSSQL$Microsoft##SSEE\sql\query, click connect.
    3. Expand Database node and right click the ShareWebDb then choose properties.
    4. Click Options in the left pane, in the right pane, please check whether the Auto Close option is set to True, if so, please change it to False.

  • 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
    ¯\_(ツ)_/¯

  • 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

  • Login failed for user 'IIS APPPOOL\DefaultAppPool' on SQL Express 2012

    I am new to both ASP.NET and SQL Server.
    I have IIS8 installed on my Windows 8 PC, together with SQL Server Express 2012. Given my ignorance, I have just set everything up using default values.
    I have a very small web site set up in its own folder and set up in IIS 8 as a virtual folder under the default web site. I have also set up a very simple database called 'StockControl' via SSMS, which contains one table called 'Colours' which has two columns.
    One page in the website is a simple ASP.NET form which runs on localhost without any problems.
    On the second page in the website I added a GridView ASP.NET control, letting Expression Web 4 generate the connection string and place it in a web.config file. I tested the SQL query and the connection as I went along and both came back as successful. So
    far, so good.However, when I try to run the page in the browser I get the error message:
    Server Error in '/' Application.
    Cannot open user default database. Login failed.
    Login failed for user 'IIS APPPOOL\DefaultAppPool'.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
    Exception Details: System.Data.SqlClient.SqlException: Cannot open user default database. Login failed.
    Login failed for user 'IIS APPPOOL\DefaultAppPool'.
    Source Error:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
    Stack Trace:
    [SqlException (0x80131904): Cannot open user default database. Login failed.
    Login failed for user 'IIS APPPOOL\DefaultAppPool'.]
    I have spent two days trying to find out what I have done wrong and even uninstalled and re-installed SQL Server just in case i'd totally messed up and corrupted the database.
    I would really appreciate some help please.

    I changed the IIS default identity to NetworkService and got this error instead
    Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\StockControl.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
    An attempt to attach an auto-named database for file C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\StockControl.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
    There is nothing running that is using the database.
     I have also set a login up for the Apppool and set the user mapping to the database but the problem persists,
    What is so infuriating is that a week ago I had several pages in this website that displayed, inserted, updated and deleted records on this database using ADO as well as ASP.NET running just fine. Then this problem came out of nowhere.

  • 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

  • Error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication" on SQL Server 2008 R2 Enterprise Edition 64-bit SP2 clustered instance

    Hi there,
    I have a Windows 2008 R2 Enterprise x64 SP2 cluster which has 2 SQL Server 2008 R2 Enterprise Edition x64 SP2
    instances.
    A domain account "Domain\Login" is administrator on both physcial nodes and "sysadmin" on both SQL Server instances.
    Currently both instances are running on same node.
    While logging on to SQL Server instance 2 thru "Domain\Login" using "IP2,port2", I get error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication". This happened in the past
    as well but issue resolved post insatllation of SQL Server 2008R2 SP2. This has re-occurred now. But it connects using 'SQLVirtual2\Instance2' without issue.
    Same login with same rights is able to access Instance 1 on both 'SQLVirtual1\Instance1' and "IP1,port1" without any issue.
    Please help resolve the issue.
    Thanks,
    AY

    Hello,
    I Confirm that I encountred the same problem when the first domain controller was dow !!
    During a restarting of the first domain controller, i tried to failover my SQL Server instance to a second node, after that I will be able to authenticate SQL Server Login but Windows Login returns Error 18452 !
    When the firts DC restart finishied restarting every thing was Ok !
    The Question here : Why the cluster instance does'nt used the second DC ???
    Best Regards     
    J.K

  • 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

  • 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

  • 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

  • SQL Server Agent job between 2 instances fails with Error 18456 - Login Failed for user

    Hi,
    SQL Server version: 2012 EE
    OS: Windows 2008 R2 Enterprise
    In my server, i have 2 instances, and I am trying to configure a SQL Server Agent job to query one table in Instance A, and insert some modified data in Instance B, both in the same server.
    When i execute the job in instance A, i get the following error:
    Executed as user: NT SERVICE\SQLSERVERAGENT. Login Failed for user "NT SERVICE\SQLSERVERAGENT". [SQLSTATE 28000] (Error 18456). The step failed.
    I have already configure instance A as Master and disabled encryption, by changing the parameter MsxEncryptChannelOptions to 0 in regedit. I've also made my target instance (instance B) as a Target.
    What am i missing?
    Thanks for your attention and pacience

    Hello,
    The NT SERVICE\SQLSERVERAGENT (virtual) account is not available on the other as you just mentioned. That is the reason for the login
    failed error. Try using a Windows login as the
    SQL Server Agent service account in both servers, the same Windows login (not a virtual account), and run jobs as the “sa” account.
    http://msdn.microsoft.com/en-us/library/ms345578.aspx
    You can also try a proxy account.
    http://technet.microsoft.com/en-US/library/ms190698(v=SQL.105).aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

Maybe you are looking for

  • Mac noob needs help

    hi guys. i am having a lot of trouble here.... could you take a look at the log and point me in the right direction? start-ups take 4 -5 minutes computer won't restart too much weirdness going on to list... sorry this is so long --- but please help!

  • Using Decode in Order By clause

    Hi all, I've a prblem with the DECODE in ORDER BY clause Could you please advise if I did something wrong with my sort order. Actually,I've a store procedure which gather all information from several tables and return with a resultset. Therefore I ju

  • New hard drive not showing up in select a destination window of install

    I just installed a 500G hard drive and went to install OS X leopard and the new drive isn't showing up in the destination pane. Do I have to format it first? It shows up under disc utilities. If I have to format it what format should I use there are

  • S_ALR_87013564  transaction

    Is there any help or documentation on how to use S_ALR_87013564  transaction?

  • How to test an scenario

    Hi, After completing a scenario(eg:file to filr),how to test it...whether it is working fine or not.. Thanks in advance.