Cannot install Opera 3 client, rollback kicking in

Hi James,

I have seen this happen when attempting to uninstall the client and reinstall it (for OperaII but I guess they are similar?). The notes we have on this are as follows:-

Checked the event log and the error below appears:-

Description:

Faulting application name: MsiExec.exe, version: 5.0.9600.16384, time stamp: 0x52158c02 Faulting module name: VFP6T.DLL, version: 6.0.8961.0, time stamp: 0x399d6138 Exception code: 0xc0000005 Fault offset: 0x0000e71a Faulting process id: 0x17c Faulting application start time: 0x01cfa02228ed9532 Faulting application path: C:Windowssyswow64MsiExec.exe Faulting module path: C:WINDOWSsystem32VFP6T.DLL Report Id: 66c79660-0c15-11e4-be81-fcf8aebe6bfc

To Resolve

Try renaming VFP6T.dll (in C:WindowsSysWOW64).

Uninstall Opera.

Reinstall Opera (the reinstall should recreate the dll file).

UPDATE: This has also occurred when trying to install Opera II clients on Windows 8 PC's. The VFP6T.dll does not exist on the PC. To resolve copy this file from another computer with Opera installed and then install the client.

Cheers,
Alex

Also, I have had to copy the VFP6T.dll from another working computer which has also resolved.

andy-parker

Hi James

I have had this before and I found that for me it was a permission issue on the Pegasus shared folder and the user need to take ownership of the folder.

i have also uninstalled the client and remove all the folder and files and scan registry for Pegasus and remove any reference. this also fixed the issue for me

hope this helps

Andy

The VFP6T problem should not happen with the current versions of Opera 3 and Opera 2 as the particular item that required Visual FoxPro 6 DLLS has now been updated to use VFP9 DLLS.

We had a similar problem recently that turned out to be due to an issue with a recent Microsoft security update to the Windows Installer Service: support.microsoft.com/.../3072630

If that update is installed, Installshield/MSI installations with certain custom action scripts will fail. The link above mentions a registry change to temporarily work around this, however we had to uninstall KB 3072630 entirely before the installation worked.

Hi

I have had rollback on other platforms and have got round it as follows:

You may need to create the registry key first.

Please use the following workarounds: - Reboot the PC to ensure that there isn't a previous installation still running which requires a reboot to complete. - Install all available Windows Updates (should resolve in the majority of cases) - Disable the windows rollback feature using a registry key as follows: To disable rollback for per-computer installations, set DisableRollback to 1 under the following registry key: HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsInstaller Data Type REG_DWORD Remember to re-enable the registry key after the installation
Hope that of some help.
However Domain/Local admin is v. important on TS installs – again how relevant depends on NOS.

Regards
Graham

Hi,

I tried the disable rollback registry key, but this just aborted the install, so a number of the dll's were not registered, and Opera crashed when logging in. For the server I had this on last week, I eventually found a simple fix, which I would be curious if it works for other installs as well.

I set the compatibility mode (see below) of the “Pegasus Opera 3 Client.msi” file, and ran this instead of Setup.exe, and the install went all the way through, without any issues.

Hope this works for you.

Trevor

Hi Guys, many, many thanks for all the suggestions. The prize goes to Alan Bourke with the winning suggestion of uninstalling KB 3072630, then a server reboot. :-) Once again, thanks for all the contributions.

Regards

James

Glad you got it sorted James. Regarding the registry change to disable rollback, I would really advise against that because as Trevor said you don't get a properly installed Opera. Unfortunately in every situation where I've had this rollback issue it's been a case of creating verbose logs from the installer and poring through those.

Yes, I would definitely agree Alan. When we first encountered "rollback, we discovered that you could disable this....got all excited, thinking it would just install it....then realised you were just installing a shafted version of the client! So I dont really entertain that. I was curious to know how you discovered it was the KB article - what did you use? Im not familiar with Verbose. Once again, really appreciated the suggestion(s). James

If memory serves it is running the SETUP.EXE from the prompt with

/L*V "example.log"

Then I look through the log for the .MSI file that SETUP.EXE uses returning an error code and from that see what component of the install causes the problem. Then I just hit Google and trawl that to see if anyone else has had the issue.

Morning all,

I am having this exact issue with a Windows 8.1 PC. The Opera II client just will not install and keeps rolling back.

The event viewer reports this as

Faulting application name: MsiExec.exe, version: 5.0.9600.16384, time stamp: 0x52158c02 Faulting module name: VFP6T.DLL, version: 6.0.8961.0, time stamp: 0x399d6138 Exception code: 0xc0000005 Fault offset: 0x0000e71a Faulting process id: 0x17c Faulting application start time: 0x01cfa02228ed9532 Faulting application path: C:Windowssyswow64MsiExec.exe Faulting module path: C:WINDOWSsystem32VFP6T.DLL Report Id: 66c79660-0c15-11e4-be81-fcf8aebe6bfc

I have tried the following:-

1. Logging on as an administrator to run the install
2. Copying the VFP6T.dll from another PC and registering it
3. Setting share permissions on the Opera share to 'everyone' read, write and modify.
4. Setting compatibility on the Pegasus.msi and installing (as suggested above)
5. Checked to make sure KB 3072630 is not installed (it isn't). Tried creating the registry key in the article anyway.
6. Using the Microsoft Fixit utility to check for installer issues. Could not use this because Opera has never been installed on this PC so the program was not listed.
7. Created an installer log as suggested above but have no idea what I'm looking for in it.

Does anyone have any other ideas?

Thanks,
Alex

I am fairly sure recent versions fixed this issue by updating the Opera DLL in question to be VFP9, removing the need for VFP6 runtimes. So maybe an upgrade is the easiest approach.

Thanks Alan. I can certainly suggest this!

Have you tried disconnecting all external devices from your PC while the client upgrade runs? When I have a external monitor connected the client upgrade always rolls back!

Simon

Strange one Simon!
I have received an update from Pegasus confirming this is a bug in the version of Opera II they are running and they have suggested disabling rollback via the registry key. This was the only thing I didn't try and it wasn't recommended! I will try that now, failing that will have to upgrade them.
Thanks all.