HI HomerJ,
Makes sure that when upgrading a project with versioning enabled, all of the entities must be checked in before the upgrade as a project with checked out entities will get a failure during the Verify-Repair process of the upgrade.

To ensure that the project has all entities checked in, run the following SQL statements on the project from the site administrator:

SELECT COUNT(*) FROM VC_COMPONENT
SELECT COUNT(*) FROM VC_REQ
SELECT COUNT(*) FROM VC_RESOURCES
SELECT COUNT(*) FROM VC_TEST
SELECT COUNT(*) FROM VC_BPM_MODELS (For 11.00 and 11.52)

If any of these queries returns COUNT(*) > 0, then checked-out entities exist. In that case, go to the project to be upgraded and check in all the entities that are checked out or use ''undo check out'' (use this as a last ditch option as all changes made will be lost and the entity will be reverted to the last known version). Re-run the SQL statements above again and repeat until COUNT(*) = 0 is returned and now the project is ready for upgrade.

I hope this helps,
Dan

I'm on a project team and we're currently trying to upgrade from HPQC 11.0 to 11.5 (once that's all sorted out and stable, we intend to move on to 12.0). We can't afford risking downtime with the production server, so we're using a new server (these are all VMWare VM's) for the new QC. The current Prod is Win 2003, the 11.5 is Win 2008 and the 12.0 will be Win 2012.

The procedure we've been using is making a clone of the database, copying over the repository and editing the db server and file location lines in the dbid.xml files. That works and we can restore projects in the new server. The problem we having is when we try to upgrade a project, we get that error stating there are checked-out files that require manual intervention.

I was hopeful we had the solution after I found this post yesterday. There were a fairly large number of old checkouts that showed up in the five tables listed above, and we got all of that stuff checked back in and all five tables are now empty. However, after deactivating all projects, making new copies of the database and repository, reinstalling QC on the new 11.5 server and restoring just the one project we're primarily using, we're still getting the checked-out items error when we try to verify the project.

Our users need to retain versioning, so turning it off to get past this error is not a viable option. Any ideas on what we should try next?

The five tables listed are not a complete list of tables that store version control information. In v11.52 there are a total of 30 tables that can hold VC information. If you go to Site Admin, the Site Projects tab, and expand an individual project you will see the full list of data tables in that project. The ones that store version control information are named with VC_*. If any of those tables have records, then Verify will report there is checked out information.

The five tables listed are the main tables. VC_TEST lists checked out test cases. If you checked them all in, then that process should've cleared the other associated Test tables - VC_TEST_CONFIGS, VC_TEST_CRITERIA, VC_TEST_MULTIVALUE, VC_TEST_PARAMS, and VC_DESSTEPS. But check all the tables to find out what is still checked out.