PRB: "Unable To Register ... Isfp.exe" Error When Installing VI

Last reviewed: December 19, 1997
Article ID: Q177069
The information in this article applies to:
  • Microsoft Visual InterDev, version 1.0

SYMPTOMS

One of the following error occurs during setup of Visual InterDev:

   Unable to register the devstudio ... isfp.exe /regserver

   -or-

   "Object 850 - SyncEXECalloutCAH - called

   Setup has encountered a problem in launching the following command line:

   D:\Program Files\DevStudio\VIntDev\isfp\bin\isfp.exe /regserver.

   If you have a system directory that contains a % sign, or the directory
   names *starts* with a space (i.e. 'C:\win95\ system'), then setup will
   fail. Please restart setup and ensure your system directory name does
   not contain the aforementioned problems. Setup will now abort... Failed
   to launch process:
   {OK}"

CAUSE

At this time, the conditions that cause this behavior are unknown.

RESOLUTION

There are two possible workarounds to this problem:

  • Install Visual InterDev into a folder whose pathname does not contain a space.
  • Modify the Istudio.stf file that setup creates during the installation process.

Workaround 1

If you don't mind installing Visual InterDev into a folder that does not have a space in its pathname, this workaround is the easiest. An example of a pathname containing a space is "C:\Program Files\DevStudio." Installing into a folder without space (for example, "C:\DevStudio\VIntDev") will complete the installation process properly.

Workaround 2

Use this workaround if you must install into a folder containing a space in its pathname:'

  1. Launch Windows Explorer.

  2. From the View menu, select Option, then choose the View tab.

  3. Select "Show All Files" option then click OK.

  4. Launch Visual InterDev setup again.

  5. Before clicking Continue from the "Welcome to the Microsoft Visual InterDev installation program" dialog box, switch to Windows Explorer (using ATL-TAB).

  6. Find your last physical hard drive. For example if your hard drive is on drive C: and drive D:, then it's probably your D: drive. Then look for the directory ~msstfqf.t, it probably located with within a directory called ~mssetup.t.

  7. Find a file called Istudio.stf.

  8. Set the permission so you can write to it.

  9. Edit this file with any text editor.

  10. Find the lines that contain the following information. NOTE: the line number might be different for a localized version.

          850      reg_isfp.exe      CustomAction
             "msistcah.dll,SyncEXECalloutCAH,%s\isfp.exe /regserver"  %840
    
    

  11. Add six quotation marks before the %s, add four quotation marks after .exe, add two quotation marks after the word /regserver. See the following example.

          850      reg_isfp.exe      CustomAction
             "msistcah.dll,SyncEXECalloutCAH,""""""%s\isfp.exe""""
          /regserver"""
          %840
    
    

  12. Save the changes.

  13. Switch back to your setup (using ALT-TAB).

  14. Continue your setup.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

REFERENCES

For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site:

   http://support.microsoft.com/support/vinterdev/

Keywords          : kberrmsg
Technology        : kbInetDev
Version           : WINDOWS:1.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: December 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.