Adding Second SCOM Management Server

I am trying to add a second SCOM Management server, but I keep getting the error shown in the screenshot.
I have reinstalled the server , rebooted the server, but still keep getting the same error.

Any help will be very much appreciated.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
What is the OS? What version of SQL? Does the first management server communicate properly?
jskfanAuthor Commented:
OS I am adding the second Management Server is Windows 2012 R2
SQL 2012 is installed  on the First Management Server
Yes , it communicates properly with the first Management Server, as you can see on the screenshot , the drop down box shows the operationsManager Database from the  first Management Server (SQL server).
Cliff GaliherCommented:
The database is on the first management server??? Umm... okay. Double check required permissions for starters. The account installing the additional server needs to be a DBAdmin, and if SQL was installed on the some server as the first management server, it may be a local service account this breaking remote servers. It could also be a firewall issue, as there are several ports required (the database name showing up isn't sufficient to guarantee good communications.)  If the SQL server were savage, you'd have nailed down potential firewall issues with the first install. But with them colocated, the firewall would not have interrupted the first setup.

There are many reasons not to colocate those two particular roles, and even the most basic test lab documentation has them separated (for good reason!) You've probably made life very difficult for yourself for awhile.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

jskfanAuthor Commented:
The same account I used to install the first MS , I am using with second MS.
As long as the Database name showed up in the drop down box, means permissions are OK...

I will try it again, and post the event logs
Cliff GaliherCommented:
"As long as the Database name showed up in the drop down box, means permissions are OK"

That is absolutely NOT true. The permissions to query an instance for its list of databases are not the same as for writing to a database itself. They can (and often are) different.
jskfanAuthor Commented:
after the failure, I can see Event 1026 and 1000
Application: SetupChainerUI.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
   at Microsoft.SystemCenter.Essentials.SetupFramework.DBPageOperationalDB.SetDatabaseScenario(System.String ByRef)
   at Microsoft.SystemCenter.Essentials.SetupFramework.DatabaseConfigurationPage.OnNextFinalValidationsDoWork(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
Event 1000
Faulting application name: SetupChainerUI.exe, version: 7.1.10226.0, time stamp: 0x522a5b85
Faulting module name: unknown, version:, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff942b50bc3
Faulting process id: 0x1e8
Faulting application start time: 0x01cfbf3fc98dae18
Faulting application path: C:\Users\administrator.TEST\AppData\Local\SCOM\Setup\SetupChainerUI.exe
Faulting module path: unknown
Report Id: 2313e53b-2b33-11e4-80ba-000c29069184
Faulting package full name:
Faulting package-relative application ID:
Cliff GaliherCommented:
Odd that there are references to System Center Essentials in there. You are running setup from the right media? And thus server hasn't had other system center products installed on it before?
jskfanAuthor Commented:
I installed windows server 2012 R2, there is no other application installed on it.
I have an extracted SCOM iso in another computer, copied the extracted files to flash drive and plugged the flush drive to this server..
Cliff GaliherCommented:
Well, beyond what I've already suggested, I have no other ideas.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jskfanAuthor Commented:
What is you suggestion ? I know you mentioned permissions, but as I said I am using the same account as the one I have installed and configured the first Management Server.

in the log file I have posted above I see something about .Net Framework...Cannot tell why
jskfanAuthor Commented:
The problem was that in the first Management Server, I have installed SCOM,SCCM,SQL2012 all in one server...I removed SCCM and re-installed clean SQL2012. Now I can add the second Management server with no issue.

Thank you for contribution!!!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.