Dynamsoft Forums

Hello,

I would like to report a bug in SourceAnywhere for VSS: at least in certain situations, in the History window, the items corresponding to labeling actions, have a wrong comment, more specifically they have the comment of the item above.

Steps to reproduce the problem: Add a file to a project. Then label that item and provide no comment. If the History window is opened, there is no comment for the labeling, as it should be. Then check out, modify and check in the file and provide a comment to the check in. Now open the History window: both the check in and the labeling have the same comment.

The wrong comment is also present in the History Details window for the labeling action.

Best wishes,
Alin.

Edit: I forgot to specify that I'm using the latest version, 6.2, of the Standard Edition. The client is running on a Windows XP machine, and the server is running on Windows Server 2003 R2.

Hi Alin,

Thanks for reporting the issue.

Unfortunately, I failed to reproduce the bug you mentioned. To help me pinpoint the issue, would you please let me know the following things?

1. Which version of VSS are you using?
2. Did the issue only occur on one specific VSS database?
3. Is it possible to reproduce the issue by using Visual SourceSafe (VSS) Client?

If you like, you can also contact our support team at LiveChat to have an online meeting:
http://www.dynamsoft.com/support/livehelp.aspx

Thanks.

Hello Catherine,

1. The VSS version is 6.0d.

2. The issue occurred in more than one database. After I observed the problem in one database, I used an empty "Common" database to recreate the issue following the steps I told you about.

3. No, VSS Explorer shows the correct comments.

Since a picture is worth a thousand words, I did a couple of screen shots of VSS and SourceAnywhere, that show the problem:

VSS: http://imageshack.us/photo/my-images/196/vssshot.jpg/

SourceAnywhere: http://imageshack.us/photo/my-images/571/sa4vshot.jpg/

In the first shot, you can see that the labeling action has no comment in VSS, and in the second shot, of SourceAnywhere, it does have a comment. This comment is the comment of the action that was done after the labeling action.

Best wishes,
Alin.

Hi Alin,

To better pinpoint the cause of the problem, shall we have an online meeting? If it is convenient for you, you can contact our support team via Live Help first:
http://www.dynamsoft.com/Support/livehelp.aspx

I contacted the support team via Live Help and provided them with more details. They will follow up by email.

Hi Alin,

We are not able to reproduce the problem on our side even with your database. Did you try upgrading VSS to a newer build?

Another possible cause of the problem is that your VSS API is not healthy. Below is the download link of VSS API 6.0d (Build 31222). You can back up your original SSAPI.DLL, unregister it using the command line:regsvr32 -u SSAPI.DLL. Copy the newly downloaded dll file to the installation folder of VSS and perform regsvr32 SSAPI.DLL. Afterwards, please restart SourceAnywhere for VSS Server service and try it.
http://www.dynamsoft.com/download/Suppo ... .31222.zip

Please keep me updated on this issue.

I've asked permission to upgrade VSS to 2005 on the machine where the SourceAnywhere for VSS server is installed.

Meanwhile, I've verified the ssapi.dll file and it's identical with the one from you're link. And by identical I mean I did a binary comparison of the two. And there is no other ssapi.dll file on that machine. I've even checked the registry and the HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F} key points correctly. There are no other versions of the ssapi.dll file on that machine.

I'll return with a message after I upgrade VSS to 2005, if I get the permission.

Hi Alin,

Please keep me updated on this issue.

Sure.

I forgot to tell that I did a reinstall of the SourceAnywhere for VSS server and to no avail. After I uninstalled the server, I deleted the "C:\Program Files\Dynamsoft" directory, to try and simulate a clean install. I really hoped that some weird setting I did on the server caused the problem.

You will be glad to hear that after installing Visual SourceSafe 2005, even without the updates, the problem is solved .

I also installed Visual SourceSafe 2005 Update from here:

http://www.microsoft.com/download/en/de ... spx?id=291

After a reboot, the problem remains solved.

Thanks!

Hi Alin,

Thanks for the update.

I am glad that the issue has been solved.

Should you have any further questions, please feel free to post in the forum.

Regards,