Bob
Wed Apr 30 13:05:08 CDT 2008
shall@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/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.