The Microsoft JET Database Engine cannot open the file

  • Hello,

    I have an SSIS package that is trying to access an access database on a network drive. I am using SQL Server 2012 and the SSIS package is in a catalog. The package will run fine from the server where SQL server 2012 is, but when I try to run it from my machine I get the error: "Microsoft JET Database Engine" Hresult: 0x80004005 Description "The Microsoft Jet database engine cannot open the file '\\server\databases$\DBAdmin\LOA\LoaBackEnd.mdb'. it is already opened exclusively by another user, or you need permission to view its data.".

    I have tried several things. I have changed the path to a mapped network drive, then I get an error message telling me it can't find the file, and I have changed the unc to not include the $.

    The only time I have gotten it too work from the server where SQL Server 2012 is and my desktop is when I moved the access database to a local drive on the SQL Server.

    Any Ideas?

    Thanks,

    Sam

  • sounds very much like a permissions issue. Do you understand what the $ means in the UNC path?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • I understand what $ means in the UNC path, I just saw a couple of posts mention that might be the problem.

    If its a permission issue, why does it work from the server where SQL server 2012 is located, and not my pc, wouldn't they be using the same login to run the package? Also I do have to run the package in 32-bit runtime, I don't know if that could be the problem.

    Thanks,

    Sam

  • myoda (10/7/2014)


    I understand what $ means in the UNC path

    What does it mean?

    myoda (10/7/2014)


    If its a permission issue, why does it work from the server where SQL server 2012 is located, and not my pc, wouldn't they be using the same login to run the package? Also I do have to run the package in 32-bit runtime, I don't know if that could be the problem.

    Thanks,

    Sam

    What path are you specifying on the server, presumably a local path such as c:\blah blah\.....

    When running on the server via the agent for instance it uses a different account, from your pc will run as you, are you local adminstrator on the server in question in the UNC path?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

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

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