getting ”Actual upgrade failed” error when creating NEW QC11 project

  • Questions
  • getting ''Actual upgrade failed'' error when creating NEW QC11 project
Question ID: 104744
1
0

We are getting this error when attempting to create a NEW project in ALM11.

What is going on?

Messages:
Failed to Create Project;
Failed to create HP ALM project;
Failed to create project ‘MyNewProject’; Failed to create new project ‘MyNewProject’; Maintenance task EnableExtensionsTask failed;
ALM-E10011: Actual upgrade failed com.mercury.td.saserver.maintenance.PopulateNewTables;
Error in writing to table CYCLE;
Failed to set params in the parametrized query; [Mercury][SQLServer JDBC Driver]Invalid parameter binding(s).;

Stack Trace:
java.sql.SQLException: [Mercury][SQLServer JDBC Driver]Invalid parameter binding(s).
at com.mercury.jdbc.sqlserverbase.dda4.b(Unknown Source) at com.mercury.jdbc.sqlserverbase.dda4.a(Unknown Source) at com.mercury.jdbc.sqlserverbase.dda3.b(Unknown Source) at com.mercury.jdbc.sqlserverbase.dda3.a(Unknown Source) at com.mercury.jdbc.sqlserverbase.ddb8.a(Unknown Source) at com.mercury.jdbc.sqlserverbase.ddb9.setString(Unknown Source) at com.mercury.optane.core.db.CTdPreparedStatement.setString(CTdPreparedStatement.java:253)
at com.mercury.optane.core.db.CTdPreparedStatement.privateSetParam(CTdPreparedStatement.java:678)
at com.mercury.optane.core.db.CTdPreparedStatement.setParams(CTdPreparedStatement.java:860)
wrapped in com.mercury.optane.core.CTdException: Failed to set params in the parametrized query at com.mercury.optane.core.db.CTdPreparedStatement.setParams(CTdPreparedStatement.java:868)
at com.mercury.optane.core.db.convertor.CDBWriter.writeData(CDBWriter.java:476)
wrapped in com.mercury.optane.core.CTdException: Error in writing to table CYCLE at com.mercury.optane.core.db.convertor.CDBWriter.writeData(CDBWriter.java:562)
at com.mercury.optane.core.db.convertor.CDBConvertor.copyTableData(CDBConvertor.java:764)
at com.mercury.td.saserver.maintenance.PopulateNewTables.run(PopulateNewTables.java:59)
at com.mercury.td.saserver.maintenance.BaseFlowStep.start(BaseFlowStep.java:61)

Marked as spam
Posted by (Questions: 185, Answers: 13)
Asked on December 10, 2012 9:34 pm
17 views
Answers (1)
1
Private answer

GoBroncos,

Check to see that your ''DB Admin'' user/password as specified in QC Site Administrator still works and has appropriate rights as per the Install Guide.
A quick check of the password would be to try to login to your DB with the SQL-Server ''Management Studio'', or by setting up an ODBC DSN to point to the DB and use that user to login.
rights can be confirmed by the DBA.

Marked as spam
Posted by (Questions: 3, Answers: 466)
Answered on December 10, 2012 9:38 pm
That was it! Our DBA changed the password without telling us. They changed it a few months ago, but we have only just now tried to create a NEW project.
( at December 10, 2012 9:40 pm)
Glad to help. Make sure that your DBA's either make the password ''static'', or that they notify you whenever they change it. Also, don't forget to change that password in Site Administrator on the DB Servers tab.
( at December 10, 2012 9:42 pm)