Microsoft KB Archive/140114

How to Install When Setup Fails on Novell

PSS ID Number: Q140114 Article last modified on 03-21-1996

4.00 | 4.00

WINDOWS | WINDOWS NT

= SUMMARY =

Visual Sourcesafe setup sometimes fails when installing to a Novell server. The step-by-step procedure provided in this article shows how you can install Visual SourceSafe after you receive a Setup error.

= MORE INFORMATION =

You can install Visual Sourcesafe to a Novell server by following the steps outlined below. This procedure consists of removing the installation from the server, installing to a local machine, copying the local installation to the server, and deleting the local installation.

Step-By-Step Procedure

 * 1) Run Setup from the compact disc or floppy disks, and choose to uninstall Visual Sourcesafe from the client and the server.
 * 2) Remove any remnants of the Visual Sourcesafe installation (directories and files) on the local machine.
 * 3) Run Setup from the compact disc or floppy disks, and click Server install to install Visual Sourcesafe on the local computer.
 * 4) Copy this installation on the server. Caution: If there is an existing SourceSafe installation, do not copy the new installation to the old directory because the copy procedure overwrites the old data directory. The copy procedure should be to a new directory and the old data directory should then be copied or moved to the new SourceSafe directory. You can then run DDCONV on the data directory if it is necessary to upgrade the data directory to a later SourceSafe version.
 * 5) Check this installation by running the appropriate Ssexp.exe file.
 * 6) Run Setup from the compact disc or floppy disks and uninstall Visual SourceSafe on the local machine.
 * 7) Delete all remnants of Visual SourceSafe on the local machine.
 * 8) Run Netsetup from the server to install the client and register it with Visual Basic or other products that are integrated with Visual SourceSafe.

NOTE: When you run the Uninstall procedure, some critical files are not erased. This prevents an accidental deletion. The directory is preserved, and if users have been added to the installation, the directories for users and files created by the SSADMIN program are also maintained. In addition, the Setup directory and the Srcsafe.ini, Users.txt, and Mscreate.dir files are preserved. All other files are deleted. If you run the Uninstall procedure and find that you need to reinstall Visual SourceSafe, reinstall back to the same location. Only customizations to the Ss.ini files for the guest and administrator users are lost.

Installing Over Older Versions
If you have an older version of SourceSafe on your server, use the Visual SourceSafe Server Setup to install Visual SourceSafe 4.0 directly on top of the existing SourceSafe installation. Visual SourceSafe creates a new directory structure, converts your database to the new format if necessary, and installs the new executables so that all existing user configurations, projects, and files are intact.

Notes About Upgrading

 * Back up your SourceSafe database before upgrading. The installation process converts your existing database into a new format. If there are problems during conversion, you will need a backup to return to your previous database.
 * Make sure all users exit SourceSafe before installing a new version.
 * If users have copies of the SourceSafe executables on their computer hard disks, they need to use the Network Setup to copy the new SourceSafe over the old, after the server setup is completed.
 * The SourceSafe directory structure and file names have changed for Visual SourceSafe 4.0, so the icons in your Windows Program Manager for SourceSafe 3.X will not work with Visual SourceSafe 4.0. New icons are installed during the setup process, pointing to the correct new program locations.

= REFERENCES =

For further information on related topics, read the Readme.wri on the distribution disks or compact disc.

Additional reference words: 4.00 error code 997 vss KBCategory: kbusage kbtshoot kb3rdparty KBSubcategory: SourceSafe ============================================================================= Copyright Microsoft Corporation 1996.