NSClient++ Help (#1) - NSClient++ 0.3.1 on NT4 (#158) - Message List

NSClient++ 0.3.1 on NT4

Hello!!

I've installed Nsclient++ 0.3.1 on an Win NT4 (SP6) server:

1.- Unzip the distribution. 2.- Edit NSC:ini 3.- Unzip the pdh.ddl into the same folder as nsclient++.exe 4.- Nsclient++ /install (this message appears: The procedure entry point RtlStringFromGUID could not be located in the dynamic link library ntdll.dll.) 5.- Allow service to interact with desktop. 6.- Nsclient++ /test (I paste the test message:

"Launching test mode.. e \NSClient++.cpp(236) Exception raised: Could not load library: 127: The specified procedure could not be found.

in module: C:\Program Files\NSClient++\modules\CheckSystem.dll

d \NSClient++.cpp(401) Loading plugin: CheckDisk...

d \NSClient++.cpp(401) Loading plugin: Event log Checker....

d \NSClient++.cpp(401) Loading plugin: Check External Scripts...

d \NSClient++.cpp(401) Loading plugin: Helper function...

d \NSClient++.cpp(401) Loading plugin: File logger...

d \NSClient++.cpp(401) Loading plugin: LUAScript...

d \NSClient++.cpp(401) Loading plugin: NRPE client...

d \NRPEClient.cpp(48) humm...

d \NRPEClient.cpp(50) check_other

d \NRPEClient.cpp(78) Added NRPE Client: check_other = host: *, port: 5666, timeout: 10, ssl: 1, buffer_length: 1024

d \NSClient++.cpp(401) Loading plugin: NRPE server...

d \NSClient++.cpp(401) Loading plugin: NSCAAgent...

d \NSCAThread.cpp(45) Autodetected hostname:

d \NSClient++.cpp(401) Loading plugin: NSClient server...

d \NSClient++.cpp(401) Loading plugin: SystemTray...

l \NSClient++.cpp(136) Using settings from: INI-file

l \NSClient++.cpp(137) Enter command to inject or exit to terminate...

d \Socket.h(627) Bound to: 0.0.0.0:5666

d \NSCAThread.cpp(114) Drifting: 0

d \Socket.h(627) Bound to: 0.0.0.0:12489

d \NSClientListener.cpp(143) Data: None&3

d \NSClientListener.cpp(168) Data:

d \NSClient++.cpp(516) Injecting: checkUpTime: nsclient

l \NSClient++.cpp(551) No handler for command: 'checkUpTime'

l \NSCHelper.cpp(223) No handler for command 'checkUpTime'.

Exiting...

d \NSClient++.cpp(375) Unloading plugin: SystemTray...

d \NSClient++.cpp(375) Unloading plugin: NSClient server...

d \Socket.h(661) Socket listener is preparing to shutdown...

d \NSClient++.cpp(375) Unloading plugin: NSCAAgent...

d \NSClient++.cpp(375) Unloading plugin: NRPE server...

d \Socket.h(661) Socket listener is preparing to shutdown...

e \NRPEListener.cpp(150) Exception caught: Error: SSL Context already initalized.

d \NSClient++.cpp(375) Unloading plugin: NRPE client...

d \NSClient++.cpp(375) Unloading plugin: LUAScript...

d \NSClient++.cpp(375) Unloading plugin: File logger...

d \NSClient++.cpp(375) Unloading plugin: Helper function...

d \NSClient++.cpp(375) Unloading plugin: Check External Scripts...

d \NSClient++.cpp(375) Unloading plugin: Event log Checker....

d \NSClient++.cpp(375) Unloading plugin: CheckDisk..."

6.- nsclient++ /start ("The procedure entry point RtlStringFromGUID could not be located in the dynamic link library ntdll.dll.")

In Nagios, all services status are "UNKNOWN" except "C:\ Drive Space" and "NSClient++ Version" that seems to run OK.

How can I fix it??

Thanks!!

  • Message #440

    1, get 0.3.2 (.1 has a memory leak you don't want :)

    Anyways have you installed both PDH and PSAPI?

    MickeM

    From the wiki page:

    NT4 does not come with the PDH library and you need to install that before using NSClient++. PDH can be downloaded from Microsoft: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q284996 and the simplest way to install it is to uncompress it directly into the NSClient++ directory.

    NT4 also (sometimes) lack the PSAPI helper which is available in the "Platform SDK Redistributable: PSAPI for Windows NT" from Microsoft. http://www.microsoft.com/downloads/details.aspx?FamilyID=3d1fbaed-d122-45cf-9d46-1cae384097ac as with the PDH either install in system32 or local NSClient++ directory.

    • Message #441

      Thanks for the replay!! :S Yes i have both libraries pdh.dll and psapi.dll in the NSClient++ directory...

      Any other idea??

      • Message #442

        humm, not as such.

        Try disabling all modules? (and then enabling them one by one and see if you can figure out which module it is)

        If it does not work with all modules disabled something is strange, and I shall investigate, it should work.

        MickeM

        • Message #443

          Ok, it seems that is the CheckSystem.dll the cause of the problem, only if it's enable the error message "The procedure entry point RtlStringFromGUID could not be located in the dynamic link library ntdll.dll." appears.

          It may use somthing of the ntdll.dll that's not in my ntdll.dll version (4.00)?? But i've the SP6 installed and it should be the last dll version for Win NT4 servers...

          • Message #444

            I think that the CheckSystem.dll use a routine (RtlStringFromGUID) present in the ntdll library. But this routine is not present in NT3 and NT4 versions of ntdll.dll (http://jedi-apilib.sourceforge.net/native/NativeList.html).

            • Message #451

              Someone knows how to update my ntdll dynamic library to a version compatible with nsclient++ 0.3.1??? Does exist any other way to solve the problem without restarting the NT4 server??

              Tahnks!!!

              • Message #452

                when I have time I shall check this it should work on nt4 so it looks like there is an error in the last build? (or do you have the same problems with previous versions?)

                Michael Medin

                • Message #453

                  I'm trying with 0.3.0, 0.2.7 and 0.2.5 and i have the same error... :S tomorrow i'll try again with older versions...

                  Thanks!

                  • Message #454

                    humm, if you get the same with 0.3.0 I would guess it is "your NT" that is broken :( Since 0.2.7 and 0.3.0 has been verified on my "testbed" (a standard NT 4 SP6 install).

                    But still I shall verify this again when I have time, it should work on NT4 and if I can remove any dependencies I dont need (and I dont use that API myself) then it would be better, but as I am swamped at the moment I cant really say when I have time to investigate :(

                    MickeM

                    • Message #456

                      Hi!! Thanks a lot for spend your time with this problem!!

                      I've test it in 3 diferent NT4 servers and in all of them i have the same problem with the RtlStringFromGUID routine and the ntdll.dll dynamic library. :S

                      Thanks!!!

                      • Message #466

                        A little more information about this problem:

                        I've installed a new NT4 (v 4.00.1381) + SP6 in a virtual machine with the nsclient++ 0.3.0 and the same error appear...

                        (The procedure entry point RtlStringFromGUID could not be located in the dynamic link library ntdll.dll.)

                        This is the output of the -test command:

                        e \NSClient++.cpp(212) Exception raised: Could not load library: 127: The specified procedure could not be found.

                        in module: C:\Monitorizacion\modules\CheckSystem.dll

                        d \NSClient++.cpp(375) Loading plugin: CheckDisk... d \NSClient++.cpp(375) Loading plugin: Event log Checker.... d \NSClient++.cpp(375) Loading plugin: Helper function... d \NSClient++.cpp(375) Loading plugin: File logger... d \NSClient++.cpp(375) Loading plugin: NRPE server... d \NSClient++.cpp(375) Loading plugin: NSClient server... d \NSClient++.cpp(375) Loading plugin: SystemTray... e \SysTray.cpp(40) SysTray is not installed (or it cannot interact with the desktop) SysTray wont be loaded. Run NSClient++ SysTray install ti change this. l \NSClient++.cpp(123) Using settings from: INI-file l \NSClient++.cpp(124) Enter command to inject or exit to terminate... d \Socket.h(538) Bound to: 0.0.0.0:5666 d \Socket.h(538) Bound to: 0.0.0.0:12489

                        I hope it'll help you to fix this error!

                        Best Regards

                        Mikel

                        • Message #1196

                          Sorry for the delay, I did some googling and it seems to be related to the pdh.dll library. Which version of pdh do you use?

                          Michael Medin

Subscriptions