September 2, 2015 at 12:10 pm
My team just recently moved to SQL server 2014 from 2008 R2.
We are migrating our SSIS packages to 2014 as well.
I set up the SQL server logging provider to log OnError and PostExcecute events but the project failed before it could log to the dbo.sysssislog table.
Before, when a job failed, i would look up the SQL server agent and right click the job and click on view history. There i would expand the log summary and click on the detail and the message below would display something like:
xecuted as user: rmX\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 12:40:43 AM Error: 2011-02-04 00:40:44.19 Code: 0xC0202009 Source: Package Connection manager "rm.rm" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'nice\rmX$'.". End Error Error: 2011-02-04 00:40:44.19 Code: 0xC020801C Source: Data Flow Task Provider SQL Query 1 [1082] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "rm.rm" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2011-02-04 00:40:44.19 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline Description: component "Provider SQL Query 1" (1082) failed validation and returned error code 0xC020801C. End Error Error: 2011-02-04 00:40:44.19 Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2011-02-04 00:40:44.19 Code: 0xC0024107 Source: Data Flow Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 12:40:43 AM Finished: 12:40:44 AM Elapsed: 0.234 seconds. The package execution failed. The step failed.
With this message I could find out why the SSIS package failed.
But now I'm getting a message telling me to go look at the standard execution reports.
Which, by the way, give no information whatsoever about why the job failed.
I need to access that message somehow, or find a way to get something similar.
PLEASE HELP!
September 6, 2015 at 9:57 pm
Though I couldn't exactly get what you are doing in the package, the error message states that
Login failed for user 'nice\rmX$'. Connection name : rm.rm
Can you verify the connection rm.rm using the account nice\rmX$?
secondly , if you have fixed the above issue, what is the error message that you are getting on sql schedule job the right now?
Regards,
Raj
September 7, 2015 at 5:33 am
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply