CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 2014
    Posts
    2

    #-2147467259 - Cannot open Microsoft Jet engine workgroup information file.

    We have an old VB6 app that has been working fine for years, but today 2 different users called up with the same problem, on startup they get this error:

    OpenDatabase error #-2147467259 - Cannot open Microsoft Jet engine workgroup information file.

    c:\blahblah\thedatabase.mdb
    The database is password protected, but we have never used workgroup information files.

    Has anyone else experienced this recently? Is there a new Windows patch that is causing this?

    We cannot reproduce the problem (at the moment).


    edit: looks to be a problem with Kaspersky
    Last edited by thallen; April 9th, 2014 at 02:23 PM.

  2. #2
    Join Date
    Apr 2014
    Posts
    2

    Re: #-2147467259 - Cannot open Microsoft Jet engine workgroup information file.

    I am encountering the same error, and have Kaspersky running. What have you found as a fix or a work around?

    Quote Originally Posted by thallen View Post
    We have an old VB6 app that has been working fine for years, but today 2 different users called up with the same problem, on startup they get this error:



    The database is password protected, but we have never used workgroup information files.

    Has anyone else experienced this recently? Is there a new Windows patch that is causing this?

    We cannot reproduce the problem (at the moment).


    edit: looks to be a problem with Kaspersky

  3. #3
    Join Date
    Apr 2014
    Posts
    2

    Re: #-2147467259 - Cannot open Microsoft Jet engine workgroup information file.

    I haven't tried it, but others have had success with an uninstall of Kaspersky

    But they are supposed to release a fix soon, like within an hour

  4. #4
    Join Date
    Apr 2014
    Posts
    2

    Re: #-2147467259 - Cannot open Microsoft Jet engine workgroup information file.

    Disable KAV and delete System.mdb in the application folder seems to have done the trick for now.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  





Click Here to Expand Forum to Full Width

Featured