By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,696 Members | 1,422 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,696 IT Pros & Developers. It's quick & easy.

Asp.Net click event fires on 2000 but not 2003

P: n/a
Hello. I am running into a strange problem moving my asp.net site (c#) from
a Windows 2000 server to Windows 2003. This problem only happens on 2 pages
out of about 30 on the entire site.

On these 2 particular pages, none of the buttons do anything. The exact
same pages work fine on the 2000 server, but when the page is moved to 2003
it is totally dead - no Windows logo in IE waving, no "click" sound or
anything. All other pages have buttons which click just fine.

At first I thought perhaps it was a security issue with the Access db, so I
created a test button which does nothing other than put text into a textbox
on the page (no database interaction), and even it does not work.

The 2003 server should have all the latest updates (unless there is
something I am not aware of)...

any help would be appreciated!,
RP

Nov 18 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
To followup with my above message - I realized that the 2 pages which do not
work use the asp.net required field validators. I removed the validators and
sure enough, the page now works.

Do I need some sort of client side scripting update to use validators on 2003?
"Rob Penner" wrote:
Hello. I am running into a strange problem moving my asp.net site (c#) from
a Windows 2000 server to Windows 2003. This problem only happens on 2 pages
out of about 30 on the entire site.

On these 2 particular pages, none of the buttons do anything. The exact
same pages work fine on the 2000 server, but when the page is moved to 2003
it is totally dead - no Windows logo in IE waving, no "click" sound or
anything. All other pages have buttons which click just fine.

At first I thought perhaps it was a security issue with the Access db, so I
created a test button which does nothing other than put text into a textbox
on the page (no database interaction), and even it does not work.

The 2003 server should have all the latest updates (unless there is
something I am not aware of)...

any help would be appreciated!,
RP

Nov 18 '05 #2

P: n/a
Rob:

I'd the same problem. I was developing in XP Pro and when I moved my web ap
to Win 2003, none of the click events fired. I fixed it by copying the folder
"aspnet_client" (that should be in your Inetpub/wwwroot folder) to your
website's root folder. I'm thinking that the client-side validation (java)
script may be different for the two operating systems (even when I'd the same
version of .Net - kind of strange). Anyway, it worked for me. Hope this fixes
your problem too.

- Hari
"Rob Penner" wrote:
To followup with my above message - I realized that the 2 pages which do not
work use the asp.net required field validators. I removed the validators and
sure enough, the page now works.

Do I need some sort of client side scripting update to use validators on 2003?
"Rob Penner" wrote:
Hello. I am running into a strange problem moving my asp.net site (c#) from
a Windows 2000 server to Windows 2003. This problem only happens on 2 pages
out of about 30 on the entire site.

On these 2 particular pages, none of the buttons do anything. The exact
same pages work fine on the 2000 server, but when the page is moved to 2003
it is totally dead - no Windows logo in IE waving, no "click" sound or
anything. All other pages have buttons which click just fine.

At first I thought perhaps it was a security issue with the Access db, so I
created a test button which does nothing other than put text into a textbox
on the page (no database interaction), and even it does not work.

The 2003 server should have all the latest updates (unless there is
something I am not aware of)...

any help would be appreciated!,
RP

Nov 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.