RTC clients cannot work on the same sandbox under Windows 7
Hello
Eclipse and Visual Studio client 3.0 cannot work simultaneously on the same sandbox under Windows 7 (64bits). They do it perfectly well under Win XP.
Step to reproduce:
-Run the Eclipse client and load a workspace
-Run the Visual Studio and load the same workspace in the same sandbox so as to track it in the Pending Changes view.
A dialog box pops up saying:
Either client works OK alone in that sandbox.
Has anyone seen that behaviour?
Eclipse and Visual Studio client 3.0 cannot work simultaneously on the same sandbox under Windows 7 (64bits). They do it perfectly well under Win XP.
Step to reproduce:
-Run the Eclipse client and load a workspace
-Run the Visual Studio and load the same workspace in the same sandbox so as to track it in the Pending Changes view.
A dialog box pops up saying:
Starting the SCM daemon (C:\Program Files (x86)\IBM\Rational Team Concert Client for Microsoft Visual Studio IDE\3rd Party\scmtools\eclipse\scm.exe) on d:\myworkspacepath returned errors: Sandbox(es) locked by an unknown process.
Problem running daemon start:
Failed to lock all sandboxes. Could not lock Status INFO: com.ibm.filesystem.client code=0 Unable to lock file d:\myworkspacepath\.jazz5\.jazzlock null.
Either client works OK alone in that sandbox.
Has anyone seen that behaviour?
4 answers
Having two different IDE's (or even, two different instances of the same
IDE) access the same sandbox at the same time seems like asking for
trouble (overwriting each other's metadata), so it sounds to me like
Windows 7 is doing the right thing, and that WinXP is being overly
permissive.
Visual Studio team: What was intended here?
Cheers,
Geoff
On 12/21/2010 7:38 AM, yannjazz wrote:
IDE) access the same sandbox at the same time seems like asking for
trouble (overwriting each other's metadata), so it sounds to me like
Windows 7 is doing the right thing, and that WinXP is being overly
permissive.
Visual Studio team: What was intended here?
Cheers,
Geoff
On 12/21/2010 7:38 AM, yannjazz wrote:
Hello
Eclipse and Visual Studio client 3.0 cannot work simultaneously on the
same sandbox under Windows 7 (64bits). They do it perfectly well under
Win XP.
Step to reproduce:
-Run the Eclipse client and load a workspace
-Run the Visual Studio and load the same workspace in the same sandbox
so as to track it in the Pending Changes view.
A dialog box pops up saying:
Starting the SCM daemon (C:\Program Files (x86)\IBM\Rational Team
Concert Client for Microsoft Visual Studio IDE\3rd
Party\scmtools\eclipse\scm.exe) on d:\myworkspacepath returned
errors: Sandbox(es) locked by an unknown process.
Problem running daemon start:
Failed to lock all sandboxes. Could not lock Status INFO:
com.ibm.filesystem.client code=0 Unable to lock file
d:\myworkspacepath\.jazz5\.jazzlock null.
Either client works OK alone in that sandbox.
Has anyone seen that behaviour?
Having two different IDE's (or even, two different instances of the same
IDE) access the same sandbox at the same time seems like asking for
trouble (overwriting each other's metadata), so it sounds to me like
Windows 7 is doing the right thing, and that WinXP is being overly
permissive.
Visual Studio team: What was intended here?
Cheers,
Geoff
On 12/21/2010 7:38 AM, yannjazz wrote:
Hello
Eclipse and Visual Studio client 3.0 cannot work simultaneously on the
same sandbox under Windows 7 (64bits). They do it perfectly well under
Win XP.
Step to reproduce:
-Run the Eclipse client and load a workspace
-Run the Visual Studio and load the same workspace in the same sandbox
so as to track it in the Pending Changes view.
A dialog box pops up saying:
Starting the SCM daemon (C:\Program Files (x86)\IBM\Rational Team
Concert Client for Microsoft Visual Studio IDE\3rd
Party\scmtools\eclipse\scm.exe) on d:\myworkspacepath returned
errors: Sandbox(es) locked by an unknown process.
Problem running daemon start:
Failed to lock all sandboxes. Could not lock Status INFO:
com.ibm.filesystem.client code=0 Unable to lock file
d:\myworkspacepath\.jazz5\.jazzlock null.
Either client works OK alone in that sandbox.
Has anyone seen that behaviour?
Hi Geoffrey
According Sreerupa's post in topic http://jazz.net/forums/viewtopic.php?t=11261, it seems that it's more than intended and we need this feature for our Java/C# developments.
If running two instances of the same IDE on the same sandbox is asking for some trouble, what about opening two VS solutions on the same sandbox? Is it such a rare use case?
Yann