I've also found this problem with the VFP9 version of Installshield and solved it by removing XML 4.0 and some ActiveX controls from my project.

Enmanuel

>Chris,
>
>Thanks for the reply. I was working from last years InstallShield project (this is a once-a-year release) and converted it over to the new InstallShield format (IS does this automatically). Everything seemed fine until I started doing test installs. Anyway, I was making changes to that project to try to figure it out and nothing worked. Then I created a new one from scratch and that one didn't work, either. Then I decided to take one that was designed to install the VFP 9 runtimes only and make a copy of it and modify it as needed. This finally got it working. I'm still not sure what caused the problem, but I'm up and running now.
>
>Thanks again,
>
>Russell
>
>
>>Russell:
>>
>>Not sure if its applicable, but i have a VERY OLD version of installshield express and someone report a similar problem. They then told me that they had mucked w/ a windows temp folder setting and had entered in an invalid character value to the variable. Thats just one example, but the MSFTKB has other examples of the temp folder being a problem.
>>
>>http://support.microsoft.com/default.aspx?scid=kb;en-us;214970
>>http://support.microsoft.com/default.aspx?scid=kb;en-us;293090
>>
>>