Hi Jens,
I am successfully running WPKG on x86 and x64, what I do is installing on
shutdown with the client installed on each machine.
Deploying the client is a one time thing, so it is much easier to do.
Installing at shutdown, takes care of running processes, since those are
already killed by Windows, while the user logged off.
---
Stefan
Jens Geile wrote:
Hi,
I've had another look at the "WNetAddConnection2-> Access denied" problem.
Sadly even with WPKG Client 1.3.6 the patch from tanqueatun making WPKG Service
depend on ALG didn't help at all.
Also as I've written before setting dependencies to other services (afd tcpip
ALG Netlogon Dhcp RasMan LmHosts) doesn't seem to affect this problem at all.
I've made it log all actions to a logfile (see below):
This is a working run:
2009-03-27 11:43:35 -> Starting WPKG on startup
2009-03-27 11:43:35 -> Before create shared memory: successfuly done.
2009-03-27 11:43:35 -> Create shared memory: successfuly done.
2009-03-27 11:43:35 -> Set script security context: successfuly done.
2009-03-27 11:43:35 -> Offline mode enabled: successfuly done.
2009-03-27 11:43:35 -> Offline mode: server connecting method selected.
2009-03-27 11:43:36 -> Server connecting: successfuly done.
2009-03-27 11:43:36 -> Network resource required
2009-03-27 11:43:38 -> Network resource: successfuly connected
2009-03-27 11:43:44 -> Script pre action execution: successfuly done
2009-03-27 11:43:44 -> Starting script action execution
2009-03-27 11:43:48 -> Script action execution done.
2009-03-27 11:43:48 -> Network resource: successfuly disconnected
2009-03-27 11:43:51 -> Script execution required restart: successfuly done
2009-03-27 11:43:51 -> WPKG Service: successfuly done
2009-03-27 11:43:51 -> Working done. Perform cleanup.
2009-03-27 11:43:51 -> Cleanup done.
This run didn't work (after the automated restart of the run above):
2009-03-27 11:44:48 -> Starting WPKG on startup
2009-03-27 11:44:48 -> Before create shared memory: successfuly done.
2009-03-27 11:44:48 -> Create shared memory: successfuly done.
2009-03-27 11:44:48 -> Set script security context: successfuly done.
2009-03-27 11:44:48 -> Offline mode enabled: successfuly done.
2009-03-27 11:44:48 -> Offline mode: server connecting method selected.
2009-03-27 11:44:49 -> Server connecting: successfuly done.
2009-03-27 11:44:49 -> Network resource required
2009-03-27 11:45:10 -> WNetAddConnection2-> Zugriff verweigert
2009-03-27 11:45:10 -> Working done. Perform cleanup.
2009-03-27 11:45:10 -> Cleanup done.
As you can see the second run failed even before the pre-action script was run.
:/
I've also checked the status of all the files on the server, disabled all file
locking mechanisms of Samba and so on. No files were locked or anything.
My biggest problem atm is that this bug seems to appear more frequently now
than a couple months ago. And nothing (neither hardware or software) really
changed either. :/ Currently almost every second or at best third run (using my
automated restart script) fails due to this error. :(
I'm completely out of ideas now.
Any ideas/patches/solutions on how to finally fix this nasty POS bug out of the
way would be greatly appreciated.
-
jens
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
