Unable to authenticate with the provided SmartDeploy Api Service URL

If you receive the error message "Unable to authenticate with the provided SmartDeploy Api Service URL" you can follow these steps to troubleshoot:

1. Open Services.msc and confirm that the SmartDeploy Api Service is running.

2. Open a browser and browse to https://localhost:8080/Health to confirm the console service is running correctly.

3. On the SmartDeploy console logon page, expand Advanced and confirm the correct URI is set; https://localhost:8080.

4. Re-try logging onto the SmartDeploy console.

If the service cannot start, or you cannot reach the health URL, try these additional troubleshooting steps:

1. Restart both the MongoDB and SmartDeploy API services through the Windows Services application.

2. If you receive the error "The specified server is already authenticated with a different account":

   1. Open an administrative command prompt

   2. Stop the SmartDeploy API service by typing Net stop sdapiservice

   3. Navigate to C:\Program Files\SmartDeploy\SmartDeploy and delete the SmartDeploy.lic file

   4. Restart the service by typing Net start sdapiservice

   5. Relaunch SmartDeploy and sign in again

3. For virtual machines, be aware that hardware changes can cause authentication issues since the SmartDeploy API Service authentication is tied to the device's Endpoint ID. In these events we highly recommend re-installing the SD console to rebuild the api service with the updated Endpoint IDs.

   1. Open Appwiz.cpl

   2. Uninstall the Smartdeploy Console

   3. Delete "C:\Program Files\Smartdeploy\"

   4. Run the latest version of SDESetup.exe to initiate the console re-install

   5. Upon opening the SD console, be sure to select the previously configured Distribution Point (C:\Smartdeploy by default).

If issues persist, collect console logs using the 'Tools -> Collect Logs' option in the SmartDeploy application or from the advanced settings of the Sign In page, and contact Support.