<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content

Okta Advanced Server Access and Okta Privileged Access Server Re-enrollment Fails With a Server Is Deleted Error

Advanced Server Access
Okta Classic Engine
Okta Identity Engine

Overview

Re-enrolling a previously deleted server into an Okta Advanced Server Access (ASA) or Okta Privileged Access (OPA) project fails when the server agent retains cached state information from the initial enrollment. Resolve this issue by stopping the service, deleting the cached state directory, and restarting the service.

 

The server agent logs display the following error:

 

time="2023-06-14T15:53:15-04:00" level=info msg="Attempting automatic server token refresh" task=refreshServerToken token_path="C:\Windows\system32\config\systemprofile\AppData\Local\ScaleFT\state\device.token" 

time="2023-06-14T15:53:15-04:00" level=error msg="automatic refresh server token failed" err="Server is deleted" task=refreshServerToken time="2023-06-14T15:53:15-04:00" level=error msg="task init failed" err="Server is deleted" task=refreshServerToken

time="2023-06-14T15:53:15-04:00" level=error msg="task init failed" err="Server is deleted" task=refreshServerToken 

time="2023-06-14T15:53:15-04:00" level=error msg="Error in mainLoop(), retrying" error="Server is deleted" retry_in=9m45.422758793s

 

Applies To

  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • Okta Advanced Server Access (ASA)
  • Okta Privileged Access (OPA)

Cause

The server agent builds a state directory that contains internal databases and caches. If the server previously enrolled in Okta Advanced Server Access or Okta Privileged Access, this directory contains cached information about the initial enrollment that causes a conflict when the server attempts to re-enroll into the project.

Solution

How is the server is deleted error resolved?

Resolve the re-enrollment error by stopping the service, deleting the cached state directory, and restarting it.

  1. Stop the ScaleFT Server Tools service (sftd on Linux) on the affected server.
  2. Delete the ScaleFT directory from the server that contains the cached state information.
    • On Windows servers: C:\Windows\System32\config\systemprofile\AppData\Local\ScaleFT
    • On Linux servers: /var/lib/sftd
  3. Restart the ScaleFT Server Tools service and wait a few minutes.
  4. Monitor the server to verify successful enrollment.

What steps are required if the re-enrollment issue persists?

Uninstall the ScaleFT Server Tools, delete the cached state directory, and reinstall the tools by following these steps.

  1. Stop and uninstall the ScaleFT Server Tools on the affected server.
  2. Delete the ScaleFT directory from the server that contains the cached state information.
    • On Windows servers: C:\Windows\System32\config\systemprofile\AppData\Local\ScaleFT
    • On Linux servers: /var/lib/sftd
  3. Reinstall the ScaleFT Server Tools and attempt to enroll the server again.

Related References

Loading
Okta Advanced Server Access and Okta Privileged Access Server Re-enrollment Fails With a Server Is Deleted Error | Okta Support