[wpkg-users] reboot problem

[Tomasz Chmielewski]

Your mail client wraps the lines in a funny way. Also, try to keep one 
topic per thread, i.e. "reboot problem" for problems with rebooting, and 
"logging problem" for problems with logging.


Anyway - if wpkg.js reboots just fine, it means there is some problem 
with WPKG Client.

Does it affect only this machine, or all other machines in your network, 
too? Is it a clean install, or was this workstation installed long time 
ago etc.?

It would be easiest if you could give me remote access to that machine. 
If you can't, I'd try the following:


1.
Perhaps WPKG Client rebooted several times in a row (wrong installer 
which wants to reboot the machine each time?). What's the value of 
HKLM\SOFTWARE\WPKG.ORG\Restart\Count?
Although in that case, you should see it in the Event Log.


2.
- Log in as Administrator
- set "Show GUI", and /debug for wpkg.js
- run cmd.exe, and there: net start wpkgservice
- did it reboot?

Also, would be useful to combine it with some debugging logging from 
wpkg.js - see below.


3.
Instead of wpkg.js, use reboot.js script (it's just this one line):

WScript.Quit(3010)

It just exits with code 3010, so WPKG Client should reboot.


4.
Are you sure you're using WPKG Client 1.2-rc5, and not any older version 
(1.0-rcX)? There was a bug with rebooting there - it would not reboot 
unless a user starting WPKG service was in Administrator's group (so, 
SYSTEM would not reboot it). Do you have a "test settings" button? It 
was added in 1.2-rcX. Are there any errors if you test settings?



#######################

As for logging, try to use two backslashes, i.e.:

  <param name='log_file_path' value='\\\\branchdc\\wpkg-xml' />


This one won't work:

  <param name='log_file_path' value='\\branchdc\wpkg-xml' />



-- 
Tomasz Chmielewski