No Engine Appears Under Privileged Remote Access

Symptom: A Platform Engine with the PRA workload is registered and shows as Online in Engine Management, but no engine is available under Privileged Remote Access. Launching a session from a secret fails with an Engine Unavailable error, or the site selection dialog offers no usable site.

Cause: When a session is launched, PRA looks up the site name assigned to the secret in both the Engine Management site list and the legacy PRA site list, and uses the first site whose name matches. If a legacy PRA site with a matching name still exists but has no engines assigned to it, PRA selects that empty legacy site instead of the Engine Management site that holds your engine. The result is an Engine Unavailable error even though the engine is healthy.

This most often happens with a site named Default: the secret is assigned to the Secret Server Default site, a legacy PRA site named Default still exists, and the Platform Engine was added to an Engine Management site with a different name. It also commonly appears after upgrading a legacy PRA Engine to the Platform Engine, when the now-empty legacy PRA site is left behind. See PRA Site Selection Behavior for how name matching works.

Diagnosing the Issue

Open the secret and note the site assigned to it.
In the Delinea Platform, open the Sites page in Engine Management (use the Search bar to find it) and note the name of the site that contains your Platform Engine, and confirm the engine is Online.
Navigate to the Privileged remote access page and open the Sites & Engines tab. This tab lists legacy PRA sites, with the number of engines on each site under Engines Count.
Look for a legacy PRA site whose name matches the site on the secret but whose Engines Count is zero. If you find one, and your Platform Engine lives in an Engine Management site with a different name, this is the cause.

Resolving the Issue

Choose one of the following options.

Option When to use it Steps and notes

Option	When to use it	Steps and notes
A. Delete the empty legacy PRA site (recommended)	The legacy PRA site has no engines and you no longer need it. This is the recommended cleanup after upgrading to the Platform Engine.	On the Sites & Engines tab, open the More Actions menu next to the legacy site and delete it. A site that still contains engines cannot be deleted; remove the engines first. See Uninstallation (Deprecated). Deleting the site requires the Delete a PRA site permission (`delinea.platform/administration/remoteaccess/site/delete`). After deleting the site, launch the session again. If only one valid Platform Engine site remains, PRA uses it automatically. If several exist, the user is prompted to select one.
B. Rename a site so the names no longer collide	You must keep the legacy PRA site, for example because legacy engines will be added back to it.	Either rename the legacy PRA site to a name that does not match the secret's site (see Renaming PRA Site), or rename the Engine Management site that holds your engine to match the secret's site (see Editing a Site). The Engine Management Default site cannot be renamed or deleted, so this option does not apply when the Engine Management site involved is Default. Renaming a site changes site matching for every secret assigned to that site name, not only the secret you are troubleshooting.
C. Create a matching Engine Management site and put an engine in it	You want the secret's existing site name to keep working, and you can add or reinstall a Platform Engine.	Create an Engine Management site with the same name as the site on the secret (see Creating a Site), then add a Platform Engine with the PRA workload to that site. A Platform Engine belongs to exactly one site and cannot be moved between sites, so you must install a new engine, or uninstall the existing one and reinstall it into the new site. If the name in question is Default and you cannot create or select a Default site, open a support ticket. See Upgrading the PRA Engine With Default Sites.

A. Delete the empty legacy PRA site (recommended)

The legacy PRA site has no engines and you no longer need it. This is the recommended cleanup after upgrading to the Platform Engine.

On the Sites & Engines tab, open the More Actions menu next to the legacy site and delete it. A site that still contains engines cannot be deleted; remove the engines first. See Uninstallation (Deprecated).

Deleting the site requires the Delete a PRA site permission (delinea.platform/administration/remoteaccess/site/delete).

After deleting the site, launch the session again. If only one valid Platform Engine site remains, PRA uses it automatically. If several exist, the user is prompted to select one.

B. Rename a site so the names no longer collide

You must keep the legacy PRA site, for example because legacy engines will be added back to it.

Either rename the legacy PRA site to a name that does not match the secret's site (see Renaming PRA Site), or rename the Engine Management site that holds your engine to match the secret's site (see Editing a Site).

The Engine Management Default site cannot be renamed or deleted, so this option does not apply when the Engine Management site involved is Default. Renaming a site changes site matching for every secret assigned to that site name, not only the secret you are troubleshooting.

C. Create a matching Engine Management site and put an engine in it

You want the secret's existing site name to keep working, and you can add or reinstall a Platform Engine.

Create an Engine Management site with the same name as the site on the secret (see Creating a Site), then add a Platform Engine with the PRA workload to that site. A Platform Engine belongs to exactly one site and cannot be moved between sites, so you must install a new engine, or uninstall the existing one and reinstall it into the new site.

If the name in question is Default and you cannot create or select a Default site, open a support ticket. See Upgrading the PRA Engine With Default Sites.

Whichever option you choose, also review the Sites & Engines tab for any other empty legacy PRA sites and delete them. Delinea recommends removing all legacy PRA sites with no remaining engines so that PRA always resolves to the correct Platform Engine. See Upgrading to the Platform Engine.

Other Causes to Rule Out

If the site names do not collide, one of the following may be the cause instead:

Missing permissions. The user launching the session needs the List Sites and List Engines permissions from Engine Management, or no sites or engines are shown at launch. See PRA Permissions From Other Platform Services.
No online engine in the matching site. A site whose name matches but that has no Online Platform Engine with the PRA workload also yields no usable engine. Check the engine status in Engine Management and see Troubleshooting the Platform Engine .
Proxy-enabled secret. When the secret uses the Secret Server proxy, the launch can fail if the Platform Engine site has no network connectivity to the secret's proxy site. See Bypassing Proxy for PRA Launches .