1

Topic: Upgrade from Version 6.16.2.241 to the latest version

Hello,
My IT department are planning to upgrade our version of Recorder 6 to the latest version.  We currently use version 6.16.2.241 on Windows XP.  They have asked me to check if there are any known issues which they should be aware of when doing this?  I have had a search through previous posts but don't see anything.  Can I double check that this a straight forward process or is there anything we should be aware of before commencing?

Thank you for your time.

Kind regards,
Christine

2

Re: Upgrade from Version 6.16.2.241 to the latest version

There are no specific problems. The person doing it needs sufficient permission on SQL Server to  update the database and also  write permission on the  folder on the server.  It can be run from a workstation. Alternativelyy if R6  can be run from the server, then the upgrade can be  run from there.  All being well it should  only  take a few minutes to run.

You will also need to run a dictionary upgrade to populate the new tables. This will take a few hours.

Mike Weideli

3

Re: Upgrade from Version 6.16.2.241 to the latest version

Thanks Mike.

4

Re: Upgrade from Version 6.16.2.241 to the latest version

Hi Again,

One more question before we upgrade.  In the Release note it warns that there is a change to the method of expanding taxonomic groups.  I'm not sure if this would affect us.  I tend to use the Report Wizard, however we do have a few user defined XML reports.  I have searched these for any mention of the Index_Taxon_Group table and there is no reference to this in the xml files.  Do you think we are safe to proceed?

Many thanks,
Christine

5

Re: Upgrade from Version 6.16.2.241 to the latest version

While XML reports could be affected, it is is very unlikely that they will. The main reason for using Index_Taxon_Group has been to expand the taxonomic hierarachy . Normally, this is then used in conjunction with Index_Taxon_Name and in these situation the reports still work. I have investigated several custom XML reports and SQL queries which use Index_taxon_Group and only in one case has some change been required.  I think you should be safe to go ahead.

Mike Weideli

6

Re: Upgrade from Version 6.16.2.241 to the latest version

Thanks Mike.  We have upgraded the version of Recorder 6 to the latest version.  We now want to upgrade the dictionary.  The version we currently use is 0000000Y.  Do we have to run every upgrade file released since this version or only the current three files for v.6.22?  We tried the current files, however we get the error message "A diffeent upgrade is required to upgrade your version of Recorder....."
Also, when exactly do we rebuild the indexes... before or after the dictionary updates or both?
And do we have to re-boot the server at any point?

Thank you for your help!

Kind regards,
Christine

7

Re: Upgrade from Version 6.16.2.241 to the latest version

You need all the upgrades from Y up in the the scripts folder. That is 0000000Z.zip to 00000028.sql

Make sure you are using the latest dictionary upgrade kit. It will take  2 hours plus  to run and you need only build the indexes once after the whole thing has completed.  You don't need to reboot the server.

Dictionary downloads are at http://jncc.defra.gov.uk/page-4615

Remember to only unzip the downloaded  zip files once, so that you end up with zip files and .sql files completing the sequence. also a few .ini files which are there in later upgrades to  allow the progress bar to work.

Mike Weideli

8

Re: Upgrade from Version 6.16.2.241 to the latest version

Thanks Mike.

The upgrade appears to have been successful on the server.  However, if we try to login on a workstation or via our Citrix virtual server we get the following error message:

'An unhandled error has occurred in the application. This error message has been copied to the clipboard and also will be saved to the following file location after this dialog is closed: ..........
If you browse the folders in Windows Explorer, then because you are running Windows XP you will see this folder displayed as:.......


The following error message was poduced when logging in on a workstation:

'date/time         : 2014-04-24, 11:54:12, 945ms
computer name     : NTS005964
user name         : owilson <admin>
registered owner  : Temp / NTS
operating system  : Windows XP Service Pack 3 build 2600
system language   : English
system up time    : 3 days 3 hours
program up time   : 774 milliseconds
processors        : 2x Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
physical memory   : 1465/3567 MB (free/total)
free disk space   : (C:) 82.05 GB
display mode      : 1680x1050, 32 bit
process id        : $130c
allocated memory  : 14.54 MB
command line      : RecorderApp.exe /2688496
executable        : RecorderApp.exe
exec. date/time   : 2014-03-24 11:48
version           : 6.22.2.274
compiled with     : Delphi 7
madExcept version : 3.0n
callstack crc     : $18fd5c47, $6706329b, $6706329b
exception number  : 1
exception class   : EApplicationSettingsError
exception message : The Object Sheet File Path setting is missing or incorrect. Recorder is not installed properly and cannot start.

main thread ($a5c):
00a7df45 RecorderApp.exe ApplicationSettings 3889  +25 TApplicationSettings.FindRegPath
00a72e3a RecorderApp.exe ApplicationSettings 1000 +122 TApplicationSettings.ReadRegistrySettings
00a71cfa RecorderApp.exe ApplicationSettings  748  +16 TApplicationSettings.Create
00a955b4 RecorderApp.exe RecorderApp          360  +25 initialization

thread $454:
7c90df48 ntdll.dll                 NtWaitForMultipleObjects
7c80958a kernel32.dll              WaitForMultipleObjectsEx
7e4195f3 user32.dll                MsgWaitForMultipleObjectsEx
7e4196a3 user32.dll                MsgWaitForMultipleObjects
00476bed RecorderApp.exe madExcept CallThreadProcSafe
00476c57 RecorderApp.exe madExcept ThreadExceptFrame
>> created by main thread ($a5c) at:
4ec67f66 gdiplus.dll

thread $c2c:
7c90daa8 ntdll.dll                 NtReplyWaitReceivePortEx
00476bed RecorderApp.exe madExcept CallThreadProcSafe
00476c57 RecorderApp.exe madExcept ThreadExceptFrame
>> created by main thread ($a5c) at:
77e7d105 RPCRT4.dll

thread $9e0:
7c90d218 ntdll.dll                 NtDelayExecution
7c8023eb kernel32.dll              SleepEx
7c802450 kernel32.dll              Sleep
00476bed RecorderApp.exe madExcept CallThreadProcSafe
00476c57 RecorderApp.exe madExcept ThreadExceptFrame
>> created by main thread ($a5c) at:
77530a23 ole32.dll

modules:
00350000 C4DLL.DLL       1.0.0.1          \\ntssvr01\Recorder 6 Server
003c0000 MS5User.Dll     5.0.0.4          \\ntssvr01\Recorder 6 Server
00400000 RecorderApp.exe 6.22.2.274       \\ntssvr01\Recorder 6 Server
014f0000 ms5cnv.dll      5.0.0.10         \\ntssvr01\Recorder 6 Server
01c80000 odbcint.dll     3.525.1132.0     C:\WINDOWS\system32
03d90000 xpsp2res.dll    5.1.2600.5512    C:\WINDOWS\system32
10000000 MS5.Dll         5.0.0.12         \\ntssvr01\Recorder 6 Server
20000000 xpsp3res.dll    5.1.2600.5512    C:\WINDOWS\system32
4ec50000 gdiplus.dll     5.2.6002.23084   C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.23084_x-ww_f3f35550
5ad70000 uxtheme.dll     6.0.2900.5512    C:\WINDOWS\system32
5d090000 comctl32.dll    5.82.2900.6028   C:\WINDOWS\system32
5edd0000 olepro32.dll    5.1.2600.5512    C:\WINDOWS\system32
6fa00000 SOPHOS~1.DLL    10.0.9.7004      C:\PROGRA~1\Sophos\SOPHOS~1
71aa0000 WS2HELP.dll     5.1.2600.5512    C:\WINDOWS\system32
71ab0000 WS2_32.dll      5.1.2600.5512    C:\WINDOWS\system32
71ad0000 wsock32.dll     5.1.2600.5512    C:\WINDOWS\system32
71b20000 mpr.dll         5.1.2600.5512    C:\WINDOWS\system32
73000000 winspool.drv    5.1.2600.5512    C:\WINDOWS\system32
74320000 odbc32.dll      3.525.3012.0     C:\WINDOWS\system32
74720000 MSCTF.dll       5.1.2600.5512    C:\WINDOWS\system32
755c0000 msctfime.ime    5.1.2600.5512    C:\WINDOWS\system32
76390000 IMM32.DLL       5.1.2600.5512    C:\WINDOWS\system32
763b0000 comdlg32.dll    6.0.2900.5512    C:\WINDOWS\system32
76780000 SHFolder.dll    6.0.2900.5512    C:\WINDOWS\system32
76b40000 winmm.dll       5.1.2600.6160    C:\WINDOWS\system32
76bf0000 PSAPI.DLL       5.1.2600.5512    C:\WINDOWS\system32
76fd0000 CLBCATQ.DLL     2001.12.4414.700 C:\WINDOWS\system32
77050000 COMRes.dll      2001.12.4414.700 C:\WINDOWS\system32
77120000 oleaut32.dll    5.1.2600.6341    C:\WINDOWS\system32
773d0000 comctl32.dll    6.0.2900.6028    C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202
774e0000 ole32.dll       5.1.2600.6435    C:\WINDOWS\system32
77b40000 apphelp.dll     5.1.2600.5512    C:\WINDOWS\system32
77c00000 version.dll     5.1.2600.5512    C:\WINDOWS\system32
77c10000 msvcrt.dll      7.0.2600.5512    C:\WINDOWS\system32
77dd0000 advapi32.dll    5.1.2600.5755    C:\WINDOWS\system32
77e70000 RPCRT4.dll      5.1.2600.6399    C:\WINDOWS\system32
77f10000 GDI32.dll       5.1.2600.5698    C:\WINDOWS\system32
77f60000 SHLWAPI.dll     6.0.2900.5912    C:\WINDOWS\system32
77fe0000 Secur32.dll     5.1.2600.5834    C:\WINDOWS\system32
7c800000 kernel32.dll    5.1.2600.6293    C:\WINDOWS\system32
7c900000 ntdll.dll       5.1.2600.6055    C:\WINDOWS\system32
7c9c0000 shell32.dll     6.0.2900.6242    C:\WINDOWS\system32
7e410000 user32.dll      5.1.2600.5512    C:\WINDOWS\system32
7e4b0000 HHCtrl.ocx      5.2.3790.4110    C:\WINDOWS\system32
7e720000 SXS.DLL         5.1.2600.5512    C:\WINDOWS\system32

processes:
0000 Idle                     0   0
0004 System                   0   0   normal
0280 smss.exe                 0   0   normal C:\WINDOWS\system32
02b8 csrss.exe                0   0
02d0 winlogon.exe             56  17  high   C:\WINDOWS\system32
02fc services.exe             4   3   normal C:\WINDOWS\system32
0308 lsass.exe                7   6   normal C:\WINDOWS\system32
03dc svchost.exe              4   1   normal C:\WINDOWS\system32
0438 svchost.exe              0   0
0498 svchost.exe              11  42  normal C:\WINDOWS\System32
04ec SavService.exe           0   0
0510 svchost.exe              4   1   normal C:\WINDOWS\system32
051c DisplayLinkManager.exe   4   18  normal C:\Program Files\DisplayLink Core Software
0588 DisplayLinkUserAgent.exe 21  6   high   C:\Program Files\DisplayLink Core Software
071c svchost.exe              0   0
0758 svchost.exe              0   0'

Can you help?

Many thanks,
Christine

9

Re: Upgrade from Version 6.16.2.241 to the latest version

the object sheet file path setting is in the registry at  HKEY_CURRENT_USER\Software\Dorset Software\Recorder 6\Settings\

Check this and any other path settings in there are correct (if you miss any you might get a similar error for those too). You may need to do this for all users on all workstations. Not sure how it comes about, but we had it quite often after new workstation installs on XP.

Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre

10

Re: Upgrade from Version 6.16.2.241 to the latest version

Thanks Rob,
I'm not sure what you mean by 'check this and any other path settings in there are correct'.  Could you provide step-by-step instructions on which paths need to be checked within the registry and how they should be amended?  I am a complete beginner at this kind of thing!

Many thanks,
Christine

11

Re: Upgrade from Version 6.16.2.241 to the latest version

Sorry, I will try to be clearer, but can't be specific as the correct entries will depend on your system.

If you navigate to the settings folder on the registry of a workstation with the problem. Find the object sheet path setting & right-click to modify it. The setting must contain the path to a folder which exists (obviously it doesn't at present). On our system the object sheet folder is a subfolder of the main Recorder 6 folder on the server.

Within the settings in the registry are several other settings which are paths to folders. Clearly these should also point to folders which exist (and in most cases to which the user has write permission), some will be within the Recorder 6 folder on the server, some will be on the C: drive of the workstation. Under XP for some reason Recorder seems to misallocate some of these, either inserting paths which do not exist, or placing them within other folders which are protected. With folders on the local C: drive, you should be able to just create a folder where R6 expects to find one in most cases.

Sorry I can't be more specific. If you are not sure, just correct the object sheet path, then restart recorder & see if you get another similar error & correct that one.

Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre

12

Re: Upgrade from Version 6.16.2.241 to the latest version

Hi Christine,

I use a tool that might help you with this. For any new users set up on our virtual server (terminal services) the Recorder startup fails. We have to run Recorder System Check, which I think checks and corrects registry paths. It must have come from somewhere on the forum, or from Mike Weideli

Gordon Barker
Biological Survey Data Manager
National Trust

13

Re: Upgrade from Version 6.16.2.241 to the latest version

Correction: it was John van Breda that sent it to me off forum. Probably best to contact him to see if it might fix your problem

Gordon Barker
Biological Survey Data Manager
National Trust

14

Re: Upgrade from Version 6.16.2.241 to the latest version

I suspect this is just the object sheet folder. It should point to a valid file path on the server.  You should be able to find it on the server, along with all the other folders  and see if the registry is pointing to the correct place. The system check file is attached.

Post's attachments

RecorderSystemCheck(2).zip 221.2 kb, 9 downloads since 2014-04-30 

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

15

Re: Upgrade from Version 6.16.2.241 to the latest version

Hello all,

We seem to have resolved the problem by re-installing each workstation before changing the file path for the 'object sheet' in the workstation registry. 

Thank you for all your help!

Kind regards,
Christine