"Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
news:4AD8F554-EDE6-4DF3-B3DD-D1B4245CB031@microsoft.com...
> Problems with the scheduler versus interactive can usually be pinned down
> to
> this
>
>
http://support.microsoft.com/?kbid=269074 >
>
> What does the syntax look like in the job? something like DTSRUN ~/Z etc
>
> If it does then copy this out and try running the line on the cmdline.
> Still work?
>
> I personally prefer to use the unencrypted version of the cmdline as if
> you
> generate things using the Right Click on the package | schedule option it
> encrypts the version of the package into the string as well.
>
> Have a look here if you are not comfortable with the syntax
>
>
http://www.sqldts.com/default.aspx?301 >
> Allan
>
>
> "news.microsoft.com" wrote:
>
>> Hello All,
>>
>> im am experiencing difficulty with automating a DTS package. if i try to
>> run it manually it work, if i try to automate it with the scheduler it
>> always fails. to debug it i executed it using dts run to gain more
>> information and i got the following output below
>>
>> C:\Documents and Settings\simon>dtsrun /S"donaldduck" /E /N"Dialler CDR's
>> Import
>> "
>> DTSRun: Loading...
>>
>> Error: -2147217900 (80040E14); Provider Error: 14262 (37B6)
>> Error string: The specified DTS Package ('Name = 'Dialler CDR's
>> Import';
>> ID.
>> VersionID = {[not specified]}.{[not specified]}') does not exist.
>> Error source: Microsoft OLE DB Provider for SQL Server
>> Help file:
>> Help context: 0
>>
>>
>> C:\Documents and Settings\simon>
>>
>> i have tried to recreate the DTS package and still get the same error.
>>
>>
>> Can anybody help?
>>
>> Many thanks
>> Simon Whale
>>
>>
>>