[wpkg-users] [Bug 172] WNetAddConnection2-> No network provider accepted the given network path.

2009-12-02 Thread bugzilla-daemon
http://bugzilla.wpkg.org/show_bug.cgi?id=172 --- Comment #8 from Jason Oster 2009-12-02 21:27:45 --- That's correct. The service starts, launches cscript, and begins updating all installed packages. It also spews all of its success messages to the Event Log. :) Just that [on some of thes

[wpkg-users] [Bug 172] WNetAddConnection2-> No network provider accepted the given network path.

2009-12-02 Thread bugzilla-daemon
http://bugzilla.wpkg.org/show_bug.cgi?id=172 --- Comment #7 from Tomasz Chmielewski 2009-12-02 21:08:53 --- Jason - I assume that when the PC boots up, and you do "net start wpkgservice", it starts correctly? -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- Y

[wpkg-users] [Bug 172] WNetAddConnection2-> No network provider accepted the given network path.

2009-12-02 Thread bugzilla-daemon
http://bugzilla.wpkg.org/show_bug.cgi?id=172 --- Comment #6 from Jason Oster 2009-12-02 20:55:28 --- No such luck with either suggestion: 1) Disable Flow Control on NIC 2) Add Terminal Services dependency to WPKG service After making the change and rebooting the system, packages still have

[wpkg-users] [Bug 172] WNetAddConnection2-> No network provider accepted the given network path.

2009-12-02 Thread bugzilla-daemon
http://bugzilla.wpkg.org/show_bug.cgi?id=172 --- Comment #5 from Jason Oster 2009-12-02 17:03:05 --- NLA (Network Location Awareness) is supposed to handle reporting network status to the OS. I'm not certain how the service gathers information about the status. But if the driver is explicitl

[wpkg-users] [Bug 172] WNetAddConnection2-> No network provider accepted the given network path.

2009-12-02 Thread bugzilla-daemon
http://bugzilla.wpkg.org/show_bug.cgi?id=172 --- Comment #4 from Tomasz Chmielewski 2009-12-02 16:57:43 --- If you have Terminal Services disabled, it won't work. For me, it fixed this issue on all laptops I had this problem (well, it's a workaround, really). I suppose some network driver

[wpkg-users] [Bug 172] WNetAddConnection2-> No network provider accepted the given network path.

2009-12-02 Thread bugzilla-daemon
http://bugzilla.wpkg.org/show_bug.cgi?id=172 Jason Oster changed: What|Removed |Added CC||parasy...@gmail.com --- Comment #3 from Jaso

[wpkg-users] [Bug 172] WNetAddConnection2-> No network provider accepted the given network path.

2009-12-02 Thread bugzilla-daemon
http://bugzilla.wpkg.org/show_bug.cgi?id=172 --- Comment #2 from Tomasz Chmielewski 2009-12-02 16:01:33 --- For all you having problems with WPKG service starting on some machines (especially laptops) - could you try this: sc config wpkgservice depend= TermService -- Configure bugmail: h

Re: [wpkg-users] Strange side effect ++

2009-12-02 Thread Chris Wilcox
> Hello all, > > in my organisation, I encounter a strange problem on PCs where MS Office > 2000 is installed. > Everytime WPKG starts a MSI installation, it triggers an update of Office. > > There is no problem on PCs without MS Office 2000 or with other versions > of MS Office. > > Installi

[wpkg-users] Strange side effect ++

2009-12-02 Thread Johannes . Brix
Hello all, in my organisation, I encounter a strange problem on PCs where MS Office 2000 is installed. Everytime WPKG starts a MSI installation, it triggers an update of Office. There is no problem on PCs without MS Office 2000 or with other versions of MS Office. Installing MSI packages by ha

[wpkg-users] Strange side effect

2009-12-02 Thread Johannes . Brix
Hello all, in my organisation, I encounter a strange problem on PCs where MS Office 2000 is installed. Everytime WPKG starts a MSI installation, it triggers an update of Office. There is no problem on PCs without MS Office 2000 or with other versions of MS Office. Has anybody seen this problem