If a picture is better than 1000 words, what about a 3 minutes video? 😲 Lot of new stuff is coming for web developers: take a look, smile and download 😊 And here is a post about what’s new in IIS7 on this release. Cheers
-
-
Integrated Authentication does not work with domain name
This is an easy one, but we got cases like this every now and then… maybe worth repeating. If you use Windows Integrated Authentication in IIS, everything works fine if you browse “http://netbiosname”, but Integrated Authentication fails is you browse “http://dnsname”. Why? Because if the DNS machine name contains a dot (“.”), the web site automatically belongs to the “Internet” zone, and by default IE does not sent the account credentials. How to solve this? Easy, you have two options: Add the URL to the “Trusted Sites” in Internet Explorer Modify the security parameter to allow “Automatic logon with current user name and password” (Control Panel -> Internet Options -> Security tab -> Internet -> Custom level…) Update: By the way, I forgot to mention that this is also true if you use the IP address instead of the netbios name: e.g. http://xxx.xxx.xxx.xxx Cheers
-
Find which w3wp.exe instance is hosting your application
Just a quick and easy one for this Friday evening: let’s say you have multiple w3wp.exe instances running on your web server (maybe you have multiple application pools, or you enabled Web Garden etc…), one of the ASP.NET applications you have on that server has some problems and you need to capture a memory dump to troubleshoot it: what can you do? Easy one: install the Debugging Tools for Windows and run adplus with something like the following: cscript adplus.vbs -hang -pn w3wp.exe But, hey, you don’t want to end up with a full dump for every w3wp.exe loaded in memory, you just need one of them, the one which is hosting your application… 🙄 Well… here is where iisapp.vbs comes to the rescue! 😊 You can find it under C:\Windows\System32 folder on your Windows 2003 machine, and if you simply run it at the command line, it’ll print to the console the PID of all w3wp.exe processes running and the Application Pool ID that particular process is hosting; here is a screenshot I just took in my machine: Since you are supposed to know under which application pool your application is running (and if you don’t know you can check…
-
Session_OnEnd not firing after applying Windows 2003 Service Pack 2
We very recently discovered a bug in classic ASP (asp.dll) you get installing the Service Pack 2 for Windows 2003; removing the SP2 makes it work again as expected, so this is a regression bug introduced by the service pack itself. Basically with SP2 installed, the Session_OnEnd() method in classic ASP is not fired anymore, thus breaking all applications which rely on that event to run cleanup code. We already have some reports from customers, either directly to CSS or in Newsgroups. I know my colleagues are already well on this, a private fix has been produced and is being tested internally (as far as I know it works) and we are writing a KB article to document this. The process is still ongoing so I don’t have (and can’t give you) further details on this, but I guess it’s a matter of days before this will be publicly available; of course I’ll update this post when we’ll have the KB available. Update (03/04/2007)The KB article is still a draft and not public yet (should be released soon, anyway) but the fix is ready; you can get it calling CSS and ask for the hotfix #934903. Update (17/04/2007)The KB article has been published: http://support.microsoft.com/default.aspx?scid=kb;EN-US;934903 …
-
Unable to get the private bytes memory limit for the w3wp process
PROBLEM DESCRIPTION =================== I can run ASP.NET applications on the server, however I have noticed that when I do there is an asp error entry in the event log: "Unable to get the private bytes memory limit for the W3WP process. The ASP.NET cache will be unable to limit its memory use, which may lead to a process restart. Error 0x80070005". ENVIRONMENT =========== – Windows Server 2003 – .NET Framework 1.1 SUMMARY of TROUBLESHOOTING ========================== This error is caused by a known issue with insufficient permissions in your IIS metabase. The metabase ACL’s on the target server did not include the IIS_WPG group on the following two nodes of the metabase (IIS_WPG is in both ACL’s on a clean install): – W3SVC/AppPools – W3SVC/Filters You can download the MetaACL utility from http://support.microsoft.com/?id=267904. After you have installed the program, open a command prompt and navigate to the directory where you installed it. Then type the following: – cscript metaacl.vbs IIS://Localhost/W3SVC/AppPools IIS_WPG RE – cscript metaacl.vbs IIS://Localhost/W3SVC/Filters IIS_WPG RE Warning: The path is case sensitive – type exactly as above; after you run this command restart the IIS services and see if this corrects the problem. Update: here is…
-
Missing ASP.NET Tab in IIS Management Console
PROBLEM DESCRIPTION =================== On a Windows 2003 64bit machine with both .NET Framework 1.1 and 2.0 installed, you are tying to configure a website on IIS, but you are unable to find the tab to specify ASP.NET settings. SUMMARY of TROUBLESHOOTING ========================== Researched turned out this being a bug that is closed as "won’t fix". If you are gong to run IIS 32-bits on WOW64, MMC Support for ASP.Net snap-in is currently not allowed. We are in the process of writing a KB article to document this. In general the ASP.net tab is giving you the UI to configure the application to run different versions. You could use the specific version of aspnet_regiis.exe utility to configure this. The utility is aspnet_regiis -i under C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727, if you want your application to run under 2.0. There are several command switches to configure specific sites or directory only. If you see these problems on 32-bit OS there’s a known workaround: Manually run the install for ASP.NET: ASPNET_regiis -i Register the dll for the MMC: regsvr32.exe "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mmcaspext.dll" "rundll32.exe" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\webengine.dll",RegisterAspNetMMC From a command prompt run: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\regasm.exe C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\AspNetMmcExt.dll /tlb:AspNetMMCExt.tlb Change the About value in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\{fedb2179-2335-48f1-aa28-5cda35a2 b36d}" from {7D23CCC6-A390-406F-AB67-2F8B7558F6F7} to {7D23CCC6-A390-406F-AB67-2F8B7558F6F6} UPDATE (5th November, 2006) Just…