running a vbs file as a step of an SqlServer job

11/12/2007, 12h19

Hi
I have a VBScript file which runs fine when I click it or when I run it
from a command prompt level.
I added it as the 1st step of an SqlServer job and the job always fails
with the error message
"Executed as user: GVIANT\Administrator. The process could not be
created for step 1 of job 0xBE3A0405EB9F624282C1A9474AA9F719 (reason: %1
is not a valid Win32 application). The step failed."

Cn anyone me understanding this error message.

Thanks 1

David Greenberg

11/12/2007, 12h55

On Dec 11, 6:19 am, David Greenberg <davi...@iba.org.il> wrote:
> Hi
> I have a VBScript file which runs fine when I click it or when I run it
> from a command prompt level.
> I added it as the 1st step of an SqlServer job and the job always fails
> with the error message
> "Executed as user: GVIANT\Administrator. The process could not be
> created for step 1 of job 0xBE3A0405EB9F624282C1A9474AA9F719 (reason: %1
> is not a valid Win32 application). The step failed."
>
> Cn anyone me understanding this error message.
>
> Thanks 1
>
> David Greenberg

Do you have VBScripting enabled on the server? Without more info I
couldn't guess at anything else. Versions? Windows 98? ;-)

11/12/2007, 14h01

scoots987 wrote:
> On Dec 11, 6:19 am, David Greenberg <davi...@iba.org.il> wrote:
>
>>Hi
>>I have a VBScript file which runs fine when I click it or when I run it
>>from a command prompt level.
>>I added it as the 1st step of an SqlServer job and the job always fails
>>with the error message
>>"Executed as user: GVIANT\Administrator. The process could not be
>>created for step 1 of job 0xBE3A0405EB9F624282C1A9474AA9F719 (reason: %1
>>is not a valid Win32 application). The step failed."
>>
>>Cn anyone me understanding this error message.
>>
>>Thanks 1
>>
>>David Greenberg
>
>
> Do you have VBScripting enabled on the server? Without more info I
> couldn't guess at anything else. Versions? Windows 98? ;-)
>

We have windows 2000 on the server.
I am sure we have VBScripting enabled on the server because the job runs
fine when I click it to run it or when I run it from the command prompt.
We use SqlServer 2000.

11/12/2007, 12h19	#1
David Greenberg Messages: n/a Hébergeur:	running a vbs file as a step of an SqlServer job Hi I have a VBScript file which runs fine when I click it or when I run it from a command prompt level. I added it as the 1st step of an SqlServer job and the job always fails with the error message "Executed as user: GVIANT\Administrator. The process could not be created for step 1 of job 0xBE3A0405EB9F624282C1A9474AA9F719 (reason: %1 is not a valid Win32 application). The step failed." Cn anyone me understanding this error message. Thanks 1 David Greenberg

11/12/2007, 12h55	#2
scoots987 Messages: n/a Hébergeur:	Re: running a vbs file as a step of an SqlServer job On Dec 11, 6:19 am, David Greenberg <davi...@iba.org.il> wrote: > Hi > I have a VBScript file which runs fine when I click it or when I run it > from a command prompt level. > I added it as the 1st step of an SqlServer job and the job always fails > with the error message > "Executed as user: GVIANT\Administrator. The process could not be > created for step 1 of job 0xBE3A0405EB9F624282C1A9474AA9F719 (reason: %1 > is not a valid Win32 application). The step failed." > > Cn anyone me understanding this error message. > > Thanks 1 > > David Greenberg Do you have VBScripting enabled on the server? Without more info I couldn't guess at anything else. Versions? Windows 98? ;-)

11/12/2007, 14h01	#3
David Greenberg Messages: n/a Hébergeur:	Re: running a vbs file as a step of an SqlServer job scoots987 wrote: > On Dec 11, 6:19 am, David Greenberg <davi...@iba.org.il> wrote: > >>Hi >>I have a VBScript file which runs fine when I click it or when I run it >>from a command prompt level. >>I added it as the 1st step of an SqlServer job and the job always fails >>with the error message >>"Executed as user: GVIANT\Administrator. The process could not be >>created for step 1 of job 0xBE3A0405EB9F624282C1A9474AA9F719 (reason: %1 >>is not a valid Win32 application). The step failed." >> >>Cn anyone me understanding this error message. >> >>Thanks 1 >> >>David Greenberg > > > Do you have VBScripting enabled on the server? Without more info I > couldn't guess at anything else. Versions? Windows 98? ;-) > We have windows 2000 on the server. I am sure we have VBScripting enabled on the server because the job runs fine when I click it to run it or when I run it from the command prompt. We use SqlServer 2000.

Outils de la discussion
Afficher une version imprimable Envoyer un lien vers cette page par email