Did u try after clearing temp and renaming resdb ? did you try running nsrexecd in debug mode ? is there anything on deamon.log ?

But if you try to start the service after Windows start, does it work? There must be a log somewhere in Windows telling why the service did not start, or at least which error the OS got after trying to start the service. Microsoft support or your Windows team probably can track down the issue during Windows startup.

Another option is to uninstall Nw client, remove everything related to Networker from the registry, and try it again. This works sometimes

The service start if we try to start manually without any error. When windows start there is no actual log in event viewer that show something related to that. like I said it's like if the service would not even try to start.

I've tried uninstalling, rebooting and reinstalling the client without any change in the state of the service on faulting servers.

If you have any other idea please feel free to help us.

Jean-Francois

I will try to see if this help, at least if i could find anything in the deamon.log it would help.

I'll be back with you when I have a chance to look into this.

If the service is not even trying to start, as you mentioned above, nothing will be logged in daemon.log, and it sounds like a Windows startup debug would help better... But if there's any error in the client's daemon.log file, then the service started and for any reason stopped, and then it's just a matter of looking into the error message. I believe you can set the nsrexecd service to start in debug mode during Windows startup, allowing more info to be recorded in daemon.log and helping you a lot more.

Well, nothing else comes to my mind at this moment. Let us know if you got any luck with the problem.