1

Re: Error importing records

I have a recurring problem when importing some records. The application crashes giving me the option to close application or restart application etc. Once it has restarted I now find that the event and the observations have been added but that there is no taxon occurrence details. If I re-import the records it works fine and I am then able to delete the phantom records. My worry is that there are some rogue records (missing taxon occurrence details) that I have previously added and thought were ok. Is there any way I can search for all the records that are missing taxon details so that I can remedy the problem? Help with this would be much appreciated.
ps the exception message reads "Error occurred transferring records for SQLSERVER_TAXON_OCCURRENCE_DATA into main database"

2

Re: Error importing records

Good luck with this one, we have been experiencing the same thing intermittently for months, as you will see from this thread http://forums.nbn.org.uk/viewtopic.php?id=1591, we haven't had much luck with a solution.

Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre

3

Re: Error importing records

We are now getting this error as well, once for taxon occurences and once for survey events (as I remember). The saved error message refers to an access violation, for instance "Access violation at address 0040475A in module 'RecorderApp.exe'. Read of address 6E614C24." and "Access violation at address 0040475A in module 'RecorderApp.exe'. Read of address FFFFFFD1."

Sounds like I had better start checking against the spreadsheets to look for missing records.

Janet


Janet

Janet Simkin
British Lichen Society

4

Re: Error importing records

We too are getting this error [version : 6.16.2.241] and I can confirm this;

Rob Large wrote:

Interestingly if we tell recorder to restart after the exception, we find that the importer has created both survey event and sample, but has not imported any records. If we repeat the import, it creates another survey event and sample  and then succeeds in importing the data. But now we have a duplicate (empty event and sample). I thought the whole import process was supposed to be wrapped in a transaction which rolls back if there is a problem.

We found that the original survey and sample cannot be deleted until the sucessful import has occurred. We find that we have to close Recorder though. On average every second or third import has an error and in this case it is the same format of xls file i.e. we supply it and it is filled out by various people.

It's a real shame that something that is intended to get data in efficiently is actually slowing it down. What should take an hour or so takes three or more.

Data Manger
Somerset Environmental Records Centre

5

Re: Error importing records

For info:

I had "Error occurred transferring records for SQLSERVER_TAXON_OCCURRENCE_DATA into main database" last week. I initially thought this may be due to lack of space in my C: drive but this wasn't the case having expanded the drive. The problem was a hidden character in a comment string in the original Excel spreadsheet. I performed a "=TRIM(CLEAN(RC))" on every comment and reimported without any exception errors.

Hope this is of use!

Les Evans-Hill
Senior Data Officer
Butterfly Conservation, Butterflies for the New Millennium and National Moth Recording Scheme