1

Topic: Moving Recorder 6 to a new server - access issues

I expect this has been covered before, but yet again we are stymied by trying to move Recorder 6.

A replacement C: drive with the exact same version of SQL Server 2012 has an attached copy of the NBNdata database, with the same users added and the same server install. All pathways are the same. However, we can't get into R6; after sorting out the Object Sheet File Path error, we now have "Login failed for NBNUser". Forcing SQL server manager to change the login password to NBNPassword (in case it had been changed before) hasn't made any difference. Does anyone have experience of how to fix this?

ta

Linda

2

Re: Moving Recorder 6 to a new server - access issues

Try running the following SQL against the NBNUser database
EXEC sp_change_users_login 'Update_One', 'NBNUser', 'NBNUser

Mike Weideli

3

Re: Moving Recorder 6 to a new server - access issues

Thanks for the quick reply Mike; no, this doesn't appear to have fixed the problem, the message is still the same.

I'm sure it's something minor but the usual "hacks for getting R6 to work" aren't applicable; it's obviously something which has been lost or re-set by our IT contractors following the replacement of the disk.

Incidentally, we had R6 server files installed on a data drive, the workstation on the C: drive of the main office server machine, and various other workstations elsewhere (which haven't been changed). They installed the server files onto the C: drive, possibly not realizing that this was a duplication of the ones used before, which were actually running from a different drive. So the registry is likely to be confused (although I have to say it looks like it should do). Foxed here.

NB I'm assuming that the NBNUser password was NBNPassword; I suppose it might have been something else.

Linda

4

Re: Moving Recorder 6 to a new server - access issues

What about this thread: http://forums.nbn.org.uk/viewtopic.php?id=5632 ?

Charlie Barnes
Information Officer
Greater Lincolnshire Nature Partnership

5

Re: Moving Recorder 6 to a new server - access issues

Thanks Charlie,
No, that was what I tried first; it just gave the message "no. of orphaned users fixed: 0" etc. Sure it will only be something similar to that, though; just can't find a solution. Our IT contractors are sysadmin only and don't really have any answers. V frustrating!

6

Re: Moving Recorder 6 to a new server - access issues

Still think it is something to do with access to the database, not registry. Run the full NBNUser SQL - see below. If NBN Users is already set up in NBN5data/Security/Users and or in Security/Logins and they are incorrect you may need to delete these first. Was it a new install of Sql server and did  you actually reinstall R6 or just attach the database.

IF NOT EXISTS(SELECT * FROM Master.dbo.SysLogins WHERE Name='NBNUser')
          CREATE LOGIN NBNUser WITH PASSWORD='NBNPassword', CHECK_POLICY=OFF

EXEC sp_addsrvrolemember 'NBNUser', 'dbCreator'

EXEC sp_addsrvrolemember 'NBNUser', 'diskAdmin'

USE NBNData

IF NOT EXISTS(SELECT * FROM SysUsers WHERE Name='NBNUser')
    CREATE USER [NBNUser] FOR LOGIN [NBNUser] WITH DEFAULT_SCHEMA=[NBNUser]
GO

EXEC sp_addrolemember 'db_backupoperator', 'NBNUser'
EXEC sp_addrolemember 'db_datareader', 'NBNUser'
EXEC sp_addrolemember 'db_datawriter', 'NBNUser'
EXEC sp_addrolemember 'db_ddladmin', 'NBNUser'
EXEC sp_addrolemember 'db_owner', 'NBNUser'

EXEC sp_change_users_login 'Update_One', 'NBNUser', 'NBNUser

Mike Weideli