If SirsiDynix Enterprise generates an unexpected error (or an error that the software doesn’t have a specific method of handling) in either Searching or the Admin console, it displays an unexpected error page and logs the error information in a log file called “vse.log” on the server.
The error page notifies the user that an unhandled error has occurred and displays the specific URL that generated the error, a summary of the problem, and the date and time (based on the server time) when the error occurred. You can use this information to find more details about the error in the “vse.log” file.
The date and time recorded in the error log entry may be a few seconds different than the date and time displayed on the error page due to processing time on the server.
Each unexpected error entry in the log file also includes the phrase “An unhandled exception has occurred” to help you more quickly locate such errors.
The error page also provides a link for users to restart their administrative user session to avoid any instability that may result from the error being invoked. When you restart your administrative user session, the system ends the current session and displays the login page, prompting you to re-enter your login credentials and initiate a new session.
If you receive an unexpected error in Searching, the error page displays the same information for patrons as for administrative users. The error page also includes an option for patrons to start their search over. When they choose to start their search over, the system clears any previous search parameters and results, but retains the patron’s profile and language settings.
Related topics
Getting started with SirsiDynix Enterprise
© 2008-2013 SirsiDynix