AM Server Is Not Accessible Anymore When Patching From AM 7.1p3 To AM 7.1p6 (Doc ID 1447716.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle OpenSSO - Version 7.1 and later
Information in this document applies to any platform.

Symptoms


When upgrading to the latest AM 7.1 patch 6 (from a 7.1p3 base for example), it is seen an issue as not able to accessing the AM server after the patch completed.

The redeployment of AM web-apps (amserver, amcommon, ampassword, etc...) finished successfully and the patching procedure itself looks to run correct and completed fine (including the run of updateschema script).

But after the patch has completed and following with a restart of the Web Server container, AM server is not accessible anymore and loading the /amserver login url always returns a 500 Internal Server Error.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms