CiviCRM Community Forums (archive)

Hi,

I'm importing about 1200 organizations into my wonderful kabissa civicrm installation, and am running into a strange problem: it only recognizes a partial set of the rows in my csv file, and doesn't display step 4 when it's finished but just goes back to the import start page. The rows it imports are quite successful. I'm now breaking up my csv into multiple files but I'd rather not do that if it can be avoided.

Is there a log file or other way for me to verify that the contacts are being imported without errors, and do you have insights into why it's not importing them all? Is it just memory? It's consistently only importing 168 records when I try to do all at once, then when I start at row 169 it then only imports 654 records.

Cheers,

Tobias

hi Dave -

(Thanks for the reply. I now realize I need to be checking the forum because I didn't get an email notification.)

Today's the day to finish this import so I am hopeful that I can get past this issue ASAP! Any guidance most appreciated.

Given that the import handles 168 rows on the first try, and then 654 of the next group of rows... I'm suspicious that there may be something in the data that's tripping a bug / error. Does the 168th row get imported? It might be worth removing row 168 and 169 from the input file and seeing what happens.

I tried this and it seems to work - I narrowed it down to one record, and now it gets further before again limiting the number of records it thinks are in the database. Bizarrely, it seems to be having trouble with records with "Congo, The Democratic Republic of the" in their country field. It accepts them when I import them one by one, but not when I import them together with the rest of the data.

Back in a few with more good news, hopefully.

Cheers,

Tobias

You should also check the Apache error log and see if there's any clues.

Nope, nothing in the apache error log.

Hi Dave-

Thanks for the help with this. I ultimately was able to import all the records by breaking it down into smaller sets. Weirdly, the records that seemed to breaking it worked when imported in a small set.

I did run into problems with a few records in Cote d'Ivoire, which has UTF-8 chars in it. I fixed this by changing them all to Afghanistan then changing them back to Cote d'Ivoire after the import.

Cheers,

Tobias