licensing7

Comments

  • *******SOLUTION FOUND******** The problem was that th %capture[1]% token yeilds a LOT more text when applied to the Security Log than when it is applied to the Event Log. We had originally configured the subject of our email alerts to include the monitor name and the text of the event. This was fine for most of the email…
    in Event Log Monitoring Comment by licensing7 January 2010
  • Recieved an email this morning from the SolarWinds tech support team: " Grant, This is an issue we have seen before. Let me do some more testing, and I will get back to you. Regards,SolarWinds Support Team http://thwack.com – "Share ideas, find solutions" in our User Support ForumsSolarWinds Certified Professional –…
    in Event Log Monitoring Comment by licensing7 December 2009
  • Please note this problem has NOT been resolved. I believe this to be a bug in IP Monitor. I have lodged a support ticket and will post results for anyone experiencing a similar issue.
    in Event Log Monitoring Comment by licensing7 December 2009
  • I think we can narrow it down to the %capture[1]% token that is stopping these alerts from being emailed. For some reason this only applies to security log events. I had removed this token from the alert and emails came through as expected. Perhaps IPMonitor has some issues capturing event text from security logs?
    in Event Log Monitoring Comment by licensing7 December 2009
  • Hi Chris, I have created a content generator using the tokens you suggested. Emails successfully reached destination for all 3 monitors (Event logs, and both security logs) I then reassigned the original CG, and added the text log action to the alert, as instructed. Viewing this log file it can be seen that the content…
    in Event Log Monitoring Comment by licensing7 December 2009
  • I'm having the same problem. However, I'm trying to monitor events on a system not added to the domain. Getting errors: "Logon failure: unknown user name or bad password; oserror: 0x52e" and "Unable to open Event Log "System" on "xxx.xxx.xxx.xxx". Reason: The ipMonitor service context does not have the necessary privileges…
    in Event Log Monitor - Help Comment by licensing7 November 2009
  • Hi Chris, I'm having a similar problem. However, I'm running IPMon 10.0 build 1371 and I'm trying to monitor events on a system not added to a domain. Getting errors: "Logon failure: unknown user name or bad password; oserror: 0x52e" and "Unable to open Event Log "System" on "xxx.xxx.xxx.xxx". Reason: The ipMonitor service…
    in Restart a service in another domain Comment by licensing7 November 2009
  • Thanks, I'll try those out!
    in MIBs and OIDs for HP servers Comment by licensing7 December 2010
  • Hi Chris, I could not locat a checkbox marked "Send Information Notifications". Where would I find this? I tried the default content generator and indeed this does work. This would seem to imply that there is a problem with the Content Generator that I created. However, I use this same CG on a number of other servers…
    in Event Log Monitoring Comment by licensing7 December 2009
  • *bump*
    in MIBs and OIDs for HP servers Comment by licensing7 December 2010
Avatar