2245162 - How to troubleshoot the error “Exception during http Transaction: Unterminated string at XXX[character YY line ZZ]”

This KBA explains on how to troubleshoot the error which is encountered in the Boomi process.

Error seen in process reporting page:

Interface Failed.

Detailed Error:

[EXCEPTION] ODATA Execution Error Code: 500

When you download the process logs for Boomi process you can find this error for SEVERE:

2015-11-17T14:21:46Z     SEVERE Connector priv_prod Connector; I08_Query_SF_PositionData    Exception during http Transaction: Unterminated string at 124479 [character 255 line 939]

Boomi , BizX environment

This is because of Bad Data in the instance.

The solution deals with:

Identifying the issue using the process logs information :-

Download the process logs from Boomi and check for the word “SEVERE” in the logs.

Now in the same line the error would say the line number and the row number where the character which is not readable/ bad data is present.

Now goto the successfactors instance and download the corresponding data log from the SFAPI/OData API audit log based on the API used in the Boomi operation.

Note: Usually it will be the last log which would have the bad data in the instance, so always download the response file based on the timestamp which is latest.

After downloading the data logs open it in a notepad++ and then check the line number given in the process log for example: [character 255 line 939]

Check in the data logs in the same line number to find the bad data

Identifying the bad data in the instance :-

1. Log into Succesfactors instance

2. Open the admin center

3. Choose manage data/manage organization pay and structure in the admin tool search bar

4. Choose relevant entity in the first dropdown and then the external code for the same/ unique identifier of the record

For Example:

5. Now click on Take action and make correction

6. Now copy the data in the field Desk Title into an excel sheet

7. Now correct the data and insert it back into the corresponding field and save the data.

Note: If the affected data field has any translations, please do not forget to correct the data there also.

KBA , odata execution error code: 500 , unterminated string at , data issue , api issue , bad data in boomi , api not reading data , LOD-SF-INT-BOM , Standard SF to 3rd Party Boomi Content , LOD-SF-INT-EC , Employee Central SFAPI & OData Entities , How To