1

Re: Unable to add new records

Happy New Year everyone,

We have recently begun to be prevented from saving new records, for instance the error message that we receive from a recording card is:

An error occurred attempting to save the data. Another user might be entering some data. Please wait a little while before trying to save again.

The database has not been changed. Message: Unable to create new record. - Taxon Occurrence

Entering from the Species Record screen provides a slightly different error:

An error occurred attempting to save the data. Another user might be entering some data. Please wait a little while before trying to save again.

Residual data was successfully cleaned up. Message: Unable to create new record. - Taxon Occurrence

We are able to edit records.

We have a network installation of Recorder 6.16.2.241 on Windows Server 2003 being accessed by a Citrix virtual desktop.  We are using SQL 2005.

It sounds similar to this previous topic:

http://forums.nbn.org.uk/viewtopic.php?id=530

We have tried various things including: different Recorder and Windows users including administrator, restarted SQL Server, rebooted the entire server, checked the size of the SQL Database files, checked the system and SQL Server logs, and applied patches to Windows and SQL Server (and fixed the issue of DEP being reset to default).

Any suggestions of where else to investigate gratefully received!

Mike Beard
Natural Course Project Officer
Greater Manchester Local Records Centre

2

Re: Unable to add new records

Have a look at  http://forums.nbn.org.uk/viewtopic.php?id=2486 just to make sure the problem is not down to the size of your database. If this doesn't help the  we can investigate further.

Mike Weideli

3

Re: Unable to add new records

Hi Mike,

Thanks for the rapid response. 

We are running SQL 2005 so there is no imposed limit on the file sizes, the database is set to automatically increment file size, and if the server was running out of disk space that would surely have been shown clearly on the server and SQL Server logs?

Mike Beard
Natural Course Project Officer
Greater Manchester Local Records Centre

4

Re: Unable to add new records

Thanks. Thought that might be the case. Will get back to you.

Mike Weideli

5

Re: Unable to add new records

First, it may be worth checking that the LAST_KEY table contents are correct, especially for the TAXON_OCCURRENCE table. You can run the last key addin to make sure that this table is up to date.  If  this fixes the problems you need to give consideration as to why it has got out of step  as it  can sometimes hide a serious problem. (eg. accidental site id change)

Secondly; can you also confirm that you haven't done any upgrading which might have got the database out of step with the software version.

If these don't help  could you upgrade  to 6.17 (available in the next day or two).  The error handling in this area will have been updated in this version to give more helpful messages.

Mike Weideli

6

Re: Unable to add new records

Thanks Mike.

I've passed on your suggestions to our IT Department and will pass on their response when I get it.

Mike Beard
Natural Course Project Officer
Greater Manchester Local Records Centre

7

Re: Unable to add new records

Result!  The Last Key addin updated 14 tables and we are now able to add records.  Strangely I was not able to view the addin in the tools menu via Citrix but IT were able to see it when accessing the server directly.

Now, that just leaves the concern that we do not know what caused the keys to go out of sequence.  IT have not reported doing any updates that might be relevant, and the site ID seemed the same when it appeared via the Last Key message box and new records, so any other ideas?

Mike Beard
Natural Course Project Officer
Greater Manchester Local Records Centre

8

Re: Unable to add new records

Firstly,  there is a known problem with addins not always appearing and this should  be fixed in version 6.17 (out in a few day).

The last key table being out of sync. is not always a sign of an underlaying  problem. Some sort of network glitch during the save of records can also cause the problem. The last key update will fix these.  If  you are satisfied that your site id hasn't accidentally been changed then you should be OK.

In some unlikely circumstances (which have in fact happened)  it is possible to cause this problem by importing your own data. However,  for there to be a problem you have either had to  clear Recorder and start again or  you have had to import data from someone who has been using your site id.  In both cases this should have shown as some unusual duplicatons when doing the import.

Mike Weideli