Hi Bill
It hasn't reappeared, at least, although I must admit I haven't installed any new updates yet this week! At least I know what to look for now.
Regards
Sue
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Bill Mosca
Sent: 12 April 2014 18:59
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Re: [MSAccessPros] error connecting to database. Cannot open the MS Jet Engine workgroup information file
Hi Sue
I don't think you would have found anything in that file. It was 0 KB in size. And I DO think the MS Office update had something to do with it. It might have broken something in Kaspersky.
Regards,
Bill
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Sue Hewson
Sent: Friday, April 11, 2014 9:35 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Re: [MSAccessPros] error connecting to database. Cannot open the MS Jet Engine workgroup information file
Hi Bill
Maybe – very strange generating that file and I intended to have a look at it before I deleted it, and then forgot. Without that input though, we might still have been searching for a solution – I was fixated on the purely coincidental Office 2010 upgrade and the program's developer was convinced it some security measure we'd implemented. So easy to lead yourself down a blind alley – thanks again!
Sue
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of wrmosca@comcast.net
Sent: 11 April 2014 15:21
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Re: [MSAccessPros] error connecting to database. Cannot open the MS Jet Engine workgroup information file
You're welcome, Sue. Maybe Kaspersky made an update at their end to fix this problem.
-Bill
---In MS_Access_Professionals@yahoogroups.com, <sue@questor-cp.co.uk> wrote :
Hi Bill
I tried disabling Kaspersky system watcher and deleted the system.mdw file, but it had no effect. However, there was, as your poster said, a 0kb system.mdb file in the application's folder, which I have deleted and hey presto, it opens. Nothing has happened to our own Access systems though, which is very odd. I've enabled Kaspersky system watcher again and application is still working, at the moment anyway.
Thanks again!
Sue
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of wrmosca@comcast.net
Sent: 09 April 2014 21:02
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Re: [MSAccessPros] error connecting to database. Cannot open the MS Jet Engine workgroup information file
Sue
This started popping up all over the internet forums. It's caused by the latest Office updates that went out on Tuesday. Are you using Kaspersky virus scanner? The advice I've found relates to that scanner.
The System.mdb (a file size of 0 KB) is created in the application directory. Disable Kaspersky system watcher and remove System.mdb file.
The above advice is sketchy. I don't know if the poster meant System.MDW or not.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
Microsoft Office Access MVP
My nothing-to-do-with-Access blog
---In MS_Access_Professionals@yahoogroups.com, <sue@questor-cp.co.uk> wrote :
I hope someone can help; I am getting this error when attempting to open an application, since moving to Office 2010.
This is the application about which I posted a few months ago, when I was trying to generate a complicated query from it. That was successful eventually, but the problem is that the app, developed by someone else, has an Access backend (.mdb, Access 2000 format) and that's the only part I can access.
Since installing Office 2010, trying to start the app produces the above error. Any database or backup will open by itself in Access so they are not corrupt. It's obviously not something the developer has come across before either so I thought I would post here in case anyone has any ideas. The standard workgroup file is in %userprofile%/AppData/Microsoft/Access/, but I can't understand why it would matter anyway as – although they are on the same machine – the access dbs are just linked tables.
I've tried several fresh installs, and this problem is occurring on 2 machines – the first of which originally had Office 2010 installed a few weeks ago in parallel with 2007, but I uninstalled Office 2007 from it yesterday – after which this issue began. The other is a new machine which had Office 2010 installed from scratch, yesterday.
Thanks in advance
Sue
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (10) |
Tidak ada komentar:
Posting Komentar