Office: Can't Run SETUP /A with Office Manager

Last reviewed: April 2, 1997
Article ID: Q110963
4.00 WINDOWS kbsetup kbusage kbnetwork kberrmsg

The information in this article applies to:

  • Microsoft Office version 4.0
  • Microsoft Word for Windows, versions 6.0, 6.0a

SUMMARY

You cannot use a network administrative setup (SETUP /A) to install Microsoft Office Manager (included in the Microsoft Office 4.0 Upgrade package). Using the SETUP /A command to run either MSOFFICE.EXE or SETUP.EXE from the network server, may produce any of the following error messages:

   Could not Open the file named: 'F:\SETUP\SETUP.INI'

   Could not open the file named: 'F:\SETUP\ACMSETUP.EX_'

   Cannot find CTR3DV.DLL

   Cannot find SETUP.LST

MORE INFORMATION

A network administrative setup of an application is designed to install a copy of the application to a network server. From a network installation, Setup can then be run from a workstation to install the files necessary to run the application on the workstation.

If you run the SETUP /A command from the Microsoft Office Manager disk, included with the Microsoft Office 4.0 Upgrade, the Setup program will appear to be successfully completed. However, when you run Setup from a workstation, you may receive errors in the following situations when you run the SETUP.EXE or MSOFFICE.EXE files from the server:

  • When SETUP.EXE on the server is run from the workstation, the following error may appear

          Could not open the file named: 'F:\SETUP\SETUP.INI'
    

    where F is the network drive specified during administrative setup.

  • If SETUP.INI is moved to the 'F:\SETUP\SETUP.INI' directory and SETUP.EXE is run again, the following message will be displayed

          Could not open the file named: 'F:\SETUP\ACMSETUP.EX_'
    

    where F is the network drive specified during administrative setup.

If MSOFFICE.EXE is run from the workstation or the server, you receive the following error message:

   Cannot find CTR3DV.DLL

WORKAROUNDS

To work around this problem, do the following.

  1. Create a directory on the server for the Microsoft Office Manager.

  2. Copy the files from the Microsoft Office Manager disk to that directory.

  3. From the workstation, log on to the network server directory created in step 1.

  4. Run SETUP.EXE to install the Microsoft Office Manager to the workstation.

- or -

Have each user copy the files to a separate diskette from which they can install and provide their own custom name and corporation information.

To obtain a copy of the full Microsoft Office 4.0 Standard which does support administrative installations, call Microsoft End User Sales at (800) 426-9400. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, see the Microsoft World Wide Offices Web site at:

   http://www.microsoft.com/worldwide/default.htm


KBCategory: kbsetup kbusage kbnetwork kberrmsg
KBSubcategory:

Additional reference words: 4.00 officeinterop word6 6.00 6.00a MOM
Keywords : kberrmsg kbnetwork kbsetup kbusage
Version : 4.00
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 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.