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!

Hi ,

The SSIS Error Code  states that why the  package failed.

It seems your 'nice\rmX$' account does not have required privileges to access the data sources in your SSIS package. To overcome this you may need to create a SQL Agent proxy account that has the required privileges and then run the SSIS package under  this account

Thank you but that is not what i was asking.

That error message is just a sample not an actual error I am having. My issue is that the place where an error like that used to appear (Job history) no longer shows that message, instead it sends me to look at the standard reports that don't show an error message or any useful information.  

I need to know where I can find this message or something similar because its not where it should be. I was thinking that maybe because I turned on the dbo.sysssislog table logging feature to log OnError events it is not creating the usual message. 

The operational reports sometimes need to be drilled down to get more info, but it should give you an indication that there was a package issue (error) otherwise it is not perhaps even SSIS related.

I don't remember if the SSIS reports were available as part of SQL Server 2008 R2, but the link below shows you how to view them in SQL Server 2012+.  The reports will list any of the error messages captured.

View Reports for the Integration Services Server
https://msdn.microsoft.com/en-us/library/hh213358.aspx

Reports for the Integration Services Server
https://msdn.microsoft.com/en-us/library/hh213362.aspx

• Edited by J I M B O 11 hours 9 minutes ago Updated links
• Proposed as answer by Katherine XiongMicrosoft contingent staff, Moderator 4 hours 11 minutes ago

Did you change the connection string for the log table when you migrated the package?  If not, it is still trying to log to the old SQL Server dbo.sysssislog.

• Proposed as answer by Katherine XiongMicrosoft contingent staff, Moderator 4 hours 11 minutes ago