1 Reply by iain (edited by iain 27-04-2011 09:24:49)

  • iain
  • Veteran
  • Offline
  • Registered: 19-01-2009
  • Posts: 91

Re: Client install on Windows 7 x64

Hi

I've just run WorkstationSetup.exe on a windows 7 x64 client and although everything seemed to install when I attempt to run recorder I just get an unhadled exception coming up. It looks like there's some attempt to access the registry and this is failing (permissions?). The general error message is below.

======================================
date/time         : 2011-04-27, 10:11:40, 735ms
computer name     : NESBREC-WS-021
user name         : iain
operating system  : Windows 7 x64 Service Pack 1 build 7601
system language   : English
system up time    : 3 minutes 16 seconds
program up time   : 624 milliseconds
processors        : 2x Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz
physical memory   : 934/1993 MB (free/total)
free disk space   : (C:) 195.29 GB
display mode      : 1280x1024, 32 bit
process id        : $133c
allocated memory  : 28.68 MB
command line      : RecorderApp.exe /393918
executable        : RecorderApp.exe
exec. date/time   : 2011-01-18 15:50
version           : 6.16.2.241
madExcept version : 2.7k
exception class   : EOleSysError
exception message : Error accessing the OLE registry.
======================================

it then trails off to display some drivel about threads and modules.

Anyone any ideas on how to attack this...? or what's going on?

Cheers

Iain

2 Reply by johnvanbreda

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

Re: Client install on Windows 7 x64

Hi Iain
First thing I would try is browsing to the RecorderApp.exe file (under C:\Program Files (x86)\Recorder 6), then right click and select Run as Administrator. After running this way the first time, if it works then the normal icon should work in future.
Best Wishes

John van Breda
Biodiverse IT

johnvanbreda's Website

3 Reply by iain (edited by iain 10-05-2011 08:19:08)

  • iain
  • Veteran
  • Offline
  • Registered: 19-01-2009
  • Posts: 91

Re: Client install on Windows 7 x64

Thanks for the reply John

Well I can now get to the advanced stage of not being able to connect to the database

This is a network install so the RecorderApp,exe is on a mapped network drive. The hk local machine in the registry isn't populated with a Dorset Software key after installation (ran WorkstationSetup.exe as administrator) so there's something not quite right there and had to copy this from an XP workstation and alter the path to include (x86). After a while of getting nowhere I decided to then copy the HKCU key across as well as the TypeLib registry stuff - all from a working XP machine and still no joy. SQL Management Studio can connect to the database without any problems on both machines. The domain policy has the firewall off on all client machines. The latest diabolical message is

An error occurred...
EOIeException: [DBNETLIB][ConnectionOpen (Connect().]SQL Server does not exist or access denied

Anyone able to shed some light on this please - and suggestions to get this thing working?

Cheers

Iain

Okay, it's now working

4 Reply by johnvanbreda

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

Re: Client install on Windows 7 x64

Hi Iain
Do you know what you did to make it work?

John van Breda
Biodiverse IT

johnvanbreda's Website

5 Reply by iain

  • iain
  • Veteran
  • Offline
  • Registered: 19-01-2009
  • Posts: 91

Re: Client install on Windows 7 x64

Hi John

Yup - it was the Wow6432Node that had me fooled - this is where a 32bit application writes to in the registry.

Cheers

Iain

6 Reply by TonyP

  • TonyP
  • TonyP
  • Veteran
  • Offline
  • From: Somerset
  • Registered: 15-05-2006
  • Posts: 306

Re: Client install on Windows 7 x64

Most helpful Iain, as I was just installing R6 on a new W7 x64 machine.

Iain referers to the WoW64 node which is found in the registry at this location;

HKEY_LOCAL_MACHINE\Software\Wow6432Node

This is where the Dorset Software entries will/should be on 64 bit machines at present because it is a 32 bit program.

[See http://en.wikipedia.org/wiki/WoW64 for an explanation]

In my case it had loaded the wrong name for the SQL server choosing to use a name of a previous installation not used for a couple of years. A quick edit and all seems fine so far.

Tony

Data Manger
Somerset Environmental Records Centre

TonyP's Website