ExpExcJustin
asked on
Database and Forms on Classic ASP pages seem to not be found after clicking submit.
I'm having a wierd issue i've never experienced with ASP before. On a particular web server (Win2k) any page using ASP connecting to an access database will "time out" if you sit on the form page for more then a few seconds. Only pages using access and forms do this. And it's after no more then say 20 seconds. If you fill out the form quickly it will process perfectly. Different programmers / Different databases / Different Scripts / Some use DSN some Don't
Same Server, All are MS Access Databases.
For instance filling out this question form would never work it takes longer then 10 seconds to fill in the info. After I click submit I get a page that comes up and states the following:
--------------------------
Internet Explorer cannot display the webpage
Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address.
What you can try:
Diagnose Connection Problems
More information
This problem can be caused by a variety of issues, including:
Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's domain.
If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.
--------------------------
Any ideas? I'm at a loss on this one. I dont even know what to try!
Also I copied one of the forms and database to my local PC and ran it on PWS without issue.
Same Server, All are MS Access Databases.
For instance filling out this question form would never work it takes longer then 10 seconds to fill in the info. After I click submit I get a page that comes up and states the following:
--------------------------
Internet Explorer cannot display the webpage
Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address.
What you can try:
Diagnose Connection Problems
More information
This problem can be caused by a variety of issues, including:
Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's domain.
If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.
--------------------------
Any ideas? I'm at a loss on this one. I dont even know what to try!
Also I copied one of the forms and database to my local PC and ran it on PWS without issue.
Last Comment
ASKER
Nothing shows up in event viewer.. The url of the forms page stays in the location field.
ASKER
Anyone?
I have a public IP natted to a private. only 1 website running on the webserver. win2k3.
If you sit on a page with a form for more then a couple seconds and then click submit it never submits.
Firewall problem? MDAC? It's a fresh install of 2k3
I have a public IP natted to a private. only 1 website running on the webserver. win2k3.
If you sit on a page with a form for more then a couple seconds and then click submit it never submits.
Firewall problem? MDAC? It's a fresh install of 2k3
The thing that you need to keep in mind is that every web server request is technically independent. When you request the web page with the form in it, the browser opens a connection to the web server, retrieves the page, then closes the connection.
When you click the submit button, the browser again opens a connection to the web server, retrieves the response, closes the connection again.
From a web server perspective, there is absolutely no difference whether the request comes immediately or a few minutes later.
If the web server has failed in the meantime, then there will be some event logged in the event viewer.
Try the same thing from the web server console. If it is only the one web site, then it should probably work the same using http://localhost/path/form.html
Also, try using the web server ip address instead of hostname (i.e. http://a.b.c.d/path/form.html)
Try opening a cmd shell, and run a ping in the background while you are testing the site/form with the browser. Use "ping -t a.b.c.d" so that the -t option causes ping to keep going after 4 tries.
Cheers.
When you click the submit button, the browser again opens a connection to the web server, retrieves the response, closes the connection again.
From a web server perspective, there is absolutely no difference whether the request comes immediately or a few minutes later.
If the web server has failed in the meantime, then there will be some event logged in the event viewer.
Try the same thing from the web server console. If it is only the one web site, then it should probably work the same using http://localhost/path/form.html
Also, try using the web server ip address instead of hostname (i.e. http://a.b.c.d/path/form.html)
Try opening a cmd shell, and run a ping in the background while you are testing the site/form with the browser. Use "ping -t a.b.c.d" so that the -t option causes ping to keep going after 4 tries.
Cheers.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Microsoft Server OS
The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.
59K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
take a look at event viewer application log and also look at the web server log.
Cheers.