cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

CLI - si co command on version11.1 fails on missing local project.pj

ilampe
4-Participant

CLI - si co command on version11.1 fails on missing local project.pj

For example

in older Integrity version the

command below worked correct  but failed in Intergrity version 11.1 because of missing local project .pj.

 

Projectpath=/Projects/Library/LibPart1/project.pj

Sandboxpath=C:\Library\LibPart1

 

working path cmd-line C:\Library\LibPart1

 

si co --hostname=... --port=... --nolock --batch --yes -S c:\Library\LibPart1\project.pj c:\Library\LibPart1\*.*

 

if Sandbox location is the same as project location it worked, otherwise not.

 

For new versions since 11.1 worked only on same pathes (project path and sandbox same hierachy):

si co --hostname=... --port=... --nolock --batch --yes c:\Library\LibPart1\*.*

 

error Message:

Checking out...
*** MKS125408: c:\..*.* is not a valid member name.

 

Can anyone show me a solution how i can checkout the files in the sandboxfolder in version 11.1?

 

I hope to get help here

 

Thank you

 

ingo

3 REPLIES 3

Hi Ingo,

 

I'd suggest opening up a Support case with PTC Integrity support, as they should be able to assist you with this.  I'm not sure exactly what you're trying to do based off your posting here, as it's not that clear.  I don't see any "si co" command in your examples here.

 

 

on changing the original pathes  and  host and port i make a copy past error.

I have corrected it.

If you're trying to check out everything, the "si co" command does not accept *.*

If you don't specify a membername, then the command applies to all sandbox members, which it sounds like, is what you want.

Announcements