Share via

Problem "communicating with OLE server or ActiveX Control."

Anonymous
2015-02-10T22:09:45+00:00

I used the tablet pc running Windows 8 to develop an Access web app. Lately however, whenever I try to open the app in Access, I get this error message: "A problem occurred while Microsoft Access was communicating with the OLE server or ActiveX Control. Close the OLE server and restart it outside of Microsoft Access. Then try the original operation again in Microsoft Access." I have no idea what is going on.

The web app does open normally on the pc at home (running Windows 8.1) but the above error message comes up when I try to open the app on another machine in the office running Windows 8. Interestingly, this tablet pc opens other apps. The only difference I know of is that the app it cannot open is a much bigger database.

I need help here because I am on the road a lot and rely on the tablet pc.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous
2015-02-17T00:50:58+00:00

Usually if the app will open on some computers, but not others, the problem is with the local database that Access uses to cache the server objects (so it doesn't have to download them every time you open the application).  If something has gone wrong with the cache database, you may see this error.

If that is the problem, you can resolve this issue by deleting the local cached database for the app.  It will get recreated when you 'Customize in Access' again.  You can find the cache database at:

  • C:\users*username*\AppData\Local\Microsoft\Access\DatabaseCache\15.0

The file will be named "appname on server.accdb" (italics replaced with your user/app/server name

Was this answer helpful?

0 comments

10 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-05-07T13:35:57+00:00

    Usually if the app will open on some computers, but not others, the problem is with the local database that Access uses to cache the server objects (so it doesn't have to download them every time you open the application).  If something has gone wrong with the cache database, you may see this error.

    If that is the problem, you can resolve this issue by deleting the local cached database for the app.  It will get recreated when you 'Customize in Access' again.  You can find the cache database at:

    • C:\users*username*\AppData\Local\Microsoft\Access\DatabaseCache\15.0

    The file will be named "appname on server.accdb" (italics replaced with your user/app/server name

    Worked perfect!  Thank You.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-02-17T04:53:06+00:00

    Thanks again. I will work on it.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-02-17T04:38:25+00:00

    I'm glad that helped!

    Now if you can figure out how to make it happen on purpose, be sure to write down the steps and maybe we can figure out how to prevent it from happening in the first place :)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-02-17T02:33:05+00:00

    Thank you very much, Shane. That solved the problem instantly.

    Was this answer helpful?

    0 comments