Source showing error -Account File Import Failed with Delimited source while aggregation is running successfully

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi Everyone,

we are facing this issue as Source showing error -Account File Import Failed with Delimited source while aggregation is running successfully on daily basis. if anyone faced such issue then please let me know how we can get this message removed

image

.

image
image805×265 12.2 KB

2

Hi @Deepak_Chaudhary Something to look at is checking how the final row in your file is terminated

3

Are you using File Upload Utility or uploading the file manually ?

4

using the file upload utility

5

will check and confirm if this is the case but the question is daily aggregation is success.

6

This might be using the oldest file that is present. Did you verified the data that is available in latest file is present in ISC or not. Maybe it is running the aggregation with the old file.

7

Hi @msingh900 I checked that the data is present in ISC as per the latest aggregation count.

8

Hi @Deepak_Chaudhary ,

Since, you’re using file utility, could you please check the logs available with your configured powershell script?

Additionally, any difference in the syntax of new and last aggregated file.

9

Hi @AsGoyal As I have checked the Account file and the schema, both looks good to me.

I don’t have access to check the logs from the IQ Service. I think need to raise the sailpoint case.

10

Hi @j_place @msingh900 @AsGoyal

I found that in the file that due to using the special character in the last name of 1 identity “Ç” which is showing as “?” in the “Account Name” in the source.

is this the real issue what are your thoughts?

11

@Deepak_Chaudhary That’s correct. If some extra character is added in the delimited file, then usually SailPoint will gives this error.

12

I have observed this behaviour in IIQ. but in ISC I have not come across this lind of issue for now.

This could be the issue.

13

Hi @msingh900 this is not extra but using as special character. what are possible solutions to handle this if you have any idea?

14

Hi Everyone

if the flat file is saved with the correct character encoding, preferably UTF-8-BOM. Can this will resolve the issue?

15

It should be UTF-8. This might fix the problem.

16

Hi @Deepak_Chaudhary , I’m having the similar issue. with the upload of csv file with a header issue i got a “Account File import failed““warning. I have fixed the csv and aggregation is also successful. However, in my source there is still a warning. Any suggestion for the fix?

17

Hi @sbikal123 ,

First of all, you need to check the account name format for all the records if having some special characters used in some names, then we need to correct those. it will show in account name as “?“. please let us know if this is the case in your feed file.

18

The file does not have special character, and it was the same csv file that was working as expected before the issue started to happen.

19

It’s happening with one of our sources that loads records using the File Upload Utility. I though we found and fixed the issue bur the error message isn’t going away.

20

Hi @pamelabowne @sbikal123 As per the sailpoint they are working on some deployment and then will do their testing and hope that will fix the issue for everyone.

Thanks

Deepak