Cheshire Cat Computing

Hey Steve.

I have runned into some problems trying to get the eventlogs running.

The first thing is that when i install nagevlog-setup-1.9.2.exe i get the error with the C runtime library that you explained elsewhere.
I installed vcredist_x86, but it doesnt help.

Anyway, after the installation i can startup the Eventlog Manager but when trying to stop og restart the service it wont stop! Its just stays in STOPPING state.
I have tried several machines, both Win2K3 and XP, and its the same.

Any ideas?

This isn't one I can currently duplicate; I've tested on XP and 2k3 (it only works on 2k8 after some security settings are changed)

Once the vcredist package is installe,d it should be able to start up correctly (which it sounds like it does) and shut down - but in your case, it hangs on shutdown. It's possible this is connected to problems with the NSCA (on shutdown, it attempts to send a 'shutting down' notification to the NSCA server if you have the heartbeat enabled).

Try disabling the heartbeat service settings, and testing that the NSCA send is working. This might be the cause of the hang on shutdown.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Just an update:

I get this STOPPING from time to time when i setup new servers.
I just restart the server, its just during setup of the eventlog that is happends. After restart everything runs smoothly. And i can live with that.

Glad to hear you have a workaround.

Despite Windows being supposedly a more consistent platformand API, in fact there are a fair number of differences between XP, 2k, 2k3 and later versions, not to mention the different MSVC++ DLL packages . The biggest problem for me to wrestle with at the moment is changing the entire thing to handle unicode, which is a huge change.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Hi!
There can be different events that lead to Windows Log Error analysis. You need a troubleshooting guide for this. This one might help.