By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,002 Members | 1,269 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,002 IT Pros & Developers. It's quick & easy.

Is there an easy way to find out If all OBJECTS are closed?

P: n/a
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
Jun 27 '08 #1
Share this Question
Share on Google+
4 Replies


P: n/a
sh***@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.
Jun 27 '08 #2

P: n/a
On Apr 30, 9:09 am, "Bob Barrows [MVP]" <reb01...@NOyahoo.SPAMcom>
wrote:
sh...@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
Jun 27 '08 #3

P: n/a
sh***@uaex.edu wrote:
On Apr 30, 9:09 am, "Bob Barrows [MVP]" <reb01...@NOyahoo.SPAMcom>
wrote:
>sh...@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/8000xxxx...5-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.
Jun 27 '08 #4

P: n/a

<sh***@uaex.eduwrote in message
news:96**********************************@x35g2000 hsb.googlegroups.com...
On Apr 30, 9:09 am, "Bob Barrows [MVP]" <reb01...@NOyahoo.SPAMcom>
wrote:
sh...@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
Jun 27 '08 #5

This discussion thread is closed

Replies have been disabled for this discussion.