SCOM server, shows disabled

I installed SCOM 2012 and run discovery wizard, to discover windows server and deploy agents
All servers were discovered and shows healthy, except for scom management server itself that shows grayed out.

I am not sure why. Though I enabled the proxy agent on it.

Thanks

sc
jskfanAsked:
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.

Abduljalil Abou AlzahabInfrastructure Team Leader – Professional ServicesCommented:
Did you tried to right click on management server and click "Configure Client Monitoring" and follow the wizard ?

Note according to Microsoft TechNet:
The Configure Client Monitoring option will be unavailable if the selected computer is a gateway server.
0
jskfanAuthor Commented:
<<<Did you tried to right click on management server and click "Configure Client Monitoring" and follow the wizard ?>>
I was going to try that, then in the wizard it prompts where to save files, then I thought that might be for different purpose..
0
Abduljalil Abou AlzahabInfrastructure Team Leader – Professional ServicesCommented:
this is How to Configure a Management Server for Client Monitoring, for more information check the below link from TechNet:
http://technet.microsoft.com/en-us/library/hh212833.aspx
0

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
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:
On the Error Collection page, do the following:
Type the local or attached File Share Path, such as C:\ErrorData, for the management server that will be used to collect error reports. The file share will be created at the local path on the management server and shared with the necessary permissions.



So I will just type C:\ErrorData and proceed with the wizard ?
0
Abduljalil Abou AlzahabInfrastructure Team Leader – Professional ServicesCommented:
Create the folder on any drive you want and mention the path in wizard if you don't want to create shared folder.
0
jskfanAuthor Commented:
I did , but the Management Server itself is showing grayed out.
.scom
0
Abduljalil Abou AlzahabInfrastructure Team Leader – Professional ServicesCommented:
0
jskfanAuthor Commented:
Where is the log file for SCOM when things go wrong, ?
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Hi jskfan.

Do you still have this error?
0
jskfanAuthor Commented:
Yes...SCOM Management server (Server4)still showing health state critical as displayed on the screenshot above
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Click on Health State Critical error to see what's complaining about. You may post here the error also, so I can see if can help you.
0
jskfanAuthor Commented:
*** SCOM Management server itself was showing critical, so I had to re-run the install and select repair. This operation helped to get rid of the critical alert of the Mangement server, however the Management server was still showing grayed out, even though it shows Healthy.
The way I fixed it was  going to C:/program files/Microsoft System Center 2012R2 /Operations Manager/Server/ and deleted Health Service State folder, that 's after stopping Microsoft Agent Monitoring service, I restarted the Monitoring Agent

then SCOM Console, and the server showed Green (Healthy)
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Let's see if it can hangs up to 24h healthy.
0
jskfanAuthor Commented:
msmo
0
jskfanAuthor Commented:
As you can see, Server4 which is the Management Server:
in the Administration tab , it shows Grayed out(Healthy)
in the Monitoring tab , It  shows Green(Healthy)

I am not sure why ?

However the other servers it monitors, are showing Healthy and green (did not include a snapshot )
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
The error message would help. Can you post it here?
0
jskfanAuthor Commented:
The event viewer shows  

Description:
Failed to store data in the Data Warehouse. The operation will be retried. Exception 'SqlNullValueException': Data is Null. This method or property cannot be called on Null values.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Check permission on OperationsManager_dw database.

But you also should check the agente heatlh message.
0
jskfanAuthor Commented:
OperationsManager_dw database.

the action account is Sysadmin in SQL permission for OperationsManager_dw database.

for the agent health, I do not see the server4 on the list:
ag
0
jskfanAuthor Commented:
I meant in SQL security login for the Action account, in server roles I gave it Sysadmin

for OperationsManager_dw database, the Action account has permissions to Connect and Update
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
The agent health from Manager Server appears in the Management Group Health.
Double-click on health column and see the error message.
0
jskfanAuthor Commented:
I realized if I restart the Monitoring agent , it will turn Green, but after a while it will go back to Gray
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
jskfan, for I help you I need to know what's the error. Please post here the error message.
0
jskfanAuthor Commented:
It is fixed now...
I had SCOM 2012 and SCCM 2012 and SQL 2012 all installed on one server....

I uninstalled SCCM and SQL then installed back just SQL...
Now the issue is gone........
0
jskfanAuthor Commented:
Sorry was not able to get back with you
Thank you Guys!!

===============
It is fixed
 I had SCOM 2012 and SCCM 2012 and SQL 2012 all installed on one server....

 I uninstalled SCCM and SQL then installed back just SQL...
 Now the issue is gone
0
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
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.