IIS 7 and Above
500 Errors - Classic ASP
Last post Nov 29, 2019 08:51 AM by Jalpa Panchal
Nov 27, 2019 05:01 PM|strensk|LINK
We are currently running Windows Server 2016 with a Classic ASP application that is running in 32 bit mode, and is leveraging ODBC32 for it's database calls. This is a load balanced farm of seven servers, and the error has occurred on all of the servers
at different times and days. There doesn't appear to be any rhyme or reason as to why it happens, I'm sure there is, but I haven't been able to find it.
The last time this occurred I tried to get a memory dump through Task Manager, but the dump didn't provide anything useful, as it was created by a 64 bit process on an application running in 32 bit mode.
What starts happening when this goes south on us, is we start getting /loginfunctions.asp Line 464 [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_DBC failed.
The last two times this occurred the application process was using over 3.6GB of memory, so my first thought is a memory, leak, but in what? Then when it is triggered, it chews up memory and can't open an ODBC connection because there isn't enough memory.
I looked into using ODBC tracing, but it is a bit of a hog when it comes to resources, and that would affect end users too much to be effective.
My thought find a way to use a low impact way of monitoring this so we can get a memory dump when it happens, or even create one on the fly while it is occurring so we can find the issue. I've been researching possibly using ProcDump but am unsure of what switches
Any help, suggestions, or even sending me down another road is something I'm grateful for and open to, I just really want to find a solution to this. Thanks in advance.
Nov 29, 2019 08:51 AM|Jalpa Panchal|LINK
did you check the event viewer for the application log? it looks like your odbc driver is corrupted, try to repair it.
make sure you close the connection of the database.
try to use some troubleshooting tools like Debug Diagnostics, Performance Monitor and generate a dump. and analyze the dump file.
you could follow the below article :
How to use the IIS Debug Diagnostics tool to troubleshoot a memory leak in an IIS process