# Troubleshooting If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support. For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Health check and test connection dependent on SFTP server To remove dependency on SFTP server, enable via API Authentication toggle in **Connection Settings** and **Save**. ## Aggregation fails with Java Heap Space error This error may occur if the extract file size is large as compared to the heap space specified in the VA. **Resolution**: To increase the heap space and resolve this issue, reach out to [SailPoint Support](). ## No records are aggregated from the CSV file during full account aggregation This error may occur if your HCM Extract is configured to drop null values. You will see errors in your ccg.log file on the virtual appliance of "Skipping Record due to column length mismatch." **Resolution**: Check your HCM Configuration for Include Null Values in HCM Extract XML Data (WRITE\_NULL\_VALUES), by performing the following: 1. In Oracle, Go to **My Client Groups \> Show More \> Payroll \> Payroll Process Configuration**, and select the **Default Group**. 2. If you don't see **Include Null Values in HCM Extract XML Data (WRITE\_NULL\_VALUES)** in the list, select the **\+** icon. 3. In **Parameter Name**, select **Include Null Values In HCM Extract XML Data allow choice to write null values in XML**. > **Screenshot** > > [![Payroll Process Configuration]()]() > **Note** > > This screenshot may vary from customer to customer depending on their environment. 4. Set the **Default Value** to **Y**. 5. Now that your configuration has been checked, ensure that WORKER\_TYPE values are correct and according to standard as defined in Create a Separate HCM Export File. ## Test connection fails when incorrect PGP keys are used You might notice one of the following errors when the incorrect PGP Public Key or PGP Private Key are used during configuration: Error 1 ```text sailpoint.connector.InvalidConfigurationException: [ InvalidConfigurationException ] [ Possible suggestions ] Ensure that pgp encrpted file is provided or correct Public Key, Private Key and Private Key Password is provided [ Error details ] Signature not found ``` Error 2 ```text sailpoint.connector.InvalidConfigurationException: [ InvalidConfigurationException ] [ Possible suggestions ] Ensure that pgp encrpted file is provided or correct Public Key, Private Key and Private Key Password is provided [ Error details ] invalid armor ``` Error 3 ```text sailpoint.connector.ConnectorException: [ ConnectorException ] [ Possible suggestions ] Ensure that configuration parameters is correct and SFTP server is reachable [ Error details ] org.bouncycastle.openpgp.PGPSecretKeyRing found where PGPPublicKeyRing expected ``` Error 4 ```text sailpoint.connector.ConnectorException: [ ConnectorException ] [ Possible suggestions ] Ensure that configuration parameters is correct and SFTP server is reachable [ Error details ] crc check failed in armored message ``` Error 5 ```text sailpoint.connector.ConnectorException: [ ConnectorException ] [ Possible suggestions ] Ensure that configuration parameters is correct and SFTP server is reachable [ Error details ] invalid header encountered ``` **Resolution**: Ensure you are using PGP Public Key or PGP Private Key in the correct format as generated by the Oracle Fusion HCM system during configuration. For example, you can use the format as shown below: ```text -----BEGIN PGP PUBLIC KEY BLOCK----- Version: BCPG v1.71 lEVFBsA1Iqt4Abh+8dWh3UtTcSuT8KIDYX+OpnVrWAUXMmnKT+JAI7Tk3vtYPiWe7E slg+8m7jXsFfZE5vaJOeFMbMfxC1jVNy+azO/EMg41kKW7pJHCTsGnChrteJ1ocv1iycl NAPf7E==ofag -----END PGP PUBLIC KEY BLOCK----- ``` Or use only the key as shown below: ```text lEVFBsA1Iqt4Abh+8dWh3UtTcSuT8KIDYX+OpnVrWAUXMmnKT+JAI7Tk3vtYPiWe7E slg+8m7jXsFfZE5vaJOeFMbMfxC1jVNy+azO/EMg41kKW7pJHCTsGnChrteJ1ocv1iycl NAPf7E==ofag ``` For more information on the PGP Public Key or PGP Private Key, refer to [Connection Settings](). ## Test connection fails with checksum mismatch at in checksum of 20 bytes You might get the following error when incorrect PGP Private Key Password is provided during configuration: ```text [ InvalidConfigurationException ] [ Possible suggestions ] Ensure that pgp encrypted file is provided or correct Public Key, Private Key and Private Key Password is provided [ Error details ] checksum mismatch at in checksum of 20 bytes ``` **Resolution**: Ensure you are using correct PGP Private Key Password generated by the Oracle Fusion HCM system during configuration. ## Test connection fails with unknown object in stream: 16 You might get the following error when the HCM export file provided is unencrypted and not signed. ```text [ InvalidConfigurationException ] [ Possible suggestions ] Ensure that pgp encrypted file is provided or correct Public Key, Private Key and Private Key Password is provided [ Error details ] unknown object in stream: 16 ``` **Resolution**: Ensure that HCM export file is encrypted and signed. For more information for creating HCM extract file, refer to Create a Separate HCM Export File. ## Test connection fails with Poor PGP. Signature not found **Resolution**: Ensure that HCM export file is encrypted and signed. For more information for creating HCM extract file, refer to Create a Separate HCM Export File. ## Get Object / Single account aggregation failure Get Object / Single account aggregation fails with the following error: ```text URL request parameter fields with value field 1, field 2 and field3 ; is not valid ``` **Resolution**: Ensure that additional fields is defined under **Workers API Additional Fields**. ## Data Is Overwritten After Provisioning After a provisioning operation, account data aggregated from the CSV extract is overwritten. The connector performs a getObject call that reads the account from the Workers API and updates the record. Attributes that exist in the CSV extract and are not returned by the Workers API might be cleared. **Resolution**: To skip the getObject call after an update, add the following entry to the source using the [Update Source API](). Key: `skipGetObjectAfterUpdate` Value: `true` ## Delta aggregation doesn't fetch the new hires As per standard API response the `DateStart` must be present in the context or changed attributes to fetch the records. **Resolution**: Ensure the `DateStart` is in the Atom feed API. If it isn't present, add it. If the `EffectiveStartDate` value is the same as the `DateStart` you must change the schemaToAttributeMapping as follows and check delta aggregation again. ```xml ``` ## Delta aggregation fails with Null Pointer Exception error **Error**: `Error in aggregation 2fb93885d3db4620a40c02d58bfd0a67: java.lang.RuntimeException - sailpoint.connector.ConnectorException: NullPointerException - java.lang.RuntimeException: sailpoint.connector.ConnectorException: NullPointerException` **Resolution**: Set the `lastAggregation` date in the DD/MM/YYYY format. ## Delay processing the atom feed data When you see issues that the Oracle target system takes a few more minutes/seconds to process the atom feed data and publish it, the changed records are not aggregated by the connector. **Resolution**: To add delay in `publishedMinDelay` in all the atom feed, the parameter given below has to be added in the application via debug. ```text ``` > [!NOTE] > > The value is in Seconds. ## Test connection fails with error during download of file ```text Caused by: java.lang.Exception: Error during download of file[ /Sailpoint_Active_09072025.csv.pgp].net.schmizz.sshj.sftp.SFTPException: /Sailpoint_Active_09072025.csv.pgp at connector.common.transport.SFTPFileTransport.internalDownload(SFTPFileTransport.java:380) at connector.common.transport.SFTPFileTransport.download(SFTPFileTransport.java:212) ``` **Resolution**: If the file is present in the home directory, then you must provide the file name. For example, `Sailpoint_Active_09072025.csv.pgp` ## Single Account Aggregation fails to fetch assignmentsDFF attributes During single account aggregation, the system does not fetch the correct values for the `assignmentsDFF` attributes. The `supplierOrAgency_Display` and `vendorAccessLevel` attributes return empty results. Worker API Response: ```json "assignmentsDFF": [ { "supplierOrAgency_Display": "Aceik Pty Ltd", "vendorAccessLevel": "Light" } ] ``` **Resolution**: 1. Update the following schema attributes: ```xml ``` 2. Update the schemaToAttributeMapping entries with the following configurations: ```xml ``` 3. Run a single account aggregation to verify the changes.