?
Solved

Cannot Open Microsoft Jet Engine Workgroup

Posted on 2012-04-03
7
Medium Priority
?
1,072 Views
Last Modified: 2012-04-11
I wrote several (I believe it's currently 7) Microsoft Access 2003 applications that people run.  The applications are linked to tables in a 4.5 GB SQL Server database running in SQL Server 2008 Express.  Five Access applications are local to each computer, and two are run from a server.  They all (local and server based applications) use the same system.mdw file.  There are four terminal servers, each with up to 30 users and about 60 stand alone computers.  Most users use more than one Access application at a time, and some of them run more than one instance of the same application concurrently.
   I converted our Access 97 applications to Access 2003 applications over 5 years ago.  Although all the applications are in Access 2003 format, the system.mdw file is still in Access 97 format.  This is because Access 2003 wouldn't convert this file.  The system.mdw file works fine in Access 97 format and I am able to manage users in this file using Access 2003.
   The past 3 business days users have been intermittently getting the error "Cannot Open the Microsoft Jet Engine Workgroup" when trying to run an Access application.  One user is able to run an Access application using the same system.mdw file while another user can not.  So far, if a user with this problem gets out of all the access applications that he is running, this has fixed the problem and he can then get into the applications without this message.  This is a big problem if it occurs on one of the terminal servers because up to 30 users have to all get out of all of the access applications that they are running to fix this problem.  
   I searched for a fix to this problem and I read that it is a sign that the workgroup file is corrupt when you get this error message.  I don't believe that is the case because other people using other computers can get into the access programs just fine using the same workgroup file.  Last night I repaired and compacted the system.mdw file in Access 97.  It dramtically reduced the size from 116,000 KB to 226 KB, but this morning a couple of users still had the same problem.  I looked at the list of Open Files on the Server 2008 computer that contains the system.mdw file and saw that system.mdw was opened 190 times and system.ldb was opened 150 times.
   What could cause this problem?  Am I reaching a limitation for how many users can open the workgroup file concurrently?  I haven't read about any such limitation, but a week ago people started using another access program that I wrote which causes the system.mdw file to be opened even more.  Would it help to make a copy of the system.mdw file and set some of the programs or some of the users to use the copy so there aren't so many people all using the same workgroup file?
0
Comment
Question by:Declan_Basile
  • 4
  • 3
7 Comments
 
LVL 58
ID: 37801926
<<Am I reaching a limitation for how many users can open the workgroup file concurrently?  >>

 Possibly.  The user limit is 255 concurrent users.  

 First, are any of the DB's secured that you know of?   If not, I would simply create a new workgroup file.

 Second, if you still have issues, I would have multiple copies of it and point users to the one of the copies using the /wrkgrp switch on the command line for the app shortcut.

 This would be very easy to do for example for the Citrix users.  Point them all to one workgroup and everyone else to another.

  You can do this whether or not the DB is secured or not.

Jim.
0
 
LVL 58

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 2000 total points
ID: 37801933
<<Would it help to make a copy of the system.mdw file and set some of the programs or some of the users to use the copy so there aren't so many people all using the same workgroup file?>>

 Sorry, I didn't read your entire comment.  That's exactly right if indeed your problem is the 255 user limit on a JET DB.

Jim.
0
 
LVL 58
ID: 37801954
Oh and the other thing; with everyone out, make sure the .LDB is deleted if it exists.  Also, make sure all users have full read, write, and delete priv for the directory where the DB and workgroup file resides.

 Finially, make sure that the base name  for any DB or workgroup in the same directory is the same (i.e. myApp.MDB and myApp.MDW).  If it is, you'll get all kinds of weird problems.

Jim.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LVL 1

Author Comment

by:Declan_Basile
ID: 37802611
Thank you.  The DB's are secured, so I'll try creating a copy of the workgroup file and pointing the terminal users to the copy.  I'll run that way for a couple of days, see what happens and report back to you.
0
 
LVL 58
ID: 37802649
<<The DB's are secured, >>

 Hopefully someone wrote down the Group, Users, and PID's used to create those.  If so, it's possible to re-create the workgroup file.

 If not, is there an old backup?  Maybe a year end tape from a couple of years past?

  Finially failing that, there are compaines that can recreate a workgroup file for you or desecure your DB's (assuming you can prove ownership).

Jim.
0
 
LVL 1

Author Comment

by:Declan_Basile
ID: 37803602
I do have backup copies.  I don't think that the file is corrupt though because only occasionally a user (or users) of a computer can't get into the programs and when that happens, every else can still get into the programs.  I think if it were corrupt then no one would be able to get into the programs.  So far I haven't seen the problem since I put the terminal users on their own workgroup file.  I'll report back in a couple of days (or sooner if I see the error occur).  Thanks.
0
 
LVL 1

Author Closing Comment

by:Declan_Basile
ID: 37833870
Every since I created a copy of the system.mdw and pointed some people to the copy I didn't get the problem and it's been about a week.  Thanks.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes a method of delivering Word templates for use in merging Access data to Word documents, that requires no computer knowledge on the part of the recipient -- the templates are saved in table fields, and are extracted and install…
Sometimes MS breaks things just for fun... In Access 2003, only the maximum allowable SQL string length could cause problems as you built a recordset. Now, when using string data in a WHERE clause, the 'identifier' maximum is 128 characters. So, …
In Microsoft Access, learn the trick to repeating sub-report headings at the top of each page. The problem with sub-reports and headings: Add a dummy group to the sub report using the expression =1: Set the “Repeat Section” property of the dummy…
In Microsoft Access, learn how to use Dlookup and other domain aggregate functions and one method of specifying a string value within a string. Specify the first argument, which is the expression to be returned: Specify the second argument, which …
Suggested Courses

807 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question