October 12, 2009 at 8:57 am
I am running a SSIS package which is calling an exe using the "Execute Process task". Earlier I used to get the error message that said Multiple Step OLEDB operation generated errors.. No work done..
Later I got rid of this error automatically and the package was running successfully.
Now the issue is I have a sql job which calls this exe in one of the Job steps. Whats happening is I am getting the same error again as mentioned in the Sucject line...
Does any one have idea about this??
Why is it not happening when I am executing the package alone and coming up when i call it in one of the SQL job steps..
NOTE:: I have also tried running the SQL job by changing the account on which SQL server agent runs to the same account which executed the SSIS package.
Help will be very much appreciated..
NEED HELP URGENTLY ON THIS....
October 12, 2009 at 9:03 am
Updating with the Actual error I am encountering in a sql job
October 12, 2009 at 9:04 am
Code: 0xC002F210 Source: Execute SQL Task Execute SQL Task Description: Executing the query "EXECUTE DBName.dbo.SPName @JobName = ?<c/> @PackageName = ?<c/> @TaskName = ?<c/> @status = 'FAIL'" failed with the following error: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value<c/> if available. No work was done.". Possible failure reasons: Problems with the query<c/> "ResultSet" property not set correctly<c/> parameters not set correctly<c/> or connection not established correctly. End Error Error: 2009-10-12 05:49:02.28 Code: 0xC0029151 Source: CFT-IMSJobExecuteTask Execute Process Task Description: In Ex
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply