I am trying to connect to a password protected Access 2010 database using PowerPivot.  After configuring the connection, I click Test Connection, I get an error saying that it can't start the application. The workgroup information file is missing or opened exclusively by another user:

============================
Error Message:
============================

Cannot start your application. The workgroup information file is missing or opened exclusively by another user.
----------------------------
Failed to connect to the server. Reason: Cannot start your application. The workgroup information file is missing or opened exclusively by another user.

============================

I know the database isn't opened exclusively by another user. I've even created my own local access database that I password protected and still get the same error.

Thanks

Jeff

• Moved by Luna Zhang - MSFTMicrosoft contingent staff Friday, November 15, 2013 5:29 AM

Hi,

Thank you for posting in the MSDN Forum.

Since the issue is more relate to the feature of Office product, I'd like to move it to Office 2010 for IT Pro disccussion forum.

The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.

Thanks for your understanding.

Hello,

Thank you for your post.

This is a quick note to let you know that we are performing research on this issue.

Regards,

George Zhao
TechNet Community Support

When you are creating a database, there are three common mistakes that enable Access users to circumvent security:

• You create the database and its objects while you are logged on as the Admin user.
• You do not remove the default Users group permissions that are granted in full for all objects.
• Your distributed application includes the same System.mdw file that was used to create the database. In the System.mdw, the Admin account has no password and is a member of the Admins group.

To protect your database from being changed by other Microsoft Access users, follow these steps:

1. Start Microsoft Access, and then open any database.
2. On the Tools menu, point to Security, and then click Workgroup Administrator. Create a new system database (System.mdw) that has a unique name, organization, and workgroup ID.
3. On the Tools menu, point to Security, and then click User and Group Accounts. Click the Change Logon Password tab, assign a password to the Admin user account, and then click Apply.
4. In the User and Group Accounts dialog box, click the Users tab. Create a new user account, and then add the account to the Admins group. 
5. In the Name box under User, select the Admin user name. Remove the Admin account from the Admins group, and then click OK.
6. On the File menu, click Exit. Restart Microsoft Access.
7. Create a new database.
   
   After you have named the new database and clicked OK, the Logon screen appears.
   
   Note that this is different from earlier versions of Access, where the Logon screen appears before Access starts.
8. Type the name of the user that you created in step 4. Leave the password blank.
9. On the Tools menu, point to Security, and then click User and Group Accounts.
10. Click the Change Logon Password tab, type a password, and then click OK.
11. On the Tools menu, point to Security, and then click User and Group Permissions. Click the Permissions tab, and then select Groups under the List options to display the group names in the User/Group Name box.
12. In the User/Group Name box, click Users. Select the appropriate object type in the Object Type box to display the various objects in the Object Name box, and then remove the default Users group permissions for the following objects that appear in the Object Name box: <Current Database>
    < New Tables/Queries>
    < New Forms>
    < New Reports>
    < New Macros>
13. Import all of the objects from your original database into the new     database.
14. Create other group and user accounts as necessary.
15. Assign group and user permissions to your objects as appropriate.
16. Optional: Close the database, and then use the Encrypt/Decrypt Database command (click Tools, and then point to Security) to encrypt the database. (This step is optional.)

• Proposed as answer by Office Support - MSFT Friday, November 22, 2013 8:40 PM

Hi Jeff,

the answer comes a bit too late, but I am sure it will help people coming after me to this topic.

I had the same issue described here. The issue seems to be connected with the encryption method used in Access 2010. The solution, to change the encryption method to "legacy" in Access.

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

"Some reports of problems with password longer than 14 characters. Also that some characters might cause trouble. If you are having problems, try change password to a short one with normal characters.

Note! Reports say that a database encrypted using Access 2010 - 2013 default encryption scheme does not work with this connection string. In Access; try options and choose 2007 encryption method instead. That should make it work. We do not know of any other solution. Please get in touch if other solutions is available!"

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

To change the encryption method in Access. Open your Database in Access, go to File -> Options -> Client Configuration -> Encrypting method and choose the legacy option.

That should make your password protected Access accessible via Power pivot (assuming you have entered the right password in the connection configuration in Power pivot :-)

For reference:  https://www.connectionstrings.com/access/