this is the scenario.
first i created a dts in my computer(local administrator account) this dts writes in an xls file in a local path for instance c:\tests... this dts uses a vb script to run this task, then.. i save it local and run it from my bids and finishes ok, after that i change the protection level to server storage and copy it to my target server.. in this server i log on with an administrator local account using windows authentication to get into the integration services, when i run my package from ssis it runs without problems.. then i use the same account to enter the database engine and scheduled a job using my dts but the job fails... the job won’t run and the message only says that the job fails, .. since this didn’t work, i created a credential using a local administrator account as the identity and created a proxy account
i used then this proxy account in my job changing the default 'sql server agent account', but it didnt work anyway, the owner of the job is my administrator account.. i also used my sa sql server account to do the same but it failed with the same error.
why why does it run ok from ssis but doesn’t success from my job what can i do
is this a problem of accounts and permissions and which permissions at which levels should i check
i'm giving up.. please somebody !!!!!!!!!!!!!!!!!!!!!!!!!!!
still cannot run my job
KeBugCheck
neemik
http://support.microsoft.com/kb/918760
Please check it out.
Dan Cathers
Christopher Roberts
these are some errors that the log provided
Event Name: OnError
Message: The AcquireConnection method call to the connection manager "Sucursales" failed with error code 0xC0202009.
Operator: XXXXXXX\Administrator
Source Name: DTSTask_DTSDataPumpTask_1
Source ID: {5F097B16-5066-4461-AEEA-B8E96B3AFCF5}
Execution ID: {7A4CD1D3-3C2D-4644-92DF-0742CF042B3C}
Start Time: 5/8/2006 12:50:59 PM
End Time: 5/8/2006 12:50:59 PM
Data Code: -1071611876
--------------
Event Name: OnError
Message: The AcquireConnection method call to the connection manager "Sucursales" failed with error code 0xC0202009.
Operator: XXXXX\Administrator
Source Name: DESIE_CatalogoDeSucursales(Semanal)
Source ID: {D1025489-4A06-4347-9674-0A73A1847829}
Execution ID: {7A4CD1D3-3C2D-4644-92DF-0742CF042B3C}
Start Time: 5/8/2006 12:50:59 PM
End Time: 5/8/2006 12:50:59 PM
Data Code: -1071611876
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------------------
Event Name: OnError
Message: component "OLE DB Destination" (40) failed validation and returned error code 0xC020801C.
Operator: XXXXXXX\Administrator
Source Name: DTSTask_DTSDataPumpTask_1
Source ID: {5F097B16-5066-4461-AEEA-B8E96B3AFCF5}
Execution ID: {7A4CD1D3-3C2D-4644-92DF-0742CF042B3C}
Start Time: 5/8/2006 12:50:59 PM
End Time: 5/8/2006 12:50:59 PM
Data Code: -1073450985
For more information, see Help and Support Center at
"Sucursales" is the name of the connection manager that maps the xls file destination. the job just fails when trying to validate it
i,ve tried changing the destination to a flat file (.csv) and the job worked fine.. but why it doesn’t run when i use and xls file destination all these errors about connection doesn’t appear when i execute the package from SSIS but when i use the job this just won’t work.. it is not a problem of permissions cause i'm using a local administrator account when i log on into the server so.... do i need to have Microsoft Excel installed in the server or some kind of service pack or system file updates!!!
please!!!!
Rajesh Kumar T
i've tried to catch the error by running each task of my dts separately.. then i found the one that is causin troubles.. it looks like by using data flow tasks something unknown happens.. i'm using an OLE DB source to retrieve some data from the db... netx step i use this data conversion task because some of the results of the query aren`t supported by mi destination which is an OLE DB destination that maps to an excel file in the target server.. this is weird cause i run this taks in my bids and runs ok.. i run this again from SSIS in the target server and runs ok.. but when i scheduled it in a job it just fails.... any solution
thanks for your help!!!!
TO
thanks to michael Entin..
There is only 32-bit Jet provider, so you need to run the package using 32-bit DtExec.exe to use it. When scheduling job in Agent, select Operating System (CmdExec) step type, and the command to run is
"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DtExec.exe" /f "package-path"