1 Reply by swtmike

  • swtmike
  • Member
  • Offline
  • Registered: 13-10-2009
  • Posts: 31

Re: usp_DefaultUser_Get_Key error after replacing 6.13 with 6.14

Hello (again),

after a network uninstall of Recorder 6.13 to install 6.14 (also network) I am struggling to get a workstation to connect - we receive the error below when trying to run Recorder on the workstation Desktop.

'An error occured whilst starting the application.
EoleException: Could not find stored procedure 'usp_DefaultUser_Get_Key'

A reply to http://forums.nbn.org.uk/viewtopic.php?id=1109 by Lynn suggests looking for a stored procedure: usp_DefaultUser_Get_Key but there is none there. The value for DB Seq in dbo.Setting is 0000005R.

The steps to get to where I am were;

1) Uninstall Workstation from clients.
2) Detach ourNBN database and log file on server and move from default location.
3) Uninstall 6.13 from server.
4) Install 6.14 on server.
5) Move ourNBN database to default location and attach overwriting default database and log files created during install of 6.14.
6) Run Workstationsetup.exe from PC.
7) Amend permissions on server and PC according to Network Installation Guide v5.1 (maybe this should have been completed before step 6?).

There is no resolution posted on the other thread but I'd be grateful for any advice that can help us to get this working.

Regards,
swtmike

2 Reply by sallyrankin

  • sallyrankin
  • Administrator
  • Offline
  • Registered: 07-04-2006
  • Posts: 371

Re: usp_DefaultUser_Get_Key error after replacing 6.13 with 6.14

I saw a similar error message on a customer site on Thursday but in that case the user stored procedure was usp_MeasurementColumns_Get. With the help of Dorset Software and the customer’s IT support we resolved it as follows. In Microsoft SQL Server Management Studio we looked at the permissions on the usp (Databases – NBNData – Programmability – Stored procedures – dbo.usp_MeasurementColumns_Get – right click – Properties - Permissions) and found that no users or roles were listed. We then looked at the users or roles for usp_Individual_Insert and added the same ones to usp_MeasurementColumns_Get. This solved the problem although we later got a similar error message for usp_SampleDetails_Get.

Simon Wood at Dorset Software then provided us with a SQL script which enabled us to check for other instances of this problem and a file that listed the permissions that usps should have. Another 8 cases were found and corrected. I will forward the information from Simon to Lynn Heeley so that she can make it more widely available.

If requested, JNCC will give the Recorder resellers access to support from Dorset Software while they are on customer sites. This has enabled me to resolve quite a few SQL Server problems so many thanks to both parties.

Sally Rankin, JNCC Recorder Approved Expert
E-mail: s.rankin@btinternet.com
Telephone: 01491 578633
Mobile: 07941 207687

3 Reply by johnvanbreda

  • johnvanbreda
  • Administrator
  • Offline
  • From: UK
  • Registered: 27-04-2006
  • Posts: 1,237

Re: usp_DefaultUser_Get_Key error after replacing 6.13 with 6.14

Looking at this problem I think what has happened is the workstation is still pointing at a database which has not been upgraded. usp_DefaultUser_Get_Key was introduced in version 6.14 in file 00000079.sql, and your database is still at version 6.13. When you run the upgrade kit, both the application files and the database structures are upgraded. Looking at the notes you've provided, it seems you have restored the 6.13 database after the upgrade, so you now have a 6.14 application running against a 6.13 database.

Fortunately there is a simple solution - just re-run the upgrade kit from one of the workstations. This will not affect the application files, but will bring your database up to date.

I'm curious why you approached the upgrade as you did though rather than by just running the upgrade kit and letting it take care of things?

One more point for Lynn and Simon - it would be nice if the Recorder application made a check on startup for the expected database version against the application and gave a warning if not compatible, as in the current setup it is not very clear what went wrong.

Regards

John van Breda
Biodiverse IT

johnvanbreda's Website

4 Reply by swtmike

  • swtmike
  • Member
  • Offline
  • Registered: 13-10-2009
  • Posts: 31

Re: usp_DefaultUser_Get_Key error after replacing 6.13 with 6.14

Apologies for the delay in replying.

I was asked to remove 6.13, due to issues elsewhere running the upgrade, and just install 6.14. Thankfully John's solution was indeed simple and resolved the issue.

Thanks again for the replies.

swtmike