Trouble with LAB_PROJECT… but we don’t even use it!
Question ID: 108768

We just did an in-place upgrade of our QC12.55 to 12.60 and many of our projects upgraded just fine (verify/repair/upgrade).
We had a few that need to be restored with the DBID file (they were archived/removed prreviously) but were still in the original database location and repository folder as the other projects.
On trying RESTORE, we get a "failed to restore" error and this strange additional info in the SA Log (below).

We have the QC/Enterprise license and can’t even SEE the Lab_Project, what does that have to do with our "regular" QC Projects?



Failed to Restore Project; Failed to restore project. Project ‘LAB_PROJECT’ already exists in domain ‘DEFAULT’; Project ‘LAB_PROJECT’ already exists in domain ‘DEFAULT’;

Stack Trace:
com.hp.alm.platform.exception.CTdException: Project ‘LAB_PROJECT’ already exists in domain ‘DEFAULT’
at com.hp.alm.platform.siteadmin.api.logics.CProjectLogic.restoreProject(
wrapped in com.hp.alm.platform.exception.CTdException: Failed to restore project. Project ‘LAB_PROJECT’ already exists in domain ‘DEFAULT’
at com.hp.alm.platform.siteadmin.api.logics.CProjectLogic.restoreProject(
at com.hp.alm.platform.siteadmin.api.logics.CProjectLogic.restoreProject(
at com.hp.alm.platform.siteadmin.requests.RestoreProject.execute(
at com.hp.alm.platform.web.RequestsDispatcher.execute(
wrapped in com.hp.alm.platform.exception.CTdException: Failed to Restore Project
at com.hp.alm.platform.web.RequestsDispatcher.execute(
at com.hp.alm.platform.server.web.CAbsServlet.executeFunction(
at com.hp.alm.platform.server.web.CAbsServlet.processRequest(
at com.hp.alm.platform.server.web.CAbsServlet.doPost(
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at org.eclipse.jetty.servlet.ServletHolder.handle(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at com.hp.alm.platform.util.gzipfilter.GZIPFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at com.hp.alm.platform.web.XSSProtectionFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at com.mercury.optane.core.state.ServerStatusFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at org.hp.qc.web.restapi.authentication.LwssoRedirectFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at com.hp.alm.platform.web.NoSniffFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(
at org.springframework.web.filter.OncePerRequestFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at com.hp.alm.platform.web.HTTPMethodsFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at org.eclipse.jetty.servlet.ServletHandler.doHandle(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.session.SessionHandler.doHandle(
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHand

Marked as spam
Posted by (Questions: 193, Answers: 14)
Asked on December 18, 2018 4:39 pm
Answers (1)
Private answer

This is actually fairly common to have issues with the LAB_PROJECT.

With the enterprise/QC license The ''Lab Management'' tab is hidden and normally you cannot see the Lab_Project.
Normally, a new LAB_PROJECT gets created with every install and the installer will attempt to upgrade an existing one if it finds the LAB_PROJECT (named something like ''default_lab_project_db'').
Now, since you are using the Enterprise license, you are not using the Lab_Project anyway (it is part of server-side test automation feature exposed with the ALM license), you can use the new/blank one, or try to manually upgrade the old one if needed.

So, the first thing to try would be to expose the LAB_PROJECT in your project list. See this post on how to add the site parameter to do that:

Then, it can be treated like a ''regular'' project and you can perform a VERIFY/REPAIR/UPGRADE as usual on it.
NOTE: In this state you now CAN ''restore'' a LAB_PROJECT like you do ''regular'' projects.

IF you for some reason don't have a LAB_PROJECT (look in the qcsiteadmin_db/PROJECTS table to see if it is there), you can re-run the configuration wizard (not re-install) and it will create a new blank one and put in the list -- don't forget to tell it to use an EXISTING qcsiteadmin_db and point to your already-upgraded one.

IF you can find an EXISTING LAB_PROJECT (database like ''default_lab_project_db'' + corresponding repository), AND it is in the PROJECTS table, you COULD just fix the DB entry for the project so it points to it properly (correct names, paths, URL's etc.), OR you could RESTORE it like a''regular'' project (assuming you set the site parameter).

If using ORACLE, make sure this ''schema-user'' has the SAME password as your ''regular'' project schemas have and then copy the encrypted password string to this row in the table.

So, all QC wants here is a WORKING/UPGRADED Lab_Project.

When restoring or creating projects, it needs to communicate with this project so it knows about all projects in case it would be used in Server-side test automation -- Even though you don't have the feature.

Lab_Project References:

Marked as spam
Posted by (Questions: 4, Answers: 509)
Answered on December 18, 2018 6:15 pm

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top