Cannot Open Microsoft Jet Engine Workgroup

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?
LVL 1
Declan_BasileITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<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
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
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
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Declan_BasileITAuthor Commented:
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
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<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
Declan_BasileITAuthor Commented:
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
Declan_BasileITAuthor Commented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.