cmd: si co... without local project.pj in another sandbox location as projectpath fails in v11.1

[ilampe]

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 viewproject --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 sam pathes this

si viewproject --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

[VladimirN]

@Jaime_Lee Please move this discussion in Integrity forum, here: https://community.ptc.com/t5/Integrity-Questions/bd-p/Integrity

[aoconnell]

Hi Ingo,

I am a bit unclear of the issue. You appear to be talking about si co command in the title but within your description of the issue you are describing viewproject commands. 

Could you please reply with a full description of your issue and could you also please send the full command that failed? 

Thanks,

Andrew

[kthierer]

Just assuming that you mixed up 'si viewproject' with 'si co'

and there is exactly one (sub)sandbox registered in the path c:\Library\LibPart1>

Im only guessing that you wanted to to something like

c:\Library\LibPart1>si resync --recurse --filter=file:*.*

or

c:\Library\LibPart1>si co --recurse --nolock --filter=file:*.*

or

c:\Some\Other\Path>si resync --recurse --filter=file:*.* -S c:\Library\LibPart1\project.pj

(in all examples --filter=file:*.* is not necessary for an all files pattern)

I would say 'si resync' fits the best for a "standard" handling of the supposed use case

with Integritys Configuration Management.

(You cant forget --nolock here 🙂 )

Regards

  Juergen

[KaelLizak]

Hello @ilampe,

Did @kthierer's response help you out with this, or are you still stuck?