Microsoft KB Archive/296632: Difference between revisions

From BetaArchive Wiki
(importing KB archive)
 
(No difference)

Latest revision as of 17:36, 18 July 2020

Article ID: 296632

Article Last Modified on 1/7/2006



APPLIES TO

  • Microsoft FrontPage 2000 Standard Edition



This article was previously published under Q296632

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry


SUMMARY

This article describes how to install and configure the following Microsoft Visual SourceSafe 6.0 installation:

  • A server computer that stores a central database that uses Visual SourceSafe 6.0.


-and-

  • A Web server computer with a Web site linked to the central database and with the content under source control.


MORE INFORMATION

To configure Visual SourceSafe, follow these steps in the order shown. You must have a server computer with the following configuration:

Microsoft Windows NT 4.0 or Microsoft Windows 2000
Internet Information Server (IIS) 4 or IIS 5
Microsoft FrontPage Server Extensions 2000

NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

Install and Configure Visual SourceSafe on a Server Computer

  1. Log on to the computer by using the local Administrator account.
  2. Install Visual SourceSafe 6.0 on the server computer.


NOTE: During Visual SourceSafe Setup, on the To choose the installation you want, click one of the following buttons page, click SHARED DATABASE SERVER.

  1. Restart the computer, and then click Finish.
  2. Start Visual SourceSafe 6.0 Admin.
  3. On the Tools menu, click Create Database.
  4. In the Create new VSS Database in box, type the location of a new database folder, for example, type C:\Program Files\Microsoft Visual Studio\VSS\VSS_DB, and then click OK. If you are prompted to create the folder, click Yes All.
  5. Click OK. You receive a message that states, "Database Creation Complete." Click OK, and then click Browse.


NOTE: For more security-related or logging options, click Options on the Tools menu.

  1. On the Users menu, click Open SourceSafe Database.
  2. In the Find Database dialog box, in the Look in list, click the database that you created in step 7 of "Install and Configure Visual SourceSafe on a Server Computer," and then click Open.
  3. In the Browse for Visual SourceSafe Database dialog box, click OK, and then click Open.
  4. On the Users menu, click Add User.
  5. In the User name box, type the name of a Domain user, for example, Administrator.
  6. In the Password box, type the Domain user's password (for example, password), and then click OK.
  7. Follow steps 11 through 13 to create additional users.


NOTE: When you create a new user, that user is created for the currently open database. To allow a user access to another database, open that database in Visual SourceSafe Administrator, and then create the user.

  1. On the Users menu, click Exit.

Share the Visual SourceSafe Program Files and Database

  1. Share the folder in which the Visual SourceSafe program files are stored. To do this, follow these steps:
    1. Start Windows Explorer, and then navigate to the Visual SourceSafe program files location. For example C:\Program Files\Microsoft Visual Studio\VSS.
    2. In the Folder list, right-click the VSS folder, and then click Sharing on the shortcut menu that appears.
    3. In the Vss Properties dialog box, on the Sharing tab, click Shared As, then click Apply, and then click OK.

      NOTE: To set Share level permissions on the shared VSS folder, click Permissions.
  2. Follow steps a through c to share the Visual SourceSafe database folder that you created in step 7 of "Install and Configure Visual SourceSafe on a Server Computer."

Create a New Project

  1. Start Microsoft Visual SourceSafe 6.0. If your database is not opened, follow these steps:
    • If the Visual SourceSafe Login dialog box appears, click Browse.


-or-

    • On the File menu, click Open SourceSafe Database.
  1. In the Open SourceSafe Database dialog box, click Browse.
  2. In the Find Database dialog box, in the Look in list, click the database folder that you created in step 7 of "Install and Configure Visual SourceSafe on a Server Computer" (srcsafe.ini appears in the File name box), and then click Open.
  3. In the Browse for Visual SourceSafe Database dialog box, click OK.
  4. In the Open SourceSafe Database dialog box, click Open.
  5. In the Visual SourceSafe Login dialog box, in the Username and Password boxes, type the name and password of a user that you created in step 13 of "Install and Configure Visual SourceSafe on a Server Computer," and then click OK.

On the File menu, click Create Project. In the Create Project in $/ dialog box, type a name for the project in the Project box (for example, Project1), and then click OK. On the File menu, click Exit.

Configure a Web Server to Access the SourceSafe Database

  1. On a Web server that will access the centralized Visual SourceSafe database, use an Administrator account to log on to the computer.
  2. Click Start, and then click Run.
  3. In the Open box, type \\servername\VSS\NetSetup.exe (where servername is the name of the server on which you installed Visual SourceSafe in step 2 of "Install and Configure Visual SourceSafe on a Server Computer," and then click OK. Visual SourceSafe NetSetup starts and installs Visual SourceSafe.

Link a Web Site to the Remote VSS Database

  1. Log on to the Web server computer from step 1 of "Configure a Web Server to Access the SourceSafe Database" by using an account with the same user name and password that you created in step 13 of "Install and Configure Visual SourceSafe on a Server Computer" (for example, Administrator and password).
  2. Start Internet Services Manager.
  3. Expand *servername (where servername is the name of the server computer).
  4. Right-click the Web site that you want to link to the Visual SourceSafe database (for example, Default Web Site), and then click Properties on the shortcut menu that appears.
  5. On the Directory Security tab, click Edit under Anonymous Access and Authentication Control.
  6. In the Authentication Methods dialog box, click to select the Anonymous access and Basic Authentication check boxes. Click to clear the Digest Authentication and Integrated Windows Authentication check boxes. Click OK.
  7. On the Server Extensions tab, click to select the Enable authoring check box, and then click Use external in the Version control list. If the Source Control Project dialog box does not appear, click Edit.
  8. In the Source Control Project dialog box, type the project that you created in step 3 of "Create a New Project" (for example, $/Project1), and then click OK.
  9. Click Apply, and then click OK.

How to Troubleshoot Integration Issues

Redirector in Srcsafe.ini File

Each Web server computer that accesses the remote VSS database must have a redirector line in the Srcsafe.ini initialization file.

  1. On the Web server computer, search for the Srcsafe.ini file.
  2. Right-click srcsafe.ini, and then click Open on the shortcut menu that appears.

    Windows Notepad opens the Srcsafe.ini file.

    Srcsafe.ini should contain a line similar to the following

    #include \\Servername\Shared_database_name\SRCSAFE.INI

    where Servername is the server on which the shared VSS database is stored and where Shared_database_name is the shared folder in which the shared database is stored.

Multiple SourceSafe Initialization Files

When a Web server that accesses a remote database has more than one Srcsafe.ini file, use the following steps to determine which file is the one that is used to access the remote database.

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.

  1. Click Start, and then click Run. In the Open box, type Regedit, and then click OK.
  2. In Registry Editor, click My Computer.
  3. On the Edit menu, click Find.
  4. In the Find dialog box, type ssapi.dll, click to select the Data check box, and then click Find Next.

    In the right pane, a Data value for the (Default) entry similar to the following appears:

    C:\Program Files\Microsoft Visual Studio\VSS\win32\SSAPI.DLL

  5. In Windows Explorer, navigate to the folder location in which the win32\SSAPI.DLL file is located as displayed in the Registry entry. For example:

    C:\Program Files\Microsoft Visual Studio\VSS

  6. In this folder, right-click the srcsafe.ini file, and then click Open on the shortcut menu that appears.

    The file is opened in Notepad.
  7. If Visual SourceSafe is directed to a database that is located on the local computer, items similar to the following appear in the file:

    Data_Path = data
    Temp_Path = Temp

    If Visual SourceSafe is directed to a remote database, a line similar to the following should appear in the file

    #include \\Servername\Shared_database_name\SRCSAFE.INI

    where Servername is the server on which the shared VSS database is stored and where Shared_database_name is the shared folder in which the shared database is stored.


REFERENCES

For additional information about integrating Visual SourceSafe, click the article numbers below to view the articles in the Microsoft Knowledge Base:

171116 HOWTO: Enable VSS Integration with FrontPage and Visual InterDev


239083 FP2000: FrontPage Features That Require Server Extensions White Paper


247683 PRB Error 'FrontPage Server Extensions on This Web Do Not Support Getting Previous Versions'



Additional query words: front page

Keywords: kbinfo KB296632