Replies to post #35046 on The Question and Answer Board (IHUB)

[IH Geek [Dave]]

>>Also reported an error in global.asa, which is a file I'd never looked at, but am glad I did.

Interesting. If the next crash comes after an Event code 36, be ready to check this out:

Troubleshooting ASP: Event ID 36 - ASP Fails, but static pages work

1. If a Global.asa file exists in the root of your Web site, rename it as Global.old, stop and restart the Web services, and then create a test ASP page in Notepad with the following code:
<%
Response.Write "This is a test ASP page."
%>

Save this file as Test.asp in the root of your Web site, and try to open the file on the Web server.

If ASP pages load in your Web browser after you have performed this step, the problem is with the Global.asa file.

If ASP pages still do not load, proceed to step 2.

continued....

http://www.iisfaq.com/default.aspx?View=A463&P=170

[Dimension]

Bob: not sure if anyone responded to any of these thoughts of yours already...just getting home.

regarding the global.asa. that in essense is a wrapper to the database access code as you probably surmise by now. it is usually not something you want to touch or modify. if you need to do anything, it is best to do it in your custom code and not play with that...

your are correct, there is no Recordset.closeAll, and unlike the old DAO, recordset and connections are totally separate.
I think the best thing is to close recordset immediately after using them. you could consider disconnected recordsets if you need to still maintain a reference to the data.
Also, i do NOT believe closing the connection will close all recordset and will likely lead to memory leaks. This is especially true if you are using connection pooling.

you mentioned several times that recordsets were being closed "AFTER" the cleanup routine. is it possible they are being executed/opened Asynchronously? if so, it is likely that you may not be able to close until they have finishing processing/fetching.

i'm leading to think the issue may be what you mentioned yesterday with session variables. has clearing that out helped any?