Post reply

ASP & SQL ERROR: An exception occurred: Open

  • May 27, 2004 at 8:25 am

    #85126

    We have a problem with an intermittent error occurring on our IIS server:

    Error Type:

    Microsoft VBScript runtime (0x800A01FB)

    An exception occurred: 'Open'

    /include/login_office_check.asp, line 10

    This is basically the first time the program goes and reads a SQL table to check authentication of the user.

    The only way to over come this is to reboot the server. We also get a few errors in the event log.

    Active Server Pages error 'ASP 0115'

    The more I read the more I hear people having the same problem, I'm sure it is connected to SQL in some manner !

    CAN ANYBODY HELP PLEASE ????

    Thanks

    Mike

  • May 28, 2004 at 6:23 am

    #508174

    May be this helps:

    http://support.microsoft.com/?kbid=262681

     

    Reshu

    Naveen

  • May 28, 2004 at 10:13 am

    #508245

    Hi,

    Thanks for the reply.

    Sorry I don't think so as I do not store record sets into a session !

    Thanks.

    Mike

  • May 28, 2004 at 11:06 am

    #508254

    You might have an asp page somewhere that opens a connection and doesn't close it. Eventually you get too many connections and can't open any more. Of course rebooting the server resets this.

  • June 1, 2004 at 6:37 am

    #508483

    Thanks, do you know if there is a way of determining the number of opened connections ? Is this set-up in IIS ?

    I could test this with a dummy script and continually refreshing the screen to create a new connection per page !

    Cheers.

    Mike

  • June 1, 2004 at 9:06 am

    #508516

    In QA, the number of current connections is shown in the lower right hand corner.

  • November 12, 2004 at 9:32 am

    #529958

    Sorry, still not got to the bottom of this !

    Problem is I have so much asp code to try and catch this it is proving very difficult.

    I still have the problem and the only way I can overcome this issue is to stop and restart the IIS services.

    In checking the code I have found occurances where I had a recordset point to a dead connection. Either I have a few more of these or it is something else !!!

    Still looking for answer to this one.

    If I come up with something I will post it...

    Mike

  • January 25, 2006 at 1:14 pm

    #617022

    Has anyone found a solution to this.

    We are experiencing exactly the same problem. I have ruled out recordets/sessions and any erroneous open connections by disabling all other websites except a test script (then restarting iis).

    Tried installing IIS on our database server(sql) and running websites off there. Still getting exactly the same problem. I would really appreciate any advice/possible solutions.

    Through process of elimination I'm thinking it must be something to do with the SQL server and not IIS as originally thought.

    Thoughts very very very much appreciated....

    Thanks

  • January 26, 2006 at 2:48 am

    #617094

    Hi,

    We still experience the problem every now and again, however, we have discovered that we have minimised it by the following:

    1. On your IIS server add the following accounts to the Administrators group IUSER_servername & IWAM_servername. This then generated more interesting events in the event log when an error occurred.

    2. Check your ASP code to ensure that you have set both your recordset & connection = nothing when finished.

    Depending upon the activity on your server, it may take a little while for it to trip up again. We noticed that in the event log the actual .asp file that caused the fault was now listed, and after spending hours going through the code there was infact missing code to set the recordset to nothing!! I convinced myself the code I had written was perfect!

    Hope this helps.

    Mike

  • January 26, 2006 at 7:57 am

    #617171

    hehehe... toldya.  

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply