PRB: Installation Conflict w/C Run-Time Library (MSVCRT20.DLL)

 Last reviewed: May 23, 1997
Article ID: Q136286
The information in this article applies to:
  • Microsoft Visual SourceSafe for Windows, version 4.0
  • Microsoft Visual SourceSafe for Windows NT, version 4.0
  • Microsoft Visual SourceSafe for Windows 95, version 4.0
  • Microsoft Visual C++, version 4.0

SYMPTOMS

Visual SourceSafe uses the Msvcrt20.dll file during installation. If older versions of the file exist on your computer, depending on which operating system you're using, this file may conflict with the Visual SourceSafe installation.

Msvcrt20.dll is the run-time version of the C language library used by any product that was created with Microsoft Visual C++ version 2.x. Earlier versions of this file may be incorrectly installed on your system, which can also create a conflict during installation.

You may see one of the following messages: 

   Setup cannot open the destination file
   'C:\WINDOWS\SYSTEM\MSVCRT20.DLL'. The file may be in
   use by another application, or marked read-only. Close
   the application or change the file's read-only attribute
   and try again.

   Setup could not open the file
   'C:\WINDOWS\SYSTEM\MSVCRT20.DLL'. The file may be in
   use by another application.

STATUS

This behavior is by design.

MORE INFORMATION

Windows 95 uses Msvcrt20.dll as an actual part of the operating system. Windows version 3.x, Windows for Workgroups version 3.1x, and Windows NT version 3.x all require that Msvcrt20.dll be installed in the \Windows\System directory. The Visual SourceSafe installation program can recognize the operating system and installs Msvcrt20.dll as needed.

However, it is possible that earlier versions of Msvcrt20.dll may be installed on the computer. If an application is loaded and using Msvcrt20.dll when you attempt to install Visual SourceSafe, the installation gives an error message and asks you if you want to continue or not. In this case, shut down all other application, and then continue with the installation.

Msvcrt20.dll only used by the Visual SourceSafe setup program. Therefore, any potential conflict can also occur in the future when using Setup to add or remove Visual SourceSafe components, reinstall Visual SourceSafe, or uninstall Visual SourceSafe. To avoid these conflicts, shut down other applications before installing Visual SourceSafe for the Server or Custom install options.

That Msvcrt20.dll is located in the correct directory based on the operating system you are using. Assuming you installed the operating system in the \Windows directory, the following shows where the Msvcrt20.dll file is placed:

  • Windows 3.x: \Windows\System
  • Windows 95: \Windows\System
  • Windows NT: \Windows\System32

The C run-time library (Msvcrt20.dll) comes with a number of products, specifically either Visual C++ or programs created by Visual C++. The following shows the versions of Msvcrt20.dll that ship with Microsoft Products. These may be the source of an installation conflict. 

   Product                 Version of Msvcrt20.dll
   -----------------------------------------------
   Visual C++ 2.0          2.00.000
   Visual C++ 2.1          2.10.000
   Visual C++ 2.2          2.11.000
   Visual SourceSafe 4.0   2.11.000
   Windows 95              2.11.000

Additional query words: FAQ Q&A
Keywords : kbsetup SourceSafe SRCSAFE ss3 ssafe vbwin
Version : 4.0
Platform : WINDOWS
Issue type : kbprb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.