We have a 32 bit installer to deploy a 32 bit application. We use to to deploy the application on xp/vista/windows 7 on both 32 bit as well as 64 bit platforms.
However, it gives us issues when we try the deployment on 64 bit windows 7. Our setup fails and the log shows following two errors.

Note: 1: 1310 2: 32 3: C:\Windows\Installer\39697f.msi
MainEngineThread is returning 110.

This problem occurs 3 out of 10 times.

We have also observed the following.

1. msiexec.exe on windows 7 spawns a 32 bit version of msiexec.exe to deploy 32 bit application. [it is visible in task manager as msiexec.exe*32 ]
2. We found that msiexec.exe*32 disappears [crashes?] when the deployment fails.
3. Never observed this problem with Windows 7 32 bit.

The docs for error 1310 say that the underlying error is 32, which isfile in use by another process error. It's possible that this is a 64-bit Windows timing issue where the 64-bit msiexec doesn't release the MSI file in time for the 32-bit MSI to access it.

It's not obvious why it's going tothe \Installer folder. That's where cached MSI files are stored, and Windows should go there only if the product is already installed. A fresh install usually uses the temp folder until the install is completed.

---

Phil Wilson

Hi All

Problem: Sometimes Our MSI installer is failing on the Win 7(64 bit) machine. This behavior is random.
Installer works fine after either restarting the machine or wait for some time after failure attempt.

Observation:

Successful Scenario:
Whenever Installer successful executes both versions of msiexec.exe - msiexec.exe(64 bit) and msiexec.exe*32 (32 bit) present in the Task Manager(running on machine).

Failure Scenario:
whenever Installer fails msiexec.exe*32 (32 bit version of msiexec.exe) not present in the Task Manager(not running on machine).
In this case only msiexec.exe (64 bit version of msiexec.exe) present(running on machine).

Please help to find the reason of this behavior.

Thanks in advance.

Best Regards
Harpreet

Doesn't sound like a Visual C++ problem. I think there is a Setup/Deployment forum somewhere. Search for it on the Forums Home page.

Hi sumit_pyk,

From my experience, we can follow these steps to solve the issue:
1. Press the Start Menu.
2. Type cmd in the Start Search box.
4. Type 'reg delete HKLM\SOFTWARE\Microsoft\SQMClient\Windows\DisabledSessions /va /f' and press Enter.

This is a blog talks about Repairing the Windows Installer service on a 64-bit OS:
http://blogs.msdn.com/astebner/archive/2006/07/20/673408.aspx.

Regards,
Aland Li

---

Please mark the replies as answers if they help and unmark if they don't. This can be beneficial to other community members reading the thread.

The docs for error 1310 say that the underlying error is 32, which isfile in use by another process error. It's possible that this is a 64-bit Windows timing issue where the 64-bit msiexec doesn't release the MSI file in time for the 32-bit MSI to access it.

It's not obvious why it's going tothe \Installer folder. That's where cached MSI files are stored, and Windows should go there only if the product is already installed. A fresh install usually uses the temp folder until the install is completed.

---

Phil Wilson