Ticket #68 (closed defect: worksforme)

Opened 5 years ago

Last modified 18 months ago

Error installing systray

Reported by: anonymous Owned by: mickem
Priority: 1 Milestone: 0.3.4
Component: None Version: 0.3.3
Severity: Bugs Keywords: install systray
Cc:

Description

Hi, i attempted to install nsclient on a windows xp and windows server 2003 machine, but when i lunch the command systray install i get the following:

C:\NSClient++>nsclient++ systray install

e .\PDHCollector.cpp(69) Getting counter info...

e .\PDHCollector.cpp(119) Attempting to open counter...

e .\PDHCollector.cpp(122) Counters opend...

e .\SysTray.cpp(40) SysTray is not installed (or it cannot interact with the des

ktop) SysTray wont be loaded. Run NSClient++ SysTray install ti change this.

e .\NSClient++.cpp(239) Module not found

I check for the systray.dll file in nsci.ini, but it is not commented.

How can i do to solve this problem?

Change History

comment:1 Changed 5 years ago by anonymous

  • Severity changed from Bugs to Support Requests

comment:2 Changed 5 years ago by anonymous

  • Priority changed from 10 to 1

comment:3 Changed 5 years ago by anonymous

  • testcase_result changed from pass to fail

comment:4 Changed 4 years ago by mickem

  • Status changed from new to closed
  • Resolution set to fixed

(sorry, really old, but...

nsclient++ -noboot SysTray install

comment:5 Changed 4 years ago by anonymous

  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:7 Changed 4 years ago by mickem

  • Status changed from reopened to closed
  • Resolution set to fixed

???

comment:8 Changed 4 years ago by anonymous

  • Version changed from 0.2.7 to 0.3.0-RC

l \NSClient++.cpp(292) Module was not loaded, attempt to load it 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.

comment:9 Changed 4 years ago by mickem

Uhmm, the solution is still to do

nsclient++ -noboot SysTray install

Or is something wrong? (if so, let me know what was wrong)

MickeM

comment:10 Changed 4 years ago by anonymous

  • Component changed from CheckSystem to None
  • Severity changed from Support Requests to Bugs

the nsclient++.exe service runs and the "M" icon shows up only momentarily and disappears if you try to mouse over it. If the -noboot option is omitted, then the error shows:

C:\NSCLient++>nsclient++ SysTray install l \NSClient++.cpp(292) Module was not loaded, attempt to load it l \SysTray.cpp(63) SystemTray is no able to run as the SERVICE_INTERACTIVE_PROCESS flag has been set, <then, after many seconds...> 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...

The strange single chars "l" and "e" are in fact on the error line and mostly, the yellow "m" looking icon shows up on the system tray but if you try to mouse over or "touch" it, it dissappears.

IF you right-click the "M" icon before "failed to terminate thread: SysTray..." appears, you have the "show log", "stop service", and "inject command" options - but then it dies as the error appears on the command line.

Either way the documentation is incorrect:

"nsclient++ SysTray" does not work because there is no command - you need at least:

"nsclient++ SysTray install" after changing the ini file to include SysTray.dll.

and this will likely cause a lot of confusion among Windows users (like me).

comment:11 Changed 4 years ago by jroztocil@…

(sorry - didn't mean to post as anonymous...)

I would add that running the client at a cmd prompt as "nsclient++ /test" the client and the system tray icon behaves the way you would expect.

On the service properties on the Log On tab I *did* make sure that the system service had the "Allow service to interact with desktop" and the service was running as the "Local System Account".

Is the local system account not privileged enough perhaps?

Thank you for any advice anyone can offer.

comment:12 Changed 4 years ago by anonymous

i have the same problem! please help me! thanks so much!

comment:13 Changed 4 years ago by anonymous

which version do you use?

comment:14 Changed 4 years ago by anonymous

  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:15 Changed 4 years ago by larryfindley@…

I have the same problem with systray as described above, including the fact that while in test, sytray works normally. i'm running windows server 2003 r2, standard x64 edition. Please help, thanks!

comment:16 Changed 4 years ago by anonymous

If you use Vista (w2k3?) the systray "might" not work "on boot" due to security issues (I need to set some flags that I don't do in the current version). It should however work if you do "nsclient++ /test".

MickeM

comment:17 Changed 4 years ago by anonymous

What do you do after you run "nsclient++ -noboot SysTray install"?

comment:18 Changed 4 years ago by mickem

nothing?

you also need to enable the systray plugin (look under [modules]) but apart from that nothing.

(On vista it does not really work due to "privileges")

MickeM

comment:19 Changed 4 years ago by roll

  • Keywords install systray added
  • Version changed from 0.3.0-RC to 0.3.3

When I install SysTray on windows 2003 server, I've got this error :

C:\NSClient++-Win32-0.3.3>NSClient++ install

C:\NSClient++-Win32-0.3.3>NSClient++ SysTray install l \SysTray.cpp(63) SystemTray is now able to run as the SERVICE_INTERACTIVE_PROC ESS flag has been set. 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... e \NRPEListener.cpp(150) Exception caught: Error: SSL Context already initalized .

Can you help me ? The utilisation of NSClient++ is OK.

Roll

comment:20 Changed 4 years ago by mickem

I shall try to fix the systray issues during next week and the realase a 0.3.4 version since the systray is the most "complained about problem" right now...

MickeM

comment:21 Changed 3 years ago by anonymous

Same problem, you can disappear systray option in INI file.

comment:22 Changed 3 years ago by mickem

??? not sure i understand what you mean?

comment:23 Changed 3 years ago by mickem

  • Status changed from reopened to closed
  • Resolution set to fixed
  • Milestone changed from 0.3.0 to 0.3.4

new systray handling in last nightly (and upcoming 0.3.4)

comment:24 Changed 3 years ago by jrodz

  • Status changed from closed to reopened
  • Resolution fixed deleted

same problem as everyone else. running windows server 2003 sp3. even try to test it without systray and it does not works. windows xp pro clients seem to be ok. I have not try linux servers nor clients yet.

comment:25 Changed 3 years ago by anonymous

Need msvcm80.dll, msvcp80.dll msvcr80.dll, Microsoft.VC80.CRT.manifest file in nsclient++ folder to use systray. I copy these files from VMWare Player 2.5.1 build-126130 folder.

comment:26 Changed 3 years ago by mickem

which version of NSClient++ ?

comment:27 Changed 3 years ago by anonymous

C:\NSClient++>NSClient++ SysTray install do this. Scofield

comment:28 Changed 3 years ago by anonymous

Im having this problem with version NSCLient++ - 0.3.6.325 2009-02-07 the client is manually unzipped at d:\program files\NSClient++-0.3.6-RC4-Win32 installed with d:\program files\NSClient++-0.3.6-RC4-Win32\NSClient++ /install

Have tried NSClient++ SysTray install still same issue.

Using 2003 Server Enterprise with SP2

Found this in log file: error:CACHEmodules\SysTray\SysTray.cpp:51: SysTray is not installed (or it cannot interact with the desktop) SysTray won't be loaded. Run NSClient++ SysTray install to change this.

comment:29 Changed 3 years ago by anonymous

As addendum to above, forgot to mention that SysTray.dll is uncommented in nsc.ini file

comment:30 Changed 18 months ago by mickem

  • Status changed from reopened to closed
  • Resolution set to worksforme

No longer relevant...

(se FAQ and various other posts on this issue)

Note: See TracTickets for help on using tickets.