Is there an easy way to find out If all OBJECTS are closed?
in [ASP]
|
From: shall on 30 Apr 2008 08:28 I have several pages ( ASP) that were working OK on NT4. We moved it to Server 2003. At random , it appears that the Server.CreateObject fails. I've looked through the code and it looks OK. Is there an easy way to make sure I have Closed all CONNECTIONS RecordSets etc. TIA Steve
From: Bob Barrows [MVP] on 30 Apr 2008 09:09 shall(a)uaex.edu wrote: > I have several pages ( ASP) that were working OK on NT4. > We moved it to Server 2003. At random , it appears that the > Server.CreateObject fails. > > I've looked through the code and it looks OK. > > Is there an easy way to make sure I have Closed all > CONNECTIONS > RecordSets No. Leaving them open MIGHT cause memory leaks that COULD cause IIS to need to be restarted, however, this would not impact CreateObject. There is something else going on. -- Microsoft MVP -- ASP/ASP.NET Please reply to the newsgroup. The email account listed in my From header is my spam trap, so I don't check it very often. You will get a quicker response by posting to the newsgroup.
From: shall on 30 Apr 2008 13:51 On Apr 30, 9:09 am, "Bob Barrows [MVP]" <reb01...(a)NOyahoo.SPAMcom> wrote: > sh...(a)uaex.edu wrote: > > I have several pages ( ASP) that were working OK on NT4. > > We moved it to Server 2003. At random , it appears that the > > Server.CreateObject fails. > > > I've looked through the code and it looks OK. > > > Is there an easy way to make sure I have Closed all > > CONNECTIONS > > RecordSets > > No. > Leaving them open MIGHT cause memory leaks that COULD cause IIS to need > to be restarted, however, this would not impact CreateObject. There is > something else going on. > > -- > Microsoft MVP -- ASP/ASP.NET > Please reply to the newsgroup. The email account listed in my From > header is my spam trap, so I don't check it very often. You will get a > quicker response by posting to the newsgroup. I have tried to close every Recordset.( I might have missed one) I'm calling a DLL and it has been working OK. I've looked through the code twice to make sure that I have Set oDLL=nothing Here's the error message( It may appear once every two weeks or longer) Error: File /fcsSelectPestMgmt.asp CreateObject Exception. The CreateObject of '(null)' caused exception C0000005.. It acts as if ,on one day, the DLL becomes unregistered. I'm running out of clues on how to solve this. TIA Steve
From: Bob Barrows [MVP] on 30 Apr 2008 14:05 shall(a)uaex.edu wrote: > On Apr 30, 9:09 am, "Bob Barrows [MVP]" <reb01...(a)NOyahoo.SPAMcom> > wrote: >> sh...(a)uaex.edu wrote: >>> I have several pages ( ASP) that were working OK on NT4. >>> We moved it to Server 2003. At random , it appears that the >>> Server.CreateObject fails. >> >>> I've looked through the code and it looks OK. >> >>> Is there an easy way to make sure I have Closed all >>> CONNECTIONS >>> RecordSets >> >> No. >> Leaving them open MIGHT cause memory leaks that COULD cause IIS to >> need to be restarted, however, this would not impact CreateObject. >> There is something else going on. >> > > I have tried to close every Recordset.( I might have missed one) > I'm calling a DLL and it has been working OK. > I've looked through the code twice to make sure that I have > > Set oDLL=nothing > > Here's the error message( It may appear once every two weeks or > longer) > > Error: File /fcsSelectPestMgmt.asp CreateObject Exception. The > CreateObject of '(null)' caused exception C0000005.. > > It acts as if ,on one day, the DLL becomes unregistered. > > I'm running out of clues on how to solve this. > I'm afraid I'm not going to of much help here, except to reiterate that you are likely chasing a red herring at the moment. Based on my admittedly faulty memory, a C0000005 exception is not one of the symptoms caused by failure to close and destroy ADO objects. From http://tutorials.aspfaq.com/8000xxxxx-errors/80004005-errors.html: This could be because you are trying to create an ADO recordset object as a session variable. See http://www.aspfaq.com/show.asp?id=2053 and http://support.microsoft.com/default.aspx/kb/262681 -- Microsoft MVP -- ASP/ASP.NET Please reply to the newsgroup. The email account listed in my From header is my spam trap, so I don't check it very often. You will get a quicker response by posting to the newsgroup.
From: Anthony Jones on 30 Apr 2008 17:53 <shall(a)uaex.edu> wrote in message news:96fd8c05-0b55-4307-8bd3-c686b9e12812(a)x35g2000hsb.googlegroups.com... > On Apr 30, 9:09 am, "Bob Barrows [MVP]" <reb01...(a)NOyahoo.SPAMcom> > wrote: > > sh...(a)uaex.edu wrote: > > > I have several pages ( ASP) that were working OK on NT4. > > > We moved it to Server 2003. At random , it appears that the > > > Server.CreateObject fails. > > > > > I've looked through the code and it looks OK. > > > > > Is there an easy way to make sure I have Closed all > > > CONNECTIONS > > > RecordSets > > > > No. > > Leaving them open MIGHT cause memory leaks that COULD cause IIS to need > > to be restarted, however, this would not impact CreateObject. There is > > something else going on. > > > > -- > > Microsoft MVP -- ASP/ASP.NET > > Please reply to the newsgroup. The email account listed in my From > > header is my spam trap, so I don't check it very often. You will get a > > quicker response by posting to the newsgroup. > > I have tried to close every Recordset.( I might have missed one) > I'm calling a DLL and it has been working OK. > I've looked through the code twice to make sure that I have > > Set oDLL=nothing > > Here's the error message( It may appear once every two weeks or > longer) > > Error: File /fcsSelectPestMgmt.asp CreateObject Exception. The > CreateObject of '(null)' caused exception C0000005.. > > It acts as if ,on one day, the DLL becomes unregistered. > > I'm running out of clues on how to solve this. C0000005 is the classic Access violation error. All the setting stuff to nothing won't help you solve this (and is superflous anyway). The most likely cause is the DLL doing bad things that it got away with on NT but 2003 is less happy about. One area you should research is Data Execution Protection some older DLLs would place something the OS considers to be executable code (usually a vtable) in data memory. Later versions of windows can block the execution of such code. -- Anthony Jones - MVP ASP/ASP.NET
|
Pages: 1 Prev: Is there an easy way to find out If all OBJECTS are closed? Next: CompilationError |