Can anyone shed some light on the following problem SSIS package run from sql server agent job(SSIS 2008 R2 excell connection error)
-
OK,the following issue has occured in a job that is supposed to run at the last day of each month,it's July run when wrong while it's June run went fine.
The last change to the job dates from 2011,a full 2 years before I started working for the company.
Now this is the error received on the 31 July 2015
Status: Failed Ran at: 31/07/2015 23:00:00 Executed as user: ...\...DB0012_svc. Microsoft (R) SQL Server Execute Package Utility Version 10.0.5500.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 23:00:01 Error: 2015-07-31 23:00:17.21 Code: 0xC0202009 Source: ..._..._AdvRep Connection manager ".DV...1_2K8" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "Unspecified error". End Error Error: 2015-07-31 23:00:17.22 Code: 0xC020801C Source: DTSTask_DTSDataPumpTask_1 Excel Destination [92] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "ADVREP1_2K8" 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: 2015-07-31 23:00:17.22 Code: 0xC0047017 Source: DTSTask_DTSDataPumpTask_1 SSIS.Pipeline Description: component "Excel Destination" (92) failed validation and returned error code 0xC020801C. End Error Error: 2015-07-31 23:00:17.22 Code: 0xC004700C Source: DTSTask_DTSDataPumpTask_1 SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2015-07-31 23:00:17.24 Code: 0xC0024107 Source: DTSTask_DTSDataPumpTask_1 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 23:00:01 Finished: 23:00:17 Elapsed: 16.256 seconds. The package execution failed. The step failed.
I have checked the SSIS package behind it and that has not given me the same error(in fact it ran without issue), since I had simelar issues with jobs on another instance we manage.
In those cases the cause was that the account which is used by the sql server agent did no longer have the neccesairy permissions on that folder.
So I checked and see the included picture the settings are in order.
The last thing I'm checking atm is if there might be a data issue for the 31 of July but since the job failed today on manual run I doubt that.
I have whited out all information that could hint at identity of the server.
-
We resolved this,I used an existing proxy used by some other jobs besides the fact that this proxy uses the same credentials as the default agent proxy used on this server.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply