|
 |  |  |  |  |  |  |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
 |
| |
10-30-2008
| #1 (permalink) |
| | problem passing args to script 'There is no script engine for file extenstion' Hello, I'm having an issue passing args to a script. I'm getting the error 'There is no script engine for file extenstion .net' I assume the '.net' is coming from the fact that one of my arguments takes a domain name, like: /ntp:my.server.net so calling script like this is causing this error: wscript scriptFile.wsf /arg1:value1 /arg2:value2 /arg3:server.net why doesn't the system know the script file is 'scriptFile.wsf' and the rest are named arguments? |
My System Specs |
|
10-30-2008
| #2 (permalink) |
| | Re: problem passing args to script 'There is no script engine for file extenstion' turns out my quotes were in the wrong place. I had everything after wscript.exe in quotes, I changed this so the end quote was after the script filename and the arguments are not quoted... essentially quotes around path to script file and thats it. Works fine now. "James" <noone@xxxxxx> wrote in message news:%23PraFqsOJHA.4776@xxxxxx Quote: > Hello, > > I'm having an issue passing args to a script. I'm getting the error 'There > is no script engine for file extenstion .net' > > I assume the '.net' is coming from the fact that one of my arguments takes > a domain name, like: /ntp:my.server.net > > so calling script like this is causing this error: > wscript scriptFile.wsf /arg1:value1 /arg2:value2 /arg3:server.net > > why doesn't the system know the script file is 'scriptFile.wsf' and the > rest are named arguments? > |
| My System Specs |
|
10-30-2008
| #3 (permalink) |
| | Re: problem passing args to script 'There is no script engine for file extenstion' Interesting that your first post showed the problematic command without *any* quotes, either in the right place or the wrong place. Kind of makes it hard to spot an error when you do not show *exactly* what you were doing... /Al "James" <noone@xxxxxx> wrote in message news:O7QPE2tOJHA.4312@xxxxxx Quote: > turns out my quotes were in the wrong place. > > I had everything after wscript.exe in quotes, I changed this so the end > quote was after the script filename and the arguments are not quoted... > essentially quotes around path to script file and thats it. Works fine > now. > > "James" <noone@xxxxxx> wrote in message > news:%23PraFqsOJHA.4776@xxxxxx Quote: >> Hello, >> >> I'm having an issue passing args to a script. I'm getting the error >> 'There is no script engine for file extenstion .net' >> >> I assume the '.net' is coming from the fact that one of my arguments >> takes a domain name, like: /ntp:my.server.net >> >> so calling script like this is causing this error: >> wscript scriptFile.wsf /arg1:value1 /arg2:value2 /arg3:server.net >> >> why doesn't the system know the script file is 'scriptFile.wsf' and the >> rest are named arguments? >> > |
| My System Specs |
|
10-31-2008
| #4 (permalink) |
| | Re: problem passing args to script 'There is no script engine for file extenstion' Al Dunbar wrote: Quote: > Interesting that your first post showed the problematic command without > *any* quotes, either in the right place or the wrong place. Kind of makes Quote: > hard to spot an error when you do not show *exactly* what you were Gets really annoying after several exchanges. :-( -- Todd Vargo (Post questions to group only. Remove "z" to email personal messages) |
| My System Specs |
|
10-31-2008
| #5 (permalink) |
| | Re: problem passing args to script 'There is no script engine forfile extenstion' could you send more datails? |
| My System Specs |
|
10-31-2008
| #6 (permalink) |
| | Re: problem passing args to script 'There is no script engine for file extenstion' yes, I know. I immediately made an incorrect assumption based on the error message and posted what I believed was relevant to the issue. I was wrong. Thats why I posted back as soon as I realized the real problem, hoping to prevent someone from wasting their time, and of course sharing answers. "Al Dunbar" <AlanDrub@xxxxxx> wrote in message news:eptSfxwOJHA.144@xxxxxx Quote: > Interesting that your first post showed the problematic command without > *any* quotes, either in the right place or the wrong place. Kind of makes > it hard to spot an error when you do not show *exactly* what you were > doing... > > /Al > > "James" <noone@xxxxxx> wrote in message > news:O7QPE2tOJHA.4312@xxxxxx Quote: >> turns out my quotes were in the wrong place. >> >> I had everything after wscript.exe in quotes, I changed this so the end >> quote was after the script filename and the arguments are not quoted... >> essentially quotes around path to script file and thats it. Works fine >> now. >> >> "James" <noone@xxxxxx> wrote in message >> news:%23PraFqsOJHA.4776@xxxxxx Quote: >>> Hello, >>> >>> I'm having an issue passing args to a script. I'm getting the error >>> 'There is no script engine for file extenstion .net' >>> >>> I assume the '.net' is coming from the fact that one of my arguments >>> takes a domain name, like: /ntp:my.server.net >>> >>> so calling script like this is causing this error: >>> wscript scriptFile.wsf /arg1:value1 /arg2:value2 /arg3:server.net >>> >>> why doesn't the system know the script file is 'scriptFile.wsf' and the >>> rest are named arguments? >>> >> > |
| My System Specs |
|
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Problem with host script engine | Vista account administration | |||
| Windows Script Host has no script engine for ".js" files | Vista General | |||
| Help with $Args in script | PowerShell | |||
| Passing variables to script | PowerShell | |||
| passing parameters to script (ps1) | PowerShell | |||
