NSClient++ Help (#1) - Cannot install SystemTray (#14) - Message List

Cannot install SystemTray

NSClient++ installs, but not the System Tray. I am using the command listed in the documentation.

C:\NSClient++>NSClient++ SystemTray install e .\NSClient++.cpp(239) Module not found.

  • Message #21

    I got the same behaviour to day: W2k3 server

    • Message #493

      I had similar problems .. looks like it installs but the icon in the tray doesn't stay.

      • Message #496

        system tray has problems on vista an possibly on w2k3 as well.

        (due to privilege changes)

        MickeM

  • Message #24

    I also got this error on Win2k3 sp1.

    After enabling SysTray.dll in the "Modules" section of NSC.ini, I received the following messages attempting to install it:

    C:\nagios_client>NSClient++ SystemTray install 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 .\SysTray.cpp(63) SystemTray is now able to run as the SERVICE_INTERACTIVE_PROCESS flag has been set.

    C:\nagios_client>NSClient++ SysTray install e .\NSClient++.cpp(239) Module not found. Failed to terminate thread: SysTray... MAJOR ERROR: Could not unload thread... e .\SysTray.cpp(53) Could not exit the thread, memory leak and potential corruption may be the result...

    Then I saw the sytem tray icon show up! I am just starting to install this for a new Nagios server so I cannot speak to its functionality, yet.

    A subsequent head-scratching session brought me back to attempting to install it again (install-or-die mentality) and I received this message:

    C:\nagios_client>NSClient++ SystemTray install l .\SysTray.cpp(63) SystemTray is now able to run as the SERVICE_INTERACTIVE_PROCESS flag has been set.

    starting NSClient++ did not produce the tray icon...

    Also, poking around in the source code, it appears that "bool SysTray::loadModule()" in SysTray.cpp cannot be false... Note: I am by no means a programmer so pls forgive me if I am barking up the wrong tree.

    I hope this info helps. -d4rthpimp

    • Message #40
      • Message #111

        I tried that but it did not work for me! I still have no system tray icon, is anything supposed to happen after you do step 5? cause i dont know how to get the Service Manager. i figured it would be in the system tray.

        • Message #112

          I take that back, wow i feel stupid! but i finished doing everything it asked and still no System Tray Icon. HELP!

        • Message #113

          I take that back, wow i feel stupid! but i finished doing everything it asked and still no System Tray Icon. HELP!

          • Message #114

            To get the system tray you do: 1, tun the following command:

            nsclient++ -install
            

            2, run the following command:

            nsclient++ -noboot SysTray install
            

            3, enable the module in the NSC.ini-file.

            4, start it as usual i.e.

            nsclient++ -start
            
            • Message #545

              hi i had a same problem now it's installed (systray) thanks buddy, anil gosai BTPL(T.S.E)

            • Message #168

              Hi,

              Im having similar problems, I followed all the documentation. The icon appears in the systray and disappears.

              Any help would be greatly appreciated

              D:\>nsclient++ -noboot SysTray install

              l \NSClient++.cpp(299) Module was not loaded, attempt to load it
              e \SysTray.cpp(40) SysTray is not installed (or it cannot interact with the desk top) SysTray wont be loaded. Run NSClient++ SysTray install ti change this.
              l \SysTray.cpp(63) SystemTray is now able to run as the  SERVICE_INTERACTIVE_PROCESS flag has been set.
              
              • Message #169

                that looks right... The "message" you get is when systray boots it does not yet know it is about to change things, but then you get the "ok, installed" message so if you start it afterwards it should work...

                does the icon not show afterwards?

                MickeM

    • Message #1019

      I've tried everything on this thread and still no dice. After nsclient++ -noboot SysTray install the tray icon shows up and then promptly disappears.

      So, I did some work in the NSC.ini and got it to work by:

      1) uninstall nsclient++: nsclient++ -uninstall 2) edit nsc.ini (version 0.35)

      Set all on: FileLogger.dll CheckSystem.dll CheckDisk.dll NSClientListener.dll NRPEListener.dll SysTray.dll CheckEventLog.dll CheckHelpers.dll

      shared_session=0 file=nsclient.log (then touch/create empty file in exe folder) root_folder=exe

      Then

      C:\Program Files\NSClient++>nsclient++ -install C:\Program Files\NSClient++>nsclient++ -noboot SysTray install l \NSClient++.cpp(370) Attempting to start NSCLient++ - 0.3.5.2 2008-09-24 l \NSClient++.cpp(388) Enabling shared session... l \NSClient++.cpp(407) Attaching to shared session... e \NSClient++.cpp(414) No session was found cant attach! e \NSClient++.cpp(416) Session is: _attached_632_ l \NSClient++.cpp(476) NSCLient++ - 0.3.5.2 2008-09-24 Started! d \NSClient++.cpp(671) Loading plugin: SystemTray... e \SysTray.cpp(46) You have enabled shared session, systray module will not load ... SystemTray is now able to run as the SERVICE_INTERACTIVE_PROCESS flag has been s et. l \NSClient++.cpp(530) Attempting to stop NSCLient++ - 0.3.5.2 2008-09-24 d \NSClient++.cpp(541) Stopping: COM helper d \NSClient++.cpp(549) Stopping: Socket Helpers d \NSClient++.cpp(557) Stopping: Settings instance d \NSClient++.cpp(561) Stopping: shared client l \NSClient++.cpp(589) NSCLient++ - 0.3.5.2 2008-09-24 Stopped succcessfully

      C:\Program Files\NSClient++>nsclient++ start

      Seems to work for me after that.

      Windows 2003 32-bit R2 Standard Server w/ Service Pack 2

      • Message #1020

        On "modern windows" there is an experimental system tray support in the form of "shared sessions". Regular system tray wont work on "modern windows" (ie. vista, wk3(?), wk8, etc etc) as they do not use "session 0".

        So all you do on "moderna windows" is:

        [modules]
        ;SysTray.dll <-- notece this is commented out!
        [Settings]
        shared_session=1
        

        BUT this is experimental and might cause problems so be ware.

        MickeM

    • Message #277

      I have the same problem, no icon i get this additionnal message too in the log :

      2008-03-12 11:53:22: error:d:\Documents and Settings\mickem\Mina dokument\Visual Studio 2005\Projects\NSCP\trunk\include\Socket.h:658: Socket did not start properly, we will now do nothing...

      mickem ??? i think there is something wrong somewhere !!!

      I also got this error on Win2k3 sp1.

      After enabling SysTray.dll in the "Modules" section of NSC.ini, I received the following messages attempting to install it:

      C:\nagios_client>NSClient++ SystemTray install 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 .\SysTray.cpp(63) SystemTray is now able to run as the SERVICE_INTERACTIVE_PROCESS flag has been set.

      C:\nagios_client>NSClient++ SysTray install e .\NSClient++.cpp(239) Module not found. Failed to terminate thread: SysTray... MAJOR ERROR: Could not unload thread... e .\SysTray.cpp(53) Could not exit the thread, memory leak and potential corruption may be the result...

      Then I saw the sytem tray icon show up! I am just starting to install this for a new Nagios server so I cannot speak to its functionality, yet.

      A subsequent head-scratching session brought me back to attempting to install it again (install-or-die mentality) and I received this message:

      C:\nagios_client>NSClient++ SystemTray install l .\SysTray.cpp(63) SystemTray is now able to run as the SERVICE_INTERACTIVE_PROCESS flag has been set.

      starting NSClient++ did not produce the tray icon...

      Also, poking around in the source code, it appears that "bool SysTray::loadModule()" in SysTray.cpp cannot be false... Note: I am by no means a programmer so pls forgive me if I am barking up the wrong tree.

      I hope this info helps. -d4rthpimp

      • Message #278

        Could you post:

        1. version of NSCP you are using.
        2. full log from:
          • NSClient++ -noboot SysTray install
          • NSClient++ /test
        3. relevant section in nsc.ini

        MickeM

        • Message #828

          Hello, I have this error on nsclient.log :

          2008-10-17 10:04:36: error:d:\Documents and Settings\mickem\Mina dokument\Visual Studio 2005\Projects\NSCP\trunk\include\Socket.h:658: Socket did not start properly, we will now do nothing...

          And the result : Current Status:

          CRITICAL

          (for 0d 0h 12m 9s)

          Status Information: (Service Check Timed Out)

          idea ?

          • Message #832

            is there anything else in the log? The socket failed to start and hopefully it should have told you why a few lines up...

            MickeM

            • Message #842

              here is the complete log :

              2008-10-17 10:04:36: message:.\FileLogger.cpp:58: Starting to log for: NSClient++ - 0.3.1.12 2008-03-11

              2008-10-17 10:04:36: error:d:\Documents and Settings\mickem\Mina dokument\Visual Studio 2005\Projects\NSCP\trunk\include\Socket.h:635: bind failed: 10048: Une seule utilisation de chaque adresse de socket (protocole/adresse réseau/port) est habituellement autorisée.

              2008-10-17 10:04:36: error:d:\Documents and Settings\mickem\Mina dokument\Visual Studio 2005\Projects\NSCP\trunk\include\Socket.h:635: bind failed: 10048: Une seule utilisation de chaque adresse de socket (protocole/adresse réseau/port) est habituellement autorisée.

              2008-10-17 10:04:36: error:d:\Documents and Settings\mickem\Mina dokument\Visual Studio 2005\Projects\NSCP\trunk\include\Socket.h:658: Socket did not start properly, we will now do nothing...

              2008-10-17 10:04:36: error:d:\Documents and Settings\mickem\Mina dokument\Visual Studio 2005\Projects\NSCP\trunk\include\Socket.h:658: Socket did not start properly, we will now do nothing...

              I don't find more explanation

              • Message #849

                and there is your "problem":

                2008-10-17 10:04:36: error:d:\Documents and Settings\mickem\Mina dokument\Visual Studio 2005\Projects\NSCP\trunk\include\Socket.h:635: bind failed: 10048: Une seule utilisation de chaque adresse de socket (protocole/adresse réseau/port) est habituellement autorisée.
                

                Now my Spanish(?) is not very good (I can pretty much only do "una cerveza porfavor") but I am guessing it says: "cant bind, the port is already used by someone else". Which translates to you are most likely already running another instance of NSClient++ on the computer...

                (humm, on second though, I am leaning a bit more on it being French maybe?)

                Michael Medin

                • Message #850

                  It's ok, the script had error. The socket was never free.

                  thanks for your help

        • Message #505

          Windows Server 2003 R2 SP2

          • installation with

          nsclient++ -install nsclient++ -noboot SysTray install

          • SysTray icon APPEARS
          • SysTray icon DISAPPEARS on mouse over
          • ... BUT, it works perfectly in test mode nsclient++ /test

          sb

          • Message #569

            I have a similar problem, after installation the system tray icon is a blue cross over a green cross. Is This not installed properly? Ive followed all the instructions so far. After restarting the computer this icon doesnt appear and all of the services appear critical in nagios. HELP!!!

            • Message #831

              systray has nothing to do with the overall "functionality"... and the icon is a blue cross over a green cross... it is the NSClient++ logo :)

              MickeM

              • Message #882

                After investigate the problem I saw in the "Windows Event viewer" this error:

                Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 11/17/2008 Time: 3:34:11 PM User: N/A Computer: MyServerName? Description: Faulting application nstray.exe, version 0.0.0.0, faulting module gdi32.dll, version 5.2.3790.4237, fault address 0x00009d33.

                For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 6e 73 74 ure nst 0018: 72 61 79 2e 65 78 65 20 ray.exe 0020: 30 2e 30 2e 30 2e 30 20 0.0.0.0 0028: 69 6e 20 67 64 69 33 32 in gdi32 0030: 2e 64 6c 6c 20 35 2e 32 .dll 5.2 0038: 2e 33 37 39 30 2e 34 32 .3790.42 0040: 33 37 20 61 74 20 6f 66 37 at of 0048: 66 73 65 74 20 30 30 30 fset 000 0050: 30 39 64 33 33 09d33

                • Message #883

                  In windows 2003 server I got this error when I started the nstray:


                  nstray.exe - Application Error


                  The instruction at "0x77c09d33" referenced memory at "0x00424fba". The memory could not be "read".

                  Click on OK to terminate the program Click on CANCEL to debug the program


                  OK Cancel


                  • Message #923

                    I get the same problem as above with NSClient 3.5.2 on a Windows 2003 SBS SP2

                    I have got around it by setting nstray to Compatibility mode 'Windows XP' but surely this should just work ?

                    Any ideas on solving this ?

                    • Message #1126

                      Actualy was having same problems. was unable to start tray icon from root folder of the program and from cmd. Than gone to inspect setting at ini file at the same root folder of NSclient. Founded string that was commented about client enable/disable

                      ;
                      ; # USE SHARED MEMORY CHANNELS
                      ;  This is the "new" way for using the system tray based on an IPC framework on top shared memmory channels and events.
                      ;  It is brand new and (probably has bugs) so dont enable this unless for testing!
                      ;  If set to 1 shared channels will be created and system tray icons created and such and such...
                      shared_session=1
                      

                      (was at 0 and commented)

                      After changing this one systray icon works fine ofcz after u take all steps described in installation manual.

                    • Message #1127

                      Actualy was having same problems. was unable to start tray icon from root folder of the program and from cmd. Than gone to inspect setting at ini file at the same root folder of NSclient. Founded string that was commented about client enable/disable

                      ;
                      ; # USE SHARED MEMORY CHANNELS
                      ;  This is the "new" way for using the system tray based on an IPC framework on top shared memmory channels and events.
                      ;  It is brand new and (probably has bugs) so dont enable this unless for testing!
                      ;  If set to 1 shared channels will be created and system tray icons created and such and such...
                      shared_session=1
                      

                      (was at 0 and commented)

                      After changing this one systray icon works fine ofcz after u take all steps described in installation manual.

                    • Message #1128

                      Actualy was having same problems. was unable to start tray icon from root folder of the program and from cmd. Than gone to inspect setting at ini file at the same root folder of NSclient. Founded string that was commented about client enable/disable

                      ;
                      ; # USE SHARED MEMORY CHANNELS
                      ;  This is the "new" way for using the system tray based on an IPC framework on top shared memmory channels and events.
                      ;  It is brand new and (probably has bugs) so dont enable this unless for testing!
                      ;  If set to 1 shared channels will be created and system tray icons created and such and such...
                      shared_session=1
                      

                      (was at 0 and commented)

                      After changing this one systray icon works fine ofcz after u take all steps described in installation manual.

                    • Message #1129

                      Actualy was having same problems. was unable to start tray icon from root folder of the program and from cmd. Than gone to inspect setting at ini file at the same root folder of NSclient. Founded string that was commented about client enable/disable

                      ;
                      ; # USE SHARED MEMORY CHANNELS
                      ;  This is the "new" way for using the system tray based on an IPC framework on top shared memmory channels and events.
                      ;  It is brand new and (probably has bugs) so dont enable this unless for testing!
                      ;  If set to 1 shared channels will be created and system tray icons created and such and such...
                      shared_session=1
                      

                      (was at 0 and commented)

                      After changing this one systray icon works fine ofcz after u take all steps described in installation manual.

  • Message #1130

    Sorry for spam browser just got halted and didnt show it posted.

Subscriptions