Driver's SQLAllocHandle on SQL_HANDLE_DBC failed

Hi there, I have 2 servers, web and SQL server. Both running in Windows 2003 server with IIS6 and MSSQL 2000 installed respectively. Basically the web server runs ASP codes and connects to the SQL server. All the updates are installed and everything runs fine for years.

Problem starts happening today, with all the pages cannot be shown (not only .asp pages but also .html pages, and even gif and jpg image files, as weird as you can imagine) giving varies errors. When I restart IIS or even rebooting both servers, the pages run fine for a while, and the same errors start coming out within 5 minutes. The error message coming out most of the time is shown as below:

"Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_DBC failed"

... or just simple "HTTP/1.1 500 Server Error"...

I've tried reinstalling IIS, even uninstall all the .NET frameworks and install the newest .NET framework 4.0, but no miracle happens.

Obviously a nightmare for me and everybody in the office is screaming at me, as expected....

Any solution?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brendt HessSenior DBACommented:
Don't look too closely at the ODBC errors.  I believe they are a symptom, not a cause (unless you store your graphics in the DB).  The failure on pages not connected to the DB indicates to me something else is going on.

My areas to check - in no particular order

    Memory errors  -- Could swap to known good RAM, or pull RAM one stick at a time to see if issues go away.
    Disk drives getting iffy  -- Use diagnostic tools, check event and system logs.
    Network cables getting iffy -- swap cables to known good cables
    Network Port Failure -- Install an ethernet board and use it for connections testing
    OTHER -- Check for overheating, dust everything.

    Check your AV scans manually
    Check for rootkits - use a different app than in #1
    Check for other possible malware - use a different app than used in #1 or #2

    Okay, check the ODBC connection manually.  If it fails intermittently (instead of on all calls), then it is not a DB issue UNLESS the DB server is suffering from one of the issues listed above.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
eurozeroAuthor Commented:
Seems so.... and the most horrible thing is that when I stop one of the sites, everything else is back to normal. I suspect there is an attack on that particular website....
I have no access to web server, thus difficult for me to check what was happened there, btw from db area, what can I says to them if this not really db performance issues?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.