Oke here I am again:

According the above error i tried to change my connectionstring into:

strConnection =
    "driver={MySQL};" &_
    "server=localhost;" &_
    "uid=root;" &_
    "pwd=pwd;" &_
    "database=database;
    "option=16387" <-- added this line to the connectionstring

Maybe you can try this also.

Thanks

thanks i will try that if i will get the error again ... because once i restarted the iis and since then everything works fine ..

Hi...,

I have the same problem. I already try to reinstall MDAC ans ODBC driver...etc, and the intermitent problem persist..., can someone help me please...!!! Thanks...

I am having the exact same errors dealing with a DB2 database. If anyone's solved this, please post.

I think it can happen when you are try to use EmpId in single quotes.
Oracle don't like numeric ids treated like varchar2. It had created problems for me in asp application. Never Select or Update a record without using CLng when the field is numeric field as in this question.
I have faced a serious problem of this kind, in production, but resolved it afterwards.

Hi @ all,

we get the same error msg from a web server (IIS) since some days (sporadically) without using any database connection but performing xslt transformation on xml documents via msxml4.

So I think, the error isn't caused directly by db connections nor msxml but a layer below used by both.

It looks like the sometimes occuring w2k problem that after closing of files or other objects an immediate open / create fails because of "already open", "in use", or other "cannots".

We'll go on for checking the user/iis/security settings. Thanks for the hints.

We have had a similar problem - intermittent 0x800A01F error on some servers and not other.

I have a theory why these are occurring, which we are currently testing, which I would appreciate comment on from others:-

In a number of place we have while loops displaying rows from a recordset, and the RS is only closed once the full list is displayed. Maybe an ethusiastic user is selecting a link from the list and stopping the complete load of the page.

We are trying two things.

1) Using the readyState for the document, to see if the load is "complete" before allowing the user to select.
e.g.
if (document.readyState == "complete")
{
    url = "<%=Application("AppDirVir")%>";
    url += "lookup/prepostsel.asp";
    url += "?PostNo=" + escape(value);
    url += "&Mode=" + escape("<%=CStr(inMode)%>");
    BusyLookingUp(url);

    Closing = false;
    NotifyClose();
}
else
{
    alert("Please wait for the full list to be loaded before making a selection");
}


2) Building the list in a buffer and only displaying the list once all rows are in the buffer with a response write. This works, but can result in a blank screen for a while which isn't very user friendly - has any-one some handy javascript for a nice loading message?


Let me know what you think
Christine

Hi!
We have exactly the same problem, with Windows 2000 SP4, MDAC 2.8 and Mssql server.
We have tried with all the options of the IIS.
We have converted some very visited ASP pages to .HTML
We have re-written connection strings, and so on.

And the problem goes on.
We are nearly crazy.
The W2000 log does not help a lot.
The IIS crashes and we have to reinitiate it each two-three hours.

Any help?
Thanks a log.

Microsoft VBScript runtime error '800a01fb'

I know where this problem is coming from.

I have a unique set of servers available to me, one of them is being used for prototyping only, and only one person has control and access to it, ME.
Recently I needed to develop a piece of unusual ASP software, kind of like a spider, with an auto repeat loop to make it do what it needs to do.
And that particular error started appearing, so I traced back to what was causing it.
It's a kind of fault in the ASP engines session controls, a bit like a non truncated file.
It only occurs when repeated actions take place using the Server.CreateObject("ADODB.Connection") command a sufficient number of times without fully closing the object properly, at that point that the session buffer overruns and locks up.

Solution.
Well now this is a killer, because if you sharing the server running the ASP, it is not necessarily you that is causing the problem, because any other hosted site using the same application server, can produce the problem for every web site using the same application server.
Now being at that I have full control over the server the solution I applied was to change the settings on the host server disabling "enable session state". And the problem was instantly solved and has never returned.
Unfortunately you might can imagine this means that effectively the server when in this state has no session ID at all.
But it is the only solution that actually properly works.

So in short what you have here is endemic fault with the Microsoft ASP engine.

I also suffer from this particular error.

What does it mean if the server has no session ID state with this option been disabled?

Thanks.
Mike