1

Re: problem with upgrade from Recorder 6.13.2 to v6.13.3 on standalone pc

In March 2009 we upgraded our Recorder database to Recorder 6 on a standalone pc and this has been working fine.
The standalone was not connected to the internet until recently and a few weeks ago I downloaded the first upgrade that I needed ie the upgrade kit V6.10 (or 6.13) to 6.13.3

My Recorder on the standalone pc is version loaded from a CD I obtained from Dorset Software is version 6.13.2.766. As I understood it from the website I would need the above upgrade for anything less than v6.13.3.

I have not been able to get the upgrade to run. I think it is a problem with the username and/or the SQL server.
I have looked at the Forum but have not been able/cannot understood how or where to put
EXEC sp_change_users_login 'update_one', 'nbnuser', 'nbnuser'

The error message we get when trying to go back into Recorder is:
an error occurred whilst starting the application. eoleexception: cannot open database “nbndata” requested by login. The login failed.

The trouble is that I am now unable to get into Recorder6 at all so am not sure the best route forward. The database is backed up as an nbnbackup.bak file.

I have tried re-running the upgrade in two ways:
If I select 'Use my NT Account' it appears to run the upgrade but I cannot get into recorder.
If I select 'Use the following SQL Server Account' and then insert my username and password I get the message ' login failed for user 'Philippa Tomlinson' and then the upgrade sticks.

I have been advised by Dorset Software not to try re-loading the software from the original CD.

Please can someone help?
many thanks
Philippa

Dr Philippa Tomlinson
Biological Records Manager
Manx Biological Recording Partnership

2

Re: problem with upgrade from Recorder 6.13.2 to v6.13.3 on standalone pc

Many thanks to Sally Rankin for sorting me out here.
Having loaded SQL Server Management Studio Express Sp3, we ran the query:
exec sp_change_users_login 'update_one', 'nbnuser', 'nbnuser'
and after we were reminded to run RecorderApp.exe (as Administrator) the first time we ran the program again after the upgrade ... it is now working fine.
I just have a few more upgrades to do and to learn some more about SQL Server before I try anything rash on my own again!
cheers
Philippa

Dr Philippa Tomlinson
Biological Records Manager
Manx Biological Recording Partnership