Office Err: Setup Parse Error in Initialize Pass

Last reviewed: September 9, 1996
Article ID: Q111262
The information in this article applies to:
  • Microsoft Office for Windows, versions 4.0, 4.2, 4.3

SYMPTOMS

When you run the Microsoft Office Setup program, you may receive the following error message after Setup searches for installed components:

   Setup parse error in initialize pass
   Object Id 40: appmaindlg object:
   Unable to retrieve bitmap

If you upgrade Microsoft Office with Microsoft Word 6.0a and you run the Microsoft Office Setup program in maintenance mode to add or remove a Microsoft Word component, you may receive one of the following error messages:

   Setup Parse Error In Initialize Pass
   Object id 137: CustomAction Object:
   Bad procedure data value

   -or-

   Setup Parse Error In Initialize Pass
   Object ID 28: Dialog Object:
   Bad Hidden Data Value

CAUSE

These error messages may appear if you have lost allocation units on your hard drive, or if there is an older copy of the SETUP.STF file on your hard drive.

NOTE: The Setup Parse Error also occurs if you use the MS-DOS EXPAND.EXE utility to decompress the file CTL3D.DL_, instead of using the decompression utility DECOMP.EXE that is included with Microsoft Office.

WORKAROUNDS

  • To avoid these error messages, use the CHKDSK /f command at the MS-DOS command prompt to fix lost allocation units by doing the following:

    1. Close Microsoft Windows.

    2. At the MS-DOS command prompt, type "CHKDSK /f" (without the quotation

          marks).
    

    3. If lost allocation units are found, type "N" to avoid saving the

          errors as files on your hard drive.
    

This will fix your file allocation table. If there are many lost clusters reported, your hard drive may be fragmented and in need of optimization. You can use a hard drive utilities application to optimize your drive.
  • If the CHKDSK /F command does not correct this problem, do the following:

    1. In a text editor, such as Notepad, open your WIN.INI file.

    2. Locate the [MS Setup (ACME) Table Files] section, and find the line

          that begins with MSOFFICE.EXE. This line contains the location of the
          Microsoft Office Setup Table File, SETUP.STF, such as
          C:\MSOFFICE\SETUP\SETUP.STF. If there are multiple lines that begin
          with MSOFFICE.EXE, remark any incorrect lines out by typing a
          semicolon (;) at the beginning of each incorrect line.
    

    3. Search your hard drive for SETUP.STF files. Verify that the SETUP.STF

          file for Microsoft Office is located in the directory specified in
          the WIN.INI file.
    

          This problem can occur for example if you update Microsoft Office
          from version 4.0 to 4.2 or 4.3. The version 4.0 SETUP.STF file may
          still be on your computer, or your SETUP.STF file may have become
          corrupt.
    
  • If neither of the workarounds listed above correct this problem, rename the SETUP.STF file located in your Microsoft Office directory, and run the Microsoft Office Setup program again.


KBCategory: kbsetup kberrmsg
KBSubcategory:

Additional reference words: 4.00 4.20 4.30



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: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.