Web Server “hangs”, stops responding, when executing an ASP script
An ASP script alone would not cause your web server to “hang” or stop responding. One of the features built into ASP is an automatic timeout period. If a PDshop script fails to complete a task within 90 seconds, it will be terminated by the server and a very specific error message will be displayed such as “The maximum amount of time for a script to execute was exceeded.” If you do not receive this message, and your server “hangs” indefinitely, this is a sign of a more serious server resource problem.
If you have made script changes and your script contains an error, or there is a problem with your setup.asp configuration, you would receive a "VBscript" "ODBC" or "ADO" type error. If you are not receiving any specific error messages from the server, than it is likely a component problem (for example, server software such as an email component, an MSXML com object, or database driver).
MSXML Objects:
If you are using Authorize.net’s AIM processing, or the UPS or USPS rate add-on, PDshop may be utilizing the MSXML server objects. There are known bugs with older versions of Microsoft's MSXML, it is recommended that you contact your web host to determine which MSXML object to use. You can change which object PDshop uses by modifying the “xmlhttpobj” variable in your setup.asp file located in your includes directory. If you are the server admin, it is recommended that you install the latest MSXML components from Microsoft.
Other Solutions for Server Administrator’s & Web hosts:
A server re-boot will often correct a server “hang”, but if the problem returns, you should consider re-installing some of the server components such as the database drivers, MSXML, MDAC, as well as latest version of "VBscript". It is crucial that your server be kept up to date with the appropriate “patches” and Service Packs.
Database Related Solutions:
If you experience “hangs” due to a database driver issue, try using a different database driver (for example, if you are using the *.mdb ODBC driver, switch your setup.asp file to connect with the “Jet” drivers). It should be noted that the drivers for Microsoft Access only handle a limited number of connections (for larger websites, with heavy traffic, the MSSQL Server database is more appropriate).
Corrupt MSAccess Databases:
If your database has become corrupt, damaged, or is extremely large, you can receive "timeout" errors or other unexpected problems. Most database corruption issues can be corrected by running the "Compact & Repair" utility built into the Microsoft Access program.
Excessive traffic and MSAccess:
If you are using the default MSAccess database and your site is fairly busy, meaning you consistently have 25 simultaneous shoppers (or over 2000 unique visitors a day), you should be using MSSQL as your database backend. MSAccess is suitable for small businesses, but is not capable of maintaining a large number of simultaneous database connections (this is a limitation of the MSAccess drivers, not PDshop). Microsoft’s SQL Server is an enterprise level database system, designed for heavy traffic. If your web server stops responding, and it coincides with increased web traffic, you may have outgrown MSAccess (you may have outgrown “shared” hosting altogether).
Shared Web Servers:
If your website is hosted on a "shared" server (these are the less expensive hosting plans), troubleshooting may be difficult. If you believe your server has a resource problem, the first step is to try and determine which component is to blame. The best way to proceed is to analyze your web logs, test your site thoroughly, and try to determine what specific functions (pages) trigger your problem. For example, if your server stops responding anytime PDshop tries to process a credit card (or retrieve Real-Time shipping rates), than the “MSXML” component may be the problem. Contact your web host for assistance with these server components; find out which components you should use (Email, MSXML, and database drivers) and edit your setup.asp file according to their instructions.
PDshop is a complex application, and requires solid and reliable server resources. If your web server is overloaded with multiple clients/websites (many bulk/low cost hosting services put too many sites on a machine), you may only have a small portion of system resources available for your site, which can result in problems if you have a busy website. Shared web servers are ideal for very small businesses, with low web traffic. If you are a busy retailer with considerable online traffic, we recommend a dedicated web server (or multiple servers with load balancing). The more web traffic you have, the more resources PDshop will use.
If you have made script changes and your script contains an error, or there is a problem with your setup.asp configuration, you would receive a "VBscript" "ODBC" or "ADO" type error. If you are not receiving any specific error messages from the server, than it is likely a component problem (for example, server software such as an email component, an MSXML com object, or database driver).
MSXML Objects:
If you are using Authorize.net’s AIM processing, or the UPS or USPS rate add-on, PDshop may be utilizing the MSXML server objects. There are known bugs with older versions of Microsoft's MSXML, it is recommended that you contact your web host to determine which MSXML object to use. You can change which object PDshop uses by modifying the “xmlhttpobj” variable in your setup.asp file located in your includes directory. If you are the server admin, it is recommended that you install the latest MSXML components from Microsoft.
Other Solutions for Server Administrator’s & Web hosts:
A server re-boot will often correct a server “hang”, but if the problem returns, you should consider re-installing some of the server components such as the database drivers, MSXML, MDAC, as well as latest version of "VBscript". It is crucial that your server be kept up to date with the appropriate “patches” and Service Packs.
Database Related Solutions:
If you experience “hangs” due to a database driver issue, try using a different database driver (for example, if you are using the *.mdb ODBC driver, switch your setup.asp file to connect with the “Jet” drivers). It should be noted that the drivers for Microsoft Access only handle a limited number of connections (for larger websites, with heavy traffic, the MSSQL Server database is more appropriate).
Corrupt MSAccess Databases:
If your database has become corrupt, damaged, or is extremely large, you can receive "timeout" errors or other unexpected problems. Most database corruption issues can be corrected by running the "Compact & Repair" utility built into the Microsoft Access program.
Excessive traffic and MSAccess:
If you are using the default MSAccess database and your site is fairly busy, meaning you consistently have 25 simultaneous shoppers (or over 2000 unique visitors a day), you should be using MSSQL as your database backend. MSAccess is suitable for small businesses, but is not capable of maintaining a large number of simultaneous database connections (this is a limitation of the MSAccess drivers, not PDshop). Microsoft’s SQL Server is an enterprise level database system, designed for heavy traffic. If your web server stops responding, and it coincides with increased web traffic, you may have outgrown MSAccess (you may have outgrown “shared” hosting altogether).
Shared Web Servers:
If your website is hosted on a "shared" server (these are the less expensive hosting plans), troubleshooting may be difficult. If you believe your server has a resource problem, the first step is to try and determine which component is to blame. The best way to proceed is to analyze your web logs, test your site thoroughly, and try to determine what specific functions (pages) trigger your problem. For example, if your server stops responding anytime PDshop tries to process a credit card (or retrieve Real-Time shipping rates), than the “MSXML” component may be the problem. Contact your web host for assistance with these server components; find out which components you should use (Email, MSXML, and database drivers) and edit your setup.asp file according to their instructions.
PDshop is a complex application, and requires solid and reliable server resources. If your web server is overloaded with multiple clients/websites (many bulk/low cost hosting services put too many sites on a machine), you may only have a small portion of system resources available for your site, which can result in problems if you have a busy website. Shared web servers are ideal for very small businesses, with low web traffic. If you are a busy retailer with considerable online traffic, we recommend a dedicated web server (or multiple servers with load balancing). The more web traffic you have, the more resources PDshop will use.
Related Articles
Related Topics
Article Applies to:
ASP (classic Active Server Pages), PDshopPro / Standard, PDshop Plus, PDshop Advanced
Search for help...