InstallAware

Hi,

we are using InstallAware15 to deploy an application which installs an instance of SQL 2008R2 Express during setup.
Some customers report problems regarding the sql setup. Their logs from the Setup Bootstrap says

The specified value for setting 'MEDIALAYOUT' is invalid. The expected values are: None Core Advanced Full

According to the MSDN http://msdn.microsoft.com/en-us/library ... .105).aspx the /MEDIALYOUT is no known parameter for command prompt installation.
I found this MSDN community post http://social.msdn.microsoft.com/Forums ... f6114fae0/.
Does this apply for the libraries provided in my current InstallAware version? If not, can you provide corresponding packages?

the customers installed .NET Framework versions are typically this:
Microsoft .NET Framework 1.1
Microsoft .NET Framework 4 Client Profile
Microsoft .NET Framework 4 Client Profile DEU Language Pack

Thanks in advance!

Dear User,

honestly, I never had any experience with a similar error.

The SQL InstallAware runtime embeds internally the exact same package available from Microsoft distribution ... and we don't have any additional library or package.

For what I seen by the MSDN community post and where it is also available a workaround, the problem seems to be caused by the presence on the target OS of the NET 4.0 runtimes.

Regards

FrancescoT wrote: honestly, I never had any experience with a similar error.

Neither did we.

For what I seen by the MSDN community post and where it is also available a workaround, the problem seems to be caused by the presence on the target OS of the NET 4.0 runtimes.

The problem is we can't expect our customers to follow this workaround. Most of our customers are not from the IT sector and doing more than clicking "Finish" in an installer is out of the question.

That would mean to manually edit the filebag that is to be included during the compilation of the setup in order to provide a working setup to our customers?

Dear User,

Yes if this the case, you should modify the default behavior of the installation script to meet your requirements.

Anyway before to proceed as above, I may suggest you to verify if exist any other workaround available and also to contact Microsoft support directly.

Regards