Sage 100: How to Resolve the User Limit Exceeded Error

Troubleshoot Sage 100's Connection Rejected: User limit exceeded message, coordinate a Sage application service restart, and verify that users can sign in again.

Remote Desktop & Applications
KB-20261111-SAGE100-USER-LIMITUpdated November 11, 20264 minutesNTS Support Team

Quick Answer

If Sage 100 rejects a connection because the user limit is exceeded, first check whether the licensed seats are actually in use. If stale sessions are suspected, have an administrator coordinate a time for everyone to save work and exit Sage, restart the correct Sage application service on the application server, then have the affected user reopen Sage and test sign-in.

Sage 100: How to Resolve the User Limit Exceeded Error

Recognize the Error

When opening Sage 100, you may see a dialog titled Connection Rejected with the message User Limit exceeded.

Sage 100 desktop with a Connection Rejected dialog stating User Limit exceeded

The connection cannot obtain an available user slot. The licensed seats may genuinely be in use, or a disconnected or hung session may still be holding one. A service restart is a recovery step for suspected stale sessions; it does not increase the licensed user count.

This procedure is based on a Sage100cloud Premium 2019 installation running its application server as a Windows service. Service names vary by version and installation. Have IT confirm the correct service before proceeding; Sage 100 Standard and installations running the application server as an application require a different procedure.

Before Restarting: Coordinate with Users

1.Ask your Sage administrator to check current usage against the licensed user count. If all seats are legitimately in use, have an unneeded session exit normally or discuss licensing with your Sage partner.
2.If the count does not reflect actual use, arrange a brief interruption with everyone using Sage. Ask them to finish processing, save their work, and exit Sage completely.
3.Confirm that no posting, import, or other scheduled Sage work is running before the restart. Restarting the application service interrupts connected sessions and can disrupt unsaved or in-progress work.

The remaining steps require server administrator access. If you are an end user, ask IT or NTS Support to perform them.

Connect to the Sage Application Server

1.Use your organization's approved remote support tool, such as BeyondTrust Remote Support (formerly Bomgar), to connect to the server hosting the Sage application service.
2.Confirm the server against your internal documentation. Do not assume the workstation you are using, or a server hosting only the database, is the correct application server.
3.On the confirmed server, press Windows key + R, enter the command below, and press Enter. Open the Services console with administrator rights if prompted.
services.msc

Restart the Correct Sage Service

1.In Services, locate the Sage application service for the installation users are trying to access. The example below shows Sage100cloud Premium 2019 (10000). The year and instance details are examples, not values to copy into another environment.
Privacy-edited Windows Services illustration showing Sage100cloud Premium 2019 and the Restart the service control

Illustration edited from the support screenshot for privacy. Remote session details, staff information, and surrounding server information are excluded.

2.After confirming everyone has exited, right-click the correct Sage application service and select Restart. Alternatively, select the service and choose Restart the service in the left pane.
3.Wait for the restart to complete and confirm the service returns to Running. Restart only the identified Sage application service; this procedure does not call for restarting SQL Server or rebooting the server.
4.If the service fails to restart or remains stopped, record the error and contact support. Do not repeatedly restart services or terminate server processes without further diagnosis.

Verify the Fix

1.Ask the affected user to reopen Sage 100 and sign in.
2.Confirm that the Connection Rejected message no longer appears and the user can open the intended company and their normal Sage task.
3.Let other users reconnect and confirm that access is restored. Record the service restarted, the restart time, and the test result in the support ticket.

If the message returns, investigate session usage and licensing rather than treating recurring restarts as a permanent fix.

If the Error Persists

Contact NTS Support or your Sage partner with the exact error text, Sage edition and version, whether one or multiple users are affected, and the steps already tried. Include the service name, restart time, whether it returned to Running, and the result of the sign-in test through your private support channel.

If the message also says No valid activation found, or the available user count differs from your registered licenses, ask support to check activation and registration. That is a separate diagnostic path; a restart alone may not resolve it.

Sage reference for user-limit and activation troubleshooting: https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=223924550036278

Share screenshots privately after removing client names, usernames, hostnames, IP addresses, and unrelated server details. Never include passwords or remote access credentials.

Request help from NTS Support

Related Articles

Remote Desktop & Applications

Nitro PDF Pro Shows Trial Expired? Sign In Again

Nitro PDF Pro showing 0 DAYS LEFT, Expired Trial, or an activation prompt? If you have an assigned account-based license, signing back in with your work account can restore access.

Read article: Nitro PDF Pro Shows Trial Expired? Sign In Again
Remote Desktop & Applications

Adobe Acrobat Device Activation Limit: How to Sign In Again

Resolve the Adobe Acrobat device activation limit by signing out of an older computer, freeing an activation slot, and continuing on your current device.

Read article: Adobe Acrobat Device Activation Limit: How to Sign In Again
Remote Desktop & Applications

Nitro QuickSign Greyed Out: How to Restore It

Troubleshoot an unavailable QuickSign button in Nitro PDF Pro for Windows. Check document restrictions, existing digital signatures, and the local Stamps folder.

Read article: Nitro QuickSign Greyed Out: How to Restore It