I'm trying to upgrade the ASP.NET Controls on a machine. Currently the following is installed:
Infragistics NetAdvantage:
ASP.NET 2010.3
jQuery 2011.1
Silverlight 2011.1
Windows Forms 2011.1
WPF 2011.1
I'm trying to upgrade the ASP.NET controls to 2011.1 to be in line with the others. I've looked at the logfile and found the following errors:
"ConfigureIIsExec: A matching web object in memory was found, but the web object in memory has no associated base"
"ConfigureIIsExec: Error 0x80070002: Failed to find Web base"
"ConfigureIIsExec: Error 0x80070002: Failed to get base of web: WebSiteLocator_0001 for VirtualDir"
"Error 26004. Failed to read IIsVirtualDirs table. (-2147024894 )"
There are 6 sites configured on this server. The server is Windows 2003 R2 Standard SP2.
I've done some googling and there aren't a lot of hits on these. What did come back appears to be WiX. And I think that's probably out of my control as my guess is it's part of the install package.
Any help you may be able to provide is greatly appreciated.
Thanks,
Nick
Hi,
The errors you mention would indicate an issue with IIS, commonly the culprit with ASP.NET installations.
Our staff has reviewed log files with similar error messages and since this is 11.2, the more general things that could be suggested should be accounted for already, such as IIS6 compatibility and having a “Default Web Site”.
We have done some searching and found that other peoplea are also having similar issues. You should review http://support.citrix.com/article/CTX127255 . This resolution may be applicable here as well.
Marianne,
Thank you for your help. I discovered the issue. My problem was not that the "Default Web Site" did not exist. My problem was that the "Default Web Site" was not configured to listen on port 80. Apparently, the installer needs both a "Default Web Site" to exist as well as it configured to listen on port 80. I sure wish the error message was more informative. I wish for that a lot, it doesn't happen, which is why I'm thankful for Google!
@Alan,
I'm not sure if Sharepoint was installed or not. After you mentioned that I THINK it might have been. But it would have only been WSS, not the full blown Sharepoint (I doubt that makes a difference in IIS.) Regardless, we have de-commissioned that server and moved over to a new server, which I built, and have had none of the same issues. There was a lot of "experimentation" on the old server which didn't help either. Thanks for the input though!
@Nick,
Typically the only reason default web site is not on port 80 is because SharePoint is installed on the same server and SharePoint is quite fond of port 80 and will ursup the thing. You will encounter many, many problems if you attempt to develop web applications on the same machine that you have SharePoint installed on. Just an FYI. If you need to work with SharePoint and develop for SharePoint, I highly recommend a dedicated server for this purpose.