Issue
How can I tell what device the alarm is coming from in the b0warlog.log file?
The b0warlog.log or "Warning Log" file does not reference individual devices therefore is difficult to see where the alarm happened.
Environment
Vista
Alarms
Cause
A lot of warnings are due to a mismatch in the Vista database and a device on the field. For instance, if you have a Xenta Server alarm that doesn't exist in the Vista database.
Resolution
You could see if the Xenta/Xenta Server is marked in Vista, look for the asterisk (*), to give you a clue where it came from.
An alternative way to do it is to use testclt program:
- Start testclt.exe from the root directory of you Vista installation.
- Login
- Go to File-Dbg
- Write alrproc
- Click Add
- Choose the Time radio button
- Click Poke
- Click Close
- Wait for the warning to happen in the b0warlog.log
- Open b0dbglog.logfile in notepad and search for "your error"
Just above the line found you should see which alarm object that sent the alarm
Example: (Searching for Error:81)
Tue Nov 23 13:26:02 2010 :alrproc >> ProcessAlarmEvent EventId:TGML_test-731-Lon-XG-Xenta401-$NETMON.offline EventType:1 Pri:9 Txt:Xenta group offline
Tue Nov 23 13:26:02 2010 :alrproc >> ValidateDataSpec Id:TGML_test-731-Lon-XG-Xenta401-$NETMON ObjType:EE_MESS
Tue Nov 23 13:26:02 2010 :alrproc >> Processed Error:81
