Share via

cannot open the microsoft jet engine workgroup

Anonymous
2014-04-09T14:36:29+00:00

Several of my customers have called this morning with the above error message when running applications using MS Access as the back end. This is on windows xp and 7.  All of the PC's having the problem received "Critical Updates" last night or this morning. A System.MDW file keeps being created with 0 bytes. What happened last night and how can I fix it.  I have 20+ clients so far with this problem, and I am sure more will come as others come into work.

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 No comments

5 answers

Sort by: Most helpful
  1. Anonymous
    2014-04-09T15:11:00+00:00

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2014-04-09T19:56:24+00:00
    • Disable Kaspersky active scan.
    • Find System.mdb (often in the application directory, but may be in other locations). It will be 0 bytes and have today's date, or date of first error
    • Delete the System.mdb file (some cases .mdw)

    Contact Kaspersky and complain. I think they know by now from their forums replies.

    Once Kaspersky releases a new update you can attempt again

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-04-09T15:39:09+00:00

    It worked, thanks so much!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-04-09T15:22:40+00:00

    Thanks, I will check it out.  Seems like the forum is really starting to hit this issue a lot now.

    Was this answer helpful?

    0 comments No comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more