Windows Script Host error

[Guest]

Every time I boot my notebook (WinXP Pro) I receive:
"Windows Script Host
Script: C:\WINNT\system32\deployment\asset\bin\acsassetlaunch.wsf
Line: 13
Char: 3
Error: Wrong number of arguments or invalid property assignment: 'logError'
Code: 800A01C2
Source: Microsoft VBScript runtime error"

Can anyone advise me on eliminating this error? Thanks!

 

[David Candy]

Well paste lines 1 - 13

 

[Guest]

Okay, here are the first 13 lines:
<job id='acsassetlaunch'>
<script language='vbs' src='common.vbs'></script>
<script language='vbs'>


binPath = registryValue("basePath") & "bin\"

Set process = GetObject( "winmgmts:Win32_Process" )

result = process.Create ("wscript acsdaemon.wsf",binPath ,null,processid)

if err <>0 then
logError "Error launching daemon", Err.Description, "0x" & Hex(Err.Number)

Thanks!

 

[David Candy]

My reference doesn't show logerror as a valid command. However logevent is. However it's still wrong for that as well. What I do, and maybe the author did too, is to wrap stuff like this in a function. Is there a line like this else where in the file. What is this file.

Sub LogError Param1, Param2, Param3 (parameter is a placeholder - I can't guess what he called them) or

Function LogError(Param1, Param2, Param3)

If it's not too big include the whole file.

 

[Guest]

David,
Here is the whole file:

<job id='acsassetlaunch'>
<script language='vbs' src='common.vbs'></script>
<script language='vbs'>


binPath = registryValue("basePath") & "bin\"

Set process = GetObject( "winmgmts:Win32_Process" )

result = process.Create ("wscript acsdaemon.wsf",binPath ,null,processid)

if err <>0 then
logError "Error launching daemon", Err.Description, "0x" & Hex(Err.Number)
end if

updateRegistry "PID", processid

</script>
</job>

[I just acquired this notebook from an employee of American Cancer Society
(ACS), and it was set up to connect to their network.]

Thanks!

 

[David Candy]

Look for a file called 'common.vbs'. And paste that as well.

--
----------------------------------------------------------

David,
Here is the whole file:

<job id='acsassetlaunch'>
<script language='vbs' src='common.vbs'></script>
<script language='vbs'>


binPath = registryValue("basePath") & "bin\"

Set process = GetObject( "winmgmts:Win32_Process" )

result = process.Create ("wscript acsdaemon.wsf",binPath ,null,processid)

if err <>0 then
logError "Error launching daemon", Err.Description, "0x" & Hex(Err.Number)
end if

updateRegistry "PID", processid

</script>
</job>

[I just acquired this notebook from an employee of American Cancer Society
(ACS), and it was set up to connect to their network.]

Thanks!

My reference doesn't show logerror as a valid command. However logevent is. However it's still wrong for that as well. What I do, and maybe the author did too, is to wrap stuff like this in a function. Is there a line like this else where in the file. What is this file.

Sub LogError Param1, Param2, Param3 (parameter is a placeholder - I can't guess what he called them) or

Function LogError(Param1, Param2, Param3)

If it's not too big include the whole file.