Support Forums

Windows Installer c…
 
Notifications
Clear all

Windows Installer crashing

8 Posts
2 Users
0 Likes
5,571 Views
0
Topic starter

Hi

Since about 3 versions or so, the Windows Installer crashes on our server, whe the setup is started.
Until version 3.2.0300.1 i was able to close the error window and proceed with the installation, but this time this isn’t working.

The full Problem Signature and the corresponding Event Log Entry below are posted below.
A screen Shot of the error message is attched as well.

——-

Problem signature:
Problem Event Name: BEX
Application Name: MsiExec.exe
Application Version: 5.0.9600.19082
Application Timestamp: 5b2905a5
Fault Module Name: MSIF7FA.tmp_unloaded
Fault Module Version: 12.4.0.0
Fault Module Timestamp: 5a27eeae
Exception Offset: 00016290
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.3.9600.2.0.0.400.8
Locale ID: 2055
Additional Information 1: 1e5d
Additional Information 2: 1e5d0d2c6fec87d873489f072c940d92
Additional Information 3: 67f3
Additional Information 4: 67f33bc3119cb2aed0fda43e8253e762

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=280262

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

——-

Application Event Log:

——-

Faulting application name: MsiExec.exe, version: 5.0.9600.19082, time stamp: 0x5b2905a5
Faulting module name: MSIF7FA.tmp_unloaded, version: 12.4.0.0, time stamp: 0x5a27eeae
Exception code: 0xc0000005
Fault offset: 0x00016290
Faulting process id: 0xf7c
Faulting application start time: 0x01d4bc8b27081af2
Faulting application path: C:\Windows\syswow64\MsiExec.exe
Faulting module path: MSIF7FA.tmp
Report Id: 652979fd-287e-11e9-8117-005056abadd5
Faulting package full name:
Faulting package-relative application ID:

——-

Jacob Dixon 2019-02-04 08:38

Are you running Bitdefender? When we saw this before it was the AV running on the server doing it 

4 Answers
0
Topic starter

No, there’s currently no av installed on this server.

After the third attempt, i was able to install the update, but now have the problem, tha CloudPanel isn’t finding the database server (just like the las time).
But this time, restoring the backup settings.xml isn’t working either.

The new settings.xml contains only ythese lines:

<?xml version=”1.0″ encoding=”utf-8″?>
<cloudpanel>
<Settings>
<Database>server=LAB-DC01.lab.local\SQLEXPRESS;database=CloudPanel;uid=sa;password=Password!;</Database>
</Settings>
</cloudpanel>

 

0
Topic starter

Correction, after restoring the settings.xml and restarting iis, CloudPanel ist up and running again.

 

Jacob Dixon 2019-02-04 12:56

The upgrade should of copied the settings.xml values from the old version. It looks like since it messed up for some reason it failed on copying the settings previously. So on the third attempt did MSIEXEC fail at all?

0
Topic starter

Yes, msiexec failed three times during the installation, once right after starting the setup, then again after the first few klicks and then again after the setup finished. Appart from that, the installation seemed to have run “fine”.

As I mentioned in my first post, this allready happened at least for the previous two updates (versions 3.2.0283.2 and 3.2.0292.0).
Also, the problem with the settings.xml had allready occoured with the previous update to 3.2.0292.0 (there’s a thread about it in this forum).

Jacob Dixon 2019-02-07 14:51

We would have to connect and look because we can’t reproduce the msiexec failing during installation like what you are describing. If you want to schedule a time, please email me at jdixon@knowmoreit.com.

0
Topic starter

Since the new version is now up and running, it would probably not make much sense to look into the problems now.
But I’d be happy to contact you, should the problem recur with the next update.

Jacob Dixon 2019-02-08 10:27

Yes please. Let us know if it happens again. We will keep an eye out for other people mentioning the same thing. We have seen this issue once before but it was BitDefender blocking it. This was about a year ago.

Share: