Using SourceAnywhere VSS version 6.3 I'm experiencing a problem for which I must find a workaround.

If a user has a file checked out on MachineAlpha and performs a Get Latest on that same file on MachineBravo, it flags the file as non-Read Only on MachineBravo.

How can I prevent the SourceAnywhere Client from incorrectly flagging this file as writeable?

Hi Mjones,

Thanks for reporting the issue.

Our test team has confirmed this issue to be a bug. The dev team will work out a fix today or tomorrow. When it's ready, Allan or I'll send you an email with the fix.

Regards,

Hi Mjones,

Our team has sent the fix to your email. Please check.

Regards,

Hello Catherine,

Thank you for the quick response.

I just tested the fix you sent me (exe properties shows as version 6.3.1.613) and there is no change in behavior.

I found another problem which is likely related.

My Visual Studio Project on MachineA is showing that I have foo.cpp checked out (red checkmark in the solution explorer)

However, the file is NOT checked out on MachineA; foo.cpp is checked out on MachineB

Hi Mjones,

Thanks for the update.

Are you using Microsoft VSS 6.*? As you know, Dynamsoft SourceAnywhere for VSS interacts with MSVSS's database through MSVSS's API. The API of MSVSS 6.* has some limitations which means the "fix" won't work for it.

If that's the case, would you mind upgrading your VSS to 8.* and test again?
I checked with R&D and they confirmed that this related issue can be fixed as well for MSVSS 8.*.

Regards,

On the system where SourceAnywhere for VSS Server is installed:
HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32
C:\Program Files\Microsoft Visual SourceSafe\ssapi.dll
Looking at the version properties for that dll I see
8.0.50727.1551
{QFE.050727-1500)

Hi Mjones,

Our team were able to reproduce the issue after the meeting they had with you. They are working on a fix. When it's ready, Allan or Tom will send it to you.

Regards,