Why am I getting an error saying No Available User Access Slots?

Answer: ExpressMaintenance includes new techniques to prevent unauthorized use of the software.  The program utilizes a method of tracking the number of connected users and grants or denies access based on the licensed version you have purchased.  If the licensed user slots are all in use, you will receive an error indicating that no user access slots are available.

Each time a user runs the program a concurrent user slot is used.  When the user exits the program, the user slot is released for use by another user.  When running ExpressMaintenance, you can check the Total, Used and Available concurrent user slots by accessing the Administration / Registration screen.

If users at your installation are being denied access due to unavailable user slots, you may need to upgrade to a larger license for more users.  However, if you believe users are being denied access incorrectly, you will need to check the steps below:

Begin by making sure you are running the latest release of ExpressMaintenance.  You can do so by check the Updates page of our website.

To Verify Proper Accounting of User Slots

1. Run ExpressMaintenance

2. Go to the Administration / Registration Screen

3. Verify the registration license for the proper number of users.

4. Verify the number of Concurrent User Access Slots – Total, Used and Available.

5. Take action as outlined below based on the Total and Available slots.

A. If the Total reflects less than your licensed users, then you have not registered the program properly and you should enter the serial number and registration codes and click the Register button to properly register.  If you do not know your registration codes, email our support department for the information at: Email Support.  Be sure to include your company name.

B. If the Total reflects the correct number of licensed users, then you have registered the program properly and the problem is likely a network permission issue. You will need to notify your IT people and let them know that the user must have read / write access to the folder where the Maintenance.exe file resides. The reason for this is that the network control file resides in that folder and it tracks the users access slots as they are used / released.  An alternative to making the entire folder read / write is to apply that permission level to the files “Connection.ini”, “ExpressMaintenance.naf” and “ExpressRequest.naf” (if applicable).  If you have concerns about allowing read write permission to these files you can place them else where and point to them in EM under Admin / Defaults.

C. On very rare occasions, the network access file has been known to become corrupt.  You can simply remove the ExpressMaintenance.naf and ExpressRequest.naf files.  They will be automatically re-created when the program is executed.  However, the folder must still offer read / write access by the users as outlined above.

D. If you cannot run ExpressMaintenance to check the concurrent user slot information then you should try running the program from the server or assume the problem is item B above.

E. If you are running Windows 2000 on the server computer and Windows XP on the client workstations, please see the special note below for more details.

Special Note About Windows 2000 Server

There is a known file unlocking bug with Windows 2000 Server and Windows XP client workstations.  When first opening, ExpressMaintenance writes and closes the ExpressMaintenance.naf file on the server.  The problem is that Windows 2000 Server will not unlock the file until the application closes rather than when the application instantly releases the file.  Below are four possible solutions for getting around the problem.

Solution #1 (recommended)

The best solution is to upgrade the Server or use a different server with XP Professional, XP Server, or Windows 2003.  It is known that the bug is confined to Windows 2000 Server.

Solution #2 (not tested)

According to Microsoft tech bulletins, installing the latest service packs on the server and workstations will resolve the problem.  We have no way of testing it since we do not run Windows 2000 Server.

Solution #3 (not tested)

The information at the following links will tell you about the problem and how to fix the problem in Windows 2000 Server.  We have no way of testing it since we do not run Windows 2000 Server.

http://support.microsoft.com/kb/810907

Solution #4 (not recommended) 

A possible but not recommended work around is to place Maintenance.exe, ExpressMaintenance.chm and Connection.ini in a folder on each workstations and point the shortcut to Maintenance.exe on the local workstation.  That will get around the problem.  However, when you update you will have to update each computer which is not the best arrangement.  It is likely the problem will surface with other applications that open and close files so the problem is better resolved permanently.