Overview
This message appears when the SmartDeploy server has not been able to successfully communicate with the SmartDeploy License Server for more than 30 days. This typically indicates a failure in license re-validation due to local cache issues, blocked outbound connectivity, or the SmartDeploy application not being opened for more than 30 days.
Resolution
The most common and effective resolution is to reset the local license file so that SmartDeploy can regenerate it and re-establish communication with the license server.
Steps to Remediate
Close the SmartDeploy console
-
Stop the SmartDeploy API Service
Open Services (services.msc)
Locate SmartDeploy API Service
Right-click and choose Stop
-
Delete the existing license file
-
Navigate to:
C:\Program Files\SmartDeploy\SmartDeploy\ -
Delete:
SmartDeploy.lic
-
-
Start the SmartDeploy API Service
In Services, right-click SmartDeploy API Service
Choose Start
Reopen the SmartDeploy console
SmartDeploy will automatically regenerate a fresh license file and attempt to reconnect to the license server.
If the Error Persists
If regenerating the license file does not resolve the issue, the problem is commonly caused by network restrictions that are preventing outbound communication to SmartDeploy’s licensing endpoints.
Add Required Domains to the Allow List
Ensure that the following domains are accessible over outbound HTTPS (port 443) from the SmartDeploy console host:
*.smartdeploy.comsmartdeploy.azureedge.netsmartdeployb2c.b2clogin.comapi.smartdeploy.comdownload.smartdeploy.com
These domains must be reachable without inspection or blocking by firewalls, proxy filters, or SSL inspection policies. If a proxy or next-gen firewall is in place, explicitly allow these domains to ensure SmartDeploy can validate its license and receive updates.
If you need further help, please submit a support ticket, and send the below log files from your SmartDeploy directory.
C:\SmartDeploy\Logs\SDApiService.log
C:\SmartDeploy\Logs\SDConsole.log
Note: C:\SmartDeploy is the default location for SmartDeploy but you could be using an different drive letter like D:\SmartDeploy or E:\SmartDeploy