Website is not getting created in IIS - limited edition of InstallShield

Question

I am using Limited Edition of InstallShield 2015 with Visual Studio 2015.

I have configured Internet information Services settings as shown below, but website is not getting created in IIS.

My IIS version is: 10.0

Here is the IIS settings inside InstallShield

Note: Source code is successfully copies [INSTALLDIR] of destination computer but it's not getting mapped with IIS.

Updates

I see only declaration related to IIS, but not used anywhere in log!

     Property(S): PROGMSG_IIS_CREATEAPPPOOL = Creating application pool %s
     Property(S): PROGMSG_IIS_CREATEAPPPOOLS = Creating application Pools...
     Property(S): PROGMSG_IIS_CREATEVROOT = Creating IIS virtual directory %s
     Property(S): PROGMSG_IIS_CREATEVROOTS = Creating IIS virtual directories...
     Property(S): PROGMSG_IIS_CREATEWEBSERVICEEXTENSION = Creating web service extension
     Property(S): PROGMSG_IIS_CREATEWEBSERVICEEXTENSIONS = Creating web service extensions...
     Property(S): PROGMSG_IIS_CREATEWEBSITE = Creating IIS website %s
     Property(S): PROGMSG_IIS_CREATEWEBSITES = Creating IIS websites...
     Property(S): PROGMSG_IIS_EXTRACT = Extracting information for IIS virtual directories...
     Property(S): PROGMSG_IIS_EXTRACTDONE = Extracted information for IIS virtual directories...
     Property(S): PROGMSG_IIS_EXTRACTDONEz = Extracted information for IIS virtual directories...
     Property(S): PROGMSG_IIS_EXTRACTzDONE = Extracted information for IIS virtual directories...
     Property(S): PROGMSG_IIS_REMOVEAPPPOOL = Removing application pool
     Property(S): PROGMSG_IIS_REMOVEAPPPOOLS = Removing application pools...
     Property(S): PROGMSG_IIS_REMOVESITE = Removing web site at port %d
     Property(S): PROGMSG_IIS_REMOVEVROOT = Removing IIS virtual directory %s
     Property(S): PROGMSG_IIS_REMOVEVROOTS = Removing IIS virtual directories...
     Property(S): PROGMSG_IIS_REMOVEWEBSERVICEEXTENSION = Removing web service extension
     Property(S): PROGMSG_IIS_REMOVEWEBSERVICEEXTENSIONS = Removing web service extensions...
     Property(S): PROGMSG_IIS_REMOVEWEBSITES = Removing IIS websites...
     Property(S): PROGMSG_IIS_ROLLBACKAPPPOOLS = Rolling back application pools...
     Property(S): PROGMSG_IIS_ROLLBACKVROOTS = Rolling back virtual directory and web site changes...
     Property(S): PROGMSG_IIS_ROLLBACKWEBSERVICEEXTENSIONS = Rolling back web service extensions...

Resolved

After adding APPLICATION inside WEBSITE issue has been resolved. Seems like just having WEBSITE in InstallShield is not enough.

Check the setup.exe command line I updated below. – Stein Åsmul Feb 28 '18 at 14:01 — Stein Åsmul, Feb 28 '18 at 14:01

Stein Åsmul · Answer 1 · 2020-01-07T23:38:13.843

1

Improved?: Different ways to create and interpret MSI logs.

Nice effort to create a comprehensible question, but I am afraid you forgot the most important part: what does the log file say? Please update your question with details.

I am adding this as an answer, and I will "evolve" it once we get more information.

Here is my standard blurb on logging for you for a start:

Logging your MSI-Install

Here is how to log your install (silent install):

msiexec.exe /I "C:\Installer.msi" /QN /L*V "C:\msilog.log"

or for a setup.exe:

Setup.exe /v"/l*v C:\msilog.log /QN"

Quick Parameter Explanation:

/I = run regular installation sequence
/QN = run completely silently
/L*V "C:\My.log" = verbose logging at specified path

If this is confusing try installsite.org's logging FAQ - how to create a log file for your installation.

Once you have a log, you can search for "value 3" in the log file as explained by Rob Mensching here. In your case the install seems to have completed successfully, so you need to look for warnings and suppressed errors as well.
This article from Robert Macdonald - from the long-since dissolved Windows Installer Team - is highly recommended as a practical look at MSI logging: How to Interpret Windows Installer Logs.
- There is a broken link in that blog to a PDF / Word file with an annotated MSI log in it. Here it is resurrected from WayBack Machine.
Wilogutl.exe - the Microsoft SDK MSI log viewer. Not the greatest thing, but has its uses. Discussion of its use.

Some Links:

Does anyone know a good MSI Log Viewer? (cross-linking)
The full range of msiexec.exe command line options. Here is the technet version.

edited Jan 07 '20 at 23:38

answered Feb 28 '18 at 11:21

Stein Åsmul

34,628
23
78
140

What project type is this? Installscript MSI? Installscript (legacy non-MSI)? Basic MSI? go `Project => Settings... => Type field` - it should say the project type. I added the command line above that you can use to enable logging for a `setup.exe` install that is MSI-based. – Stein Åsmul Feb 28 '18 at 13:59
Yes, Its InstallShield MSI. Log generated. I have updated the log. Log is huge. How can I upload? – kudlatiger Feb 28 '18 at 14:04
Most people seem to use https://www.dropbox.com for log file upload, I have never used it myself unfortunately. Did you search for "**value 3**" in the log file as suggested above? Also try to search for "Error" and maybe "IIS". In Installshield, are the IIS components added to a proper feature? You can see component / feature assignment in "Setup Design". You can also go to the "Components" view and check if there are any red exclamation icons (component is not assigned to any features)? – Stein Åsmul Feb 28 '18 at 14:12
There is no "error", no "value 3". Code is successfully copied to destination folder but IIS is not creating the website. I doubt it's some mapping issue in configuration. – kudlatiger Feb 28 '18 at 14:24
OK, have you tried the setup on another box? Just to eliminate any machine-specific issues? I am not familiar with the LE editions of Installshield. [**The WiX toolkit**](https://stackoverflow.com/a/25005864/129130) (free, open source) may give you more flexibility for IIS installations. Fiddly to set up, but great when you get it working (full flexibility & control). [**Sample**](https://www.codeproject.com/Articles/115036/Creating-WIX-Installer-for-ASP-NET-Web-Application) (not tested by me, looks OK). – Stein Åsmul Feb 28 '18 at 14:34
Let me give a try. keep you posted. – kudlatiger Feb 28 '18 at 14:36
Let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/165976/discussion-between-stein-asmul-and-codetoshare). – Stein Åsmul Feb 28 '18 at 14:36
Resolved.After adding APPLICATION inside WEBSITE issue has been resolved. Seems like just having WEBSITE in InstallShield is not enough. – kudlatiger Feb 28 '18 at 17:04
@codetoshare, so glad to hear that your issue is solved, you can add a reply and mark it, that will help other community members to easier search this helpful information, thanks. – Sara Liu - MSFT Mar 01 '18 at 09:16

score 1 · Answer 2 · answered Jul 23 '18 at 09:46

1

I created another website outside default website in InstallShield Evaluation version 2010. I changed the TCP Port Number to 8080.

answered Jul 23 '18 at 09:46

Barshan Das

3,451
3
27
44

kudlatiger · Accepted Answer · 2018-03-02T03:05:51.197

0

This issue has been resolved by adding a Application inside Website.

Seems like just having Website in Configure the Target System->Internet Information Services is not enough.

Reason: InstallShield Limited Version does not support creating website outside default web sites.

edited Mar 02 '18 at 03:05

answered Mar 01 '18 at 09:38

kudlatiger

2,355
3
30
67

Website is not getting created in IIS - limited edition of InstallShield

3 Answers3

Logging your MSI-Install

Linked