IIS weirdness - can anyone explain

[Bo Andersen]

Hi guys,

We have two editions (server and personal) of our software, the install scripts are essentially the same.
The software is a web app that is installed on IIS. We have used the same installaware 8 script for months without any problems.

We used to have to resort to a
~InstallAware Clipboard Data~
~Run Program~
~{3D9654E0-4DB0-4C27-8D83-978633ACBB16}~
~$WINSYSDIR$\\inetsrv\\APPCMD.exe~
~TRUE~
~add app /site.name:"Default Web Site" /path:/$VDIRNAME$ /physicalPath:"$TARGETDIR$\\DLCL"~
~TRUE~
~~

to get the virtual folder to register on Vista, but since IAW801 we were able to use the regular Create Virtual Folder command:
~InstallAware Clipboard Data~
~Create Virtual Folder~
~{F272E878-CF53-449A-9C31-16DAFC4050E9}~
~$VDIRNAME$~
~$TARGETDIR$\\DLCL~
~FALSE~
~TRUE~
~FALSE~
~FALSE~
~TRUE~
~TRUE~
~1|Dynpool~
~1|0~
~TRUE~
~loc.asp~
~~
~TRUE~
~FALSE~
~FALSE~
~~
~$XSITENO$~

Now, the thing is that since building new test releases 3 days ago, we've seen this odd behvaiour:
Installing on XP, everything is good
Installing our server edition on vista is good
but installing the personal edition on vista, the virtual folder just does not get created. I have verified that the statement is executed (messagebaloon just before and after) and also verified that the variables are populated with the expected values at the statement execution time.

I of course suspect a microsoft vista hotfix to be the culprit, but then again, why does the server edition that uses the very same command not fail?

Any thoughts on this puzzle will be grately appreciated.

By the way, I did try building the project with both IAW 8 and 9, but see the same result on multiple updated vista machines.

Our old old setupscript that used the appcmd to create the web folder wtill works on those machines.

Thanks
Bo

[Bo Andersen]

Seem to have found a "solution".

When installing multiple apps to IIS, do not use the same App Pool name for both - I dont understand what the problem is, but the app pool being there already somehow prevents web folder creation

Thanks
bo