January 14, 2008 at 5:20 pm
All:
A DTS job cannot be opened for editing or run after being moved to a new server. I CAN open it from the Enterprise Manager on the old server (the new server is registered on the old so I can manage objects from there.) This suggests to me that something is missing on the new server, rather than the job being corrupt.
http://support.microsoft.com/kb/288910 suggests the following causes:
How can I tell if this is the cause?
The old server is SQL2000 SP3a, the new one is SQL2K SP4. This isn't it.
OK, so how do I register it?
Thanks.
January 14, 2008 at 6:57 pm
It happened to me before. How did you move your DTS to the new server?
You may try different approach to move.
1. Save As from the old server;
2. Save as a script and load it on your new server;
3. Using SELECT clause from your old server to get the output, then using INSERT clause on your new server.
Please feedback how you solve your problem eventurally.
Many thanks in advance.
January 15, 2008 at 10:22 am
I moved it initially by opening it on the old server and selecting SAVE AS and saving it directly to the new server.
The other SAVE AS options are a visual basic file (*.bas) and a *.dts file. The DTS file gets the same error when I try to open it on the new server. I don't know how to run the BAS file to install the job on the new server. How to I do that?
January 15, 2008 at 1:39 pm
Fixed.
Here's the fix:
The KB said it could be a missing CLSID from a custom task, so I searched the CLSID section of HKEY_CLASSES_ROOT for "DTS." I found a reference to a DTS custom task and a DLL file in C:\Program files.
I copied this DLL file to the new server, registered it, and now the DTS works on the new server.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply