0% found this document useful (0 votes)
19 views

Caught Exception Error

After upgrading the Remedy web client, users may receive Java Caught Exception errors due to invalid cached browser data. Clearing the browser cache by deleting temporary internet files and browsing history in Internet Explorer, logging out and restarting the browser should resolve the issue. Enabling the option to delete browsing history on exit can prevent future errors. Unresolved issues should be reported to the eis-ars-as support group.

Uploaded by

Boris Noack
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views

Caught Exception Error

After upgrading the Remedy web client, users may receive Java Caught Exception errors due to invalid cached browser data. Clearing the browser cache by deleting temporary internet files and browsing history in Internet Explorer, logging out and restarting the browser should resolve the issue. Enabling the option to delete browsing history on exit can prevent future errors. Unresolved issues should be reported to the eis-ars-as support group.

Uploaded by

Boris Noack
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Java Caught Exception Error in the Remedy Web Client

After upgrading the Remedy web client to a new version it might be possible that your local browser
holds information that aren’t valid anymore.

If you receive a error message like this in your browser please clear/delete your local browser cache first:

In Internet Explorer 6:


Go to Extras Internet Options General Tab Temporary Internet files Press ‘Delete Files…’
In Internet Explorer 8:
Go to Extras Internet Options General Tab Browsing history Press ‘Delete…’

After this please logout, close your browser and relogin into Remedy web client.

To prevent this error in the future please enable the ‘Delete browsing history on exit’ check box.

If the failure doesn’t disappear please raise an incident ticket and assign it to the support group:
‘eis-ars-as’

You might also like