Documentation Comments

Use this form to comment on this topic. You can also provide any general observations about the Online Documentation, or request that additional information be added in a future release.

Reality V15.2 Online Documentation (MoTW) Revision 3

Troubleshooting (Windows Installation Guide) (M6848IG+Troubleshooting.htm)

To	Reality
Version
Topic
Submitted by
Company
Location
Email address
Comment

Troubleshooting

Reality records error details in logs according to the class of error. Useful log files for diagnosing problems when starting and running Reality on Windows are:

Daemon Log%REALROOT%\files\daemon.log

Records major events and errors with Reality daemons and Reality processes.

Session Log%REALROOT%\files\session.log

Records incoming and outgoing connections both successful and failed.

Event Log%REALROOT%\files\event.log

Records other SMANAGER (Reality session manager) activity.

Notes

If the Reality service fails to start, error messages can be found the in Windows application event log, which can be viewed using the Windows Event Viewer.
If more than one version of Reality is installed the session and event logs are held in the files folder for the LIVE version of Reality.

Error numbers

Reality error numbers can be converted into human readable messages by using the perror command from the Windows command prompt; for example:

$ perror 2004
Error  2004: RFE_NOITEM     Item does not exist

From Reality TCL you can use: sys perror 2004.

Example messages

Below is an example of a message logged in the daemon log.

Oct 30 07:55:20 #2240  tlrestore WARNING: Image 000000E4 Result (2027) File section already exists

This message indicates that an attempt was made by the 'tlrestore' process (part of Reality resilience) to create a file, which already exists on the database. Running perror 2027 would report:

Error  2027: RFE_SECTEXISTS          File section already exists.

Note More verbose error logging can be activated by running killreal -l 6 from the Windows command prompt.

Below is an example of information logged in the session log:

Session :11  Thu, 21 Nov 2002  15:14:29  IC
    System :demodb, User Id :SYSMAN, Account :SYSMAN, Server :SQLSRVR
    Client Id :, PLID :INET-207.238.117.133-9
    Class :Process, Flags :0, Timeout 1
Session :11  Thu, 21 Nov 2002  15:14:29  Session Terminated by Server Rejection
    Database Initialisation Failed 2008

Running perror 2008 would report:

Error  2008: RFE_INVACCPASS          Invalid logon attempt