I recently updated from an older version of Plastic SCM (10.0.16.6573) to the latest version of Unity version control (11.0.16.8101). My local workspace is still there, but I’m having trouble with using it.
Loading the local workspace in Workspace Explorer or loading any changes in Sync Repositories shows “no connection could be made because the target machine actively refused it”. Switching to pending changes shows “The server spec is not correct: invalid.”
What could have gone wrong after the update? Should I delete and re-add the workspace?
Hi,
Can you check in the Windows services panmel if your “Plastic SCM Server” service is up and running?
Regards,
Carlos.
Hi,
Thank you for your response. The service is indeed up and running when I checked.
I tried removing my local workspace just now, added a new one in the same path, updated it, and now I can see the workspace listed under the repo. However, if I try to set up a sync view and select local for the server, I get the “No connection could be made because the target machine actively refused it” message. As an aside, I used to work distributed before the update.
Can you attach a screenshot? When configuring a sync view, please always set the local repo as the source and the cloud one as the destination (doesn’t matter if you plan to push or pull branches).