My Oracle Support Banner

Troubleshooting Contract Management (CM) Application Deployment in WebLogic is in a Failed State (Doc ID 1332267.1)

Last updated on JUNE 04, 2021

Applies to:

Primavera Contract Management - Version 12.0 and later
Information in this document applies to any platform.
Application Server: WebLogic



Purpose

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...

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>.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

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


In this Document
Purpose
Troubleshooting Steps
 Cause 1: Contract Management WebLogic Domain Not Properly Configured
 Cause 2: Contract Management Primavera Administrator Utility Not Populated (Version 13 and Above Only)
 Cause 3: WebLogic JDBC Data Source JNDI Name Field Value Using Wrong Case Format
 Cause 4: Contract Management Group References Do Not Match WebLogic JDBC Data Sources
 Cause 5: Server Instance Target Not Specified for WebLogic JDBC Data Sources
 Cause 6: Contract Management Install Wizard Has Not Been Run
 Cause 7: JDBC Data Sources Not Created
 Cause 8: WebLogic Cannot Connect To Database Server
 Cause 9: Invalid JDBC Data Source Connection Information
 Cause 10: Database User Account Locked or Not Mapped to Database Server Instance Login Account (MS SQL)
 Cause 11: Target WebLogic Server Instance Not Running
 The Contract Management application and/or JDBC data sources have been deployed to a WebLogic server instance that is not in a RUNNING state. To confirm that this is the case, take the following steps.
 Cause 12: Sharepoint Integration Set Up Incorrectly
 Cause 13: Contract Management Deployed On Node Manager Started Instance That Is Not Referencing Valid Start Script
 Cause 14: Incorrect Application Server EAR File Being Deployed
 Cause 15: Primavera Administrator Not Upgraded After Applying Service Pack to Contract Management 14.0.0.0 or 14.0.1.0
 Cause 16: Contract Management Integrated With UCM System That Has Invalid User Environment Variables
 Cause 17: Incorrect Microsoft SQL Server JDBC Driver Being Used
 Cause 18: Primavera Administrator (admincm.cmd) needs to be upgraded
 Cause 19: Data Source information for unique EXPADMIN name is incorrect (Version 14.x) only
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.