Hi --

I've created a DTS package on my computer and saved to a remote server.

I can execute the package locally and it runs without problems. I can also
open it within DTS Designer (where I created it) without problems.

I've noticed that the package cannot be scheduled and would fail when trying
to execute. Today, I went to the local server and thought I'd attempt
running the package from there to see if it would work. Well, when I try
and execute within EM, it returns an "unspecified error". To make matters
worse, when I try and open the package on the remote server, it returns the
same error.

What do I do? Why won't the package open on the remote server?

I've tried saving the package to a .DTS file on my computer, deleting it
from remote server, and re-opening and saving... but the package still won't
open/run on server. It runs from my PC fine.

If anyone has any ideas or help, it would be appreciated.

I'm not looking forward to having to re-write the package.

When you run the package on your own box, it is using the drives and
security context of you and your box. So, if you refer to drive E:, it uses
drive E: on your box. If your remote server has no drive E:, it will fail.

Also, if you schedule a job on the remote box, it will run under the SQL
Server Agent service. If it has to access network drives, you'll need to
use UNC names and the agent service must run under a domain account.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"dm4714" <spam (AT) spam (DOT) net> wrote

Hi --

I've created a DTS package on my computer and saved to a remote server.

I can execute the package locally and it runs without problems. I can also
open it within DTS Designer (where I created it) without problems.

I've noticed that the package cannot be scheduled and would fail when trying
to execute. Today, I went to the local server and thought I'd attempt
running the package from there to see if it would work. Well, when I try
and execute within EM, it returns an "unspecified error". To make matters
worse, when I try and open the package on the remote server, it returns the
same error.

What do I do? Why won't the package open on the remote server?

I've tried saving the package to a .DTS file on my computer, deleting it
from remote server, and re-opening and saving... but the package still won't
open/run on server. It runs from my PC fine.

If anyone has any ideas or help, it would be appreciated.

I'm not looking forward to having to re-write the package.

Yes, I agree and understand. I'm only using C:\TEMP and they both exist on
both boxes. Even if this were the case, it doesn't explain why DTS Designer
on the server fails to open the package. It opens fine on my PC from the
same server where it is saved.

Only difference is the server is MSDE 2000/SP4.

My PC is SQL Server 2000 Developer. SELECT @@VERSION shows I have SP2, even
though I've run the SP4 upgrade successfully. So I'm not sure why this is
the case or if this is any reason to be concerned.



"Tom Moreau" <tom (AT) dont (DOT) spam.me.cips.ca> wrote