Install fails at Publish - Error 1935

[jwosen]

Install fails at Publish. Error message is not enlightening.

First project. Running eval version. Target install has one .exe and a handful of .dlls and data files.

Does the following make any sense?

PublishFeatures: Feature: MainFeature
MSI (s) (08:50) [16:06:19:025]: Executing op: FeaturePublish(Feature=Kvaser_Driver_Installation,,Absent=2,Component=Au@d-MmyF945`qH@[v0(,O`,RaHW6AM3mSC3B1.A)
PublishFeatures: Feature: Kvaser_Driver_Installation
MSI (s) (08:50) [16:06:19:041]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
Action 16:06:19: PublishProduct. Publishing product information
MSI (s) (08:50) [16:06:19:041]: Executing op: CleanupConfigData()
MSI (s) (08:50) [16:06:19:041]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\27360D3E4CFCD264CBE6D5A66916471B\Patches 3: 2
MSI (s) (08:50) [16:06:19:041]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=1,Remove=0)
MSI (s) (08:50) [16:06:19:041]: Note: 1: 1402 2: UNKNOWN\Products\27360D3E4CFCD264CBE6D5A66916471B\Patches 3: 2
MSI (s) (08:50) [16:06:19:041]: Executing op: ProductPublish(PackageKey={70D2C3D1-C234-491B-8B14-955C5E11F58F})
1: {E3D06372-CFC4-462D-BC6E-5D6A966174B1}
MSI (s) (08:50) [16:06:19:041]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:041]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:041]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:041]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:041]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:041]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:056]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:056]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:056]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:056]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:056]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B 3: 2
MSI (s) (08:50) [16:06:19:072]: Executing op: UpgradeCodePublish(UpgradeCode={1E257896-5779-467D-BEAC-8C110335371C})
MSI (s) (08:50) [16:06:19:072]: Executing op: SourceListPublish(,,DiskPromptTemplate=[1],,NumberOfDisks=1)
MSI (s) (08:50) [16:06:19:072]: Note: 1: 1402 2: UNKNOWN\Installer\Products\27360D3E4CFCD264CBE6D5A66916471B\SourceList 3: 2
MSI (s) (08:50) [16:06:19:087]: Executing op: ProductPublishClient(,,)
MSI (s) (08:50) [16:06:19:087]: Executing op: SourceListRegisterLastUsed(SourceProduct={E3D06372-CFC4-462D-BC6E-5D6A966174B1},LastUsedSource=C:\Documents and Settings\osenjw\Application Data\The Toro Company\ToroDiagnostics\install\)
MSI (s) (08:50) [16:06:19:087]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (08:50) [16:06:19:087]: Specifed source is already in a list.
MSI (s) (08:50) [16:06:19:087]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (08:50) [16:06:19:087]: Machine policy value 'DisableBrowse' is 0
MSI (s) (08:50) [16:06:19:087]: Machine policy value 'AllowLockdownBrowse' is 1
MSI (s) (08:50) [16:06:19:087]: Adding new sources is allowed.
MSI (s) (08:50) [16:06:19:087]: Set LastUsedSource to: C:\Documents and Settings\osenjw\Application Data\The Toro Company\ToroDiagnostics\install\.
MSI (s) (08:50) [16:06:19:087]: Set LastUsedType to: n.
MSI (s) (08:50) [16:06:19:087]: Set LastUsedIndex to: 1.
MSI (s) (08:50) [16:06:19:087]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=4645897)
MSI (s) (08:50) [16:06:19:103]: Note: 1: 1935 2: {D49B4352-A569-404C-86D6-8F6B44D07F1A} 3: 0x80131043 4: IAssemblyCacheItem 5: Commit 6: ToroDiagnostics,Version="1.2.0.0",PublicKeyToken="cf9e8a11eac5ec95",Culture="neutral",ProcessorArchitecture="X86"
Error 1935. An error occurred during the installation of assembly component {D49B4352-A569-404C-86D6-8F6B44D07F1A}. HRESULT: 0x80131043. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: ToroDiagnostics,Version="1.2.0.0",PublicKeyToken="cf9e8a11eac5ec95",Culture="neutral",ProcessorArchitecture="X86"
MSI (s) (08:50) [16:07:28:477]: Product: ToroDiagnostics -- Error 1935. An error occurred during the installation of assembly component {D49B4352-A569-404C-86D6-8F6B44D07F1A}. HRESULT: 0x80131043. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: ToroDiagnostics,Version="1.2.0.0",PublicKeyToken="cf9e8a11eac5ec95",Culture="neutral",ProcessorArchitecture="X86"

[jwosen]

Seems like projects without .dlls publish without issue.

[Cosmin]

Hi,

I'm not sure why you are encountering this behavior. Can you please send us the .AIP (project) file you are using to support at advancedinstaller dot com so we can investigate it?

Regards,
Cosmin

[Cosmin]

Hi John,

It seems that one of your assemblies (ToroDiagnostics.exe) has an incorrect configuration file. So Windows Installer returns FUSION_E_UNEXPECTED_MODULE_FOUND when trying to install it.

Try investigating your assembly configuration to determine if its information is correct. This forum thread may also help:
http://www.advancedinstaller.com/forums ... f=2&t=7723

Regards,
Cosmin

[jwosen]

I am not sure which of the following changes fixed the issue. However, they all are acceptable changes.

A colleague of mine uses AI. He sat down with me and made multiple changes to my solutions/projects:
1) moved my project to release rather than debug configuration
2) moved my application from a "three VS solutions using five VS projects" to "one VS solution using five VS projects"
3) added filters in AI for the .pdb, .xls, ... files

The build is now installing as expected.

[Bogdan]

Hi,

I'm glad to hear everything is working as expected. I am not sure which of the changes you've done helped you,
maybe the release version included the required information in the configuration file and Windows Installer was able to install the assembly successful.

Regards,
Bogdan