I had a dozen or so ASP Runner projects communicating with our Windows 2000 SQL server. They were still working, but I could not get any new ones to work. When I opened the Index page, it jumped to the list page and give me an HTML 500 error.
Based on another question I saw, I removing the (') before the "one error resume next" line on the project's "list" page. A refresh returned error number -2147467259, error description [DBNMPNTW]Access denied. While this is going on, I had SQL Profiler running, and the logs were returning virtually nothing.
Google searches on this error all seemed to revolve around issues with Named Pipes. I found that "Microsoft does not recommend Named Pipes for use in communicating with MS SQL server". On my web server, my SQL Server Client Network Utility listed this as the default. It was also enabled on my SQL server (in addition to TCP/IP).
The solution to this turned out to be fairly simple. I changed the default to TCP/IP on my web server. 1) Run the Client Network Utility (Start->Run and type cliconfg.exe ) on my web server 2) Change the default protocol from Named Pipes to TCP.