Issue creating projects using ”Create a project by copying data from an existing project” option in QC 10
« Back
Tags:
Category:
Question ID: 104068
▲
1
▼
♥ 0

I have an issue with creating a new project using the "Create a project by copying data from an existing project" option. I can create a new empty project with no problem.

I’m running QC 10 with patch 10 installed in a Win 2003 server and SQL 2005 Database.

Error Details

Messages:
Failed to Create Project;
Failed to create Quality Center project;
Failed to create project ‘Training’;
Failed to perform borrow operation for project ‘Training’;
Failed to borrow project;
Failed to execute job com.mercury.optane.core.parallel.CParallelJobsExecutor.Caused by
Error 1:Failed to execute job com.mercury.optane.core.db.convertor.workers.borrow.CTableCopier_1.Caused by
Error 1:Failed to copy table ‘ACTIONS’ from schema ‘usi_sandboxproject_db.td’ to schema ‘usi_2_training_db.td’;
;

Error 2:Failed to execute job com.mercury.optane.core.db.convertor.workers.borrow.CTableCopier_1.Caused by
Error 1:Failed to copy table ‘ACTIONS’ from schema ‘usi_sandboxproject_db.td’ to schema ‘usi_2_training_db.td’;
;

Error 3:Failed to execute job com.mercury.optane.core.db.convertor.workers.borrow.CTableCopier_1.Caused by
Error 1:Failed to copy table ‘ACTIONS’ from schema ‘usi_sandboxproject_db.td’ to schema ‘usi_2_training_db.td’;
;

Error 4:Failed to execute job com.mercury.optane.core.db.convertor.workers.borrow.CTableCopier_0.Caused by
Error 1:Failed to copy table ‘ALERT’ from schema ‘usi_sandboxproject_db.td’ to schema ‘usi_2_training_db.td’;
;
;

Stack Trace:
com.mercury.optane.core.CTdException: Failed to execute job com.mercury.optane.core.parallel.CParallelJobsExecutor.Caused by
Error 1:Failed to execute job com.mercury.optane.core.db.convertor.workers.borrow.CTableCopier_1.Caused by
Error 1:Failed to copy table ‘ACTIONS’ from schema ‘usi_sandboxproject_db.td’ to schema ‘usi_2_training_db.td’;
;

Error 2:Failed to execute job com.mercury.optane.core.db.convertor.workers.borrow.CTableCopier_1.Caused by
Error 1:Failed to copy table ‘ACTIONS’ from schema ‘usi_sandboxproject_db.td’ to schema ‘usi_2_training_db.td’;
;

Error 3:Failed to execute job com.mercury.optane.core.db.convertor.workers.borrow.CTableCopier_1.Caused by
Error 1:Failed to copy table ‘ACTIONS’ from schema ‘usi_sandboxproject_db.td’ to schema ‘usi_2_training_db.td’;
;

Error 4:Failed to execute job com.mercury.optane.core.db.convertor.workers.borrow.CTableCopier_0.Caused by
Error 1:Failed to copy table ‘ALERT’ from schema ‘usi_sandboxproject_db.td’ to schema ‘usi_2_training_db.td’;
;

at com.mercury.optane.core.parallel.CParallelJob.getError(CParallelJob.java:201)
at com.mercury.optane.core.db.convertor.workers.borrow.CBorrower.copyProject(CBorrower.java:54)
wrapped in com.mercury.optane.core.CTdException: Failed to borrow project
at com.mercury.optane.core.db.convertor.workers.borrow.CBorrower.copyProject(CBorrower.java:54)
at com.mercury.optane.core.db.convertor.CDBConvertor.borrow_i(CDBConvertor.java:1135)
at com.mercury.optane.core.db.convertor.CDBConvertor.borrow(CDBConvertor.java:1083)
at com.mercury.optane.core.db.convertor.CDBConvertor.borrow(CDBConvertor.java:1042)
at com.mercury.optane.core.db.convertor.CDBProject.borrow(CDBProject.java:309)
at com.mercury.td.saserver.api.logics.CProjectLogic.copyExistingProject(CProjectLogic.java:4025)
wrapped in com.mercury.optane.core.CTdException: Failed to perform borrow operation for project ‘Training’
at com.mercury.td.saserver.api.logics.CProjectLogic.copyExistingProject(CProjectLogic.java:4096)
at com.mercury.td.saserver.api.logics.CProjectLogic.createProject(CProjectLogic.java:1885)
wrapped in com.mercury.optane.core.CTdException: Failed to create project ‘Training’
at com.mercury.td.saserver.api.logics.CProjectLogic.createProject(CProjectLogic.java:1898)
wrapped in com.mercury.optane.core.CTdException: Failed to create Quality Center project
at com.mercury.td.saserver.api.logics.CProjectLogic.createProject(CProjectLo

Marked as spam
Posted by (Questions: 5, Answers: 1)
Asked on March 31, 2010 6:26 pm
109 views
Answers (3)
▲
1
▼
✔
Private answer

Could be caused by wrong ownership of some tables in QC project schema.

Log into SQL Enterprise manager, go to that project schema, double-click ''Tables'', on the right pane, you mayfind the ''Owner'' of some tables is ''dbo'', not ''td''.

That's why when you try to copy this project, it gives you these errors.

You need to assign the td user ownership to that schema.......

How to restore td as db owner to project tables.

Run these commands in the project database

CREATE USER [td] FOR LOGIN [td] 
Go
CREATE SCHEMA [td] AUTHORIZATION [td]
Go
Alter user [td] with DEFAULT_SCHEMA=[td]
Go
sp_addrolemember [db_ddladmin], [td]
Go

If the First command returns the td user, run the second command

/ Make td account work again /

EXEC sp_change_users_login 'Report'
go
EXEC sp_change_users_login 'Update_One', 'td', 'td'
go

exec sp_MSforeachtable ''ALTER SCHEMA td TRANSFER ? PRINT '? modified' ''
Marked as spam
Posted by (Questions: 6, Answers: 167)
Answered on April 1, 2010 1:26 am
▲
0
▼
Related Link: http://eyeontesting.com/questions/5278/is-there-an-easy-way-to-switch-our-sql-server-qc-p.html
( at January 16, 2014 2:16 am)
▲
1
▼
✔
Private answer

Also, make sure that you double-check the authentication setting for DB_NATIVE_AUTHENTICATION. If you are using the 'td' user as the project's owner, make sure this setting is set to 'N' for native SQL authentication. If you are using 'dbo', then this should be changed to 'Y' for Windows Authentication.

Marked as spam
Posted by (Questions: 2, Answers: 477)
Answered on April 2, 2010 3:15 pm
▲
1
▼
✔
Private answer

The issue was resolved by creating a new Database Server in QC using different authentication type than the one used when QC was installed. The QC project I was trying to copy was a backup from a QC install that was using Windows Authentication, the error was happening in a QC install using SQL Authentication type. Below are the steps performed to resolve the issue:

  • Created a new database server using Windows Authentication.
  • Changed the Database name (new database server name) and native authentication to ( Y )
  • Removed QC project that I wanted to copy from QC.
  • Restored the QC project using the updated dbid.xml file.

Then I was able to create a copy of the project with no issues!

Marked as spam
Posted by (Questions: 5, Answers: 1)
Answered on April 5, 2010 2:52 pm
« Back
EyeOnTesting

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

Got it!
X
Scroll to Top