We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

blaze
Posts: 16
Joined: Wed May 23, 2007 7:16 pm
Location: Macrovision
Contact: Website

Merge Module and regsvr32

I am using AI 7.1.3. I have a DirectShow component that will no longer register during install. I believe that the failure is with the merge module installation of the MS Visual Studio CRT libraries. If I install an older release of my product than I can manually register & unregister the DirectShow component. When I uninstall the older release I can no longer register the DirectShow component.

Looking at the installation log I note that the older release creates a new directory within the winsxs directory. The new release log shows these property steps skipped and uses an existing winsxs directory to attempt installing the MS Visual Studio CRT libraries.

I don't understand the machinations, but I think that my debugging to this state is sound.
Attachments
RegistrationFailure.zip
This contains the production and test AI config files and sample installation logs.
(239.2 KiB) Downloaded 438 times
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Merge Module and regsvr32

Hi,

Can you please specify which file has this problem? Also, is the file already registered in the "winsxs" folder when the new version runs?

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
blaze
Posts: 16
Joined: Wed May 23, 2007 7:16 pm
Location: Macrovision
Contact: Website

Re: Merge Module and regsvr32

The file that fails to register is Sky2PCAVSrc.ax
MSI (s) (70:90) [14:21:10:984]: Executing op: RegSelfReg(File=Sky2PCAVSrc.ax,FileID=Sky2PCAVSrc.ax)
MSI (s) (70:90) [14:21:11:234]: Product: TVGOS TES8 Framework -- Error 1904. Module C:\Program Files\TVGOS TES8 Framework\TechniSat ATSC Tuner\SkyNet DirectShow\Sky2PCAVSrc.ax failed to register. HRESULT -2147010895. Contact your support personnel.
The DirectShow component Sky2PCAVSrc.ax is a 3rd party tool. It uses two dll that are installed with the ax file and MSVCR80.dll. It is access to MSCVR80.dll that appears to be the problem.

I don't understand how merge modules work. If I search the WINDOWS directory for MSCVR80.dll when my product is not installed I'll find two instances within subdirectories of the winsxs directory. Manually attempting to register the Sky2PCAVSrc.ax will fail. This implies to me that the two instances of the MSCVR80.dll are only available to some installed software due to some os magic. If I install the 1.5.4 release of our software than a new subdirectory and instance of MSCVR80.dll is added to the winsxs directory. I can then register/unregister the Sky2PCAVSrc.ax component. When I uninstall the 1.5.4 release the 3rd instance of MSCVR80.dll is removed from the winsxs directory and I loose the capacity to register the Sky2PCAVSrc.ax component. The new install kit built with AI 7.1.3 does not create a 3rd subdirectory and instance of MSCVR80.dll to the winsxs directory. The install then fails when registering the Sky2PCAVSrc.ax component.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Merge Module and regsvr32

Hi,

I'm not sure why this happens. The file registrations from the merge module are not handled by Advanced Installer (they use special custom actions). You can try testing the packages on other machines. If the behavior is the same you can try contacting Microsoft.

When a package is built all the merge modules in its project are merged with it (the tables in the merge modules are merged with the ones in the MSI). This shouldn't affect the merge module behavior.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
blaze
Posts: 16
Joined: Wed May 23, 2007 7:16 pm
Location: Macrovision
Contact: Website

Re: Merge Module and regsvr32

Hello Cosmin,

I am at a loss as to why the behavior changed, but after more effort I found that the 3rd party components require the Visual C++ 2005 Redistribution kit to be installed and my C++ components require the Visual C++ 2005 merge modules to be installed. Only if both are modes are covered will the 3rd party code and my code work.

Note: I did verify that AI 6.8 would still trigger the creation of a new sub-directory in winsxs. That the new AI 7.x is more efficient in somehow not triggering Windows Installer to populate another winsxs sub-directory with VS libraries appears to have been an interesting, but unimportant diversion.

Thank you for all your assistance!
--Blaze

Return to “Common Problems”