Documentation

Mistake on this page? Email us
Docs › Troubleshooting › Secure Factory CLI errors

Secure Factory CLI errors

CLI errors might occur because of setup, configuration and connectivity issues.

In the event of an error, Secure Factory CLI exits, returns a non-zero exit code, and provides an error message as output; for example:

ERROR SRC:TOOL
MSG Unauthorized request

ERROR SRC:TOOL
MSG Failed to connect to factory tool service

ERROR SRC:TOOL
MSG No PKCS #11 slot detected

ERROR SRC:TOOL
MSG Error invalid pin code for secure token

Rerun the new_device command after resolving the error.

Configuration and installation errors

  • Config file <file-name> failed to load

    Check that the file exists. The expected file format is ini.

  • Server certificate file was not configured for <host-url>

    Check that the FT_SERVER_CERTIFICATE_FILE parameter is configured correctly in the factory_tool.ini file.

  • Missing server certificate file: <file-name>

    Server CA certificate file not found at the workstation. Check that the CA certificate file is copied over to the workstation and is configured correctly in the factory_tool.ini file.

  • Failed to connect to factory tool service

    Check that Secure Factory Service is running. Check network connectivity.

  • Invalid PIN code for secure token

    Check that the PIN code for the hardware token is configured correctly in the workstation configuration file.

    If you don't have the PIN code for the hardware token, you may need to initialize the token. For more information, see Initializing and pairing a hardware token to a workstation.

For more information related to configuration and installation errors, see Configuring a Secure Factory CLI workstation.

  • Error communicating with secure token

    Communication with hardware token failed. Reinitialize the hardware token.

    Note: After you reinitialize the hardware token, you must reconfigure and reapprove the workstation.

  • No PKCS #11 slot detected

    Hardware token not detected at workstation. Try to disconnect and reconnect the hardware token.

  • More than one PKCS #11 slot detected

    Multiple hardware tokens detected at workstation. Remove unnecessary tokens.

  • No private key detected on secure token

    Check that the hardware token has been initialized and paired to a workstation.

  • No cert detected on secure token

    Check that the hardware token has been initialized and paired to a workstation.

For more information related to the hardware token, see Initializing and pairing a hardware token to a workstation.

Workstation registration errors

  • Unauthorized request

    Unknown or unregistered workstation. Verify that the workstation is registered correctly.

  • Unauthorized request: workstation registration is pending approval

    Registration process started, but workstation is yet to be approved.

For more information related to workstation registration errors, see Managing workstations.

Next