In this situation, the problem is a 'communication' issue between QMS and QVS, and in this case the protocol in use is QVP, as communication to/from QVS is always via QVP protocol, and that runs over TCP port 4747, which I suspect may be blocked somewhere, but if this is the case, the QMC\Status\Services view should show the QVS as done too, as it would not be able to get its status if the port is blocked.
The only other thing that makes any sense is if you still have the QMS running on the other server as well, things are licensed to that QMS, not the new one, and if the QVS license allows only one server to be registered, that may be where things are getting hung up here somehow. Your best course of action would really be to open a Support Case, so we can do a WebEx with you and have a look at things directly, trying to troubleshoot these via chat can be a bit difficult, and I would not want you to post your license etc. here either.
Regards,
Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question.
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
.png "Former Employee"){kind=icon}
