Hi Rudragouda Masaraddi, In addition to what Deborah wrote, please check also did this blog entry by Kevin Holman: Enabling Scheduled Maintenance in SCOM 2016
As per Kevin:
This is caused by the SCOM Data Access account needing some additional permissions in SQL in order to control maintenance schedules via SQL Agent. You will need to configure this just once to get it going.
Please check the solution in the article. There could be also another reason for this, which is depicted here: How to suspend monitoring temporarily by using maintenance mode and here: Creating a maintenance schedule with more than 216 objects causes the Operations Manager console to disconnect
While creating or editing a maintenance schedule, you can't include more than 216 Objects at a time. If the number of objects exceeds 216, the following error message appears: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Stoyan Chalakov