March 29, 2007 at 9:08 am
I am finding that DTS packages are failing with an "Unspecified Error" when run as a job. I RD to the server and cannot open the DTS package. I can open it on my laptop, I can also run it on my laptop via DTSRUN.
We have a mixed enviroment, some SS2000 and SS2005. We have deployed the SS2005 management studio to all the DBA's machines and it is running with the SS2000 client tools still installed.
Using a machine that has both installed, a DTS package is checked out of VSS (stored as a SSF) and saved onto a SS2000, SP4 server. I then try and execute the package on the server (which only has SS2000) via DTSRUN and it fails with the dreaded "unspecified error". If I run it remotely via the DBA machine (dtsrun from command line), it executes just fine.
I RD to the server again and delete the package. From the server, I open the SSF and redeploy it on that same server. The DTS runs fine via a job or DTSRUN.
This leads me to believe that there is an issue deploying DTS packages to a SS2000 machine using a client machine that has both clients.
Has anyone run into this and if so, any work arounds, other than using a seperate machine for deployment?
Thanks in advance for the help/comments.
Russ
"I'm a DBA because they haven't developed a 12 step program yet."
Russ
"I'm a DBA because they haven't developed a 12 step program yet."
April 3, 2007 at 1:59 pm
My understanding is that if you have SQL 2000 client tools and you install SQL 2005 client tools it also upgrades the SQL 2000 stuff, especially the DTS tools. One suggestion I have heard...haven't tried...is to uninstall SQL 2000 and reinstall it (in other words...install SQL 2005 first, then 2000).
-SQLBill
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply