September 4, 2002 at 3:18 am
Hi,
We have a package that runs every day - 99% of the time it runs with no error - then out of the blue we get the following error;
DTSRun:
Loading...
DTSRun:
Executing...
Error: -2147220499 (800403ED);
Provider Error: 0 (0)
Error string: No Steps have been defined for the transformation Package.
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts.hlp
Help context: 700. Process Exit Code 1. The step failed.
This has happened randomly about 5 or 6 times in the last year - I can find no cause for this - any thoughts?
Tim
September 4, 2002 at 4:04 am
If it occurrs so infrequently you may never find an answer as anything could be the case. You might want to check the package for multiple versions within it's history where one may have been this way. I usually delete the old items when I have the final package created and it tests fine. But that may not be the answer, just to infrequent to know for sure.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
September 4, 2002 at 4:56 am
Hi,
Thanks for the reply - I'll get rid of old versions - wait a couple of months and see what happens
Whilst searching for information on this error I found a vague reference to upgrading MDAC to 2.5 or above (SQLMag forum) but can find nothing on TechNet or MSDN that backs this up.
Does this ring true?
(Current MDAC version is v. 2.12.42202 - I will not get the change through unless I can justify the requirement to upgrade)
Thanks
Tim
September 4, 2002 at 12:51 pm
I haven't heard this, but stranger things have happend. Try the most current MDAC as long as it fits your environment. Known issue with clustered servers.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
September 4, 2002 at 7:15 pm
If you are running any Analysis Services apps on the same server, you may want to upgrade to MDAC 2.6 and not MDAC 2.7...2.7 overwrites the OLEDB OLAP drivers but does not register them correctly. There is a patch available via MS Tech Support but it didn't work for me...reinstalling SP2 for Analysis Services corrected the problem with the drivers but it was exasperating chasing it down...
Michael Weiss
Michael Weiss
October 7, 2002 at 10:02 am
An update to this:
Deleting the multiple versions worked!
One month on and there have been no more reports of this error.
Thanks Antares
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply