I am trying to install Houdini and receive the following error:
1607: unable to install - installshield scripting runtime.

Can anyone tell me how to fix this problem.
Thanks.

Which Windows version are you using? Note that Houdini only runs on Windows NT/2000/XP. We also recommend that you have the latest service pack installed for your software. On Windows NT, service pack 6 is required. Do you have the latest service pack installed?

edward
Which Windows version are you using? Do you have the latest service pack installed?

I am using WindowsXP professional.

How much space do you have on your C: drive? I've seen situations where the InstallShield installer will fail if you don't have enough disk space in your temp directory.

This can be caused by a missing registry entry. I have come across this before when creating installers using Installshield Developer 7 but, as I am not sure if this is the version and product that SideFx used for the Apprentice installer, I cannot say if this will fix your problem but it is worth a try.

The following is taken directly from a KB article at installshield.com and has worked for me in the past.

From the command line, cd to this folder:

C:\Program Files\Common Files\InstallShield\Driver\7\Intel 32

and then type:

IDriver.exe /regserver


Hope this helps,

Dave Carroll
Product Specialist
DevGuru.com

I attempted this fix and found the folder was C:\program files\Installshield\engine\6\intel32 and typed in IDriver.exe /regserver.
It could not find the file.

Still stuck and need to get this program installed.

Thanks

eauboy101,

Does this mean you have InstallShield Developer installed? On my computer, it is under C:\Program Files\Common Files\InstallShield\Driver\7\Intel 32. From the Start Menu, choose Run…, then find the file using the “Browse…” button. After that, add the (space) /regserver option.

Looking at the KB at installshield.com, i learned that they in fact have at least 3 causes for this error:
1. Running the setup program from a virtual drive (as defined from having created it via the SUBST command) (Windows XP only: KB #Q106766)
2. Permissions on the Windows directory may be set incorrectly (KB #Q105819). Make sure that the user that you logged in as has administrator privileges. As a minimum test, can you create files in your C:\Windows directory?
3. Not all the install information was not fully removed from a previous setup attempt (KB #Q106250). The MS website has a utility for cleaning up broken set ups, unfortunately it hasn't been updated for Windows XP yet. (In case you're curious, see the MS KB#Q238413).

Hope this helps,
-Edward

PS. Thanks Dave, for pointing out the installshield KB.

eauboy101,

One more thing. You never did tell me how much free disk space you have on your hard drive as this is also another possible cause.

Just out of interest, try installing the scripting runtime seperately. Just locate and run the ‘isscript.msi’ package to see if you get the same error.

Cheers,

Dave


PS You're welcome, Edward. The Installshield KB has helped me out a lot when debugging setups, some of which can become almost as complex as the software they are installing

Usable space on hard drive 19 gig.

I ran the isscript.msi off of the installation cd and received the error: The installer service could not be accessed. This can occur if you are in safe mode or installer is not correctly installed.

Got frusted so I tried to install on a different computer running windows 98SE and again came up with the original 1607 error message.

What the !!!!

Thanks for your help so far - appreciate it.

Ron

Ok, try running ‘instmsiw.exe’ from the CD. This will install the Windows Installer service. Then try running the Houdini setup again.

If this doesn't work, locate ‘Msi.dll’ on your machine, right-click and select Properties and then the ‘Version’ tab. This should be at least 2.0.xxxx. The version supplied on the CD is, I think, 2.0.2600.0 but there is a later version (2.0.2600.2) available from here:

http://www.installengine.com/Msiengine20/instmsiw.exe [installengine.com]

Don't know if this later version will make any difference but might be worth a try as I am running out of ideas here!

Good luck,

Dave

Checked Install CD and there is no file instmsiw.exe.

Went to the web location and downloaded the file. Executed the file and received a wrong o/s message.

Tried to go to the root of the download site but not have access authority.

Yuks

Ok, grab it from here. This is the CD1 contents listing for Houdini Apprentice on the VisLab site:

http://www.vislab.usyd.edu.au/sidefx/cd1/Windows/ [vislab.usyd.edu.au]

Sorry to be such a pain in the ass but I went to the site and downloaded instmsiw.exe and received the error message

Wrong o/s

Ron

From the command line type:

msiexec /unregister

and then:

msiexec /regserver

and then try running the (original) Houdini installer again.

I have this same problem. Also running WindowsXP Pro. Please help, I really want to dig my claws into this software and see what magical things I can do with it <cry>

Did you try what whodini suggested in his last post here?
I'm running WinXP Pro here and never had any problems. Did you read my post in this thread to see if any of them apply?

yes, I did try what whodini suggested. yes, i read the wholre thread

Make sure that you have administrative privileges to run the setup on the machine. To run InstallShield Express 3.5 SP4 setup, users need full admin privileges on Windows NT, 2000, and XP machines.
yes, I am logged on as administrator
Download and run IsScript.msi. This file internally sets the ALLUSERS property, which is known to fix the issue in some cases. After downloading the attached file, replace the IsScript.msi shipped with InstallShield Express 3.5 SP4 setup with this updated version. The file IsScript.msi can be found in the same path as InstallShield Express 3.5 SP4 Setup.exe.
I dont understand this, it wants me to replace it with an existing file? what file? all I see is a single install program and I can't unzip it
Make sure that the Installer folder in the Windows directory on the machine is not read only. The path to the installer folder is typically C:\Winnt\Installer on Windows NT, 2000, and XP machines and C:\Windows\Installer on Windows 9x and Me machines. Right-click on the Installer folder and select Properties. Make sure that it is not read only. On some machines, the Installer folder may be hidden. Before searching for this folder in the above path, make sure to show hidden files and folders in the Windows Explorer options.
No, the folder is not read only. I tried moving the installation file to C:\ and run it from there, it didnt work.
You may want to manually uninstall any previous version of InstallShield Express 3.x from the machine before installing the new version. If the uninstallation fails, use MsiCleanUp utility to uninstall the old product. You can download MsiCleanUp from MSDN at Q238413 OFF2000: Windows Installer CleanUp Utility.
dead link but i did find the windows cleanup utility. ran it and it told me “The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not crrectly installed.”
Launch the Task Manager to see if multiple instances of Msiexec.exe or IDriver.exe are running on the machine. You can launch the Task Manager by pressing Ctrl+Alt+Delete. You should have at least one instance of these files running as these engine files drive the setup. However, if you see more than one instance of Msiexec.exe or IDriver.exe, it could be the cause of the issue. If this is the case, reboot the machine and run the installation again.
hmm glad they put that bold part in or I wouldnt have noticed it… no, I don't have them running. Quick check with msconfig and no I havn't disabled them from starting, I dont even have them listed.
# Run the file InstmsiA.exe on Windows 9x or Me or InstmsiW.exe on Windows NT, 2000, or XP to install and configure the Windows Installer Service on the machine. These files can be found in the same path as Setup.exe for the InstallShield Express 3.5 SP4 setup. If the issue persists, register the file Msiexec.exe manually on the machine. To do this, run the following command-line option in the Start > Run command or command prompt of the operating system:

* Windows NT, 2000:

C:\Winnt\System32\Msiexec.exe /REGSERVER
* Windows 9x, Me or XP:

C:\Windows\System\Msiexec.exe /REGSERVER
uhhh…. something seems to be missing here, I don't have that file.
If your installation is trying to uninstall a file that is in use, the Windows Installer Service throws the File In Use Dialog. However, when you attempt to uninstall the installation via the Remove option of the Add/Remove Programs applet (ARP), the Windows Installer setup runs the uninstallation in a basic User Interface mode, which does not display the File In Use Dialog, displaying error 1607…..
definitely not the problem, I'm not trying to remove anything.


Well, I think I can safely say that my problem is I'm missing something. However, I have no idea what it is I'm missing nor where to get it.