Highlighted
Absent Member.. Absent Member..
Absent Member..
3418 views

ALM Patch 10

Jump to solution

Has anyone successfully installed ALM Patch 10?  I get a failure when it trys to deploy the change.  I've installed Patch 3,5 and 9 without issues

0 Likes
1 Solution

Accepted Solutions
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Steve, we have solved the problem - in our case, it was because we had relocated the DB server since the last patch (9), and there was a configuration file that was still pointing to the old DB server.

 

The file is located at 'C:\ProgramData\HP\ALM\conf'\qcConfigFile.properties'.

 

The 'dbConnectionString' value was still pointing to the old DB server.

 

I think that the Server Configuration Wizard might have been able to fix this, but we just updated the file directly and the patch installed successfully!

 

Hopefully this will help you solve your problem.


Regards,

 

Fred Gaumont

View solution in original post

5 Replies
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Hi Steve.  I'm currently in the middle of attempting this myself.  What error message(s) are you getting?  I'm running into "SA Schema is not accessible".

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

I'm getting the same message.  Here is the entire message:

 

WorkerTask: Deploy engine failed com.mercury.optane.core.CTdException: SA Schema is not accessible at com.hp.qc.install.setup.QcServerConfigurationBean.setRepositoryPathFromSASchema(QcServerConfigurationBean.java:735) at com.hp.qc.install.core.configuration.AbstractInstallationConfiguration.takeRepositoryFromSATables(AbstractInstallationConfiguration.java:552) at com.hp.qc.install.deploy.wizard.QcDeployWorkerTask$1.run(QcDeployWorkerTask.java:96) at com.hp.qc.install.setup.AbstractWorkerTask$ActualTask.<init>(AbstractWorkerTask.java:143) at com.hp.qc.install.setup.AbstractWorkerTask$2.construct(AbstractWorkerTask.java:75) at com.hp.qc.install.setup.SwingWorker$2.run(SwingWorker.java:114) at java.lang.Thread.run(Thread.java:619)

0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Steve, we have solved the problem - in our case, it was because we had relocated the DB server since the last patch (9), and there was a configuration file that was still pointing to the old DB server.

 

The file is located at 'C:\ProgramData\HP\ALM\conf'\qcConfigFile.properties'.

 

The 'dbConnectionString' value was still pointing to the old DB server.

 

I think that the Server Configuration Wizard might have been able to fix this, but we just updated the file directly and the patch installed successfully!

 

Hopefully this will help you solve your problem.


Regards,

 

Fred Gaumont

View solution in original post

Highlighted
Absent Member.
Absent Member.

Well done. Thank you Mr. Gaumont!

--
Forj: continuous integration & delivery for the masses
http://www.hp.com/go/forj
Do not hesitate to mark a question as closed if you think you have all you need (Kudos do help too 🙂 )
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..
HI

There three firlds to change
dbServerName
dbaPassword
dbConnectionString

Then start to work for me.

Thank you for solution !!!
0 Likes
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.