VA2 FAQ

For example, if you want to find a particular error strings just for the Component TxnRouter – you could add a error definition here – and that particular component log file will be searched for the error definition. You must define the error definition first, under the Error Definition tabs. Reference the documentation, look up the Error Definitions section, and the Error Definitions for Components section for more info.

If an Event is generated, for example EIM exits with error, you should look under the Events tab to see if an event is generated. If you have you Communication Servers, Schedules, and Administrators set up correctly, you will be routed an error message.

"Application Log File Error Definition" is for adding a Error Definition that operates on the application log file directory. Instead of being Component specific, it will search for a defined error string for any log file for the whole application. You should see under your Appserver, a Error Definition called "Process or Component exited with Error". This means that any Log created under the appserver with the string "Process exited with error" should generate an event. Once again, if an event is generated it will be available under the Events tab.

You should see Tasks if the Siebel Server is running… if not there is a serious error.

. There are several potential causes. One is if you are working with Siebel 7. When running the setup for Siebel 7, the Siebel password that VA2 imports is encrypted. This parameter is stored in the Software Element that represents your Siebel Enterprise - in the Software Elements Option tab. Here you will see a username and password options. You must change the Password to be your Siebel password instead of the encrypted one. Unfortunately, if it is not set appropriately, no Server Tasks or Monitored Components will show up - and the log files do not list an error, but it is not able to harvest Siebel Server information. If you change the password restart the LSM and then check the Server Task and Compnent information. This step is documented in the installation steps under Siebel 7 Install notes.

You may want to check the log files for the LSM. Log files are under \VA2\LSM\log – if there is SQL errors in the vsrvrmgr(servername).log file, it means that for some reason you don’t have the most up to date executable for harvesting Task information. Stop the LSM service, replace the LSM. Make sure you have the latest executable. Check the modified date on your vsrvrmgr.exe is before 11/26/2002 at 4:30 pm, you'll need to download a new version.

When launching the debugger, the path to the debugger.exe must be set in the VA2 console. This is not done on install. You should set it in Virtual Administrator tab > Edit > System Variables.