This section provides resolution to issues that you may encounter/face while working with the CipherTrust Intelligent Protection (CIP) solution.
|The ||1. Open the Transparent Encryption application on the CipherTrust Manager GUI. The Clients page is displayed.|
2. Under Client Name, check whether the CTE client is registered with a hostname or an IP address.
3. Open the Data Stores page (Data Discovery and Classification > Data Stores). This page shows the configured data stores.
4. Under Name, check whether the data store is added with a hostname or an IP address.
5. Make sure that both the resources (the data store and the CTE client) are configured using an IP address or a hostname.
|Scan failed in the ||To resolve this issue, make sure that:|
• GuardPoint status is Active.
• The classification profile used in the scan and CTE policy is same.
• The CTE client should match the DDC data store hostname/IP address.
• Both the resources (the data store and the CTE client) are configured using an IP address or a hostname.
|Scan failed with ||One of the possible reasons for |
1. Uninstall the DDC agent (ER2) package from the CTE client.
2. Change the hostname of the CTE client.
3. Install the DDC agent (ER2) package on the CTE client.
4. Configure the DDC agent at the CTE client.
5. Create the Data Store in DDC.
|DDC scan failed in multi-node TDP|
Inconsistent namespace mapping properties. Cannot initiate connection as SYSTEM:CATALOG is found but client does not have
|This issue occurs if you copy |
To resolve this issue, copy
|Target path not set on the Windows CTE agent: ||Install the DDC agent (ER2) package at the CTE agent.|
|1. Verify TDP configurations on the Ambari UI.|
2. Refer to Knox > Advanced Topology.
3. Check for entry of the Livy Server in
|Make sure that HDFS folder should exist.|
|Scan failed with ||1. Check the |
2. Access TDP using the Ambari UI.
3. Check the Spark2 configurations:
• Spark2 > Configs > Advanced > Advanced livy2-conf >
• Spark2 > Configs > Advanced > Custom livy2-conf >
• Spark2 > Configs > Advanced > Custom spark2-defaults >
4. Check the HBase configurations:
• HBase > Configs > Advanced > Advanced hbase-site >
Refer to Configure TDP for details.
|Scan failed with ||To resolve this issue, try the following:|
• Check that the
• If not, copy the
• Assign the desired permissions for
|TDP services are not working||To resolve this issue:|
1. Go to the Ambari UI.
2. In the left pane, click the three dots (...) next to the Services tab.
3. Click Start All services.
4. Review the
Note: Reboot the CTE agent if the TDP IP address or hostname is changed.
If you reboot TDP or Start/Restart All services:
1. Check that the Knox service is up.
2. Click Actions > Start Demo LDAP.
Data governance exception with the error:
|This issue could be due to the CTE agent is not able to resolve the hostname of PQS server.|
The following steps can help to resolve this issue:
1. Make sure that the TDP IP address and hostname are correct.
2. Reboot the CTE agent if the TDP IP address or hostname is changed.
Location of the hosts file:
|Check the Ambari server UI all services should be green and working. If not, start/restart all services.|
|GuardPoint does not have UUID.||• Check the CTE agent installation.|
• Make sure that LDT on CIFS (File Header Support - FHS) capability is turned off.
Note: This resolution is only applicable for local.