'Missing' redgate.com-activated Licenses in SQL Monitor

You are tying to allocate licenses from red-gate.com to servers, in SQL Monitor (Configuration > Licensing). Licenses you believe should be available to allocate to your servers are not. This could simply mean that someone else has used the licenses on another installation. However, 'missing' licenses can also be caused by:

User incorrectly added to a license

Adding a User to a license will consume an entitlement, which is then unavailable to use on a server. This User will need to be removed to free up the license. Only assign owner or admins to a SQL Monitor license.

In this example, a 4-server license has been purchased but only 3 are available for use on this SQL Monitor installation, leaving one server unlicensed.



  1. Click Allocate your licenses
  2. Find the license in the list and check which installations are using it. In this example, 3 of the 4 licenses are in use on the current installation, and one on "other installations":mceclip4.png
  3. Click on View license details
  4. Review entries under current allocated users:
    • If you see only Device: (<installation name>) entries, this is the correct behavior for SQL Monitor.
    • If you see a user's email address listed here, this is a mistake. Click Remove to free up the entitlement:mceclip1.png
  5. Return to Configuration > Licensing and refresh the page. You should now see the entitlement appear in the Licenses table, and you can assign it to a server (SQL Monitor will automatically use entitlements to license any currently unlicensed servers)

Zero licenses available having switched from serial key to redgate.com licenses 

When you are trying to dynamically switch your perpetual licenses from serial key to the RedgateID-based process, you find that after adding your license via the RedgateID process your Number of licenses still shows as '0'. 

This may be due to old serial key activations of your license still being present in the Redgate licensing portal, having previously activated your license more than once, such as if you had previously activated serial key across other base monitors on your network. It may also be due to your SQL Monitor webserver being unable to connect to the Redgate client service. 

Resolution 1:

  1. Log on to the Redgate license portal and go to the Manage license section, or alternatively you can also click “Allocate your licenses” from the SQL Monitor license page, and then “View license details”.
  2. Select the applicable license and on the Users tab. You will see something like the following (you may see more or fewer activations than this): 
  3. Remove any old serial key activations, these look like “Device: xxxx-xxxx-xxxx-xxxx”. If you see “Device: (<installation name>)” then leave those in place.  
  4. Return to SQL Monitor (Configuration > Licensing) and refresh the browser. The Licensing table should now show  the correct number of licenses. 
  5. Click Allocate you licenses to confirm that all licenses are now listed as "Devices: (<installation_name>)".


By removing those old activations and adding your licenses with your RedgateID you will be able to apply the same license across multiple base monitor installations. In the past this would have required you to split the license. 

Resolution 2:

If you are still showing '0' under Number of licenses after trying the above steps then the cause could be that your webserver isn't connecting to Redgate.

 In the case of SQL Monitor, all the webserver needs to contact is permits.red-gate.com via HTTPS (on default port of 443). It's the only endpoint it uses for new licensing.

To verify if there is block, log into the host running the web server and try to fetch https://permits.red-gate.com/test in Powershell whilst running in the user context that the web server runs in:

">Invoke-WebRequest https://permits.red-gate.com/test"

To resolve this you will need to add permits.red-gate.com to the AllowList on your Firewall. This should allow SQL Monitor to connect to Redgate and fetch the license information. 

Go back to your SQL Monitor webserver and refresh the license configuration page. If all is working then the Number of licenses should reflect correctly. 



Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request