1 (edited by boneill 24-02-2014 10:48:03)

Topic: Dictionary Upgrade to 0000001R, 0000001S Fails

Hi Guys,
I have run into an unusual problem. The dictionary upgrade to version 0000001S fails. I will attach the bug report to this post. Here is some background information:

R6 Version: 6.18.1.260
Current Dict Verstion: 0000001Q (All four indexes were rebuilt before update was attempted to level the playing field)

Server: Windows 2008 R2
Database: SQL Server Express 2008 R2
Client: Windows 7 SP1

I have been able to reproduce this error even with a reinstall, the other dictionary updates ran fine again but 0000001S fails almost immediately.

I wonder if anyone else is experiencing this error?

The key bullet point of the error report appears to be "Error occurred transferring records for SQLSERVER_TAXON into the main database".

Thanks,
Barry.

Post's attachments

0000001_upgrade_ bug_report.txt 24.12 kb, 8 downloads since 2014-02-21 

You don't have the permssions to download the attachments of this post.
Barry O' Neill, Data &  ICT Manager
National Biodiversity Data Centre, WIT West Campus, Carraiganore, Waterford, Ireland
+353 (0) 51-306247 | boneill@biodiversityireland.ie | http://www.biodiversityireland.ie

2

Re: Dictionary Upgrade to 0000001R, 0000001S Fails

Please can you check in R6  Help/About Recorder 6  to see how far R6 thinks it has got with the upgrades. There is nothing in 0000001S which relates to inserting into the Taxon_Table, so the problem might be in 1R.

Mike Weideli

3 (edited by boneill 24-02-2014 09:35:11)

Re: Dictionary Upgrade to 0000001R, 0000001S Fails

Mike,
Good morning. You are indeed correct.  I was using the recommended upgrade file "0000001R,1S.zip" to patch the dictionary up to 0000001S. I will also give a little more background on this in case it helps to track down the issue.

I am moving an existing network install to a new server. The settings table reported that the pre-existing application version was 6.18.1.260 and that the dictionary version was 0000001Q.

Knowing that the latest version available via installation media is 16.7.2, I attached my "NBNData.bak" file and set up the required permissions and users in sql server 2008 and then verified that I could connect to it via NBNUser on the client. All went fine. I then installed 16.7.2 and logged into recorder 6 without issue after which I patched the application up to the latest version. I then logged in again without issue. However the moment I try to bring the dictionary up to 0000001R,1S.zip, the application crashes and gives me the aforementioned error report.

In order to rule out the possibility that the database version was too far advanced to work properly with the older 16.7.2, I then reinstalled a brand new fresh version of both the application and the database and patched the application and database up to the matching versions(6.18.1.260 & 0000001Q) of my "NBNData.bak" file. At this point I then swapped out the fresh database for my pre-existing one and thus my application version now matched what was in the settings table of the pre-existing database file. I logged in and ran recorder 6 without issue. However as soon as I run the dictionary update it crashes again.

Also on your question, the recorder 6 help dialog agrees with the settings table and shows the version numbers 6.18.1.260 & 0000001Q for both the application and dictionary respectively.

Any thoughts are appreciated.

Barry O' Neill, Data &  ICT Manager
National Biodiversity Data Centre, WIT West Campus, Carraiganore, Waterford, Ireland
+353 (0) 51-306247 | boneill@biodiversityireland.ie | http://www.biodiversityireland.ie

4

Re: Dictionary Upgrade to 0000001R, 0000001S Fails

I am not sure about this, because the upgrade doesn't usually fail even if there are issues with entries, it just ignores them.  Please could you try temporarily  removing upgrade 1S from the scripts folder leaving just the  0000001R.zip  and see whar happens. If it works you can put back 0000001S and run again. If not let me know what happens.

Mike Weideli

5 (edited by boneill 24-02-2014 10:36:20)

Re: Dictionary Upgrade to 0000001R, 0000001S Fails

I just tried removing 0000001S and running the upgrade again but no luck unfortunately, it again fails with the same error report within seconds. All previous upgrades ran without issue, in my case there seems only to be an issue with 0000001R.

Barry O' Neill, Data &  ICT Manager
National Biodiversity Data Centre, WIT West Campus, Carraiganore, Waterford, Ireland
+353 (0) 51-306247 | boneill@biodiversityireland.ie | http://www.biodiversityireland.ie

6

Re: Dictionary Upgrade to 0000001R, 0000001S Fails

I attach a  test 000001R.zip for you to try.  Replace the 1R in the scripts folder and give it a try. This isn't a fix just a test. If it works this will prove that the problem is in the data. You  will need to change the setting table back to 0000001Q, so that we can run 1R again when the problem has been identified.

Post's attachments

0000001R.zip 2.26 mb, 3 downloads since 2014-02-24 

You don't have the permssions to download the attachments of this post.
Mike Weideli

7 (edited by boneill 25-02-2014 09:56:27)

Re: Dictionary Upgrade to 0000001R, 0000001S Fails

Morning Mike, I ran the custom 0000001R.zip that you provided and it worked fine. So this means that the problem is in the data itself then? How will we go about ascertaining where the actual problem is, as the database in question has a lot of data and many surveys. Do you have any troubleshooting queries to seek out potential problems on file? Thanks again for the help it is much appreciated.

Barry O' Neill, Data &  ICT Manager
National Biodiversity Data Centre, WIT West Campus, Carraiganore, Waterford, Ireland
+353 (0) 51-306247 | boneill@biodiversityireland.ie | http://www.biodiversityireland.ie

8

Re: Dictionary Upgrade to 0000001R, 0000001S Fails

Just to check before looking elsewhere, but has your database got too big for the version of SQL you are using ? 

If this isn't an issue, then I will break down 1R into individual upgrades for each tables, so that we can isolate the problem.

Mike

Mike Weideli

9

Re: Dictionary Upgrade to 0000001R, 0000001S Fails

This was actually one of the first things that I checked into as well before even doing the re-install testing. I am on SQl Server 2008 Express R2 so the limit would be 10GB. The current database size is 1938MB with auto-grow by 10% unrestricted enabled. So there should not be any issues on that side of things.

Barry O' Neill, Data &  ICT Manager
National Biodiversity Data Centre, WIT West Campus, Carraiganore, Waterford, Ireland
+353 (0) 51-306247 | boneill@biodiversityireland.ie | http://www.biodiversityireland.ie

10

Re: Dictionary Upgrade to 0000001R, 0000001S Fails

Sorry about delay -  missed your reply.  I have broken down 1R into separate tables. The zip file containing all the parts is at www.lfield.co.uk/downloads/0000001R.zip

Unzip this just the once into a empty scripts folder so that you have 0000001R.zip to 0000001Z.zip in the folder  and give it a try. Make sure before you start that the Dictionary sequence in the setting table is 0000001Q . What I am trying to do is identify which table is causing the problem. Although the error message implies it is the Taxon table there doesn't seem to be any logical reason for it to cause a problem.

Mike Weideli