Resolve reported issues
- Last UpdatedSep 05, 2024
- 4 minute read
This section provides a list of the issues, grouped by Indicator, which may be detected in an AVEVA Common Services Portal scan. These issues need to be resolved manually, steps for which are detailed in the table below.
|
Indicator |
Description |
Steps to Resolve Issue |
|---|---|---|
|
Binding Certificate |
Secure mode with no Ssl thumbprint value. |
Reconfigure the system. |
|
Certificate not found. |
Re-install the certificate or reconfigure the system. |
|
|
Unable to access the certificate. |
Reconfigure the system. |
|
|
PCS certificate is overridden. |
Reconfigure the system. |
|
|
ArchestrAWebHosting group has no access to the certificate private key. |
Grant access to ArchestrAWebHosting user group for this certificate using the Manage Private Keys option under Manage computer certificates in Windows. |
|
|
Unable to access the certificate private key. |
Reconfigure the system. |
|
|
Core Services |
The process does not exist or the count is not correct. |
1. From the Windows Control Panel, select System and Security>Administrative Tools>Services. 2. Start or Restart the ‘AVEVA Agent (Watchdog)’ service. Repair or reinstall Platform Common Services if the issue persists. |
|
The Configuration file for services is invalid. |
Repair or reinstall Platform Common Services. |
|
|
File System Permissions |
The specified configuration does not exist. |
Repair or reinstall Platform Common Services. |
|
File system permissions is invalid. |
||
|
Global Discovery |
The Deployment Agent Service cannot be discovered. |
Repair or reinstall Platform Common Services. |
|
Found no node with the Service Repository feature installed. |
||
|
Local Discovery |
The Deployment Agent Service cannot be discovered. |
Repair or reinstall Platform Common Services. |
|
Machine Name |
Cannot find the machine name. |
Repair or reinstall Platform Common Services. |
|
The machine name is not the name of current machine. |
||
|
No such host. Maybe the host name is too long. |
||
|
Machine Role |
The specified configuration does not exist. |
Repair or reinstall Platform Common Services. |
|
It is the SR node while the format is invalid. |
||
|
Management Server |
The System Management Server is not configured. |
Configure the proper option for System Management Server via the Configurator. |
|
Unable to connect to the System Management Server. |
Ensure the System Management Server has been configured and been running properly. |
|
|
Port Sharing |
The 'NetTcpPortSharing' service does not exist. |
Make sure port sharing is enabled by the operating system. |
|
The 'NetTcpPortSharing' service is not running. |
1. From the Windows Control Panel, select System and Security>Administrative Tools>Services. 2. Start the Net.Tcp Port Sharing Service. |
|
|
Registry Key |
The configured registry is invalid. |
Repair or reinstall Platform Common Services. |
|
Unable to find PCS OIDC issuer information in the configuration. |
1. Reconfigure System Management Server (SMS) by launching Configurator from Windows Start menu. 2. In the System management Server (SMS) plugin, set the machine configuration to No System Management Server configured. 3. Change the machine configuration back to Connect to an existing System Management Server or This machine is the System Management Server. 4. Restart the AVEVA Common Services Portal and perform the scan. |
|
|
Registry Permission |
The specified configuration does not exist. |
Repair or reinstall Platform Common Services. |
|
Registry permissions is invalid. |
||
|
Solution |
The 'DefaultASBSolution' key in registry is invalid. |
Repair or reinstall Platform Common Services. |
|
The NodeRegistration is invalid. |
||
|
The ASB solution is invalid. |
||
|
Transport Permissions |
Port permissions is invalid. |
Repair or reinstall Platform Common Services. |
|
Version |
The specified configuration does not exist. |
Repair or reinstall Platform Common Services. |
|
Cannot find the PCS version. |
||
|
Configured PCS version is invalid. |
||
|
Windows Services |
The 'AVEVA Agent (Watchdog)' service is not running. |
1. From the Windows Control Panel, select System and Security>Administrative Tools>Services. 2. Start the <Service Name>. |
|
The 'AVEVA Identity Manager' service is not running. |
||
|
The account 'account' for 'AVEVA Agent (Watchdog)' service is not correct. |
1. From the Windows Control Panel, select System and Security>Administrative Tools>Services. 2. Double-click <Service Name>. The Properties dialog box is displayed. 3. Select the Log On Tab. Set NT SERVICE\<Service Name> account with no password as the log on account. 4. Click OK. 5. Start or Restart the <Service Name> . |
|
|
The account 'account' for 'AVEVA Identity Manager' service is not correct. |
||
|
The start mode 'mode' for 'AVEVA Agent (Watchdog)' service is not correct. |
1. From the Windows Control Panel, select System and Security>Administrative Tools>Services. 2. Double-click <Service Name>. The Properties dialog box is displayed. 3. Select the General Tab. 4. Set the Startup type to Automatic. 5. Select OK. |
|
|
The start mode 'mode' for 'AVEVA Identity Manager' service is not correct. |
||
|
Windows Services |
The recovery configuration for 'AVEVA Agent (Watchdog)' service is not correct. |
1. From the Windows Control Panel, select System and Security>Administrative Tools>Services. 2. Double-click ‘AVEVA Agent (Watchdog)’ service. The Properties dialog box is displayed. 3. Select the Recovery tab. 4. Set First Failure, Second Failure and Subsequent Failures to Restart the Service. 5. Set the Reset fail count after field to 0 days. 6. Set the Restart service after field to 1 minute. 7. Select OK. |
|
The 'AVEVA Agent (Watchdog)' service does not exist. |
Repair or reinstall Platform Common Services. |
|
|
The 'AVEVA Identity Manager' service does not exist. |