Quantcast
Channel: All Forums
Viewing all articles
Browse latest Browse all 27852

Intermittent “Out of present range” from Classic ASP after SQL2000-2008 migration

$
0
0

Background: I have just completed a move of approximately 50 classic ASP sites from an IIS6/Sever 2003 and SQL 2000 environment to a new virtual environment of 2 machines behind an nginx load balancer. Each MS machine is running IIS7.5 and SQL2008R2. They current each have 6Gb & 2 VCPUs. The databases are set up in a mirroring configuration (currently without a witness).

During testing all sites appeared to function correctly.

Once live traffic started to hit the sites it became apparent quite quickly that the initial resource allocation (2Gb & 1 VCPU was way too low and was quickly increased). The main problem has come from an intermittent ASP error occuring on approximately 10 (and probably including the busiest) sites on the servers. They will produce a 500 response from an ASP error of Provider error '8002000a' Out of present range.

All research has pointed to causes such as numbers too large to fit into an integer variable and some people have mentioned some correlation with the newer implementation of RAND and NEWINT() in SQL2008 compared to 2000. The stored procedures that appear to cause the error are relatively simple, with some as simple as accepting a single VARCHAR variable (well within the limits) and doing a single field select on a table. Most do not even involve INTs at all and if they do, the values are well within range.

The error can appear on one machine for a given amount of time while during this same time the other server will not necessarily have the error, it sometimes will though. After a while the error will stop occuring, this doesn't seem to correlate with excessively overloaded system resources either.

ASP to database is done via a DSN using SQL Client 10 drivers. The code is using the ADODB connection and command objects. This code has been working happily for 6+ years on the previous servers. The databases are set to compatibility mode 80 (SQL2000).

Can anyone shed any light on where I should be looking to try and solve this please? If there is any other information I can share, specific code snippets etc please just let me know.

Many thanks Eric


Viewing all articles
Browse latest Browse all 27852

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>