[kmf165]

Hi everybody there.

I have been read through every post regarding this error but it is not what I faced.

I have two website within same IIS ( One as default and another I put a host header value) . I created and point both two virtual site to the same asp application called REMS into both website. But sometimes the one with host header will prompt error

ADODB.Recordset error '800a0e78'
Operation is not allowed when the object is closed.
/REMS/includes/overall_header.inc, line 17

The one with default website no problem (but actually pointing same application file)

The problem sloved when i restart IIS. Any advices?

Thanks

[minority]

your record set is closed you need to make sure that it is open.

make sure you have this and it is correct (Note the rsinsert can be called anything)

set rsinsert = server.CreateObject ("ADODB.Connection")
rsinsert.open = "Provider=Microsoft.Jet.OLEDB.4.0; Data strCon=C:\Intranet\ncr\database\db.mdb;User Id=admin;Password=;"
rsSQL = "SELECT * FROM table"
rsinsert.Open strSQL, strCon
rsinsert.close

Make sure if you are using the database that all the calls are made within the rsinsert.open and the rsinsert.close as if you do them out side then you will get the error you are having.

if that doesnt help you will need to post your code.

[kmf165]

Hi, thanks for reply.

Basically I think it is not the problem of unclosed rs. I am making a asp page which will refresh every 30 second, and I can say it works atleast more than once ( normally it happen after 30min). I dont understand why it happened only after certain time period but not from the begining.

And I also find out my server's AppPool eaten up my memory up to 400mb.

I have checked from MS support site and mention that there is a hotfix in Windows Server 2003 SP1 but actually I already patched before.

Thanks

connection timeouts & connection limits. what type of database?

[kmf165]

Ok, lets make it clear on my application process.

I am using three tier which asp scripts serve as client. I created a object dll which will handle database connection while the database is in another server. My problem now is the connection from the dll was terminated on its own after certain amount of time.

I test my application on two platform. One is windows 2k with IIS 5.1 where another is windows server 2003 SP1 with IIS 6.

My asp pages will refresh every 3 minutes which will show updated info, these runtine runs perfectly under W2K IIS5. Where as for Windwos server 2003, it runs well from begining but after certain time of amount, that error happended.

Thanks