This documentation supports the 20.16.01 version of BMC Remedyforce.

To view the latest or an earlier version, select the version from the Product version menu.

Troubleshooting common issues when importing data

The following table describes the troubleshooting tips that you can use to resolve common issues that you might face when importing data.

 Error or issueApplies to the Pentaho package forDescription or procedure
Viewing logs of the import jobsAll

Log files are created in the folder where you have saved the KJB files. Success and failure rows files are also created in the same folder.

If a failure occurs, the error code and its description are provided in the failure row file. You can also use the failure row file to import data to Salesforce.

Not all records are importedAllDelete the delta time stamp file of the job that you ran, and run the job again.
An "out of memory" error occursAll

While importing a large number of records, if you get the OutofMemoryError or Java heap size error message, increase the heap size in the Spoon.bat file.

  1. Navigate to the location where you downloaded and unzipped the Pentaho Data Integration tool.
  2. Navigate to the data-integration folder.
  3. Right-click the Spoon.bat file, and select Edit.
  4. Locate the following line and replace 512 with a higher value:
    If "%PENTAHO_DI_JAVA_OPTIONS%"=="" set PENTAHO_DI_JAVA_OPTIONS="-Xmx512m" "-XX:MaxPermSize=256m"
  5. Click Save.
  6. Relaunch the Spoon.bat file and rerun the job file.
A "too many script statements" error occursAllWhen you run an import, if you receive "Too many script statements" as an onscreen Apex error message or in an email, reduce the batch size by 10 in the Batch Size field in the Settings section on the Salesforce Upsert window.
Records are not being to your CMDB.AllRaise a case with Salesforce to create a custom index on the Assembly ID field of the Base Element object.
Importing users by using the failure rows file for LDAPLDAP server

A failure row file is a text file that is saved in the folder where you have saved your KJB files. Perform the necessary steps to remove the error provided for the failure rows in the failure rows file, and then import the data by using the following steps.

The following Pentaho packages provide a transformation file in the FailureRowsInput folder. You can use this transformation file for importing users from the failure rows file to the Salesforce organization.

To import data from the failure rows file

  1. Double-click and open the FailureRowsInput folder.
  2. Double-click and open the LDAP_FAILURE_ROWS_
    Where YYYYMMDDHHMMSS is the time stamp of the file.
    The first line in the file displays the header row and from the second line onward details of the failed import are displayed. 
  3. For each failed import record:
    1. Read the information under the headings Error Description, Error Fields, and Error Codes.
    2. Resolve the error.
  4. Open the FailureLDAP transformation file with the Spoon batch file of the Pentaho Data Integration tool.
  5. Double-click the Salesforce Upsert step, and enter your Salesforce organization username and password in the Connection section.
  6. (Optional) To verify the connection, click Test connection.
  7. Click OK.
  8. To save the FailureLDAP transformation file, click .
  9. Click .
  10. In the Execute a transformation window, click Launch.
Failed in writeToSalesForce: java.lang.IllegalArgumentException: The char '0x0' after 'Print' is not a valid XML characterAllSome unicode characters that cannot be parsed by the XML parser are present in any of the mapped fields. Either delete these characters in data or delete the mapping of such fields.
Unable to query SalesforceAllCheck your Salesforce organization credentials in the Salesforce Upsert and Salesforce Input(CMDB_Classes) steps.
The job does not appear in Atrium Integrator.BMC Atrium CMDBEnsure that you have saved your KTR and KJB files in a folder in Atrium Integrator.
Error setting value #2 [ARDelta_1 Integer] on prepared statement (Integer)BMC Atrium CMDBThis error is generated if multiple records are created in the BMC Remedy AR System NGIE:Delta form for the running transformation. Delete the additional ARDelta entries that are created for the error transformation file by deleting the records. To find the duplicate records for a transformation file, open the NGIE:Delta form in BMC Remedy AR System. In the TransName field, enter the transformation file name, and click Search.
Did not find Remedy Application Service password for server<server name> in UDM:RAppPassword Form on server <server name>BMC Atrium CMDBCheck your Atrium Server Connection credentials in the ARInput step.
'Oracle Database Server 10g Release 2' is not valid for the type xsd: <data type >BMC Atrium CMDBCheck the data type of the mapped fields in the Salesforce Upsert step.
Duplicate LAN Endpoint entries are created in BMC Remedyforce CMDB.BMC Client Management

In BMC Remedyforce Summer 15 Patch 1 and earlier versions, when you imported LAN Endpoint data from BMC Client Management, duplicate LAN endpoint entries might have been created in BMC Remedyforce CMDB. This duplicate data was created because of the following factors:

  • In BMC Client Management, a LAN endpoint could periodically obtain multiple IP addresses using DHCP.
  • In BMC Remedyforce Summer 15 and earlier, the Network Interface IP address was used as the unique source identifier for LAN endpoints imported from BMC Client Management.

In BMC Remedyforce Summer 15 Patch 1 and later versions, instead of the Network Interface IP address, the MAC address is used as the unique source identifier for the LAN endpoints imported from BMC Client Management, and new duplicate LAN endpoint entries are not created in BMC Remedyforce CMDB.

To resolve this issue, you must install the latest Pentaho package for BMC Client Management released with BMC Remedyforce Summer 15 Patch 1 or later. Also, you must manually delete any existing duplicate LAN endpoint entry on the Remedyforce CMDB. For more information, see Deleting configuration items.

The HTTP Status 404 error is displayed when trying to connect to Salesforce.All

Ensure that your Pentaho transformations connect to<API version> instead of<API version>.

Starting from January 1, 2016, Salesforce retired as an API endpoint. For more information, see the announcement on BMC Communities website. To view a video demonstration of how to update your Pentaho transformations, see Salesforce API Endpoint Retirement.

BMC Remedyforce has updated the API endpoint in the Pentaho packages that are currently available on the BMC Communities website.

Error connecting to your Salesforce organization when using version 5.4 of the Pentaho Data Integration Tool.All

Check whether the Require TLS 1.1 or higher for HTTPS connections Salesforce critical update is enabled in your organization.

Pentaho Data Integration Tool 5.4 does not support TLS 1.1 and cannot connect to your Salesforce organization if this Salesforce critical update is enabled in the organization.

To resolve this issue, perform one of the following actions:

  • Use version 6.1 of the Pentaho Data Integration Tool to import data from various data sources to BMC Remedyforce.
  • Deactivate the Require TLS 1.1 or higher for HTTPS connections Salesforce critical update in your Salesforce organization.
    For information about when the critical update will be automatically activated, see Salesforce Knowledge Article Number 000232871.

Error running the Pentaho packages.

In some cases, you might also not be able to open the Enter Mapping window by clicking Edit Mapping in the Salesforce Upsert window.


In the Pentaho packages provided by BMC Remedyforce, ensure that the API version in the Salesforce Webservice URL field in steps, such as Salesforce Upsert, is supported.

  • In the LDAP Pentaho packages, the default API version in the Salesforce Webservice URL field is 27 (
  • In all other Pentaho packages, the default API version in the Salesforce Webservice URL field is 24 (

In the Salesforce Upsert window, when you click Edit Mapping, the following error message is displayed:

Certain referenced fields were not found!


Perform the following steps to resolve this issue:

  1. In the Salesforce Upsert window, click Edit Mapping.
    The Certain referenced fields were not found! error message is displayed.
  2. To open the Enter Mapping window, click OK.
    The tool removes all referenced fields from the existing mappings. The Pentaho package provided by BMC Remedyforce includes only one referenced field, BMCServiceDesk__CMDB_Class__c. The CMDB_Class field is no longer available in the Mappings column.
  3. In the Source fields column, select CMDB_Class and click Add.
    When you move CMDB_Class from the Source field column to the Mappings column, the c in the field name is replaced with r. For example, BMCServiceDesk__CMDB_Class__c is replaced with BMCServiceDesk__CMDB_Class__r.
  4. (Optional) Update mappings for other fields based on your requirements.
    For information about updating the out-of-the-box mapping, see Field mapping in CMDB 2.0.
  5. To save your settings and close the Enter Mapping window, click OK.
  6. In the Salesforce Upsert window, in the Module field column in the Fields area, click BMCServiceDesk__CMDB_Class__r, and replace r with c.

  7. To save your changes and close the Salesforce Upsert window, click OK.

Was this page helpful? Yes No Submitting... Thank you