Replica not adding
If you receive a persistent message that says, An internal request has timed out... when you attempt to add an appliance to a cluster, ensure that the appliance is at the same version of Safeguard for Privileged Passwords as the primary. All members of a cluster must be the same.
System services did not update or restart after password or SSH key change
If the system services do not update or restart after an automatic password or SSH key change, first check your audit logs in the Activity Center.
If the audit logs do not adequately explain the problem, then check the options on the Change password or Change SSH key tab of the profile that governs the service account.
- Navigate to Administrative Tools | Partitions.
- Select a partition then click Password Profiles or SSH Key Profiles.
- Double-click the selection in the grid.
- On the profile dialog, go to the Change Password or Change SSH Key tab.
For service accounts that run system services or scheduled system tasks, verify the options on the profile's Change password tab or Change SSH Key tab that enable or disable automatic service update, or restart. You must update the setting to change these options.
Test Connection failures
The most common causes of failure in Safeguard for Privileged Passwords are either connectivity issues between the appliance and the managed system, or problems with service accounts.For more information, see Connectivity failures.
Disabling User Account Control (UAC) Admin Approval Mode on a remote host can also resolve Test Connection failures. For more information, see Change password or SSH key fails.
If you have entered values for Specify Domain Controllers and if SPP does not find a domain controller in the list, the test connection fails and an error is returned. For more information, see Management tab (add asset).
The following topics explain some possible reasons that Test Connection could fail.
Test Connection failures on archive server
There could multiple reasons why you receive an Unexpected copying error... when attempting to run Test Connection on an existing archive server.
When you run Test Connection, Safeguard for Privileged Passwords adds a file named Safeguard_Test_Connection.txt to the Storage Path location of the archive server owned by the Account Name you entered when you created the archive server. To run Test Connection on an existing archive server with a new account name, you must first delete the existing Safeguard_Test_Connection.txt file.