locked
System.Data.OleDb.OleDbException: Unspecified error RRS feed

  • Question

  • User-2104361029 posted

    Hi All,

     

    I have a ASP.NET website that is using an access database. In the website on the pages where the data is fetched from the database sometimes it gives the below error. When I delete the .ldb file the website starts working. Can any body suggest me a possible solution for it?

     

    Server Error in '/' Application.

    Unspecified error

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Data.OleDb.OleDbException: Unspecified error

     

    Monday, February 28, 2011 2:47 AM

Answers

  • User1867929564 posted

    Yes,I think you are not closing the connection properly.
    objRS.Close
    SET objRS = Nothing
    or simply con.Close
    dr.dispose()

    give delete permission to folder where ldb/mdb file reside.

    ldb file automatically get reated and auto get delete.it doesn't harm.
    if connection is not properly close then ldb file won't get deleted and hence the problem.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, February 28, 2011 5:04 AM

All replies

  • User967319531 posted

    My best quess is that you are not closing the database connection. Does the stacktrace contain any detailed information?

    Monday, February 28, 2011 3:40 AM
  • User1867929564 posted

    Yes,I think you are not closing the connection properly.
    objRS.Close
    SET objRS = Nothing
    or simply con.Close
    dr.dispose()

    give delete permission to folder where ldb/mdb file reside.

    ldb file automatically get reated and auto get delete.it doesn't harm.
    if connection is not properly close then ldb file won't get deleted and hence the problem.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, February 28, 2011 5:04 AM
  • User3866881 posted

    Well, you can try to see this nice article. Maybe this helps : http://support.microsoft.com/kb/825738/en-us

    If this still cannot solve your problem. I think you should debug your application and tell us by pointing out which statment will cause this kind of error for more analyses……

    :)

    Tuesday, March 1, 2011 3:49 AM