Problems installing Opus

Frequently asked questions.
User avatar
jon
GPSoftware
Posts: 7412
Joined: 04 Nov 2004, 02:40
OS: Windows 10 64-bit
Opus: Latest Beta
Location: Melbourne
Contact:

Problems installing Opus

Postby jon » 29 May 2011, 17:14

See also: Installer says XP SP3 is required on a later OS version

Directory Opus uses the industry standard InstallShield installer. Despite InstallShield's ubiquity and $3000 price-tag, there are still sometimes problems and conflicts with it.

Below is a list of issues that people have encountered with the Directory Opus installer, and how to solve them.


  • The installer gets stuck and stops making progress, typically around 70%.

    If you open Task Manager you may find one or more ISBEW64.exe processes stuck in the task list.

    If you have a program called Airfoil installed then it may be to blame, although newer versions are probably fixed as we have not heard of this problem in some years (as of 2016).

    Airfoil allows you to pipe audio to Apple iOS devices which act as wireless speakers, but it has also been known to cause conflicts with some installers and other software.

    We recommend that you uninstall Airfoil, then reboot and try the Opus installer again. You can probably reinstall Airfoil afterwards, but remember that you may need to remove it each time you install/update Opus or other software, at least unless/until Airfoil is fixed to prevent the conflict.


  • While installing Opus, you get an error message similar to this:

    Feature transfer error

    Feature: Program Files
    Component: Program Files
    File:
    Error: Access is denied.


    This error is not InstallShield's fault, but the error message is not particularly helpful either.

    The error is usually caused by one of two related problems:

    1. An existing shortcut to Directory Opus on your desktop cannot be replaced.

      This is usually because the shortcut's read-only attribute has been set. It can also be due to file permissions.

      This is the easiest case to deal with. If there is an existing Directory Opus shortcut on your desktop, delete it and run the installer again.

    2. The Public Desktop (or, if you are on Windows XP, All Users Desktop) folder has incorrect permissions.

      The folder should allow Administrator accounts to create files but if that is not the case then the installer will fail when it tries to add a shortcut to the public desktop.

      (If you search the web for "Feature transfer error", the same error affects lots of different installers but it is not clear what causes the folder permissions to go wrong in the first place. Possibilities include moving or sharing system drives between Windows installs and incorrectly applying a recursive permissions change to the root of the system drive.)

      The folder permissions for the Public Desktop folder should give Administrator full control (example screenshot) and should not deny any permissions to your own username. You should not modify the folder permissions unless you know what you are doing, as doing so incorrectly can result in problems (like this one :)). Ask for help if you need it.
    If you want to confirm that either of these issues are the problem, you can use a tool like Process Monitor. Process Monitor will show the failure as an Access Denied error when opening a shortcut (.lnk file) to the desktop (example screenshot).


  • After upgrading to a new major version of Opus (e.g. Opus 9 to Opus 10), you get an error similar to this:

    The procedure entry point XXXXXX could not be located in the dynamic link library dopuslib.dll


    First, make sure that you rebooted after installing the new version. If you still get the error after a reboot then, unfortunately, you have struck a fairly rare problem where, for some reason, the installer does not replace some of the old files. So far, the only reliable way we have found to fix this is to completely uninstall Opus and then reinstall it again.

    The disadvantage of this is that if you completely uninstall Opus you will lose your configuration. There are a few ways to deal with this:

    • If you already have a backup of your configuration, you can just restore this once the new major version is reinstalled.

    • You can try reinstalling the old version (e.g. Opus 9) first, then make a backup of your configuration, and then uninstall the old version and install the new version (e.g. Opus 10).

    • You can make a manual backup of your configuration folder. The usual location varies depending on Windows version:
      • C:\Users\<Your Name>\AppData\Roaming\GPSoftware\Directory Opus (newer Windows versions)
      • C:\Documents and Settings\<Your Name>\Application Data\GPSoftware\Directory Opus (older Windows versions)
    • There is also a 'global' configuration folder but you should not normally need to back this up unless you had switched Opus into 'shared' configuration mode:
      • C:\ProgramData\GPSoftware\Directory Opus (newer Windows versions)
      • C:\Documents and Settings\All Users\Application Data\GPSoftware\Directory Opus (older Windows versions)

  • During the installation, you get an error similar to this:

    Error Code: -5006 : 0x80030005
    Error Information:
    >Kernel\CABFile.cpp (651)
    >SetupNew\setup.cpp (570)
    PAPP:Directory Opus
    PVENDOR:GPSoftware (http://www.gpsoft.com.au <http://www.gpsoft.com.au> <http://www.gpsoft.com.au>)
    PGUID:5D4F167D-CCC8-413E-A6EE-F2FABBBBF50D
    $17.0.714PAK
    @Windows 7 / Server 2008 R2 Service Pack 1 (7601)
    IE Version: 9.0.8112.16421


    This seems to be caused by a bug in InstallShield. A method to solve this is as follows:

    • On a 32-bit (x86) system,
      • In Explorer, double-click My Computer
      • Double-click Local Disk (C:)
      • Double-click the Program Files folder
      • Double-click the Common Files folder
      • Locate the InstallShield folder.
      • If found, right-click the folder and select Delete
      • Go back to C:\
      • Double-click the Program Files folder
      • Double-click the Installshield Installation Information folder

        If you do not see the Installshield Installation Information folder then the folder is hidden:
        • From the menu bar, select Tools > Folder Options
        • Click the View tab
        • Select Show Hidden files and folders
        • Click OK and then double-click the Installshield Installation Information folder.
      • Locate the folder ending in 12EF1
      • Right-click the folder and select Delete
      • Close all Web pages and programs
      • From the desktop, select Start > Run
      • Enter %TEMP% and click OK
      • Delete all the files in this temp folder.
    • On a 64-bit (x64) system,
      • In Explorer, double-click My Computer
      • Double-click Local Disk (C:)
      • Double-click the Windows folder
      • Double-click the SysWOW64 folder
      • Locate the InstallShield folder.
      • If found, right-click the folder and select Delete
      • Go back to C:\
      • Double-click the Program Files (x86) folder
      • Double-click the Installshield Installation Information folder

        If you do not see the Installshield Installation Information folder then the folder is hidden:
        • From the menu bar, select Tools > Folder Options
        • Click the View tab
        • Select Show Hidden files and folders
        • Click OK and then double-click the Installshield Installation Information folder.
      • Locate the folder ending in BF50D
      • Right-click the folder and select Delete
      • Close all Web pages and programs
      • From the desktop, select Start > Run
      • Enter %TEMP% and click OK
      • Delete all the files in this temp folder.

    Once you have completed these steps, reboot and try installing Opus again.


  • Another possibility is that the installer was not downloaded completely. See How to check for a corrupted installer or main program.

Return to “Directory Opus FAQs”