| | | Forum Newbie
       
Group: Forum Members Last Login: 12/22/2008 3:17:10 PM Posts: 7, Visits: 36 |
| Howdy,
I've setup a passive monitor to check when a server has been rebooted. I added a Windows Event Log and created a new library to monitor Windows Event Log = 6009. When I check under passive monitor error reports, it shows up (kinda cryptic) but under Windows Event Logs there's nothing. It shows that it's on and passively monitoring. I'm running version 11.3.
Can someone give me an idea why is not detecting the reboot or the Event ID = 6009? Perhaps there's a better way of monitoring when a server gets rebooted. Any help would be appreciated...Thanks! |
| | | | 
Member of the WhatsUp Gold team
       
Group: Administrators Last Login: 6/29/2009 4:20:10 PM Posts: 513, Visits: 1,080 |
| Did a quick search of our defect database and found one issue that might be affecting you. It was reported against version 11.0.2.
There is a defect with Windows Event log passive monitors that requires the same credentials on the computer sending the event and the WUG computer. (This is issue #10158). Can you confirm that the same account exists and is being used on both?
__________________________________________________
Will Sansbury
Member of the WhatsUp Gold team
Twitter: @willsansbury
 | If you need help with anything, let me know!
|
Help make WhatsUp even better! Sign up for the WhatsUp Gold v14 Technical Preview Program! |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 12/22/2008 3:17:10 PM Posts: 7, Visits: 36 |
| | Yep. Same user credentials. All those machines are on the same domain. |
| | | | Junior Member
       
Group: Forum Members Last Login: 5/13/2009 12:38:57 PM Posts: 15, Visits: 53 |
| | looks like the event is getting logged before the NIC Negotiates a physical connection with the network. Try monitoring for a different event that only gets logged at Bootup (IE Anti-Virus application starting) Still trying to figure this one out myself to find something more accurate. For the time being im relying on the Symantec End Point Service to act as my trigger since that only starts at bootup. |
| |
|
|