Hi,
We created a package which we use to install our application on Win 2008 R2 server, 64 bit.
We defined MS SQL Server Express R2 x64 as a pre-requisite which will install as a feature. However, to install SQL Server, the .NET feature must be enabled on Win 2008 R2.
To detect a missing .NET framework on the server we defined as search condition as follows:
Criteria: Registry key does not exist
Value: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5
Then we use the search criteria to control the execution of a custom action under InstallExecuteSequence->Begin. The custom action enables the .NET Framework feature on the server using the following command:
`[System64Folder]ServerManagerCmd.exe -install NET-Framework –restart`
During installation on a system which does not have the .NET framework feature enabled, the following happens:
1. The installer correctly identifies that the .NET feature is missing and runs the custom action to enable the feature. This is successful as we can see the feature appear in the feature list for the server.
2. The installer starts the installation of the MS SQL Server which fails complaining that the .NET framework is required.
However, if we restart the installation (and this time the .Net framework feature is already enabled from the first run), then the installer install MS SQL Server correctly.
Is there a way to find out why the installation package fails to install the SQL Server right after it enables the .NET Framework feature? For some reason the SQL Server install fails to detect the .NET Framework during the first run of the installation.
Thank you
Emil
FOLLOW US
Get the latest news in Application Packaging