HP Insight Control Server Provisioning 7.2 Online Help

12.29 Error: Mid and crypto not found
This error is often seen when a server that was previously installed and managed is booted into a
service OS that cannot access the server identification information stored on the server’s hard drive.
12.29.1 Possible cause checklist
• If you are trying to reprovision the server, either run one of the Prepare Server for Reprovisioning
Build Plans to clear the managed status of the server or be sure the decommission server Build
Plan step is part of your Build Plan in the appropriate location.
• When you see this error while trying to add a server, it is likely the target server is already
registered in Insight Control server provisioning. If this is true, you will see the target server
on the Servers Overview screen and you can delete it.
12.30 Message: Processing of response file failed ...
12.30.1 Symptom
When booting WinPE, you see a terminal window for a while, and you may see a message:
“Processing of response file failed: Can’t find a response file on the floppy drives.”
12.30.2 Resolution
No action is required; this is normal and may be ignored.
12.31 Error: can’t get packet
12.31.1 Symptom
When booting WinPE with an external DHCP server, you might see a message in the terminal
window that reads, “Error, can’t get packet.”
12.31.2 Resolution
No action is required; this is normal and may be ignored.
12.32 OS Build Plan or add iLO fails at Wait for HP SA Agent step
12.32.1 Symptom
A Build Plan or add iLO function fails at the Wait for SA Agent step with the error message:
Timeout while waiting for agent registration. Wait for HP SA Agent
failed with exit code 6.”
This indicates the server failed to complete a triggered boot, start the agent, and register itself with
the appliance. This is one of the most common errors as it can be caused by any number of things
that might interfere with that process.
12.32.2 Possible causes
• “atMost parameter is too small” (page 110)
• “Target server is inaccessible” (page 110)
• “Target server did not get a DHCP address” (page 110)
• “The BIOS hardware date and time are incorrect” (page 110)
• “The decommission step broke the agent connection” (page 110)
12.29 Error: Mid and crypto not found 109