Troubleshooting Contract Management (CM) Application Deployment in WebLogic is in a Failed State
(Doc ID 1332267.1)
Last updated on JUNE 04, 2021
Primavera Contract Management - Version 12.0 and later Information in this document applies to any platform.
Application Server: WebLogic
This article will assist in troubleshooting why the Contract Management application deployment in WebLogic is in a Failed state. To confirm that the Contract Management deployment is in a Failed state, log into the WebLogic admin console site (default URL: http://[server name]:7001/console) and click the Deployments link in the Domain Structure tree on the left.
Along with the failed deployment, error messages in the WebLogic admin console or in the server log file can include...
"StartupServlet" failed to preload on startup in Web application: "exponline".
weblogic.common.ResourceException: Unknown Data Source...
<javax.naming.NameNotFoundException: While trying to lookup 'jdbc.....' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/......'>
<javax.naming.NameNotFoundException: Unable to resolve 'jdbc.....'. Resolved 'jdbc'; remaining name '......'>
If the Contract Management Web Services application deployment is in a failed state, the below solutions may be helpful as well. However in that scenario, please also see <Document 1430798.1>.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!