Version 3.0.0 Diff Tool Not Working

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
dan_quinn
Posts: 16
Joined: Tue Apr 13, 2004 1:44 pm
Location: San Diego, CA
Contact:

Version 3.0.0 Diff Tool Not Working

Post by dan_quinn » Wed Jan 12, 2005 8:00 pm

The Diff Tool's window is not created. I observed this problem, compared the settings to mine & made them the same, re-installed the Client... No luck.

Client Information
Vault Client Version: 3.0.0.2752
Operating System: Microsoft Windows 2000 Professional
Service Pack: 4.0
OS Version: 5.0.2195
Total Physical Memory: 511.43 MB
Time Zone: (GMT-08:00) Pacific Time (US & Canada); Tijuana

Server Information
Vault Server Version: 3.0.0.2752
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 0.0
OS Version: 5.2.3790
Timezone: (GMT-06:00) Central Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: )
Dan in San Diego

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Wed Jan 12, 2005 8:16 pm

Does the diff tool come up outside of Vault? (it is the sgdm.exe executable in the client folder)

dan_quinn
Posts: 16
Joined: Tue Apr 13, 2004 1:44 pm
Location: San Diego, CA
Contact:

Post by dan_quinn » Thu Jan 13, 2005 11:46 am

Uncovered the culprit...


After updating to Vault client 3.0, I received an error when trying to perform a file difference. The error was that the difference tool (SGDM.exe) was unable to locate a required DLL (MSVCR71.DLL). I searched for the file on my system and found it in the C:\....\Microsoft.NET\Framework\v1.1.4322 folder. The SourceGear website has at least one message posted in the forums section describing this problem and a work-around. The work-around is to copy the MSVCR71.DLL file from the Microsoft.NET folder to the Vault Client folder (C:\Program Files\SourceGear\Vault Client). This work-around seems to fix the problem. I would recommend applying this work-around since SourceGear indicated that it would be some time before an installation fix is available.



The forum message can be read at: http://support.sourcegear.com/viewtopic.php?t=2411.
Dan in San Diego

Post Reply