Web Deployment Tool (MS Deploy)
Last post Oct 01, 2009 10:19 PM by Andrew Zhu - MSFT
Sep 15, 2009 03:59 PM|merk|LINK
Used msdeploy to copy sites from iis6 to 7. I'm trying to test some of those sites now to see if the copy worked and when i drill down into many of the settings, i get a popup window saying:
There was an error while performing this operation.
ideas what this is about?
Sep 15, 2009 04:14 PM|yaminij|LINK
Are you trying to view the applicationHost.config file? You must be an administrator or in a elevated command-prompt to view this file.
Sep 15, 2009 04:17 PM|moshaikh|LINK
This error indicates there is an error in applicationhost.config.
It should tell you the cause of the error in the message when you see this message box. If not can you look in the event log and see if it shows you what the error is?
Sep 15, 2009 04:32 PM|merk|LINK
I get this error when i am using the management console. also, this error only appears to occur for some sites. Other sites seem to be ok.
I could not find anything in the event log related to this. the only error that i found in the event log related to IIS is:
The directory specified for caching compressed content C:\Windows\IIS Temporary Compressed Files\AspNet2.0 is invalid. Static compression is being disabled.
I've made no changes to any of these sites since using msdeploy to copy them. So if there is some sort of corruption in the config file, i think msdeploy is the one that created it.
Sep 15, 2009 05:04 PM|merk|LINK
I tried testing it a bit.
I had a virtual directory which was an application. if i tried to change any settings in there, i'd get that error.
So i deleted the virtual directory in IIS. I then re-created it. And i could access all the settings. However, once i converted the virtual directory to an application, i get the error again.
Sep 15, 2009 06:40 PM|merk|LINK
further discovered it's only when it's pointing to the default app pool that this happens. What can i check to narrow down why thats happening?
Sep 15, 2009 06:54 PM|yaminij|LINK
Can you check if your application pool identity for DefaultAppPool is messed up? To view identity, Right Click DefaultAppPool in the IIS 7.0 management console and chose Advanced Settings
Sep 15, 2009 07:05 PM|merk|LINK
Identity is set to NetworkService, which is the same thing the asp.net 2.0 pool is set to, and it works when i set the app to that pool.
Default app pool is set to:
enable 32bit - true
managed pipeline - classic
I check and there is no windows\IIS temp folder on the server. I would have assumed it would create the folder if it's not there. I did not pick that directory myself - it was either then when the server was first installed or it copied it from the IIS6
server i migrated the sites from.
Sep 16, 2009 09:17 AM|zsweb|LINK
I get this error message here on a 64-bit box if i use a ASP.NET 1.1 application pool.
If i use an ASP.NET 2 pool i can change settings without error.
On a 32-bit box ASP.NET 1.1 works fine.
Sep 16, 2009 11:22 AM|merk|LINK
Sep 21, 2009 12:01 AM|Andrew Zhu - MSFT|LINK
.NET 1.1 do not support x64. That is why Windows Server 2003 x64 and XP x64 do not have it installed by default unlike regular Server 2003.
Please use .NET framework 2.0 or above.
Sep 21, 2009 03:12 AM|merk|LINK
Sep 30, 2009 11:27 PM|Tofiology|LINK
It is not true that asp.net 1.1 does not run on a 64 bit OS. Here are the basic steps to check:
First make sure you have IIS Metabase Compatability installed from the 'windows' or 'server role' features.
I am not sure if it matters, but I install the compat feature, then install the .net 1.1 framework and then .net 1.1 SP1
Next setup the .net 1.1 isapi filter in IIS 7.0
here is a good guide:
Next you need to enable 32 bit apps on a 64 bit server by running
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
Then I run the aspnet_regiis -i
Finally open the applicationHost.config and find the entry for the .net 1.1 isapi filter (<add path="C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll" allowed="false" groupId="ASP.NET v1.1.4322" description="ASP.NET v1.1.4322" />) and
set the attribute 'allowed="true"'
If you still have problems, double check the file security permissions in the directory of the web-site.
I have .net 1.1 applications running on multiple x64 Server 2008 Standard / Enterprise and Web Server editions.
Oct 01, 2009 12:59 PM|merk|LINK
Oct 01, 2009 10:19 PM|Andrew Zhu - MSFT|LINK
Here is an article talking the exact issue you have, below is a quote from this article:
"The problem is that when the runtime tries to load the corresponding configuration, it doesn't take the bitness of the application pool into the consideration. As you know, ASP.NET 1.1 is only supported on 32-bit. So if you have a 64-bit OS, in order
to run ASP.NET 1.1, you have to enable 32-bit applications in the application pool. So, with the QFE/SP2 on 64-bit OS (and only on 64-bit OS), the runtime is incorrectly looking for the 1.1 version of the configuration under Framework64, which does not exist."
Check this link: