Hi,
New in install aware - need some help please. Here is my problem:
I am trying to repack and create a silent install -- from a Legacy MSI installer originally created using install shield. i am using a Eval version of InstallAware_18_with_runtime.exe full version. also installed all features.
when I use MSI/MSM import wizard, I get the project created. But at build I get an error:
.......
Building Project: XXService Broker
Output Folder: c:\users\smadmin\documents\XXservice broker\Release\SingleDeployment Type: Compressed Single Self Installing EXE
Code Signing: Disabled
Compression: Best
Compiler Variables: BUILDMODE=SFX,LANGUAGE=English,"TITLE=XXService Broker",TARGETDIR=$TARGETDIR$,IADIR=C:\PROGRA~2\INSTAL~2\INSTAL~1,PROJDIR=c:\users\smadmin\DOCUME~1\UGSERV~1,IAVER=18.08
###
Cleared output folder c:\users\smadmin\documents\XXservice broker\Release\SingleBuilt plug-in action Windows Installer
Built plug-in action .NET Framework
Built plug-in action (Un)Install MSI Setup
Built plug-in action Windows Installer
Built plug-in action .NET Framework
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.Service.EXT
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.Service.FKY
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.Service.KCI
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.Service.TAB
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.ServiceProvider.EXT
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.ServiceProvider.FKY
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.ServiceProvider.KCI
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.ServiceProvider.TAB
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.version.EXT
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.version.FKY
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.version.KCI
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\Create Scripts\v1\dbo.version.TAB
Copied file C:\Users\smadmin\Documents\XXService Broker\ServiceBrokerDatabase\ScriptIndex.xml
Error during build: Unable to compile MSI action install assembly
--------------
When I use PackageAware, and use capture setup, the process captures the setup activity OK and creates the project. when building I get this error:
-----------
Building Project: XXservicebroker
Output Folder: c:\users\smadmin\documents\XXservicebroker\Release\SingleDeployment Type: Compressed Single Self Installing EXE
Code Signing: Disabled
Compression: Default
Compiler Variables: BUILDMODE=SFX,LANGUAGE=English,TITLE=XXservicebroker,TARGETDIR=$TARGETDIR$,IADIR=C:\PROGRA~2\INSTAL~2\INSTAL~1,PROJDIR=c:\users\smadmin\DOCUME~1\XXSERV~2,IAVER=18.08
###
Cleared output folder c:\users\smadmin\documents\XXservicebroker\Release\SingleBuilt plXX-in action (Un)Install MSI Setup
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.Service.EXT
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.Service.FKY
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.Service.KCI
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.Service.TAB
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.ServiceProvider.EXT
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.ServiceProvider.FKY
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.ServiceProvider.KCI
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.ServiceProvider.TAB
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.version.EXT
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.version.FKY
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.version.KCI
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\Create Scripts\v1\dbo.version.TAB
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerDatabase\ScriptIndex.xml
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerWebServices\bin\XXXXXXXXXX.Base.dll
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerWebServices\bin\XXXXXXXXXX.Base.ServiceBroker.WebServices.dll
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerWebServices\bin\XXXXXXXXXX.Base.ServiceBroker.dll
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerWebServices\Global.asax
Copied file C:\Program Files\XXXXXXXXXX\XXServiceBroker\ServiceBrokerWebServices\Service_v1.asmx
Copied file C:\Windows\inf\ASP.NET_4.0.30319\aspnet_perf.h
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0000\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0009\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0001\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0404\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0005\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0006\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0007\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0008\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\000B\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\000C\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\000D\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\000E\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0010\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0011\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0012\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0013\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0014\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0015\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0416\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0019\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\001D\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\001F\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0804\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\0816\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET_4.0.30319\000A\aspnet_perf.ini
Copied file C:\Windows\inf\ASP.NET\aspnet_perf.h
Copied file C:\Windows\inf\ASP.NET\0000\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0009\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0001\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0404\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0005\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0006\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0007\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0008\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\000B\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\000C\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\000D\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\000E\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0010\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0011\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0012\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0013\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0014\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0015\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0416\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0019\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\001D\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\001F\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0804\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\0816\aspnet_perf2.ini
Copied file C:\Windows\inf\ASP.NET\000A\aspnet_perf2.ini
Copied file C:\Windows\SysWOW64\PerfStringBackup.INI
Error during build: No files matching pattern "C:\Windows\System32\inetsrv\config\applicationHost.config"
Build error : Error during build: No files matching pattern
-
- Posts: 1
- Joined: Thu Nov 27, 2014 3:47 am
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Build error : Error during build: No files matching patt
Dear User,
The error message "Unable to compile MSI action install assembly" usually occurs when trying to install non-strongly names assemblies.
You may try to replace the Install Assembly command with Install Files and if the assembly is not strong named, you cannot install it into the GAC in any way.
That assembly should be listed in the Assemblies page of the project (Setup Architecture node from the left tree pane in IA Design IDE).
The other error instead referred to a missing file.
Please note that PackageAware should be used on clean-machines while capturing setups. A clean machine is a plain installation of Microsoft Windows with no other software installed (and ideally, no optional Windows components installed either).
I suggest to you to use always the MSI/MSM import wizard when you have to convert an MSI package.
Hope this helps you.
Regards.
The error message "Unable to compile MSI action install assembly" usually occurs when trying to install non-strongly names assemblies.
You may try to replace the Install Assembly command with Install Files and if the assembly is not strong named, you cannot install it into the GAC in any way.
That assembly should be listed in the Assemblies page of the project (Setup Architecture node from the left tree pane in IA Design IDE).
The other error instead referred to a missing file.
Please note that PackageAware should be used on clean-machines while capturing setups. A clean machine is a plain installation of Microsoft Windows with no other software installed (and ideally, no optional Windows components installed either).
I suggest to you to use always the MSI/MSM import wizard when you have to convert an MSI package.
Hope this helps you.
Regards.
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Who is online
Users browsing this forum: No registered users and 141 guests