Home > Servers > Systems Management > White Papers > Server Configuration Profiles: Reference Guide > Common issues
If issues are detected while an SCP Import or SCP Import Preview operation is running, generally the first step is to check the job status and the configuration results. Most issues can be resolved by reviewing these two data points.
If the issue is still unclear, the next recommended step is to review the iDRAC Lifecycle Logs. The start of the SCP operation can be found in the LCL by searching for the Job ID (JID). Each SCP Import operation begins with a “SYS191: Importing Server Configuration Profile” message, which can be used as a starting point in the LCL for triaging issues.
SYS041 - Unable to apply some component configuration values.
If an SCP Import operation fails with a SYS047: Input file for import configuration is not compliant with configuration schema message, the configuration results typically provide a line number for the failure.
racadm>>lclog viewconfigresult ‐j JID_035451979234 SeqNumber = 8304
Job Name = Import Configuration
Message ID = SYS064
Message = Input file for import configuration is invalid at line 2911
If the line number is unclear, run the template through an external XML or JSON validator to check for errors.
SYS051 - The system could not be shut down within the specified time.
The operating system can potentially deny or ignore the graceful shutdown request. If the SCP Import operation times out this error, consider the following options:
SYS055 - Import of Server Configuration Profile operation completed with errors.
SCP Import operations use a “continue on error” policy. Detected errors are reported to the LCL, but the job continues to apply all settings. SCP Import has intelligent attribute dependency resolution and multiple layers of retries to resolve all possible conflicts. However, any unresolved errors are logged to the LCL.
Most issues are reported in the configuration results. These issues include schema validation issues and dependency issues that SCP Import was unable to resolve.
If the operation Completed with Errors and the reason is unclear from the configuration results, review the iDRAC Lifecycle Logs for more information.
racadm>>jobqueue view ‐i JID_041519610631
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ JOB ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
[Job ID=JID_041519610631]
Job Name=Configure: Import Server Configuration Profile Status=Completed with Errors
Scheduled Start Time=[Not Applicable] Expiration Time=[Not Applicable]
Actual Start Time=[Sat, 31 Oct 2020 08:46:01]
Actual Completion Time=[Sat, 31 Oct 2020 08:46:04]
Message=[SYS055: Import of Server Configuration Profile operation completed with errors.] Percent Complete=[100]
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
racadm>>lclog viewconfigresult ‐j JID_041519610631 SeqNumber = 10430
FQDD = LifecycleController.Embedded.1
Job Name = Import Configuration Operation Name = CHANGE
DisplayValue = BIOS Reset To Defaults Requested Name = LCAttributes.1#BIOSRTDRequested
OldValue = False
NewValue = badvalue
MessageID = RAC015
Status = Failure
ErrCode = 9240 Operation Name = CHANGE
DisplayValue = Default Ignore Certificate warning Name = LCAttributes.1#IgnoreCertWarning
OldValue = On
NewValue = Off
Status = Success
ErrCode = 0
In the preceding example, the job resulted in Completed with Errors. The BIOSRTDRequested attribute only accepts True or False, but the template contained badvalue for this attribute. The error shows RAC015 for the attribute.
The error code lookup for RAC015 shows the message as Unable to run the method because the input value is not one of the possible values for AttributeName arg1.
Error Code Lookup: Events and Error Message Reference Guide for Dell EMC PowerEdge Servers
The Attribute Registry shows that badvalue is not one of the possible values for BIOSRTDRequested.
Attribute Registry: www.dell.com/idracmanuals
SYS072 - Server Configuration Profile import operation timed-out.
SCP Import maintains an internal timer for all operations. This timer scales based on the size of the configuration changes, firmware updates, and other operations being performed by SCP Import.
In the unlikely event that the SCP Import operation times out, check your host boot status. Confirm that the server completed POST successfully. The F1 / F2 Error Prompt setting might have been triggered and prevented the SCP Import operation from completing its tasks.
Perform a GetRemoteServicesStatus check before performing any SCP operation. This command provides a quick rollup of the server and LC (LifecycleController) status.
racadm getremoteservicesstatus
Server status: Out of POST
LC status : Ready
RT status : Ready
Status : Ready
If the LC status is In Use or Reloading, wait until it shows Ready to perform the operation.
If the Server status shows any error, such as Server has halted at F1/F2 error prompt because of a POST error, resolve that error before attempting an SCP operation.