Table A-1
Intel SCS error messages (continued)
Description
Error
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 137 - Another process
currently working on AMT
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.
See
“Integrating Intel SCS with Active Directory”
on page 55.
Error 139 - Failed to update Kerberos
Password with Kerberos Integration
is disabled on server
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 407 - Batch exit code 0xfffff
171
Troubleshooting Out of Band Management Component
About Intel SCS error messages
