1

Topic: NBNData SQL Server Login failure

I'm hoping this will be a simple one to resolve.

Our ICT have moved R6 onto a new server. If we try and access any of the tables in NBNData we ger a SQL Server Login connection failure message.

This then displays the SQL Server Login dialog which specifies the name of the old server, changing this to the new server fails to connect again, but will connect the second time it is changed.

Any server name changes are subsequently lost and you have to do the whole routine again.

I assume the old server name is being stored in settings somewhere, but we have not been able to find it.

Any help appreciated.

2

Re: NBNData SQL Server Login failure

On our setup the path to the server is set in the registry on the server in:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Dorset Software\Recorder 6 - Server Name

Craig

Craig Slawson
Staffordshire Ecological Record

3

Re: NBNData SQL Server Login failure

Each workstation will also need to be updated to point to the new server (Same path as above on each workstation).

There is also a file called InstallSettings.ini, in the root of the Recorder6 folder on the server, this is used when you do a workstation install, and the server name needs to be edited in there too, so that subsequent workstation setups work correctly.

At least I think that is correct.

Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre

4

Re: NBNData SQL Server Login failure

Thanks.

Our IT guy says the server registry path does not  correspond to any they have.

The workstation registry entry appears to point to the correct server.

5

Re: NBNData SQL Server Login failure

I don't think there is a registry entry on the server, we have never had to change one in the past.

Try doing an uninstall of one of the workstations and reinstalling (after checking the ini file is correct) see if that fixes it

Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre