For those of you programmers out there who are chucked to do ASP.NET programming despite the fact that your resume didn't state that you know ASP.NET, and is encountering a problem with ASP.NET. This entry might help you.
I've recently been assigned the company's ex-programmer's ASP.NET project as the programmer has left the company.
Until yesterday, if not mistaken after a Windows update, this problem started giving tons of headache.
If you have ever received an error message on a .NET application that simply stated "Server Application Unavailable" you might find this useful.
The Probable Cause:
Microsoft identified an issue with the MS03-32 Security Update for Internet Explorer security patch and ASP.NET 1.0/2.0 running on Windows XP. This patch can be installed manually or by obtaining recent critical updates from the Windows Update site.
The symptom of this issue is that after installing the patch on a Windows XP machine, all requests to ASP.NET applications running on the local IIS 5.1 web server result in an error message saying "Server Application Unavailable". Requests to remote web servers are unaffected.
This issue only impacts installations running ASP.NET 1.0/2.0 on Windows XP. It does not impact machines running Windows 2000 or Windows Server 2003. It also does not impact machines running Windows XP with ASP.NET 1.1 installed.
Please note that this issue is not a security bug with ASP.NET. It does not open up or allow any malicious attacks against an ASP.NET application or server. Instead, it is purely a functional bug caused by the patch itself.
For my case, I'm running a Microsoft.NET Framework v2.0.50727 along with IIS 5.1.
I tried to "Start Debugging" my project yesterday and all I get was a "Server Application Unavailable" error code.
When I went to check my Event Viewer (Control Panel > Administrative Tools > Event Viewer) for the error log, I got this:
 |  |
The Solution:
Download this batch file and run it. The steps:
1) You must be running as an account with Administrator privileges
2) Double click the fixup.cmd.
3) When prompted, enter 1pass@word as the password.
4) If you have previously custom access control settings or database account permissions for the ASPNET account, you'll need to re-apply these settings now.
If you are wondering what does the batch file does, it does the following:
ile does the following:
1) Stops the IIS and ASP.NET state services
2) Deletes and recreates the ASPNET account with a known temporary password
3) Uses the Windows runas command to launch an executable that creates an ASPNET user profile
4) Re-registers ASP.NET. This creates a new random password for the account and applies default ASP.NET access control settings for it
5) Restarts the IIS service
After running the batch file, run the Aspnet_regiis.exe utility:
1) Click Start, and then click Run.
2) In the Open text box, type cmd, and then press ENTER.
3) At the command prompt, type the following, and then press ENTER:
%windir%\Microsoft.NET\Framework\version\aspnet_regiis.exe -i
In this path, version represents the version number of the .NET Framework that you installed on your server. You must replace this placeholder with the actual version number when you type the command.
Reference: http://www.asp.net/learn/whitepapers/ms03-32-issue/
You can get the version number from your Microsoft.NET Framework directory. For Windows XP it should be located here: "C:\WINDOWS\microsoft.net\framework"
Your problem should be solved by now =) Hope it did helped you out. Cheers!!
0 peepz:
Post a Comment