Support Center > Search Results > SecureKnowledge Details
After adding a Virtual Device, the Security Management Server cannot establish SIC with the new Virtual System Technical Level
Symptoms
  • After you add a Virtual Device, the Security Management Server cannot establish SIC with the new Virtual System.

    Error:

    # cp_pull_cert -d -h [Identifying Information]

    [DATE TIME] SIC initialization started
    [DATE TIME] cpsic_init: msg client name = pull
    [DATE TIME] cpsic_init: common name = [Identifying Information]
    [DATE TIME] cpsic_init: context id = 0
    [DATE TIME] get_my_sicname_from_registry: Read the machine's sic name: [Identifying Information]
    [DATE TIME] Initialized sic infrastructure
    [DATE TIME] FAILED to find registry entry PROVIDER-1//CPLocalAuthDir
    [DATE TIME6] Initialized SIC authentication methods
    [DATE TIME] Pulling certificate from management ...
    [DATE TIME] CPSIC Error: Could not receive the SIC certificate from SmartCenter Server.
    [DATE TIME] Error is: Connection error
    [DATE TIME] CPSIC Error: Could not receive the SIC certificate from SmartCenter Server.
    [DATE TIME] destroy_pull_info: Could not pull certificate from management.
    [DATE TIME] destroy_pull_info: CPSIC Error: Could not receive the SIC certificate from SmartCenter Server.
    DATE TIME] Failed to pull certificate for context_id 0

Cause
The Common Name (CN) in the Command Line Interface and in the registry do not align.


Solution
Note: To view this solution you need to Sign In .