.NET Framework 1.1 Service Pack 1 problem | Tech Off

Odin

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 Sad

Any thoughts would be appreciated.
Thanks.

Minh
WOOH! WOOH!

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

harumscarum
out of memory

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

Odin

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 Sad

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.

Odin

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.

lars

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

gabe19
bang bang shoot shoot

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?

Odin

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 Wink

Blkbam
Bam, Bam! Bam, Bam Bam!

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.

dkuyper

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

shivaries
Arian

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.

Odin

Thanks Dan.

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

adham

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.

Odin

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.

TheBadger

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...

shivaries
Arian

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

Odin

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.

Shannon

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.

Odin

Shannon wrote:

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.

In case of failure, yes, you would still have your old scripts. In my case, the administrator has noticed that error "Failed to copy scripts..." and manually (!) copied new files. Actually, at first, he got rid of the virtual directory "aspnet_client" and then created a real folder "aspnet_client" and copied new scripts. After that we have discovered that "side effect"

Daniel121904

Odin,
We're having a 404 resource not found error, we think its the service pack for the framework that is causing this error. We've tried using your suggestion on switching the smartnav back to its original state after intsall but we keep having the same problem. Any suggestion on this.

We've placed aspnet_client on the root and on the website.

Thanks,
George

Odin

Daniel121904 wrote:
Odin,
We're having a 404 resource not found error, we think its the service pack for the framework that is causing this error. We've tried using your suggestion on switching the smartnav back to its original state after intsall but we keep having the same problem. Any suggestion on this.

We've placed aspnet_client on the root and on the website.

Thanks,
George

There are many reasons why you see 404. Unfortunately, I can not tell you for sure what it is, but you can use monitors to see what is going on.
For example, try this simple Microsoft FIddler: http://www.fiddlertool.com/fiddler/

You should be able to see the request and response bodies. See what page has been requested, what has been sent and etc.

I have seen a few reports about problems with SP1, but nothing about 404 error.

Chad

Odin, thanks for your help. You definitely saved me a lot of pain....

Chad

http://www.pear-mouse.com

Skinner

I'm currently working over a 500 error - Service Application Unavailable. I installed SP1 via Windows Update and got a bunch of perf counter errors first. Then I installed it again from a downloaded exe. No dice. I then went to uninstall it, and try to install WSE 2.0 SP1 to see if it would verify that 1.1 was installed... buuuzzz wrong answer: 1.1 framework not installed. We'll see what they tell me on the ticket I opened with MS support...
Mark

rescobar

I just begun to have the same problem. After an automatic update for Windows 2003 server some PCs can access my applications normally but some does not (validation controls are not recognized and there is no postback). The OS of PCs are Win98 and XP.
In a PC with Win XP, a user can access and other user in the same machine does not.
I am very worried as all my apps use validation controls and we are stopped a few days ago.
I tried to uninstall Framework but I think that that is no posssible as is part of OS.

any idea?
Thanks in advance

tdp

i installed framework 1.1 yesteday and got the same problem with server.trancfer where nothing happend.

I then removed smartnavigation from the page directive, and all was running normal again. Bur what to do now then, if you need the smartnavigation?