DirtyHippy

This is now resolved with the help of support. First I checked the config files (it defines the server listening port): C:\Program Files\PlasticSCM5\server\remoting.conf And then the client configuration (that's where the targeting port is located):* C:\Users\<USER>\AppData\Local\plastic4\client.conf* C:\Users\<USER>\AppData\Local\plastic4\profiles.conf These were ok - they pointed it the correct port. Next - Finally, it might be your workspace still pointing to the 8084 port. To solve it:* Open a command line window.* cd to the workspace path.* run "cm ss" to check the target, it might be something like:rep "REPONAME@HOSTNAME:8084" path "/" smartbranch "/main/SCM27239" I ran this command, and my first line simply was "rep "REPONAME"". No host/port. I believe this data is stored in /plastic/plastic.selector in your workspace. * I was told next to run a switch operation to target the right port, something like (you need to adapt this to your scenario):cm switch br:/main/SCM27239@REPONAME@HOSTNAME:8087 This didn't work as I had modified a file in order to test and it complained it wanted me to have no pending changes (and "cm status" wouldn't run because of the original issue in the original post so I couldn't revert that one file). I then ran cm lrep HOSTNAME:8087 which listed my repos on the server so I think we knew at this point it was a workspace-only issue and not a server issue. So at this point - because I knew my workspace had no changes in it since I had checked everything in before the migration - I did this - BE CAREFUL when using this as I believe this kind of a nuclear option. It doesn't delete the files in your workspace - just the meta for the workspace and recreates it I assume. cd "path/to/wks" -> Replace the path with the correct one.cm rmwk . cm mkwk wkREPONAME . --repository=REPONAME@HOSTNAME:8087cm update . This solved my problem!

I installed PlasticSCM cloud version about November 2017. I had been planning to use the cloud but I ended up just using the local repo. I ended up cancelling the subscription and my local repo continued to work so I just kept using it. 2500 changesets later, I decided to upgrade to newest, today, and had all sorts of problems. 1) I made a backup of the entire PlasticSCM5 folder first 2) I downloaded the community edition, installed it over top of the old install and had issues with licensing. I finally gave up, and just subscribed to a year of the Team license to get me a license which seemed to resolve the issue. 3) For some reason my username for all my old changesets was my email but Plastic thought I was a different user (my local user on my box). It showed 0 shelves by me and a bunch of shelves by my original user so that was another indication it didn't have me mapped correctly. I then added a user with the same email to plastic (not sure why he wasn't already aware of him considering it showed the user as the owner of 2500 changesets), changed my authentication to Plastic user/pass, and after that it seemed to associate me correctly with that user. 4) In the client, changeset view, repository view, etc all seem to work now. I can diff old changesets so it must be hitting the server correctly. However, any time I hit branch explorer, or just hit F5 on pending changes (with one change as a test) it displays: "No connection could be made because the target machine actively refused it 127.0.0.1:8084". The server is definitely running in services.msc, and I'm betting if I can see changesets that it must be connecting anyway. I've searched all the files in the Plastic dir - I don't see anything for 8084 except for two of the config sample files. I see in my old log files stuff lines like the one below - but they don't happen after the new install. "2018-12-03 00:34:33,332 (null) (null) (null) (null) (null) INFO networkserver - Server listening locally on port 8084" I should note it is configured to run off 8087 (the default). And the server/client run on the same box. Any insight what to try next? Thanks! Kirk