- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Issues while migrating from InstallShield 2016 to 2019 R2
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Issues while migrating from InstallShield 2016 to 2019 R2
Hi,
We are now migrating projects from Installshiled 2016 premier comp to InstallShield 2019 R2PremierComp version.
We have one issue while creating IIS sites through the InstallShield. During IIS site creation, “System.web” section is being added to the server’s “applicationhost.config” file during the installation process. With this section, IIS sites are going to stopped state and we are unable to start them back because of this system.web section.
We have identified from where this “system.web” section coming, there is a new entry(Forms authentication) added in the authentication access section of IIS properties for Installshield 2019.
If I set forms authentication to “NO” then the tool is updating the applicationhost.config file as follows:
<location path="website">
<system.web>
<authentication mode="windows" />
</system.web>
<system.webServer>
<handlers accessPolicy="Read, Script" />
<directoryBrowse enabled="false" />
<asp>
<session timeout="00:20:00" />
<limits scriptTimeout="00:01:30" />
</asp>
<security>
<authentication>
<anonymousAuthentication enabled="true" />
<basicAuthentication enabled="false" />
<windowsAuthentication enabled="true" />
</authentication>
</security>
<httpLogging dontLog="false" />
</system.webServer>
</location>
If forms authentication is YES then tool updating as :
<location path="website">
<system.web>
<authentication mode="Forms" />
</system.web>
<system.webServer>
<handlers accessPolicy="Read, Script" />
<directoryBrowse enabled="false" />
<asp>
<session timeout="00:20:00" />
<limits scriptTimeout="00:01:30" />
</asp>
<security>
<authentication>
<anonymousAuthentication enabled="true" />
<basicAuthentication enabled="false" />
<windowsAuthentication enabled="true" />
</authentication>
</security>
<httpLogging dontLog="false" />
</system.webServer>
</location>
My problem now is that the below section is being added to my IIS applicatiohost.config file, sites are not starting and application installation is failing.
<system.web>
<authentication mode="Forms" />
</system.web>
If I remove manually the above section, I'm able to start the IIS site without any issues.
In earlier versions, we never saw this issue.
We have compared our IIS website settings with 2016, everything seems the same except the new feature (Farms authentication) added in 2019 InstallShield.
Could you please provide your inputs on this issue?
Thanks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Any update on this request?
Thanks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hello,
I have the same problem after upgrade projects to IS2019. Did you find a solution for this?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi,
We didn't get a reply back yet from Flexera support. We still have the same issue.
Thanks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hello, after 3 days of work, i found a solution. It's seems that it is a problem with what is wrote in web.config file because with another web.config file it's works and doesn't create the <system.web> node in
c:\Windows\System32\inetsrv\Config\applicationHost.config
So, to avoid this, i moved ISIInstall custom action after CreateFolders and before InstallFIles so web.config will not be available when msi configure webApplication and everything it's works in my case. The node will not be written in applicationHost.config
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi,
Thanks for sharing your findings.
We have tried it but no luck, still have the same issue.
Can you check the Execute sequence from the below screenshot, is I'm doing correctly?
Thanks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
yes, it is ok. For me works. It is upgrade or clean install? Did you check that no web.config already exists when ISIInstall executed? Try to put a dumy web.config to see if you have the same behaviour. In my case, ai have 3 webApp, and only 1 had the problem, it's seems to be something special in web.config
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Thanks for the update.
Do you know when Installshield 2020 will be released? I searched but i didn't find anything.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
I have the same issue, migrated from 2016 to 2019.
Now, I migrated the project from 2019 to 2020 R1 and still the same issue.
Is there an additional step to perform in 2020 R1 to fix this issue?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @banna_k ,
Good to know, that this issue is addressed in the latest 2020 release.
Currently, we are using InstallShield 2016 version? Is the upgrade path is safer for migrating my projects from InstallShield 2016 version to the latest 2020 release? Please confirm!
Thanks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @spothuri,
Thank you for your reply.
Sorry about the delayed response.
As of this post, InstallShield 2020 was released a while back.
Only if you have not yet evaluated InstallShield 2020, you can evaluate InstallShield 2020 and see if the upgrade of your projects to InstallShield 2020 works for you. We cannot guarantee that the upgrade will be seamless. There were a few InstallShield versions between InstallShield 2016 and InstallShield 2020, so you would need to test and see whether you experience any issues with the upgrade. There are migration / upgrade scenarios where starting the project from scratch is best, but we will not know until you give the upgrade a try.
Please give the upgrade a try. Does that work for you?
Please let us know if you have any questions or concerns. Thank you for your patience and cooperation.