NSClient++ Help (#1) - 64bit Client crashe with Application Error ID 1000 (#712) - Message List
Hi forum,
i have a problem with the client on a Windows Server 2008 (64bit) R2 system. The client run some days without any problem.
Then he crashed with an application error ID 1000. When I try to restart the service, I get the same error again after a minute.
Does anybody have an idea how to fix this problem?
-
Message #2006
If you are feeling daring you could try the new build with features crash reporting. But all in all try to resolve which check causes the error. Some performance counter (for instance HP) are known to cause intermittent problems.
Michael Medin
mickem12/13/10 11:08:07 (3 years ago)-
Message #2018
Hi mickem,
thanks for your reply. Indeed it's a hp server (Proliant DL 360 G6).
Do you have another hint for me?
I installd the newest client version and now get the following errors from nsclient.log:
"2010-12-16 13:59:57: debug:CACHENSClient++.cpp:554: Attempting to start NSCLient++ - 0.3.9.173 2010-12-12 2010-12-16 13:59:57: message:CACHENSClient++.cpp:578: Enabling shared session... 2010-12-16 13:59:57: message:CACHENSClient++.cpp:580: Starting shared session... 2010-12-16 13:59:57: message:CACHEinclude\nsclient_session.hpp:459: Created new master session: channel-server= {Global\NSClientPP_channel_server_write, Global\NSClientPP_channel_server_signal, Global\NSClientPP_channel_server_memory} 2010-12-16 13:59:57: error:CACHEinclude\nsclient_session.hpp:265: Starting session responder for: server 2010-12-16 13:59:57: message:CACHEinclude\nsclient_session.hpp:754: Creating session for: __2__ 2010-12-16 13:59:57: message:CACHENSClient++.cpp:90: Running: C:\Program Files\NSClient++\\nstray.exe 2010-12-16 13:59:57: message:CACHENSClient++.cpp:91: Running: "C:\Program Files\NSClient++\\nstray.exe" -channel __2__ 2010-12-16 13:59:57: message:CACHENSClient++.cpp:158: Started tray in other user session: 2 2010-12-16 13:59:57: message:CACHEmodules\FileLogger\FileLogger.cpp:87: Log path is: C:\Program Files\NSClient++\\nsclient.log 2010-12-16 13:59:57: message:CACHEinclude\nsclient_session.hpp:768: __2__ says hello (was detached)! 2010-12-16 13:59:57: error:CACHEmodules\CheckSystem\PDHCollector.cpp:140: Failed to open performance counters: \(_total)\: PdhAddCounter failed: Das angegebene Objekt wurde nicht auf dem Computer gefunden. (C0000BB8) 2010-12-16 13:59:57: error:CACHEmodules\CheckSystem\PDHCollector.cpp:185: Failed to open performance counters: \Memory\Commit Limit: PdhAddCounter failed: Das angegebene Objekt wurde nicht auf dem Computer gefunden. (C0000BB8) 2010-12-16 13:59:57: error:CACHEmodules\CheckSystem\PDHCollector.cpp:219: No performance counters were found we will not wait for the end instead... 2010-12-16 13:59:57: error:modules\CheckSystem\PDHCollector.cpp:334: Failed to get MEM_CMT value: <UN ATTACHED>: No value has been collected yet 2010-12-16 14:03:10: message:modules\CheckSystem\CheckSystem.cpp:799: Failed to open process: 4: 2010-12-16 14:03:10: error:modules\CheckSystem\CheckSystem.cpp:796: Unhandled exception describing PID: 4: Failed to open process: 4:"The service NSClient++ crashes after last error message with the message I mentioned in my posting before.
bruce_leeroy12/16/10 14:40:53 (3 years ago)-
Message #2019
Humm...
First off I would generally NOT use the shared_Session if I have problems as it is known to have a lot of strange issues.
The second thing I notice is that counteres are not detected and seems it is not "understood" which I guess is worse. THat i need to fix.
Last log refers to a checkProceState which should not crash as well.
So all in all this ia bit od.
Usually when it is HP problems it is related to CHECKING specific HP counters (hardware stuff) not just running on a hP machine.
I shall see if I can digup a localized windows and see if there is som glitch there.
Michael Medin
mickem12/16/10 19:29:03 (3 years ago)
-
-








