vbscripts won't run in FBA

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've been searching for days. I've seen similar posts, but they are never
resolved.
Please help!

Okay -- I am unable to run any vbscript during any phase with FBA. The
scripts run fine from the command shell after login. I've even created a
script called test.vbs that contains a single line -- WScript.Echo "Hello!"

I've tried different paths, different commands (cscript.exe & WScript.exe).
All I ever get in the FBALOG.txt is:

[FBALaunch] C:\WINDOWS\system32\cscript.exe C:\WINDOWS\system32\test.vbs
(ExitCode: 0x1)

The relevent FBA generic command resource settings are (one of the attempts,
anyway):
Arguments: %11%\test.vbs
FilePath: %11%\cscript.exe
Flags: 0
Phase: 8501
Reboot: FALSE
Timeout: 0

Again -- the scripts all run fine from the command line. I always run them
in a phase after Windows Scripting is available.

I'm using SP2 and all VBSFile registry settings are correct (no missing %1).

When FBA attempts to run the script using cscript.exe, a command window
flashes open and immediately closes -- with no text whatsoever -- so I know
it's at least trying.

I even un-installed XP Embedded (yep, the whole thing -- database and all),
re-installed it and re-imported all my components.

I'm really at a loss.

Any help is greatly appreciated,

JBL
 
Hi JBL

Try to use the "%systemroot%/system32" variable instead of
"%11%" or "%systemroot%" instead of "%10%".

I had the same problem to run a simple batch file until
I changed thees kind of variables.

--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
It didn't like that one bit. Seems to not handle the % when its not a TD
variable. FBALOG.txt showed:

[FBALaunch] C:\WINDOWS\system32\wscript.exe ?ystemroot\system32\test.vbs
(ExitCode: 0x1)

I'll try some different escape sequences, but it seems strange that
(according to FBALOG.txt) my previous %11% was being correctly resolved to
C:\WINDOWS\System32. Or am I missing the point?

Thanks for the quick response!


--

-JBL


Martin Grossen said:
Hi JBL

Try to use the "%systemroot%/system32" variable instead of
"%11%" or "%systemroot%" instead of "%10%".

I had the same problem to run a simple batch file until
I changed thees kind of variables.

--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

JBL said:
I've been searching for days. I've seen similar posts, but they are never
resolved.
Please help!

Okay -- I am unable to run any vbscript during any phase with FBA. The
scripts run fine from the command shell after login. I've even created a
script called test.vbs that contains a single line -- WScript.Echo
"Hello!"

I've tried different paths, different commands (cscript.exe &
WScript.exe).
All I ever get in the FBALOG.txt is:

[FBALaunch] C:\WINDOWS\system32\cscript.exe C:\WINDOWS\system32\test.vbs
(ExitCode: 0x1)

The relevent FBA generic command resource settings are (one of the
attempts,
anyway):
Arguments: %11%\test.vbs
FilePath: %11%\cscript.exe
Flags: 0
Phase: 8501
Reboot: FALSE
Timeout: 0

Again -- the scripts all run fine from the command line. I always run
them
in a phase after Windows Scripting is available.

I'm using SP2 and all VBSFile registry settings are correct (no missing
%1).

When FBA attempts to run the script using cscript.exe, a command window
flashes open and immediately closes -- with no text whatsoever -- so I
know
it's at least trying.

I even un-installed XP Embedded (yep, the whole thing -- database and
all),
re-installed it and re-imported all my components.

I'm really at a loss.

Any help is greatly appreciated,

JBL
Click to expand...
Click to expand...
 
Just noticed these entries in FBALOG.txt. Not sure if it's related -- I've
been scrolling straight to the script related section and completely missed
it!

17:33:39 PM - [FBAApplySecurityStringToRegKey] RegSetKeySecurity Failed!
Error: 0x6

17:33:39 PM - [FBAReplaceSecurityInRegistry]
FBAApplySecurityStringToRegKey(009) #1 Failed!
 
Never mind about the security errors -- I found this on MSDN (
http://msdn.microsoft.com/library/d...icrosoftWindowsXPEmbeddedWithServicePack2.asp )

Release Notes for Microsoft Windows XP Embedded with Service Pack 2

The FBA log will show a harmless error if the Performance Counter
Configuration component is included in a runtime. The log text is as follows
and can be disregarded:

[FBAApplySecurityStringToRegKey] RegSetKeySecurity Failed! Error: 0x6
[FBAReplaceSecurityInRegistry] FBAApplySecurityStringToRegKey(009) #1 Failed!


--

-JBL


JBL said:
Just noticed these entries in FBALOG.txt. Not sure if it's related -- I've
been scrolling straight to the script related section and completely missed
it!

17:33:39 PM - [FBAApplySecurityStringToRegKey] RegSetKeySecurity Failed!
Error: 0x6

17:33:39 PM - [FBAReplaceSecurityInRegistry]
FBAApplySecurityStringToRegKey(009) #1 Failed!


--

-JBL


JBL said:
I've been searching for days. I've seen similar posts, but they are never
resolved.
Please help!

Okay -- I am unable to run any vbscript during any phase with FBA. The
scripts run fine from the command shell after login. I've even created a
script called test.vbs that contains a single line -- WScript.Echo "Hello!"

I've tried different paths, different commands (cscript.exe & WScript.exe).
All I ever get in the FBALOG.txt is:

[FBALaunch] C:\WINDOWS\system32\cscript.exe C:\WINDOWS\system32\test.vbs
(ExitCode: 0x1)

The relevent FBA generic command resource settings are (one of the attempts,
anyway):
Arguments: %11%\test.vbs
FilePath: %11%\cscript.exe
Flags: 0
Phase: 8501
Reboot: FALSE
Timeout: 0

Again -- the scripts all run fine from the command line. I always run them
in a phase after Windows Scripting is available.

I'm using SP2 and all VBSFile registry settings are correct (no missing %1).

When FBA attempts to run the script using cscript.exe, a command window
flashes open and immediately closes -- with no text whatsoever -- so I know
it's at least trying.

I even un-installed XP Embedded (yep, the whole thing -- database and all),
re-installed it and re-imported all my components.

I'm really at a loss.

Any help is greatly appreciated,

JBL
Click to expand...
Click to expand...
 
Okay -- I am unable to run any vbscript during any phase with FBA. The
scripts run fine from the command shell after login. I've even created a
script called test.vbs that contains a single line -- WScript.Echo "Hello!"
Click to expand...

The vbscript runtime has to be installed before you can run scripts, and
one of the things FBA does is install such things - so maybe you're trying
to early in the FBA process.

Can you see if it works very late in FBA, with a reboot before the script
test?
 
As I said in my original post:

"Again -- the scripts all run fine from the command line. I always run them
in a phase after Windows Scripting is available."

I know my example used 8501, but I've tried it in every phase -- even as a
RunOnce request -- with no luck whatsoever.

Any other thoughts?
 
JBL,

Have you tried launching the command shell (cmd.exe) in FBA Generic command
and then launching your scripts as one of the arguments- something like:
Arguments: %11%\test.vbs
FilePath: %11%\cmd.exe
Flags: 0
Phase: 8501
Reboot: FALSE
Timeout: 0
 
Back
Top