Unable to Install SMS Client Software with VSAFE

 Last reviewed: April 23, 1997
Article ID: Q129550

The information in this article applies to:
  • Microsoft Systems Management Server versions 1.0 and 1.1

SYMPTOMS

If you install Systems Management Server client software on a computer running Windows 3.1, and VSafe was started from the AUTOEXEC.BAT file, WIN.INI LOAD= entry, WIN.INI RUN= entry, or from the Startup group, several error messages appear referring to the Systems Manager Server client software files. The following is one of the error messages that appears on a Windows 3.1 computer: 

   SMS caused a fatal exception error at <mem address> in VXD VMM

WORKAROUND

To work around this problem, change the entry of VSafe to "VSAFE /8-" (without the quotation marks), or:

  1. Clean boot to MS-DOS and run VSafe (Detect and Clean).

  2. Run SMSLS and exit Windows. You may receive an error message from VSafe. Choose the Update option and reboot the computer.

  3. When the following error message appears, run VSafe (Detect and Clean) again: 

          Access to the specified device, path or file is denied.

  4. If you receive errors during verification of files, choose Update on all files and reboot the computer.

  5. Install the Systems Management Server client software again.

Additional query words: prodsms sms wfw wfwg
Keywords : kbnetwork ntinterop smsconfig
Version : 1.0 1.1
Platform : WINDOWS

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: April 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.