Error 102 - Intel AMT device is already configured
Trying to configure an Intel AMT device that is not in an unconfigured state within the Intel SCS database.
For example, you configure Intel AMT, and then go to the MEBx and choose to un-provision (un-configure) the Intel AMT device. Intel AMT starts sending Hello messages, but the Intel SCS database shows that the Intel AMT device was already configured, so Intel SCS rejects the Hello request.
This error indicates that the Intel SCS database has the target system that is identified as configured. If the target system was manually unconfigured through the local MEBx, then manually delete the entry from the Intel SCS console.
From a configuration security perspective, this error may also indicate an attempt to replay a setup and configuration sequence. Intel SCS rejects additional requests if the system is already listed as Configured.
Error 103 - Request is already in the queue
This error can be caused in the following situations:
Trying to delay a request that is already set to be delayed
Trying to push a request that is already in the queue
Trying to push a request to the poller that is already in the poller
This error is a status or an awareness indicator. Configuration and maintenance requests are queued within the Intel SCS database and processed by Intel SCS servers. In larger implementations, multiple Intel SCS servers can be configured to process requests within a single Intel SCS database queue. The queue includes immediate and delayed requests. Thus, if a request is already delayed, this error is generated. Similarly, if the request is being processed or handled by the poller, a competing request generates this message.
Error 137 - Another process currently working on AMT
This error is typical if an action is attempted on a device that is already undergoing a procedure (such as configuration). Typically, you can retry the action as soon as the previous request is completed.
For example, if a partial unconfiguration request has not completed and a reconfiguration request is sent, this generates the error. Reasons for the previously queued request not completing can include connectivity, difference of configuration state, and so forth. If the error is persistent for a target Intel AMT system and connectivity to the target system is available, try executing a management function if the system is in a configured state (for example, remote inventory, remote power on/off, etc.). If unsuccessful, the target system may be in an unsupported state. A manual process of partial unconfiguration may be required. Removing the assigned profile at the console should occur also.
Error 139 - Failed to update Kerberos Password with Kerberos Integration is disabled on server
Intel SCS has the ability to integrate with Microsoft Active Directory for Kerberos based authentication. Check to ensure that schema extensions have been applied and proper authentication to the Kerberos server (for example, Microsoft Active Directory) is in place.
The script that is used for extracting the UUID map information has failed to run properly.
This error is a -1 return that is caused between a configuration script and the SCS instance. Incomplete configuration profile, missing configuration data, or other console configurations are likely causes of this error.
Error 602 - Exception in clock sync worker
Clock synchronization is important in Kerberos environments, because the authentication process has a timestamp dependency. This error is benign in non-Kerberos authentication environments. It refers to a SOAP call failure; further environment and infrastructure investigation may be needed for future environmental considerations.
Error 907 - Request execution failed
This error can occur in the following situations:
Invalid status of delayed table
Duplicate entry for the same request
Empty value for PID parameter
Invalid length PID parameter
Empty value for PPS parameter
Invalid length for PPS parameter
Error Configuring Intel AMT device: Error executing properties script, process exit code indicating a failure: WIN32 Error [-8]: "WIN32 Error [-8]: "Unknown"
For configuration to occur, the UUID and the FQDN of the target Intel AMT system are mapped together.
The configuration script may attempt to use WMI, reverse DNS, previously stored asset data or client agents to obtain this data.
This error occurs when the configuration script cannot obtain this data.
To resolve this issue, you can manually assign a configuration profile and type the FQDN of the Intel AMT device.
Cannot execute SQL code.
As a general rule, these errors resolve themselves. The major cause of many of these errors is slow progress while computers are in a configuration state. Check the Intel AMT Systems node in the Symantec Management Console for the status of AMT devices.
Cannot contact back AMT with IP:xxx.xxx.xxx.xxx Exception
The recorded IP address from the Hello packet sequence is not responding to requests. If the target system sends a new Hello packet with an updated IP address, Intel SCS updates the queue entry.
This error commonly occurs when the system has been connected, an IP address and DNS resolution have occurred, a Hello packet was sent, and then the system was disconnected from the network before the Intel SCS response. A common scenario is pre-staging (initializing) a system before sending to the intended location.
Proper certificate that matches the pre loaded certificate was not found in the user certificate store. PKI configuration failed.
A Remote Configuration capable computer is requesting configuration, but the matching Remote Configuration certificate is not found.
The Certificates - Current User > Personal > Certificates store on the OOB site server computer (by default, the Notification Server computer) must contain the Remote Configuration certificate. The Thumbprint field of the certification authority certificate that issued this Remote Configuration certificate must match one of the hashes that are programmed into the Intel AMT device.
Configure Out of Band Management Component to use the Remote Configuration feature or use the manual initialization method.