OpsMgr account permissions with SQL 2012 alwayson

Hello opsmgr gurus,

I'm installing opsmgr in a lab using a single server deployment and 2 SQL servers with an alwayson availability group configured. From what i understand, the OpsMgr accounts are given certain permissions in SQL only on the first node after the OpsMgr installation and they are not replicated to the replica servers so you would have to manually add those permissions.

Following this technet article https://technet.microsoft.com/en-us/library/jj899851.aspx, I attempted to do just that, only to get the following error in SQL:

Failed to update database "OperationsManager" because the database is read-only. (Microsoft SQL Server, Error: 3906)

My SQL availability group has an option for a readable secondary and it is set to yes. I don't see anything else that removes the read-only setting. Has anyone encountered this? any ideas?

Thanks,

September 13th, 2015 7:00pm

Please refer to Paul Keely SQL 2012 and System Center 2012 R2 which has detail on how to deploy SCOM database on SQL always on.
https://gallery.technet.microsoft.com/SQL-2012-and-System-Center-553b5161
I think that you issue may be come from the SQL always on setup
Roger
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2015 11:36pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics