General discussion

Locked

Too many active users

By markkorolevich ·
System: Netware 4.11, 22 Win95/98 users, MS Access database on the server.

I have a Visual Basic program using ADO to connect to the Access database. Every so often, some users will get the message "Too many active users."

I have searched the MS Knowledge base only to find the message in a list of trappable errors, and no explanation as to what it means.

I have been on the Novell forum and several other people have had this same problem. The problem seems to also happen with SQL Server.
I don't appear to be getting any errors on the server. No one seems to know what is generating this error.

Any Ideas what might be happening here?

Thanks

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Too many active users

by TOAB In reply to Too many active users

Mark,
have you checked your system locks?
At the console type set, Select the number for locks, check the values for the following:
Maximum Record Locks per connection,
Maximum File Locks per connection,
Maximum Record Locks,
Maximum File Locks.

Try increasing the values of these and see if it reduces or stops those errors.
Brett

Collapse -

Too many active users

by markkorolevich In reply to Too many active users

The question was auto-closed by TechRepublic

Collapse -

Too many active users

by rwscc In reply to Too many active users

The very first thing to check is that ALL clients have a connection defined as a "system dsn" or "user dsn", if one client connects as a "file dsn" it will lock out the database. Check for this in ODBC definitions. That the database file is flagged as sharable. For data integrity, change the advanced setting on the clients to "True Committ = On". To make the locking mechanisms more efficient keep all directories in the path to the database less than 9 characters long and name the file with an 8.3 filename. If this hasn't resolved the problem, you can increase the file locking parameters using servman. Note that increasing these parameters uses up memory.

Collapse -

Too many active users

by markkorolevich In reply to Too many active users

The question was auto-closed by TechRepublic

Collapse -

Too many active users

by rwscc In reply to Too many active users

The very first thing to check is that ALL clients have a connection defined as a "system dsn" or "user dsn", if one client connects as a "file dsn" it will lock out the database. Check for this in ODBC definitions. That the database file is flagged as sharable. For data integrity, change the advanced setting on the clients to "True Committ = On". To make the locking mechanisms more efficient keep all directories in the path to the database less than 9 characters long and name the file with an 8.3 filename. If this hasn't resolved the problem, you can increase the file locking parameters using servman. Note that increasing these parameters uses up memory.

Collapse -

Too many active users

by markkorolevich In reply to Too many active users

The question was auto-closed by TechRepublic

Collapse -

Too many active users

by rwscc In reply to Too many active users

The very first thing to check is that ALL clients have a connection defined as a "system dsn" or "user dsn", if one client connects as a "file dsn" it will lock out the database. Check for this in ODBC definitions. That the database file is flagged as sharable. For data integrity, change the advanced setting on the clients to "True Committ = On". To make the locking mechanisms more efficient keep all directories in the path to the database less than 9 characters long and name the file with an 8.3 filename. If this hasn't resolved the problem, you can increase the file locking parameters using servman. Note that increasing these parameters uses up memory.

Collapse -

Too many active users

by rwscc In reply to Too many active users

Sorry for the multiple entries. My commection died as I hit the submit button. When it came back, I hit submit again because I was still on the same page. Ooops!

Collapse -

Too many active users

by rwscc In reply to Too many active users

I've seen VB applications (in house) start multiple connections to the same database. It made our SQL Server run out of licensed connections way to soon. But on Novell I think you could see the extra connections in Monitor taking you above the licensed connection count.

Collapse -

Too many active users

by markkorolevich In reply to Too many active users

The question was auto-closed by TechRepublic

Back to Networks Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums