HTTP 500.100 Microsoft Jet database Engine could not open the file.. already..

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • student2
    New Member
    • Aug 2009
    • 36

    HTTP 500.100 Microsoft Jet database Engine could not open the file.. already..

    Hi,
    I'm a student looking for any recommendation to finding a solution to the following problem.

    (Hope I'm posting in the correct 'section' of the forum, since my error says both IIS and ASP)

    I'm running IIS on my WIndows XP Pro OS.
    I'm connecting an Access database (.mdb file) to Dreamweaver CS4.
    I've made the connection with the following string

    "Provider=Micro soft.Jet.OLEDB. 4.0;Data Source=C:\Inetp ub\wwwroot\mySi te\mySite.mdb;"

    When tested it shows as successful. If I add words, tables, images and simple html codes it works fine when tested and previewed through the web browser.

    However, once I add a recordset/or query it produces the following error:-

    HTTP 500.100 Internal Server Error- ASP Error IIS

    Error Type:
    Microsoft Jet database engine cannot open the file C:\Inetpub\wwwr oot\mySite\mySi te.mdb
    It is already opened exclusively by another user or you need permission to view its data
    /mySite/index.asp/line 9


    Line 9 is where my recordset is when I view the code.
    I've tried IUSR/Localmachine
    I've tried to work with user permissions
    Uninstalled and re-installed IIS
    I seem to be getting no solution.

    Any help rendered would be greatly appreciated.
    Thank you :-)
  • Frinavale
    Recognized Expert Expert
    • Oct 2006
    • 9749

    #2
    It sounds like you aren't properly closing the connection to your database.
    If the resource is not properly closed then the next person accessing the website won't be able to do anything with the database.

    If this isn't the problem then it could be that you need to implement some sort of lock on the database ensuring that new connections have to wait their turn while the existing connection uses the database.

    I would first investigate the possibility that you aren't properly closing your connection though because I think that is the root to your problem.

    -Frinny

    Comment

    • student2
      New Member
      • Aug 2009
      • 36

      #3
      Thank you very much!

      Comment

      Working...