1 Reply by writter

  • writter
  • Member
  • Offline
  • Registered: 12-01-2009
  • Posts: 30

Re: Upgrading from 6.13.2 to 6.14.4

Hello,
the fact, that there is now Recorder 6.14.4 available, triggered me to upgrade our version of Recorder, because we were on 6.13 before that. At the end of the installation process I got the message, that:

"The SELECT permission was denied on the object 'MAP_SHEET', database 'NBNData', schema 'dbo'.

When I now start Recorder, I get the following message after logging in:

Version: 6.13.3.182
Date: 21/08/2009 12:25:29

The following addins could not be loaded for the specified reasons:
    StdValLib.Recorder 6 Standard Validation: Class not registered

The following addins loaded successfully:

What have I done wrong? What shall I do now? I would like to upgrade to 6.14.4., but I think that is not useful at the moment?

Can somebody help me please?


Thanks,
Wolfgang

2 Reply by SimonWood

  • SimonWood
  • Veteran
  • Offline
  • Registered: 09-09-2008
  • Posts: 63

Re: Upgrading from 6.13.2 to 6.14.4

Hi Wolfgang,

When you ran the upgrade did you specify a user account with admin privelages to upgrade the SQL database?  The first error message you're encountering sounds like a problem with the SQL permissions.  It sounds like it is worth rerunning the upgrade ensuring to specify an account with admin privelages on the SQL server.

If you have access to management studio or enterprise manager can you please inform me of the 'DB Seq' (Database Sequence Number) from the SETTING table in the database.  This will help identify as to what stage the upgrade process did get.


As for the Addin issue, it might well be worth adding back in the standard validation library via Recorder (if the issue still occurs after rerunning the upgrade).  This can be done via Tools -> Install -> Addin Module.    From here look to see if the 'Recorder 6 Standard Validation' item is present, if it is remove it.  Then select 'Install' and navigate to the Recorder 6\ Addins directory, from here select StdValLib.dll.  This will re-install the Standard Validation Library.


Hope this helps

Simon Wood
[url=http://www.dorsetsoftware.com/]Dorset Software Services[/url]

SimonWood's Website

3 Reply by writter

  • writter
  • Member
  • Offline
  • Registered: 12-01-2009
  • Posts: 30

Re: Upgrading from 6.13.2 to 6.14.4

Hi Simon,
thank you very much for your reply.

I looked at the rights for my admin account and the account seems to have all possible rights. But I must say, that I don't undersrtand, what all the different levels of rights mean.
I have access to management studio, but I couldn't find out the DBSeq entry from there. I could only see the structure of the table. But I could see the entries from an Access database, which is linked to the Recorder database. According to that the DB Seq is 0000005P, the software version is 6.13.2.176.

The Addin issue is now solved. I did, what you told me and I don't get this message any longer.

The interesting thing is, that according to Recorder itself, the version of Recorder is now 6.13.3.182, which is different from the information in table Setting.
If I now try to update from somewhere to 6.13.3. again, assuming, that the Setting table is true, I get the same message as before:
"The SELECT permission was denied on the object 'MAP_SHEET', database 'NBNData', schema 'dbo'.

If I now try to update to 6.14., assuming Recorder is true, I get the message, that the file "U:\Program Files\Recorder 6 Server\Help\AbundanceQualifiersMatch.htm" can't be upgraded, because it's either in use or I don't have sufficient privileges. But it is not in use and I can open it.

So I'm one step further, but I still need some steps to successfully upgrade to 6.14..

It would be great, if you could help me with the next steps.


Wolfgang

4 Reply by SimonWood

  • SimonWood
  • Veteran
  • Offline
  • Registered: 09-09-2008
  • Posts: 63

Re: Upgrading from 6.13.2 to 6.14.4

Hi Wolfgang,

Firstly can you please ensure that the AbundanceQualifiersMatch.htm file is not readonly as  this may hinder the upgrade process.  Also do you have permissions to actually amend/delete the file at hand?  Although you can open the file up it doesn't necessarily mean you have permissions to delete/replace it. 

It still sounds like you're experiencing issues when upgrading the database too.  When do you actually receive the "The SELECT permission........" message?  is it whilst the upgrade kit is identifying that it is upgrading the database structure?  Also is there any other information present on the error message?

When you run the upgrade kit, you are prompted for a method in which to login to the SQL Server, are you using the "Windows Authentication" method or specifying a SQL server admin username and password? 

If you are using Windows Authentication it is worth checking you rights by trying to open up the MAP_SHEET table via Management Studio, if you can't view the data, then your account doesn't have sufficient privellages, hence why the upgrade fails.  If this is the scenario then it will be worth contacting your systems administrator for an account with the required permissions to upgrade Recorder.

Hope this helps and let me know how you get on

Simon Wood
[url=http://www.dorsetsoftware.com/]Dorset Software Services[/url]

SimonWood's Website

5 Reply by writter

  • writter
  • Member
  • Offline
  • Registered: 12-01-2009
  • Posts: 30

Re: Upgrading from 6.13.2 to 6.14.4

Hi Simon,
thank you very much again.
Everything is solved now. The AbundanceQualifiersMatch.htm file and other files were protected against writing, I could have known without asking you, sorry!
Accessing the database I always used an account, where I thought, I would have the most rights. When I tried another account, where I thought to have less rights, I could do more.
The last problem was, that the antivir software stopped some of the update processes without asking and telling me. I told the software to trust these files and processes and then it was fine.

So thanks again and apologies for asking some questions, which I could have answered by myself with more thinking before.

Wolfgang