Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: Integration of Visual SourceSafe, Visual InterDev, and FrontPage does not succeed and the file does not appear to be under source control


View products that this article applies to.

Symptoms

If a user saves a file in Microsoft FrontPage or Microsoft Visual InterDev, the vti_sourcesafeversion line and the vti_sourcesafecookie line are removed from the file's metadata. The file is still saved to the site and the user does not receive an error message. However, the file no longer appears to be under source control.

If you view this file in Microsoft Visual SourceSafe Explorer, the file appears to be checked out to the user who saved the file. The other files in the Web remain under source control and can be checked in and checked out.

↑ Back to the top


Cause

The Rights.dat file must be read to connect to a Visual SourceSafe database. This problem occurs because the Rights.dat file is locked in use by another user.

↑ Back to the top


Resolution

To resolve this problem, obtain the latest Visual SourceSafe 6.0 service pack. For more information, visit the following Microsoft Web site:

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual SourceSafe service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Hotfix file information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version    Size       File name
   -----------------------------------------------------
   23-May-2001  17:16  6.0.92.39    199,952  Analyze.exe
   23-May-2001  17:16               295,184  Ddconv.exe
   23-May-2001  17:16               420,112  Ddupd.exe
   23-May-2001  17:16               397,072  Ss.exe
   23-May-2001  17:16  6.0.92.39     12,048  Ssadmin.exe
   23-May-2001  17:16  6.0.92.39    561,424  Ssapi.dll
   23-May-2001  17:16  6.0.92.39    498,960  Ssarc.exe
   23-May-2001  17:16  6.0.92.39     16,656  Ssexp.exe
   23-May-2001  17:16  6.0.92.39  1,135,376  Ssgui.dll
   23-May-2001  17:16  6.0.92.39    496,912  Ssrestor.exe
   23-May-2001  17:16  6.0.92.39  1,414,416  Ssscc.dll
   23-May-2001  17:16  6.0.92.39    480,528  Ssus.dll

Hotfix installation instructions

This hotfix affects all Visual SourceSafe OLE Automation by causing more retries to connect to the database. Therefore, it may take longer to receive feedback or errors.

This hotfix does not affect performance unless a file is open. Typically, if a file is open, Visual SourceSafe cannot connect to the database.

The retries occur on all logon files, including Um.dat, Rights.dat, and *.log files.

To activate this hotfix, you must modify the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\SourceSafe
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

You only have to apply this hotfix to the server computer that is running Visual SourceSafe, Microsoft Internet Information Services (IIS), and FrontPage 2000 Server Extensions from Microsoft.
  1. Verify that no users are using Visual SourceSafe, IIS, and FrontPage Server Extensions on the server computer.
  2. Open the IIS Microsoft Management Console (MMC), and then write down the status each of the services on the server computer.
  3. Close the IIS MMC.
  4. Stop the IISAdmin service:
    1. At a command prompt, type the following, and then press ENTER:
      net stop iisadmin
      You receive a message that lists the other services that must be stopped.
    2. Press Y to answer "yes."
  5. Copy all the files from this hotfix to your \VSS\WIN32 folder.
  6. Create a DWORD value that is named RetryCount in the registry under the following registry key:
    HKEY_LOCAL_MACHINE\Software\Microsoft\SourceSafe
  7. Set the RetryCount value between 0 and 100 in decimal.
  8. Start the IISAdmin service. To do this, type the following at a command prompt, and then press ENTER:
    net start iisadmin
  9. Use the list of services that you wrote down in step 2 to restart all services that were running before you stopped the IISAdmin service.
Notes
A RetryCount value of 0 causes an instant retry. This setting is the same as not applying the hotfix.

A RetryCount value data of 100 causes 25 seconds of retries to connect to the database before the connection operation fails.

The RetryCount value data is read from the registry one time per session.

Changes to the registry during the lifetime of the session are not be automatically used. You must restart the IISAdmin service for Visual SourceSafe to use the new value.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: KB299900, kbssafe600fix, kbqfe, kbprb, kbfix, kbautomation, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 299900
Revision : 5
Created on : 10/12/2005
Published on : 10/12/2005
Exists online : False
Views : 219