Absent Member.. Absent Member..
Absent Member..
235 views

<QC/ALM Support Tip>'Error: EntityUtils.TheProjectShouldContainOnlyOneLinkToLabProject'

Dear Customer,

 

Sometimes when we upgrade a project migrated from previous version of ALM/QC in ALM12.x, especially the ALM12.x installed and configured using 'Copy and upgrading existing site administration schema' option, and the project is PC extension enabled. During the project verify, we might meet the following error in the verify log:

 

***********************************************************************

2015-01-09 11:06:59.0 Project is corrupted. Refer to the following knowledge base article for possible solutions:

2015-01-09 11:06:59.0 For possible causes and solutions, refer to the errors in the upgrade log above, the ALM Site Administrator Guide, and the following knowledge base article:

2015-01-09 11:06:59.0 http://support.openview.hp.com/selfsolve/document/KM1281892

2015-01-09 11:06:59.0

2015-01-09 11:06:59.0 EntityUtils.TheProjectShouldContainOnlyOneLinkToLabProject

2015-01-09 11:06:59.0 Exception occurred. Message: ALM-E10011: Actual upgrade failed

2015-01-09 11:06:59.0 Error: EntityUtils.TheProjectShouldContainOnlyOneLinkToLabProject

2015-01-09 11:06:59.0 Stack: com.mercury.td.pcextension.domainprojects.DomainsProjectDirectoryServicesImpl.getLabProject(DomainsProjectDirectoryServicesImpl.java:55)

2015-01-09 11:06:59.0 Stack: com.mercury.td.pcextension.EntityUtils.getLabProject(EntityUtils.java:82)

2015-01-09 11:06:59.0 Stack: com.mercury.td.pcextension.LabAlerts.AlertsProjectPropertiesHelper.getLabSession(AlertsProjectPropertiesHelper.java:95)

2015-01-09 11:06:59.0 Stack: com.mercury.td.pcextension.LabAlerts.AlertsProjectPropertiesHelper.addProjectToLabAlertsProjectPropertiesUsingFrec(AlertsProjectPropertiesHelper.java:117)

2015-01-09 11:06:59.0 Stack: com.mercury.td.pcextension.LabAlerts.AlertsProjectPropertiesHelper.addProjectToLabAlertsProjectPropertiesByPUIDFromUpgrade(AlertsProjectPropertiesHelper.java:63)

2015-01-09 11:06:59.0 Stack: com.mercury.td.pcprojectextension.upgrade.AlertsProjectPropertiesUpgrader.addProject(AlertsProjectPropertiesUpgrader.java:28)

2015-01-09 11:06:59.0 Stack: com.mercury.td.pcprojectextension.upgrade.AlertsProjectPropertiesUpgrader.run(AlertsProjectPropertiesUpgrader.java:15)

2015-01-09 11:06:59.0 Stack: at

2015-01-09 11:06:59.0 Error: ALM-E10011: Actual upgrade failed

2015-01-09 11:06:59.0 The task that failed belongs to PCPROJECT extension

Server exception. Process stopped

2015-01-09 11:06:59.0 Exception occurred.


Finished

***********************************************************************

 

The root cause for this issue is the link number to Lab project for the problematic project is not equal to 1. 

 

Actually when we verify a project with PC extension enabled, ALM will check its link number to the Lab project. If the link number is equal 1, the verify will pass. But if the link number is not equal 1 (0 or >1), this error will be reported in the verify log.

 

How to check the link number to the lab project for a ALM project:

 

1. To check if there are multiple links to the Lab project for the ALM project, please run the following queries on the schema of the lab management project and get the result of it

 

SELECT PRJP_PROJECT_UID, count(*) as count from LAB_PROJECT_PROPERTIES group by PRJP_PROJECT_UID having count(*)>1

SELECT PRJP_PROJECT_NAME, count(*) as count FROM LAB_PROJECT_PROPERTIES group by  PRJP_PROJECT_NAME having count(*)>1

 

The first query should not give any result, the second query can provide duplicates (project might have same name if they are in different domains but this can be an indication).

 

 

2. To check if there is no link to the Lab project for the ALM project, please have this query run on the site admin schema (for SQL database) and get the result of it:

SELECT *  FROM PROJECT_LINKS join PROJECTS on PRL_ID = PROJECT_ID where PRL_TO_PROJECT_UID not in (SELECT PROJECT_UID FROM PROJECTS where PROJECT_NAME = 'LAB_PROJECT')

 

3. To check if there is data inconsistency between site administration DB and Lab project DB and cause the link data compromised, please check site administration DB->PROJECT_LINKS table and the Lab_project DB-> LAB_PROJECT_PROPERTIES table.

 

If a project with PC extension works ok, there will be only one link entry to each other in PROJECT_LINKS table and LAB_PROJECT_PROPERTIES table. For example, if a project’s UID is 1782ff63-5366-4b17-a4ea-88aaffc7ef09, there should be the following entry in the PROJECT_LINKS table and LAB_PROJECT_PROPERTIES table:(Please refer to img1)

 

In most of the cases the issue is due to point 3- there is data inconsistency between site administration DB and Lab project DB and cause the link data compromised. The data inconsistency is caused by the Lab project DB is empty. There is a very important note in ALM12.x installation guide->Chapter 15: LAB_PROJECT Installation Considerations. Please refer to ALM12.x installation guide for more detail.

 

Thanks & Regards

 

HP Support

Labels (1)
0 Likes
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.