/build/static/layout/Breadcrumb_cap_w.png

Kbox1100 Scripting Issue

 

Hi,

My colleague and I are having trouble running scripts though KBOX1100. We can see the batch file gets downloaded onto the local computer but doesn’t want to run. If we run the downloaded batch file manual, the scripts starts to run, just not prompted with the KBOX agent. We’ve tried running the script with our domain admin credentials and as a local user and it doesn’t work. I’ve attached the klaunch log which gives this error “Failed to convert the stdout/stderr content in  to UTF-8 using code page 850”. We’ve double checked that the batch file is encoded as “UTF-8” but we still get the same error. Are you able to help with this issue?

 

Find below copy of the klaunch log file.

 

Thank you ,

 

[Tue Oct 22 15:00:31 2013] KLaunchProcess: KLaunchArgs error launching '. -nowait -show:' (87) The parameter is incorrect.

 

 

[Tue Oct 22 15:00:31 2013] kbot[278:1382414368] @ 2013-10-22T15:00:31 (output) Error creating process: \ : (87) The parameter is incorrect.

 


kbot[278:1382414368] @ 2013-10-22T15:00:31 (output) Error Code: 87

kbot[278:1382414368] @ 2013-10-22T15:00:31 (output) Status Code: 0

runkbot : Failed to create kbot process: (87) The parameter is incorrect.

 

 

[Tue Oct 22 15:00:31 2013] kbot[278:1382414368] @ 2013-10-22T15:00:31 (status) FINISH (in state 'verification_failed')

Uploading Log file [C:\Users\itadmin\AppData\Local\Temp\dkl4EF5.tmp]


[Tue Oct 22 15:00:31 2013] DOWNLOADFILE: CURL DEBUG INFO --->>> START <<<---


[Tue Oct 22 15:00:32 2013] DOWNLOADFILE: CURL DEBUG INFO --->>> END <<<---


[Tue Oct 22 15:00:32 2013] DownloadFile: Downloaded C:\Users\itadmin\AppData\Local\Temp\dkl529E.tmp from http://kbox1100.saintaug.nsw.edu.au/service/kbot_service_notsoap.php?METHOD=getuploadpath&KUID=D85B9F5E-749E-4D88-AC74-F1CAE5B5669A&FILENAME=KBOT_LOG.txt Download speed: 3396.000000 bytes/second


[Tue Oct 22 15:00:32 2013] UPLOADFILE: CURL DEBUG INFO --->>> START <<<---


[Tue Oct 22 15:00:32 2013] UPLOADFILE: CURL DEBUG INFO --->>> END <<<---


[Tue Oct 22 15:00:32 2013] UploadFile: Uploaded to http://kbox1100.saintaug.nsw.edu.au/service/kbot_upload.php?machineId=3895&filename=KBOT_LOG.txt&checksum=4e56b6191dd0e26308d867c524c05a1d&mac=D85B9F5E-749E-4D88-AC74-F1CAE5B5669A Upload speed: 0.000000 bytes/second


[Tue Oct 22 15:00:32 2013] Cleaning up log file [C:\Users\itadmin\AppData\Local\Temp\dkl4EF5.tmp]

 


[Tue Oct 22 15:00:32 2013] runkbot    ----- Exiting runkbot.exe -----


[Tue Oct 22 15:00:32 2013] KLaunch    End of ExecuteThread
[Tue Oct 22 15:00:32 2013] KLaunch    Local command returned 0(0x0)
[Tue Oct 22 15:00:32 2013] Failed to convert the stdout/stderr content in  to UTF-8 using code page 850
[Tue Oct 22 15:00:32 2013] KLaunch    ----- Exiting KLaunch.exe (Error 0, Status 0)-----

 

 

 


4 Comments   [ + ] Show comments
  • Does that command -nowait -show work if you just run it in a command window? It seems to be failing on those arguments. - petelanglois 11 years ago
  • can you post the batch file - SMal.tmcc 11 years ago
  • Hi SMAL.tmcc

    find below script.

    setlocal

    REM *********************************************************************
    REM Environment customization begins here. Modify variables below.
    REM *********************************************************************

    REM Get ProductName from the Office product's core Setup.xml file, and then add "office15." as a prefix.
    set ProductName=Office15.PROPLUS

    REM Set DeployServer to a network-accessible location containing the Office source files.
    set DeployServer=\\ServerName\Software\MSOffice2013\MSOffice2013

    REM Set ConfigFile to the configuration file to be used for deployment (required)
    set ConfigFile=\\ServerName\Software\MSOffice2013\MSOffice2013\ProPlus.WW\config.xml

    REM Set LogLocation to a central directory to collect log files.
    set LogLocation=\\ServerName\Software\MSOffice2013\MSOffice2013\LogFiles\

    REM *********************************************************************
    REM Deployment code begins here. Do not modify anything below this line.
    REM *********************************************************************

    :CheckOS
    IF EXIST "%PROGRAMFILES(X86)%" (GOTO 64BIT) ELSE (GOTO 32BIT)

    :64BIT
    Echo 64-bit
    Copy "\\ServerName\software\MSOffice2013\MSOffice2013\SilentUninstallconfigs.xml" "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\"
    "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall PROPLUS /config SilentUninstallConfigs.xml

    GOTO Next

    :32BIT
    echo 32-bit...
    Copy "\\ServerName\software\MSOffice2013\MSOffice2013\SilentUninstallconfigs.xml" "C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\"
    "C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall PROPLUS /config SilentUninstallConfigs.xml

    GOTO Next

    :Next
    IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)

    REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
    :ARP64
    reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
    if NOT %errorlevel%==1 (goto End)

    REM Check for 32 and 64 bit versions of Office 2013 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS)
    :ARP86
    reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
    if %errorlevel%==1 (goto DeployOffice) else (goto End)

    REM If 1 returned, the product was not found. Run setup here.
    :DeployOffice
    start /wait %DeployServer%\setup.exe /adminfile %DeployServer%\updates\staff.MSP
    echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

    REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
    :End

    Endlocal - mgrnovic 11 years ago
    • only thing I can think of is it does like not some command in your config.xml or
      msp file. and that is where the passing parameter errors are coming from.

      you might try running this without the start /wait in front of the setup.exe or put quotes around the command after the start /wait "%DeployServer%\setup.exe /adminfile %DeployServer%\updates\staff.MSP" - SMal.tmcc 11 years ago
  • SMal.tmcc

    Thanks for your reply. We're just about to add the quotes and double check the xml and msp file. Would you by any chance know why the batch file could run manually once it's been copied to the computer with KBOX but not run with Klaunch? - mgrnovic 11 years ago
    • the real difference is it runs as system with kace vs the user manually. That could also be a problem unless that share is open to everyone even non domain users. you may try using a net use command to map a drive and calling the install from the drive letter. then deleting the mapping at the end.

      net use i: \\servername\software passsword /user:doamin\user

      REM Set DeployServer to a network-accessible location containing the Office source files.
      set DeployServer=i:\MSOffice2013\MSOffice2013

      REM Set ConfigFile to the configuration file to be used for deployment (required)
      set ConfigFile=i:\Office2013\MSOffice2013\ProPlus.WW\config.xml

      REM Set LogLocation to a central directory to collect log files.
      set LogLocation=i:\MSOffice2013\MSOffice2013\LogFiles\ - SMal.tmcc 11 years ago
    • When I ran into a weird install error with office 2013 it was in the msp we created. - SMal.tmcc 11 years ago

Answers (0)

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ