June 11, 2003 at 9:06 am
When I execute the DTS job (multi-step,looping) from the designer it runs perfectly. When I schedule the job I get the following error: DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnError: DTSStep_DTSExecuteSQLTask_1, Error = -2147217887 (80040E21) Error string: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147217887 (80040E21); Provider Error: 0 (0) Error string: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun: Package execution complete. Process Exit Code 1. The step failed.
We are using SQLServer 7.0 Service Pack 3. I checked Microsoft's support page and it says I could get this error if the DTS package was create on a Windows 2000 machine and it was not. It was created on a Windows NT 4.0 machine.
Any help would be appreciated.
Regards,
Bessebo
June 12, 2003 at 10:37 am
Hi,
Did you read this article
DTS schedule problem
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q269074
Maybe help to find the problem
Regards
JFB
June 12, 2003 at 5:17 pm
Not sure if this is your problem, but if your dts runs in isolation and it's only when scheduled that you receive the error......then the first thing I check is the user that the job is to run under (and the target). Remember the job runs on the server but the dts will run on the server, i.e. put a simple vbscript task in there to create c:\temp\test.txt and run the dts locally and then scheduled....checkout where the file is created.......
If you are aware of this then sorry for the egg sucking contest...
Another thing to check is that if you are using ODBC connections in your dts then ensure that they exist on your workstation and server (same principle as above !!!).
Regards
Andy P
Andy P
June 13, 2003 at 4:48 am
May also be that on your machine you have network mappings which is not present in the sql server account. Always use fully qualified names.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply