Skip to main content

Windows 2003 SP1 Broke My ASP.Net

ARGH!! The saga continues...

Back in December I had this problem before -
Andrew MacNeill - AKSEL Solutions: Reinstalling DotNet/ASPNet on a Windows 2003 Server

Now, after upgrading to Windows 2003 SP1, the problem has returned. Users cannot click on an ASP.Net button and have it work.

Funny thing? It works in Firefox but not in Internet Explorer. Just like the last time. No error, no nothing. And it's only on certain buttons.

Once again to the rescue

Real Checklist for verifying AspNet is working properly on a Windows 2003 server

1. Verify in IIS that ASP.Net web service extension is Allowed. (check)
2. If it is, and something's still not working right, re-register it. Go to the \WINDOWS\Microsoft.NET\Framework\v1.1.4322 folder and run:

aspnet_regiis -i (didn't fix the problem)

aspnet_regiis -r (didn't fix the problem)

aspnet_regiis -c (note the -c didn't seem to work on my version but you can also do it with an -r to reinstall)

This was brilliant - Windows said You Must Have Admin rights to run this tool. I AM the administrator.

So - what to do?

Uinstall ASP.NET 1.1.4322 with
aspnet_regiis -ua

Then reinstall with
aspnet_regiis -i

NOW - go to IIS Web Service Extensions and make sure it's Allowed (by default it was prohibited). STILL not working.

I'm not going to bother trying to repair my Windows 2003 install - for right now, I'm just going to try and uninstall my SP1. This is just crazy. See my next post to find out if it was successful.

Comments

Anonymous said…
This won't help you much but I loaded SP1 to my dev box earlier today haven't had any problems running VS2003. My web apps are also working without any problems. Wish you good luck fixing the problem.
Anonymous said…
If you are using source control, remove aspnet_client from source control and try re-running aspnet_regiis -c.
Best of luck!
Anonymous said…
I loaded Windows 2003 SP1. It killed SMS. No ASP is working. SO there is a problem. So far I found an article explaining about the DCOM changes. Problem Still not fixed.
Anonymous said…
I've had the same problem. Everything was working fine, then SP1 installs and blam gone.

I've tried re-installing Win2003 afresh, then installing SP1 before I install VS.NET etc and it's still broken.

I also get it telling me I don't have rights when I am the admin. This is a complete joke.
Anonymous said…
Had the same problem. Found the source and fixed it.
Compare wwwroot\aspnet_client\system_web\1_1_4322\WebUIValidation.js
on the 2003 server and on a server that works (or your development machine). Mine were different. Replaced a javascript function on the 2003 server with the one off my machine. Here is the working version of this function that should be replaced on the 2003 server:
function ValidatorCommonOnSubmit() {
var result = !Page_BlockSubmit;
Page_BlockSubmit = false;
event.returnValue = result;
return result;
}

Good luck.
Anonymous said…
we have had 2 customers install the
service pack 1 on their servers and all third party software stopped working properly. of course the microsoft nonsense applications continued to run.

more bullshit from these losers.

sam basile
eos software
syracuse
Anonymous said…
Search for the URLSCAN.INI on the ISS server. It is probably what is preventing ASP execution. I figured this out after 7 hours of messing around and there doesn't seem to be any documentation on it online.
Anonymous said…
Has anybody got solution to it???
Anonymous said…
I was able to get one of my apps working again by installing Dot Net 2

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP