/build/static/layout/Breadcrumb_cap_w.png

IIS app install fail on server 2008

Hi
I am trying to install an msi on Windows Server 2008 but am getting an error around creating virtual directories.
The exact same msi installs perfectly on windows server 2003.

The msi log is 9mb, so here is the section from msi log file at point of error…

InstallShield 12:25:21: Creating application 'Web Services' with virtual directory 'SWCCommon\WebServices', website '33', and physical path: 'D:\Nortel\Contact Center\Manager Administration\Apps\Common\WebServices\'
InstallShield 12:25:21: No element found with property 'path' value of '/Web Services'.
InstallShield 12:25:21: Searching for parent virtual directory with the following path: /SWCCommon
InstallShield 12:25:21: No element found with property 'path' value of '/SWCCommon'.
InstallShield 12:25:21: No element found with property 'path' value of '/SWCCommon'.
InstallShield 12:25:21: No element found with property 'path' value of '/SWCCommon'.
InstallShield 12:25:21: Error with IISRT: -2147024893. Error translation: The system cannot find the path specified.

The msi eventually returns 1603 - install failure.


Has anyone run into this problem with IIS apps the installed fine on 2003 but fail on 2008?

I suspect it has something to do with caCreateVRoots.

All help appreciated.
Thank you

0 Comments   [ + ] Show comments

Answers (6)

Posted by: anonymous_9363 14 years ago
Red Belt
0
My knowledge of Server 2008 could be summarised on the back of a postage stamp but, to me, here's a clue-ette:InstallShield 12:25:21: Searching for parent virtual directory with the following path: /SWCCommon
InstallShield 12:25:21: No element found with property 'path' value of '/SWCCommon'.
It's hard to determine, owing to the strangulated grammar in use but either the path to which the parent VD points is invalid or there's no path beneath it named 'SWCCommon'.
Posted by: donwar 14 years ago
Yellow Belt
0
Thanks for the input VBScab.

What 'path' property is the log file on about? and how do I change it?

Why would this work fine on Windows 2003 server, but not on Windows 2008 server?

I am using Installshield 2009, I have also tested with an evaluation version of IS 2010, but it still fails around the Virtual Directory creation section of the install.
Posted by: anonymous_9363 14 years ago
Red Belt
0
Some thoughts:

- The log entries don't look like MSI log entries to me. They look like they're generated by InstallShield function calls.
- The word "element" instantly says to me "XML" - is there an XML parser installed on the server? Does the app mention such as a pre-requisite?
- Changing your authoring tool won't make a blind bit of difference to the actual installation.
Posted by: donwar 14 years ago
Yellow Belt
0
Thanks VBScab

I have looked through the ism & there are no XML changes that I can can see.

I agree with you that the logging is coming from installshield custom action.
I think it is caCreateVRoots

The logfile reads: "CustomAction caCreateVRoots returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)"

The full log is 10 mb large - is there a way of copying this up (sorry - im a bit new to this forum)
Posted by: AngelD 14 years ago
Red Belt
0
Maybe any of the below links will help:
caCreateVRoots fails on Vista
http://community.acresso.com/showthread.php?t=180383
caCreateVRoots causing rollback on Server2008 (IIS7)
http://community.acresso.com/showthread.php?t=186572&page=3
Posted by: anonymous_9363 14 years ago
Red Belt
0
Thanks, Kim. So it looks like it's either the location of the VDir root which may be the problem or malformed XML in an IIS configuration file (note: nothing to do with InstallShield XML files!).
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ