February 15, 2008 at 11:36 am
Hi all. I'm currently working with SQL Server 2K, and I've installed Analysis Services as well as SP4.
I previously wrote a DTS that had several FTP steps in it. I was able to view/edit/run this package until recently. We were testing out SQL Server '05, and when we uninstalled it, it really screwed up my install of SQL 2k.
Long story short, I've scrubbed the system and reinstalled SQL Server 2K, but am unable to open the DTS package. The error I get is:
Error Source: Microsoft Data Transformation Service (DTS) Package
Error Description: Unspecified Error
Then a prompt that says:
The selected package cannot be opened. The DTS Designer has been closed
I've googled like crazy, and have been unable to find any resolution on this. Any help would be greatly appreciated!
Small update: Ok, small update. I was unaware that NO user was able to access this DTS package. Currently, all our environmetns are running SQL Server 2000 ver. 8.00.2039. Is there any way to access the DTS and at least export the steps?
April 15, 2008 at 11:12 am
I experienced the same recently with opening a DTS package on a 2000 SP4 server. This is a standalone installation with no other instances or versions of SQL. It contains an FTP task as yours did though. I was able to open the package remotely though from a client machine and revert to a prior version of the package. I only received the error message when trying to open it locally on the server. Were you able to open the package from a client machine?
May 12, 2008 at 1:31 pm
Does any one have a resolution to this problem?
Prakash B
May 22, 2008 at 1:28 pm
I am also having the same problem with a DTS package with an FTP step.
I recreated the package with all the objects minus the FTP. Copying all the relevant FTP configuration information into a text box within the package.
Then saved the package out as a structured storage file (*.dts).
You could also just use the Save As and backup the file.
With the backup safely stored I then add the FTP step and run the package. Next week when I go to run the package again it will give me the Unspecified Error - Cannot be opened.
Recreate and re-run, I haven't been able to find a true solution.
A nod is as good as a wink to a blind bat.
May 22, 2008 at 1:41 pm
It seems that there's a major problem with the FTP process in SQL Server. I understand that you can run the FTP with vbScript and the http://ftp.exe process that's native on the server.
I have some code that FTPs files from a web app to a server, and it uses Wscript to do it. I'll clean it up and see if I can't get it running in SQL Server. If I can, then I'd be happy to post the code.
June 20, 2008 at 3:08 pm
I was exactly in the same problem, with several DTSs, all of them with at least 1 FTP-Task.
I wanted to put in production(SQL2KSP4) the new DTSs, which were working fine on QA(SQL2KSP4). First I tried several attempts to save them from the QA server registered in the SQL Enterprise Manager of my PC; the Saving process to the production server worked fine but when I wanted to open any of them, the 'Unspecified error' appeared. Then I tried using the DTSBackup2000 utility, but didn't work either. So, I connected to the production server using Terminal Services, then I register the QA server in the SQL Enterprise Manager and transferred all the packages to the new server (at that time 'local' server), and this way I could open all of them, make them any change, save it, and reopen it again perfectly.
Warning: The issue was still in the environment, cause any additional change to the DTS, I have to make it directly in the production server using TermServ. If I change the DTS from my PC, the DTS get crashed again. At least this way I accomplished the task of put it in production. Hope this help someone.
December 17, 2008 at 11:34 am
I have the same problem. SP4 installed.
I have an FTP object in 2 DTS packages I cannot open. I am currently remote, so I hope as others have found they can open them from where they were created.
It almost seems that to me that there is a reference to something in the package that when you are not on the same machine, it cannot access, so EM from another machine can't open the package.
No solution yet, other than use Active X vs built in FTP object
February 10, 2009 at 6:41 am
Hi
I had exactly the same error with my DTS which also contained a FTP Protocol task plus a Dyanmic Properties Task.
After much pain, I found (accidentally) that I had opened the DTS in Enterprise Manager on a PC that had a slightly different version of EM (think I put Sharepoint on it a while ago). The main difference being a dll called custtask.dll in C:\Program Files\Microsoft SQL Server\80\Tools\Binn folder.
On the original PC this was dated 17/12/2002, on the PC I had amended the package on it was 04/05/2005. Somehow after using the new EM it would never open again on PC with old EM (and kept giving the Unspecified error)
I did copy over new custtask.dll (after renaming original one) and it then also require a msvcr71.dll from Windows\System32 dir, but it did work! No registering dlls required. I got the package working again on the original PC. However in the end I worried too much about the effect of these new dll's on my other packages, that I ended up re-writing the FTP package on original old PC........... oh my
February 10, 2009 at 6:56 am
Moving the newer version of the custtask.dll from my workstation to the database server resolved my problem. Note that I had recently installed the SQL 2005 tools on my workstation. I cannot say for sure if this is the product that placed the newer version of the custtask.dll on my workstation.
Thanks for the help!!
COGunn
March 2, 2009 at 12:06 am
Hi Sharon,
Thankyou very much for useful tips
November 5, 2013 at 3:35 pm
I know this post is couple of years old, but this has helped me to resolve a similar problem today.
Thank you
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply