Connection Error

  • *newbie disclaimer*

    I'm trying to do a report that pulls information from an Access 2.0 database (don't ask ) set up as a shared data source.  It works fine inside .NET when I go to the preview tab.  When I deploy to my web server and try to run the report, it tells me I can't connect to the database with this error: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

    I'm pretty sure it's not a permission issue.  Any Ideas?


    Two muffins are sitting in an oven. The first one turns to the second and says "pretty hot in here, huh?"
    The second muffin glances at the first and then shrieks in fear,
    "AAAAAAHH!!! A TALKING MUFFIN!!!"

  • Okay... I've been fiddling with this and have more info to add...

    Apparently on a shared data source, you modify the credentials the web server uses by clicking on your data source and changing them there.  However, to change the credentials you're using inside .NET, you change them through the solutions explorer. 

    The way it works in the preview tab is to use no credentials.  So, I changed it on the server to not require them, and now it tells me my database "is already opened exclusively by another user, or you need permission to view its data."

    I made a copy of my database that nobody else is using, so I'm thinking it's not locked by another user.  Maybe it is a permissions issue after all.

    The user in IIS that the server uses for anonymous access has been given full access to the mdb file.  What else do I need to do?

    Thanks in advance for your help,

    Casey


    Two muffins are sitting in an oven. The first one turns to the second and says "pretty hot in here, huh?"
    The second muffin glances at the first and then shrieks in fear,
    "AAAAAAHH!!! A TALKING MUFFIN!!!"

  • Make sure that the Connection string does not have a Mode= setting that may be causing multi-user issues.

    If you are using IIS, on the Web server: Add the IUSR_<machinename> and ASPNET accounts to the local IIS_WPG group, add domain IIS_WPG membership to the local IIS_WPG, and for the MDB directory grant full access to the domain IIS_WPG. This will fix all MDB access permission issues.

    Tip: Create a test.udl file on your desktop, and double click it to launch the Data Link Properties UI, after changing settings, choose OK; then open this file in notepad to see what connection strings settings are possible. The Mode= setting is on the Advanced tab, Other section and can also be seen in the All tab list. You use the Test connection to verify your settings, just remember that you are accessing the MDB directory as the logged on user account.

    Andy

  • I was able to get it working by creating a local copy of the database on my web server.  Even with the permissions set exactly the same, it still bombs when I try to access it through a share on another server.  I'm not really sure what's causing this, but I can continue to poke at it... being able to see it at all was the step I couldn't get past.

    Thanks a lot for your help!

    Casey


    Two muffins are sitting in an oven. The first one turns to the second and says "pretty hot in here, huh?"
    The second muffin glances at the first and then shrieks in fear,
    "AAAAAAHH!!! A TALKING MUFFIN!!!"

Viewing 4 posts - 1 through 3 (of 3 total)

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