Our QC Server was just changed to do HTTPS, Now our QC-Synchronizer can’t connect to QC

  • Questions
  • Our QC Server was just changed to do HTTPS, Now our QC-Synchronizer can't connect to QC
Question ID: 106152
0
0

The other day, our Systems team upgraded our QC 11 server to 11.52 and at the same time enabled SSL/HTTPS for QC.

Now, our links all fail on the QC (Endpoint1 side) in QC-Synchronizer saying the "Server is not available".
I changed the URL to include HTTPS instead of HTTP, what else should we be doing?

Marked as spam
Posted by (Questions: 185, Answers: 13)
Asked on July 1, 2015 3:33 pm
3 views
Answers (2)
0
Private answer

Usually, no additional settings are required other than changing the HTTP to HTTPS.

Do you by chance have a PROXY login required when using IE to access QC on the QC-Sync server?

If so, you should edit the ''HP Application Lifecycle Management Synchronizer'' service and provide a Service User (''logon as'' tab) that has FULL Internet Explorer access (if you login to the Server PC with this user, you are NOT asked to also login to the Proxy to access various pages including QC).

Marked as spam
Posted by (Questions: 3, Answers: 466)
Answered on July 1, 2015 3:38 pm
0
Private answer

On QC server, run ''netstat -a -n -p tcp'' command, and monitor whether there is incoming communications from the QC synchroniser or not?

Also, try re-register/re-install/re-run ''HP ALM client Registration'' and ''HP ALM connectivity'' on the QC Sync server (by accessing QC using IE using https)

Marked as spam
Posted by (Questions: 0, Answers: 2)
Answered on August 10, 2015 1:09 pm