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.

Similar Messages

  • Unable to connect to XL Reporter.  Login failed for user 'xlruser'

    Hi,
    I have one user getting the following error when starting XLR in 2005:
    Unable to connect to XL Reporter.  Login failed for user 'xlruser'
    I have done a clean uninstall of XLR on the client but the message still appears on starting the add-on
    Greig

    Check this SAP Note: 847981 Unable to connect to XLR after installation
    [https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=847981]

  • "Login Failed for user" in Standard Report Creation Wizard

    I am trying to create a report using the report wizard in CR 08. When I choose new connection ==> OLE DB(ADO)==>Microsoft OLE DB Provider for SQL Server and enter the Server and user ID (no password), I get the error "Login failed for users".
    SQL State: 42000
    [DataBase Vendor Code: 18456]
    I was using CR 10 and called the 1-866 # and was told to try it wil CR 08 and Im getting the same error. I know the log on information is correct because I use the same server name and userID to login with SQL Server management studio and Visual Studio 08.
    Please let me know what I can do to link CR to my SQL Database.
    Thanks,
    John

    How is your user accessing the site? 
    Did you extend it to a different zone, and if so what authentication provider are you using for that zone or is it the same zone?
    Looks like the domain is a workstation name?  are they logging in with valid credentials for the WIN-IMH9QUCN1FU workstation, which may be different than what they usually log in as?
    ieDaddy
    Blog: http://iedaddy.com
    Twit: @iedaddy

  • 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

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

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

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

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

  • 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 open database "ReportServer" requested by the login. The login failed. Login failed for user 'USER LOGON'

    I want to grant permissions to all domain users to view reports on our Report Server. Domain users are able to access our Report Server URL and folder, but when they click on a report item they get an error message: 
    "Cannot open database "ReportServer" requested by the login. The login failed. Login failed for user 'USER LOGON'"
    I'm using windows authentication and configured the local service account in SSReportS Config Manager as the credentials to connect to the Report Server DB. 
    Can someone please help how I should properly do this step by step to give all domain users permissions to view a report in SSRS?
    Thanks much! - Rookie DBA

    Hi IWAR,
    The error message "Cannot open database "ReportServer" requested by the login. The login failed. Login failed for user 'USER LOGON'" means the user 'USER LOGON' does not have permissions to access the "ReportServer" database.
    To fix this issue, please verify that the user has a valid database user login. For more details, please refer to the following steps.
    In SQL Server Management Studio, open Object Explorer and expand the Databases folder.
    Expand the database in which to create the new database user.
    Right-click the Security folder, point to New, and then click User.
    On the General page, enter a name for the new user in the User name box.
    In the Login name box, enter the name of a SQL Server login to map to the database user.
    Click OK.
    Reference:
    http://technet.microsoft.com/en-us/library/ms156468(v=sql.105).aspx
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • 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

  • Non-SysAdmins get error 18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.

    I have a SQL 2008 R2 system (10.50.4000) where I'm having problems connecting any user that is not a SysAdmin.  Example: I setup a new SQL Login to use Windows Authentication and grant that user db_datareader on the target database.  The user attempts
    to connect using Excel client or Access or SQL Management Studio and receives Error 18456.  The SQL Server Logs shows Error 18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
    The strange part is that if I temporarily grant the user the sysadmin server role then the user can connect successfully and retrieve data.  But, if I take away that sysadmin server role then the user can no longer connect but again receives the Error
    18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
    We've turned off UAC on the client machine to see if that was the problem, but no change.
    I have dropped and re-added the user's SQL Login (and the related database user login info).  No success.
    The Ring Buffers output shows:
    The Calling API Name: LookupAccountSidInternal
    API Name: LookupAccountSid
    Error Code: 0x534
    Thanks for any help.
    -Walt

    Yes, you understand correctly.  The user is logging onto a workstation (not the server) with a Windows Authenticated id.  The user is using either Excel or Access or SSMS and connecting to the server using a Windows Authenticated SQL Login account.
     If the account has sysadmin role (which is only for testing) then the connection is successful.  If I take away sysadmin role from the account then the connection is unsuccessful and the SQL Server Log shows Error
    18456 Severity 14 State 11 Login Failed for user _ Reason Token-based server access validation failed with an infrastructure error.
    (SQL Authentication is not an option here.  I must use Windows Authentication).
    Any other troubleshooting assistance you can offer would be appreciated.  Thanks.
    -Walt 

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

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

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

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

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

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

  • 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

  • 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

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

Maybe you are looking for

  • Fatal! Book not bound error on B&N Nook upload of EPUB

    When exporting to EPUB, Indesign 2014 issues the following metadata: <metadata xmlns:dc="http://purl.org/dc/elements/1.1/"> If you've modified any of the metadata with opf attributes, this leads to the error "Fatal! book not bound" when uploading to

  • Migration of photos from one iMac to another

    Recently, I bought a new iMac and used the Migration Assistant to transfer files.  When I opened iPhoto, all of the pictures were there, but all my events were gone.  I had to recreate events for over 7,000 pictures.  A real pain. I am now in the pro

  • Airplay Question (wasn't sure where to place it)

    I know that it's only possible through the aid of third party software (such as Rogue Amoeba's Airfoil), but is there a reason that iOS devices and Macs (or even a PC running iTunes) are unable to receive Airplay data?  For instance, if I have an iPo

  • AE CC crash when drag jpg and png files to comp

    Hi I have noticed photoshop exports of jpg and png files cause AE CC to crash when drag these files  to comp Same jpg and png exported from CS6 do not cause crash.

  • Burning a slideshow to a dvd to play on tv

    I have a mac osx 10.9.4 and are trying to make a slideshow to burn to a dvd to play on tv would like more than 1 song as there are quite a few photos - cannot find idvd please can someone help I have spent a lot time and getting nowhere