|
The technical forum of the NBN Trust for use by the Network. It includes discussions and announcements on the NBN Atlas, Recorder 6 and Indicia |
You are not logged in. Please login or register.
Forum → Recorder Troubleshooting and Bug Reports → Installing network version of R6 on standalone PC
I am emailing on behalf of a user who is trying to install a network version of R6 on a standalone PC running SQL Server 2005. Problems are being experienced during stage 3 of the installation when trying to install the Recorder 6 server. I can find out exactly what - but could it be due to a compatibility issue between R6 and SQL 2005?
Why is your user trying to install a network version on a standalone PC?
I don't know, but it seems to me that this may be the cause of the problem. The last time I did the network install, I seem to recall the software telling me that it should only be used for a network installation and that if you need the standalone install, you should get a standalone copy.
I haven't come across any compatibility problems between R6 and SQL2005
Hi Rob
I think you can use the network version for both network and standalone PCs - certainly we have before. Thanks anyway for your reply - good to know that you haven't come across any compatibility issues with SQL 2005.
Francesca
Hi Francesca
You are right, you can indeed use the network installation CD to install on a standalone PC - you just have to install both the server and workstation components. This approach is a bit more complex but the benefit is that it is more flexible as well. There should not be any compatibility issues with SQL 2005 now in Recorder 6, though you don't mention which version you are trying to install and some old versions will indeed have issues.
It would be helpful to know the exact message they are getting if you need a bit more help with this.
Best wishes
It is a network version of 6.10.4.
The error message is appearing on stage 3 - 'Recorder 6 Server installation'. The installation folder is selected, the database server selected, the server login options given, and then on the 'Installing Recorder 6' screen, this error message appears:
Failed to connect to Server '(server name given)'
OLE error 80044814
Please ensure that you have selected the correct MSDE/SQL instance.
The PC is already running SQL 2005 so MSDE was not installed, and the NBN database installation was successful. The installation procedure has been repeated several times and this message always appears.
Thank you, Francesca
Hi Francesca
Have they double checked the server login details they give? There are 2 methods for logging in, as the SQL Server already existed it may be that you have to use the second method (trusted authentication, rather than supplying a username and password).
Regards
Hi John
Thank you very much for your replies.
The second method was tried originally and failed, but has been tried again, and appears to have worked, as the installation proceeded onto the next step. The workstation was then installed as in stage 4 of the instructions, and the PC restarted.
However - on clicking on the Recorder icon on the desktop, the following error message appears:
An error occurred whilst starting the application.
EOleException: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
SQL Server is installed on the PC and is used with other applications. Don't suppose you have any ideas?
Thank you again,
Francesca
Ok, that message just means that Recorder could not connect to the server, either because it is missing, or the login did not work. Can you check the following value in your registry (best to ask someone for a hand if you are not used to using the registry as you don't want to accidentally change something!):
HKEY_LOCAL_MACHINE\SOFTWARE\Dorset Software\Recorder 6\Trusted Security. It should be set to 0x00000001 (1). While you are there, check the value under Server Name to check it points to the instance of SQL Server on the machine.
What operating system are they using by the way?
Hi John
The setting is correct and it points to the right instance. The operating system is XP.
Thanks anyway if you have run out of ideas!
Francesca
Hi Francesca. Not quite yet! First, when you try to connect to Recorder, are you using a login that has local machine administrator rights? If not, then your user will only be able to access the SQL Server database if they have explicitly been granted access to it. The other option is to re-enable the NBNData login by changing the Trusted Security registry setting mentioned earlier to zero. This approach might need a change to your SQL Server's settings so let me know if it does not work and I will sort out some instructions.
Forum → Recorder Troubleshooting and Bug Reports → Installing network version of R6 on standalone PC
Powered by PunBB 1.4.6, supported by Informer Technologies, Inc.