|
Home > Archive > MS SQL Server DTS > July 2005 > DTSRun: Loading... -- then nothing
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
DTSRun: Loading... -- then nothing
|
|
|
| Suddenly no dts jobs can be run using the dtsrun utility (or scheduled).
Get message
DTSRun: Loading...
then nothing -- no errors -- nothing. Any ideas?
| |
| Darren Green 2005-07-20, 8:24 pm |
| In message <B4F16959-29AD-403B-B026- A18E09BC04D6@microso
ft.com>, jl
<jl@discussions.microsoft.com> writes
>Suddenly no dts jobs can be run using the dtsrun utility (or scheduled).
>Get message
>DTSRun: Loading...
>
>then nothing -- no errors -- nothing. Any ideas?
A couple of wild ideas -
Check the version of dtsrun that is being used. If you had 7.0 installed
it relies on the PATH variable being correct, 2000 path before 7.0 path,
to find the correct version.
Check your TEMP and TMP location disks, as temporary space is required
for many packages and tasks.
Assuming local storage, run a profiler trace and watch for calls to the
msdb database, and the package loading procedure sp_getdtsackage (I
think).
--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org
| |
|
| Thank you for the reply.
Some additional info:
I tried copying in the dtsrun from a server on which the packages work fine,
and it still didn't make a difference. Version is 2000.80.534.0
There is a TEMP dir on both the server that is working and not working in
the same location. Plenty of space available.
DTSRun is not even getting to the stage of logging into the db -- no
profiler activity from it at all.
This stopped working suddenly with no errors in the event or error log.
"Darren Green" wrote:
> In message <B4F16959-29AD-403B-B026- A18E09BC04D6@microso
ft.com>, jl
> <jl@discussions.microsoft.com> writes
>
> A couple of wild ideas -
>
> Check the version of dtsrun that is being used. If you had 7.0 installed
> it relies on the PATH variable being correct, 2000 path before 7.0 path,
> to find the correct version.
>
> Check your TEMP and TMP location disks, as temporary space is required
> for many packages and tasks.
>
> Assuming local storage, run a profiler trace and watch for calls to the
> msdb database, and the package loading procedure sp_getdtsackage (I
> think).
>
> --
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
>
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>
>
|
|
|
|
|