On 02/19/2013 04:49 AM, David Petterson wrote: > On 2013-02-18 23:14, Stefan Pendl wrote: >> Am 18.02.2013 19:16, schrieb David Petterson: >>> On 2013-02-15 16:29, Marco Gaiarin wrote: >>>> Mandi! Kühne Jörg HCARE-ZLM >>>> In chel di` si favelave... >>>> >>>>> We use the WPKG Client version 1.3.6. Since our network replacement >>>>> to 1GB we >>>>> use to have problems with our software distribution. Normally WPKG >>>>> works fine >>>>> when we kick off it manually but during restart of our hosts >>>>> (several) the >>>>> WPKG-Service (start-type: auto mode) do not working properly. Maybe >>>>> it has >>>>> something to do with our WPKG settings, see below: >>>> >>>> 1.3.6 have known trouble in this aspects, so please move to the latest >>>> (1.3.14) and retry. >>>> >>>> More or less, the trouble came from WPKG Client service not correctly >>>> depending on the network setup, so starts before the network came in. >>>> And fail. >>>> >>> >>> I have the same problem with 1.3.14. On "some" computers, WPKG Client >>> will start before the network causing the service to fail startup. >>> "WNetAddConnection2-> The network path was not found" >>> >>> A fix for this is most welcome! >>> >>> >> >> There have been some fixes posted, so you just need to search for them. >> >> One was to introduce a dependency on the network service, if I remember >> correctly. > > None of the "fixes" I found so far works. I have added all network > related services that I could find as dependants and it still wont work. > I am currently testing a scheduled start (on system start) that seem to > work. > Hi David, I had the same issue, and I used the setting "WPKG execution on failure" to solve my issue. ---snip---- On 04/10/2012 04:06 PM, John Danks wrote: > I use the setting in WPKG Client called "WPKG execution on failure" > repeat count set to 3 seems to be enough. ---snip--- Best Regards, Paul Griffith |