1

Re: Problems with starting Recorder after upgrade to 6.13

Hi

Running R6 over networked MSDE we ran into a problem when attempting to start recorder after the upgrade to 6.13.

The login/password dialogue was not coming up, with the programme appearing to hang with the initial Recorder screen up, on all machines except that of IS.

Problem was solved by having IS person with admin rights on all machines login and start up Recorder on each machine, now works for subsequent logins by any user.

We assume that the first run of Recorder on each machine updates some files related to the workstation installation, and that ordinary users did not have the correct permissions to do this, preventing Recorder from continuing to the login dialogue.

(just for info in case anyone else has similar problems)

Gordon

Gordon Barker
Biological Survey Data Manager
National Trust

2

Re: Problems with starting Recorder after upgrade to 6.13

does this solve the problem with unable to run Recorder 6 v1.3 on server?

Cheers

IT Officer
rECOrd (A Biodiversity Information System for Cheshire, Halton, Warrington and Wirral)
www.record-lrc.co.uk

3

Re: Problems with starting Recorder after upgrade to 6.13

This solved it for a MSDE server install, obviously I don't know if there are similar problems for a SQL server install but it might do if you have complicated permissions arrangements.

Gordon

Gordon Barker
Biological Survey Data Manager
National Trust

4

Re: Problems with starting Recorder after upgrade to 6.13

It's probably something to do with Recorder trying to update registry entries that only an Admin has rights to change. I'm often dogged by this problem, particularly with HKEY_CLASSES_ROOT\TypeLib\{801EBE82-91CE-11D3-B564-005004B0B698}\1.0\0\win32. This key contains a path to RecorderApp.exe. If that path is slightly different to the one you have mapped (even a difference in case), then Recorder will attempt to rewrite the key with the mapping as it exists on the workstation. If you're a non-admin, then the change is denied and Recorder falls over.

Charles Roper
Digital Development Manager | Field Studies Council
http://www.field-studies-council.org | https://twitter.com/charlesroper | https://twitter.com/fsc_digital

5

Re: Problems with starting Recorder after upgrade to 6.13

the new update seems to be running fine on other workstations apart from when i'm trying to run Recorder on the server. it only works if run the program with restricted access.

IT Officer
rECOrd (A Biodiversity Information System for Cheshire, Halton, Warrington and Wirral)
www.record-lrc.co.uk

6

Re: Problems with starting Recorder after upgrade to 6.13

Any comments and/or ideas on this one from Dorset Software (Simon?), John VanB, Sally, Mike W., or NBN staff ??

It is something that would be useful to have 'fixed' if at all possible by the next release or at least a workaround.

Anyone ??

Cheers

Steve  :)

Steve J. McWilliam
www.rECOrd-LRC.co.uk
www.stevemcwilliam.co.uk/guitar/

7

Re: Problems with starting Recorder after upgrade to 6.13

Hi All,

We've looked into this but unfortunately don't have a definite answer yet. It relates to the fact that if Recorder is upgraded and the new executable file contains an updated type library (i.e. the COM addin interfaces have been changed) then when you run Recorder it must re-register the details of those interfaces with Windows. This, unfortunately, has to be done on every client machine, and also requires admin rights. So if you run the upgrade on one machine with admin rights, on a network install the upgrade cannot re-register the Recorder exe on all the other machines. The only way I know around this is to login with local machine admin rights on each of the workstations after the upgrade and run Recorder.

I will raise this issue with our system administrators to see if they can suggest a way to distribute the registry changes to the clients automatically, or other deployment options.

I'll keep you informed of our progress,

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

8

Re: Problems with starting Recorder after upgrade to 6.13

After months of thinking. I have manage to track down where the problem might be but I might be wrong here.

I have found 2 ways to get Recorder 6.13 to run on the server.
1. Run RecorderApp.exe as restricted user. This way you cannot access any local files when you try to import a file.
2. Set deny read to the current account in Recorder registry. This way you can access the file on your pc for doing import ect. But when starting up the program, you will get a screen saying "Updating Recorder 6 Settings...". I assume Recorder try to rebuild the registry.
Anyway the program seem to be running just fine and allow Recorder 6 to be running on the server again.

My question will be why Recorder 6.13 can't access to registry when it has every right to do so? And how to fix this?

Cheers

Luck

IT Officer
rECOrd (A Biodiversity Information System for Cheshire, Halton, Warrington and Wirral)
www.record-lrc.co.uk

9

Re: Problems with starting Recorder after upgrade to 6.13

Hi,

This area will be addressed in version 6.14 of Recorder.  The install and upgrade kits will automatically register the Recorder type libraries after an install/upgrade.  This will mean that there will no longer be a need  for a user with admin rights to actually load up Recorder after an install on a workstation. 

This should also resolve the issue that  has been encountered with Recorder trying to update a few registry settings that it may not have access to (such as Charles issue above).

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