Since Googling has helped me not at all with this one, I'll report on my findings. I think I know what it means. You get it if you log into Perforce, browse for a workspace, and then pick a workspace from a different machine than you're currently on. You might need to create your own workspace. And it's a good sign, because at least it means you've succesfully connected to the server. Much better than the 'partner exited unexpectedly' or 'unable to create workspace' messages, which probably mean you're not connected at all.
I concur with your advice. I have found that a computer domain change may result in to such errors.
also sometimes change in server's name in DNS could also lead to this
Posted by: Soumit | February 18, 2014 at 03:15 AM
change the root of your client to local path. it will work.
Posted by: EL Hasrouni - WIAM | July 21, 2014 at 01:51 AM
We just solved this exact issue. In our case, the user had recently enabled bitlocker, and the drive this workspace was on was locked.
Posted by: Nick | February 28, 2023 at 01:54 PM