Unable to create new workspace

[d0mokun]

Hello everyone,

 

I'm having a bit of a bother with Plastic when it comes to creating a new local workspace. I have created a cloud repo with no issues whatsoever.

 

When I try to create a new local workspace, Plastic tells me that the 'workspace already' exists.. but for my existing workspace and not the new one. Plastic happily creates a new local folder and the same issue occurs if I choose an already existing local source folder.

 

I've only got a single pre-existing workspace also linked to a cloud repo. The new one has nothing to do with the existing one.

 

Perhaps someone could advise me as to a solution?

 

Thanks

Dan.

[manu]

Hello Dan,

 

can you run a "cm lwk" command and post us the result? Can you also tell us the path where you are trying to create the new workspace?

 

Notice you can't create a new Plastic SCM workspace inside another one, not sure if it's your case.

 

Best,

Manu.

[d0mokun]

Hi Manu,

 

The result of that command is 

KehuaMap@PIXL-HUDSON c:\Users\Dan\wkspaces\KehuaMap 

I'm attempting to create the directory outside of the above one, indeed it already exists. Even if I use the workspace tool to create a new folder, it gives the same error.

 

Thanks

Dan.

[manu]

Ok, the following root directory paths are excluded:

 

* c:\

* c:\Users

* c:\Users\Dan

* c:\Users\Dan\wkspaces

 

But for example, the following command should work:

cm mkwk wkTest c:\Users\Dan\wkspaces\Test

[d0mokun]

Hi Manu,

cm mkwk wkTest c:\Users\Dan\wkspaces\Test

The above didn't work. The command seemed to execute and the folder created, though no change in SCM. It still says the workspace already exists for the previous project.

 

Thanks

Dan.

[manu]

Hi Dan, 

 

it has to be a configuration issue. Are you available next Monday for a very fast connection? 

 

We can review it with you in order to better understand what's happening.

[d0mokun]

Hi Manu,

 

Certainly. Thanks!

[manu]

Sent you an email

[JEP]

Wanted to add this here because it's the hit that comes up when you search for this issue.

I had this issue as well, and for me it was due to copying an existing project that had a repo/workspace in Plastic to a new directory. I did not know it, but there's a hidden .plastic directory. It saves information about the workspace. Since it was copied into the new project, it confused Plastic and caused this erroneous claim about the workspace. The solution was deleting the .plastic folder in the newly copied project.