Too many active users

[Shane Suebsahakarn]

I have a rather odd problem that I'm at a loss to explain.

The mdb is in A2K2 format, and has many tables linked to around 3-4
different back end mdbs. It is running on a Win2K3 server (set up as a TS
application server, if that's relevant).

The process that is running is producing a large number of reports,
sometimes to .snp format, sometimes to printer. When trying to access one
particular mdb, it will come up with the error "<mdb file> in use" or "Too
many active users". This latter one has only come up recently.

The odd thing is that the only thing it is trying to do at this point is a
DCount. When the error message occurs, I can resume code execution and it
runs properly. I *could* error trap that message and resume, but I would
rather get to the bottom of this.

The error is intermittent. When I run the test without other users using the
same data, the error does not occur. The front end is not shared.

Any ideas would be appreciated.

[Larry Linson]

Are your users running using Terminal Server?

Does each user have a separate copy of the front end? If not, that would be
the first step.

Is there a possibility that someone might actually have opened one of the
back end databases for exclusive use? Certainly if all users are logged in
to the same front end, and anyone is modifying design, the other users will
get a message of this kind.

Larry Linson
Microsoft Access MVP

"Shane Suebsahakarn" <sh_a_n_e@gciXc_om.net> wrote in message
news:d4**********@hercules.btinternet.com...

I have a rather odd problem that I'm at a loss to explain.

The mdb is in A2K2 format, and has many tables linked to around 3-4
different back end mdbs. It is running on a Win2K3 server (set up as a TS
application server, if that's relevant).

The process that is running is producing a large number of reports,
sometimes to .snp format, sometimes to printer. When trying to access one
particular mdb, it will come up with the error "<mdb file> in use" or "Too
many active users". This latter one has only come up recently.

The odd thing is that the only thing it is trying to do at this point is a
DCount. When the error message occurs, I can resume code execution and it
runs properly. I *could* error trap that message and resume, but I would
rather get to the bottom of this.

The error is intermittent. When I run the test without other users using the same data, the error does not occur. The front end is not shared.

Any ideas would be appreciated.

[Shane Suebsahakarn]

I did cover the basic stuff properly, I think :-)

Each user does have their own copy of the FE and the BE is definitely not
open exclusively.
Some users do use TS and others run the FE across the network, but the error
seems to
occur regardless of whether it's being run on TS or not - I have
successfully run a full output
run of something like 16-17K files on TS without a problem though.

I've found some references about this message occuring on Access running on
a Linux
fileshare, but that doesn't apply in my case, although I'm wondering if it
could be an issue
with Windows reaching a maximum number of filelocks. The "too many active
users"
*might* suggest that the LDB file is not being cleared out correctly, so I
may just have
to sit and watch it with LDBView and see what's happening.

*sigh*

If you've any other suggestions, I'd be grateful.

"Larry Linson" <bo*****@localhost.not> wrote in message
news:euf9e.20654$Zn3.13697@trnddc02...

Are your users running using Terminal Server?

Does each user have a separate copy of the front end? If not, that would
be
the first step.

Is there a possibility that someone might actually have opened one of the
back end databases for exclusive use? Certainly if all users are logged in
to the same front end, and anyone is modifying design, the other users
will
get a message of this kind.

Larry Linson
Microsoft Access MVP

"Shane Suebsahakarn" <sh_a_n_e@gciXc_om.net> wrote in message
news:d4**********@hercules.btinternet.com...

I have a rather odd problem that I'm at a loss to explain.

The mdb is in A2K2 format, and has many tables linked to around 3-4
different back end mdbs. It is running on a Win2K3 server (set up as a TS
application server, if that's relevant).

The process that is running is producing a large number of reports,
sometimes to .snp format, sometimes to printer. When trying to access one
particular mdb, it will come up with the error "<mdb file> in use" or
"Too
many active users". This latter one has only come up recently.

The odd thing is that the only thing it is trying to do at this point is
a
DCount. When the error message occurs, I can resume code execution and it
runs properly. I *could* error trap that message and resume, but I would
rather get to the bottom of this.

The error is intermittent. When I run the test without other users using

the

same data, the error does not occur. The front end is not shared.

Any ideas would be appreciated.

[Larry Linson]

Shane,

This is not something that I have encountered myself. I remember some
threads on the subject here and, as I've said many times, the best
collection of information and links on Access in the multiuser environment
is at MVP Tony Toews' site http://www.granite.ab.ca/accsmstr.htm. Perhaps
someone with specific experience with this problem can join in here with
some suggestions.

Larry Linson
Microsoft Access MVP
"Shane Suebsahakarn" <sh_a_n_e@gciXc_om.net> wrote in message
news:d4**********@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com...

I did cover the basic stuff properly, I think :-)

Each user does have their own copy of the FE and the BE is definitely not
open exclusively.
Some users do use TS and others run the FE across the network, but the error seems to
occur regardless of whether it's being run on TS or not - I have
successfully run a full output
run of something like 16-17K files on TS without a problem though.

I've found some references about this message occuring on Access running on a Linux
fileshare, but that doesn't apply in my case, although I'm wondering if it
could be an issue
with Windows reaching a maximum number of filelocks. The "too many active
users"
*might* suggest that the LDB file is not being cleared out correctly, so I
may just have
to sit and watch it with LDBView and see what's happening.

*sigh*

If you've any other suggestions, I'd be grateful.

"Larry Linson" <bo*****@localhost.not> wrote in message
news:euf9e.20654$Zn3.13697@trnddc02...

Are your users running using Terminal Server?

Does each user have a separate copy of the front end? If not, that would
be
the first step.

Is there a possibility that someone might actually have opened one of the back end databases for exclusive use? Certainly if all users are logged in to the same front end, and anyone is modifying design, the other users
will
get a message of this kind.

Larry Linson
Microsoft Access MVP

"Shane Suebsahakarn" <sh_a_n_e@gciXc_om.net> wrote in message
news:d4**********@hercules.btinternet.com...

I have a rather odd problem that I'm at a loss to explain.

The mdb is in A2K2 format, and has many tables linked to around 3-4
different back end mdbs. It is running on a Win2K3 server (set up as a TS application server, if that's relevant).

The process that is running is producing a large number of reports,
sometimes to .snp format, sometimes to printer. When trying to access one particular mdb, it will come up with the error "<mdb file> in use" or
"Too
many active users". This latter one has only come up recently.

The odd thing is that the only thing it is trying to do at this point is a
DCount. When the error message occurs, I can resume code execution and it runs properly. I *could* error trap that message and resume, but I would rather get to the bottom of this.

The error is intermittent. When I run the test without other users

using the

same data, the error does not occur. The front end is not shared.

Any ideas would be appreciated.