Cannot Open Microsoft Jet engine workgroup information file

[Steve]

Hi all.

I've searched this newsgroup for similar postings and they all seem to
be under a slightly different scenario than what I'm experiencing.

I have an application with my own User Security file (BB.MDW) which is
used to access several secured access databases. The workgroup file
resides in the same directory as the .mdb files with a different name
than the .mdb files.

What happens, though, is several users will be running fine and
accessing the databases without problems and subsequent users will
attempt to access the secured database(s) and encounter the error.
The applications are being run within an Application Pool. The
application pool processes have the proper permissions to the
directory where the .mdb and .mdw files reside so I know it's not a
file permissions issue.

Also, I'm pretty confident that the BB.MDW file is not corrupt because
the users tell me that the problem clears up when: 1) Application Pool
is restarted; 2) system is rebooted; 3) left alone for a while.

This leads me to believe the cause of the problem is due to a maximum
number of users connecting to the workgroup (or .mdb) file. To test
this theory, I created a simple VB application that used ADO to create
an array of open ADODB.Connection objects against my database using
the BB.MDW to see if there is a limit on open connections and after 64
connection objects I received an ADO error of 'Unspecified
error' (-2147467259).

Would the "cannot open workgroup informatino file" error still occur
if the User workgroup file is not corrupted but the system.mdb/.mdw is
bad?

Does anyone else have any suggestions as to why this error message may
occur and affect some users but not all users?

I'm running out of ideas on what else may cause this problem since the
suggestions provided in other postings don't quite fit my scenario.

Thanks in advance for any and all suggestions.
Steve Cummings

 

[S.Clark]

Sorry I don't have an answer, but try posting this question to the 'Access
Security' newsgroup. It may have a better change to be seen by the right
people there.

 

[Steve]

Sorry I don't have an answer, but try posting this question to the 'Access
Security' newsgroup.  It may have a better change to be seen by the right
people there.














- Show quoted text -

Thanks for the suggestion. I'll post it there too.

 

[david]

Access can handle 256 simultaneous r/w connections from
different users, so the problem at 64 connections is not a
Jet/Access problem, it is a problem with your connection pool,
Windows, or ADO.

Probably a Windows problem, because the simultaneous use of
a particular security database should be totally transparent to
the connection pool.

No, a problem with system.mdw should not show up as a problem
with user.mdw.

When using Access in design mode, you may see exclusive locks
on user.mdw, but no reason to expect your application pool to
do that.

Your application pool is a single user, so perhaps some kind of
user file connection limit? or perhaps a server load problem (timeout)?

(david)

 

[Steve]

Access can handle 256 simultaneous r/w connections from
different users, so the problem at 64 connections is not a
Jet/Access problem, it is a problem with your connection pool,
Windows, or ADO.

Probably a Windows problem, because the simultaneous use of
a particular security database should be totally transparent to
the connection pool.

No, a problem with system.mdw should not show up as a problem
with user.mdw.

When using Access in design mode, you may see exclusive locks
on user.mdw, but no reason to expect your application pool to
do that.

Your application pool is a single user, so perhaps some kind of
user file connection limit? or perhaps a server load problem (timeout)?

(david)















- Show quoted text -

David,

Thanks for the input. I suspected my 64 ADO connections wasn't due to
the workgroup limit of 255. Was looking for confirmation, I guess.

As for the application pool suggestions, I'll ask my field tech what
the settings of the application pool are to see if there is anything
in there that might "stand out".

Regards,
Steve