0.4.0 RC build 131 : .msi installation fails ( service can't start )

[pierro78]

here is an extract of the facebook nsclient page :

Pierre PP Thanks so much for the build 131 !
1 février, 18:04

Pierre PP Unfortunately the install won't work (it says the service can't start - there is a 30 seconds timeout in the windows event log). How can I provide you more info ??
1 février, 18:05

NSClient Humm... debug log... presumably you can set Set: settings/log log mask=debug as well as enable FileLogger module to get a log file with infor when it is starting... but was the previous build working? (havent changed anything which should break things I hope)... You can also run nscp test to start the client in debugt mode...
1 février, 19:24

Pierre PP humm ... a problem is that this is happening during the setup so I don't have a .ini file yet ... actually I had one from the build 129 which was seemingly installed OK ...
to make things a little more complex I install nsclient in a non standard directory (c:\esup.new) ... but apparently no new nsclient directory is created there when I try the installation ... so I don't really know how to start nscp test ? should I install from the .zip file instead of the .msi ?
2 février, 12:11

Pierre PP ‎(thanks !)
2 février, 12:11

Pierre PP ps : I tried the regular installation. same issue apparently ...
2 février, 13:22

Pierre PP this is on the computer where I had build129 installed, I suppose I could check on another computer ...
2 février, 13:26

Pierre PP I tried the .msi on a windows 2003 machine and it didn't install either ... it said "service nsclien++ (Win32) (nscp) failed to start. Verify that you have sufficient privileges to start system services" (I am a member of the admin group on this machine)

the .msi installation worked with build 129 though ...

thanks again for your help !

[mickem]

Sorry for not fixing this sooner but I was stuck refactoring the objects API.
It was pretty easy to fix and should be fixed in 134 (out in a bit).

Michael Medin