.NET Framework 1.1 Service Pack 1 problem

We have installed SP1 on our servers. It is good thing that we did it on DEV, STAGER and QA environments, but not on production.

Here is a problem. When you navigate to the login screen, type user name and password, click on "Login" button -> nothing happens!!! No action, no postback...nothing. I have checked the page and it has FORM tag and method as POST and etc.
Clicking on button does just nothing, like this button is not binded or there is no event associated.
This is really weird and I'm trying to understand what is going on, but I'm really short on ideas

Any thoughts would be appreciated.
Thanks.

Using ASPX?
If so, passing XML in a hidden textbox?
If so, might be running in a security feature.

Did you viewsource to see if anything in the markup stood out?

The page looks fine. There are other web applications on the same server and they are working just fine. It is something wrong with this one

It is simple Form Authentication login page. No XML, nothing.

One thing I have noticed that the validater is working. If I do not provide User name and password, client side validation pops up, saying "no user/password", but if I do type the credentials in, nothing is happening when I click the LOGIN button.

OK, this is really strange.

I have checked the event logs on the web server and found an error message. I have checked the logs before, but I did not look at earlier messages. At the time when our web admin installed SP1, there is an error “Failed while copying the ASP.NET client side script files to directories under D:\Dev03\Support. Error code: 80070005”. Our web application has virtual directory called “aspnet_client” and it points to “c:\inetpub\wwwroot\aspnet_client”. I have checked permissions and etc and it looks fine. There is another application that is still running and working fine on this server, so I checked what it has for aspnet_client and found that it is not a virtual folder, it is a physical copy of aspnet_client and sure thing, it has old scripts – “pre-SP1”. I have compared scripts “SmartNav.js” and “WebUIValidation.js” and they are different. The next step was to get rid of virtual directory “aspnet_client” and copy that old “aspnet_client” to my web application root.

Well…guess what? It worked.

Now, I’m totally confused.

My workstation bluescreened twice before booting up normally after applying this service pack. That was not a very nice experience.

I have actually noticed a similar failure in some aspx postback actions recently, however they appear to be IE6 related in that the same pages work when viewed with FireFox. Perhaps there is some relation to the javascript changes in 1.1 SP1?

Any thoughts from MS?

I have called Microsoft Premier Support and created a case. I will post here the information if we solve that mistery. I still think that it is something minor ro something stupid that we've done, not SP1

Glad to see I wasn't the only with problems with this.  Mine won't install on my system at all.  I get an unhandled exception error during the installation.

Odin,

I was having similar problems with events not firing.  There could be a couple things going on here, but I got it solved by doing the following:

1) Run the command: aspnet_regiis -c

   This should take the new javascript libraries from the .NET framework and put them in your C:\inetpub\wwwroot\ directory.

2) Restart IIS (at least I did)

3) Make sure all your web applications are using the new aspnet_client directories.  I was running into an issue where an application was using the old JavaScript libraries because they had been copied into an application directory.

As a note, I am running IIS 6.0, XP with SP2.

Good luck!  This was a pretty frustrating problem; hopefully this will save some folks a lot of pain.

Dan

Even I have the same problem. I guess it is something to do with html server side control buttons because aSP.net controls works just fine.

Thanks Dan.

I got some info from Premier support, i will post it soon.

I had this same exact problem as well.  I finally copied the client-side JS validation files manually to my website's aspnet_client folder and that worked but it's definitely an issue with SP1.

OK, here is some information about this problem.

Just to remind you, the problem was in client side scripts. The submit button of your ASP.NET page does not work if you upgraded .NET Framework on a server with SP1.

The problem is the javascript file WebValidationUi.js in aspnet_client folder. The changes in that file prevent a page to be submitted.

The workaround is simple, just copy the old WebValidateionUi.js over the new one. Microsoft will release the patch at some time, meanwhile, I bet you would like to have SP1 installed on your servers.

We do not practice having aspnet_client folder in every web site's root - we are using virtual folders that point to the one aspnet_client folder (per server) that is located using default patch for inetpub.

Hi,

Your thread has shed a lot of light on an identical  problem I am experiencing, thanks.

I have tried to run aspnet_regiis -c to deploy the client side scripts, but I get the error:

"An error has occurred (0x80070005)
You must have administrative rights on this machine in order to run this tool"

I am logged in as "administrator" and have checked all permissions and rights on the local machine without success, so I have kinda given up on the automatic deployment.

Would it be possible to make the working aspnet_client script files that you have successfully used available  (email?) ?

Many thanks for your time...

Thanks Odin your solution fixed my problem. Thanks for sharing.

Hi TheBadger,

I'm afraid that it is different problem. I had "Failed to copy" error. In your case I would just create a folder aspnet_client manually and copy 3 files from that folder over.

There is noting special about the script files that I used. Just get them from C:\Inetpub\WwwRoot\aspnet_client from the server that has not been upgraded. (First, try to copy SP1's aspnet_client and replace only one file WebValidationUi.js.
If it will not work, then copy over the whole old folder.

Odin, you seem to be stating 2 problems.  Is the js included in SP1 broken?  If so, then the "failed to copy" error would have been a good thing, right?  If the failure to copy was the problem, then you would have still been using the old js, right? 

I'm confused.