Creating IIS applications changes the Web Site root path!

[adi]

Hello,

I have found a serious bug in IA12. Creating IIS applications changes the root path of the whole Web Site if the given application already exists.
The bug must have been introduced in IA10/IA11 since in IA9 it works good.

The result of this behavior is a completely broken Web Site / IIS.

How to reproduce the bug:
Preconditions:
- IIS7, with Web Site index 1. I haven't tested it with IIS6 yet.
- physical directory: c:\InstallAwareTest (or any else you choose)

1. Create a simple project with just two commands or use the project I attach to the ticket :

Code: Select all

Create Virtual Folder "InstallAwareTest" in IIS Site #1, pointing to physical location c:\InstallAwareTest
Terminate Installation

UPDATE: the code below updated to create IIS application and not IIS virtual directory

Code: Select all

~InstallAware Clipboard Data~
~Terminate Install~
~{ED83046B-83B4-4BFD-8210-1B3B82E437E7}~
~Create Virtual Folder~
~{FA9CDDEE-AB0A-451C-96E4-C7DDCE7188E5}~
~InstallAwareTest~
~c:\InstallAwareTest~
~FALSE~
~TRUE~
~FALSE~
~FALSE~
~TRUE~
~TRUE~
~2|~
~1|0~
~TRUE~
~Default.htm,Default.asp,index.htm,Default.aspx~
~~
~TRUE~
~TRUE~
~FALSE~
~~
~1~

2. Run the installer once - the InstallAwareTest application will be created
3. Run the installer second time - the root path of the whole Web Site will be changed to c:\InstallAwareTest. This completely ruins the Web Site. In my case we have broken two productive servers this way.

Attached three screen shots demonstrating the bug.

The state before the second run:

Initial Web Site configuration

IA12 bug - Initial Web Site configuration.jpg (33.83 KiB) Viewed 39467 times

Already existing application:

IA12 bug - Already existing application.jpg (48.03 KiB) Viewed 39467 times

The state after the second run:

Broken system

IA12 bug - Broken Web Site configuration.jpg (45.23 KiB) Viewed 39467 times

How soon can you fix this bug?

Best regards,
adi

[adi]

Example setup.exe here (I have reached the attachments limit in the first post).

New Project.zip

(1.96 MiB) Downloaded 1451 times

[giaviv]

adi,

This doesn't reproduce with the IIS template in IA.

Could you please attach your setup sources?

[adi]

adi,

This doesn't reproduce with the IIS template in IA.

Hello,

It is my fault - I am sorry. The bug can be reproduced only if you create IIS application (and not IIS Virtual Directory like in the attached example). I was testing both and attached the wrong one to the report.

Could you please attach your setup sources?

The new version of the script is attached to this post. The only difference to the previous one is to create the IIS application (security: medium pooled).

I have been able to reproduce this bug three times today, on three different machines: two Windows 2008 R2 and one Windows 7.

Best regards,
adi

[adi]

Hello,

Were you able to reproduce the problem now?

Best regards,
adi

[giaviv]

adi,

As a work around to this, you can manually remove your IIS application before entering a reinstallation - is that an option for you?

[adi]

adi,

As a work around to this, you can manually remove your IIS application before entering a reinstallation - is that an option for you?

Hello,

So you confirm the bug? The solution you proposed is not an option - I have no influence on what our customers are doing.
The easiest work around is to remove the application before creating it (in the script). This will make sure that the error doesn't occur.

But the real problem here is that it was working good in IA9. The bug was introduced in of of the IA10, IA10 or IA12. I don't want to apply the work around in all our applications.
Will you fix it?

Best regards,
adi

[giaviv]

adi,

The project you attached is a Multiple Instance sample project and has nothing to do with IIS..

[adi]

adi,

The project you attached is a Multiple Instance sample project and has nothing to do with IIS..

Hello,

Have you really taken a look at it? Here is what you should see after opening the project (I've double checked it btw.):

Project.jpg (213.85 KiB) Viewed 39407 times

As you can see - it's the standard "Multiple Instance" sample with two lines at the beginning of the script:
- the first one which creates the IIS application
- the second one which terminates the installation (there is no need to execute the rest - the bug is demonstrated in the first line).

Have you tried to compile and execute the project? Were you able to reproduce the bug?


--
adi

[sinan]

Unfortunately, the binary file you sent is a black-box - it doesn't help us diagnose the issue. You could be running any program from that binary and it might be the culprit.

So many thanks for sending us the sources, but I'm quite perplexed. When I load it up here, I see the standard Multi Instance template project. Maybe you forgot to save the project before zipping it up for us? I've attached my screen shot for your convenience.

Note that I also did test the scenario you described, and was unable to reproduce the issue as reported. Even if a virtual folder already exists, nothing wrong happens. Aviv can also send you the test project I used in my analysis.

The one thing you haven't provided is a screen shot of the actual command editor window for Create Virtual Folder, maybe that is the last missing piece of the puzzle? Or of course, the actual sources for the project file would be nice.

Another potential culprit would be, if for example, you are using an InstallAware 9 license on an InstallAware 12 installation; or something similar. That creates a totally "random" combination and will lead to innumerable strange issues, possibly like this one. So please also double-check that for us.

[adi]

Hello sinan,

Thank you for your quick answer.

When I load it up here, I see the standard Multi Instance template project. Maybe you forgot to save the project before zipping it up for us? I've attached my screen shot for your convenience.

Indeed I did something wrong (zipping before saving is most probably the reason). I am really sorry for wasting your time giaviv.
So now, I would kindly ask you to have one more look at the problem. I promise - no errors from my side this time.

First some information about the environment:
Build machine 1: Windows XP DE, InstallAware 12 with the IA12 license. Before we had IA9 on that machine.
Build machine 2: Windows 7 EN, InstallAware 12 trial. Before we had IA9, IA11 on that machine.

Test machine 1: Windows 7 EN
Test machine 2: Windows 2008 R2 EN
Test machine 3: Windows 2008 R2 EN

In both cases (build machine 1 & 2) I have been able to successfully reproduce the bug on all test machines.

Note that I also did test the scenario you described, and was unable to reproduce the issue as reported. Even if a virtual folder already exists, nothing wrong happens. Aviv can also send you the test project I used in my analysis.

I don't know if you tried to create just a virtual folder, or IIS application. The problem doesn't occur for virtual folders - only applications.

The one thing you haven't provided is a screen shot of the actual command editor window for Create Virtual Folder, maybe that is the last missing piece of the puzzle? Or of course, the actual sources for the project file would be nice.

Below I attach:
1. The screenshot of the IIS settings
2. The simplest possible project which demonstrates the problem (empty project + 2 lines of script, no more base template)
3. The binary version of the project from point 2.

To successfully reproduce the error you should execute the installer twice (the first attempt will create the IIS application, the second one will change the root path). And please remove any virtual folder with the name InstallAwareTest if you have any before doing the test.

Virtual Folder Configuration.jpg (62.49 KiB) Viewed 39390 times

I hope you will be able to reproduce the bug now.

[adi]

Hello again,

Do you have any progress in that topic? I tried to contact you directly with no luck.

Best regards,
adi

[giaviv]

Hi,

As I have indicated to you, I am unable to reproduce this problem. Could you please post specific steps to reproduce this - maybe I am doing the wrong thing?

[adi]

Hello,

This is very strange. Did you get my answer to your email and tried after that? Or my email got lost?

Anyway - from the very beginning - how to reproduce the problem:

1. Download the IISBug - sources.zip - http://forums.installaware.com/download/file.php?id=517
2. Extract the zip file somewhere on your drive
3. Start InstallAware 12. Load the project. You should see the code like below:

step3.jpg (114.65 KiB) Viewed 39139 times

4. Make sure that the folder C:\InstallAwareTest exists on your C drive
5. Make sure that the "Default Web Site" is pointing to wwwroot. Also make sure that the "Default Web Site" is using index 1 (which should be the default).

step5.jpg (21.11 KiB) Viewed 39139 times

6. Make sure that no "InstallAwareTest" exist in IIS inside "Default Web Site" (delete any applications/virtual folders with that name).
7. Compile the project (single file).
8. Start the project for the first time. It will create the "InstallAwareTest" application in IIS, inside "Default Web Site". So far so good.
9. Start the project for the second time. It will change the physical path of the "Default Web Site" to c:\InstallAwareTest. This is the bug.

step9.jpg (21.39 KiB) Viewed 39139 times

Another method would be to run the already compiled project - IISBug - binary.zip - http://forums.installaware.com/download/file.php?id=516
If you still are unable to reproduce the problem than maybe we could organize some remote session if you like.

Best regards,
adi

[adi]

Hello,

Should I contact you directly? Do you still have problems reproducing the bug?
I am really blocked... We have bought an update and cannot use it because of this bug.

Best regards,
adi