All Management Servers Resource Pool Unavailable Error
I install 2012 and add agents, everything is fine for about 2 weeks, then I get a "All Management Servers Resource Pool Unavailable" error condition and cannot recover from it. I have built 2 totally seperate envinments now and each time they have literally broken without doing anything...we let them sit and monitor without making any changes then we get this error and cannot get around it. One MS as an all in one server. SQL 2008R2 30 agents in our test domain. What is going on here?
January 24th, 2012 3:31pm

Hi Are the management servers actually available? Is it just the alert? If so, then this is a known issue: http://technet.microsoft.com/en-us/library/hh561709.aspx "All Management Servers Resource Pool Unavailable alert remains active The All Management Servers Resource Pool Unavailable alert can remain active after all management servers have recovered from an unavailable state. This can occur when more than one management server in the server pool reports as unavailable within the same second, which generates multiple alerts. When the availability issue is resolved, only one alert is resolved. Workaround: Verify that all management servers have network connectivity, are not in maintenance mode, and that the Health service is generating a heartbeat, and then resolve the alert manually in the Operations console. Do not resolve the alert manually if the majority of management servers are unavailable." Regards Graham New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/ View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2012 1:34am

Thanks GMan. The error instantly comes back and I'm unable to do much with SCOM after that. It seems everything is broken for no real reason. I've spent HOURS trying to resolve. 2 new builds, same results after letting them just "sit" without any further customization. I will NOT install 2012 in production after seeing this happen twice now. I opened a case with MS and they would not help since I was not a beta customer. I do not trust 2012 at all as stable. I'll wait for final RTM I guess. Sad face.
January 26th, 2012 8:07am

Hi This is still the release candidate and it is a known issue so should hopefully be fixed in the RTM. You can still learn the new functionality of SCOM 2012 by using the RC in a test environment. Just disable this alert and there is another powershell alert (monitor) that needs to be disabled as it is alerting falsely. Just so that everyone is aware - SCOM 2012 RC is not upgradable to SCOM 2012 RTM unless you are on an approved Microsoft TAP programme so it shouldn't be deployed to Production environments. SCOM 2012 RC is also 180 time limited so you can't keep using indefinitely. If you are deploying SCOM to production today then it needs to be SCOM 2007 R2. Cheers Graham New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/ View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
January 26th, 2012 8:17am

Yeah, this is in a test domain, my env is too large to play russian roulette with beta bits. I'm reinstalling a third time today. :D
January 26th, 2012 3:00pm

I'd probably suggest not reinstalling. It doesn't sound like you have a problem. What you are seeing is just a known issue (and there are others you'll find!). Use it to play with and to learn the new features such as APM (especially if you haven't used Avicode) and test out the new network monitoring functionality. Depending on your current production environment you might find you'll be on SCOM 2007 R2 for a while. E.g. there is no support for windows 2000 in SCOM 2012 and if you have been using Avicode then be aware that APM only supports IIS 7 and later. Cheers GrahamNew SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/ View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
January 26th, 2012 3:50pm

Regarding the issue, please also post it to Microsoft Connect: Microsoft Connect https://connect.microsoft.com/OpsMgr/Feedback Thanks. Nicholas Li TechNet Community Support
February 1st, 2012 5:34am

This is still a problem in RTM version. Argh.
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2012 1:47pm

We have the same issue SCOM 2012 RTM. any ideas?
May 13th, 2012 5:41pm

It seems to pop up if you reboot your remote SQL box hosting your OM DB. Then a flush of your MS servers HS cache helps to remove it. It seems to be a come and go kind of error that I cannot pinpoint an exact cause/fix for. DB Connectivity is definitely in the mix. Also, MS recomends these 2 Reg Hacks for this issue for 'all in one' boxes: HKLM\SYSTEM\CurrentControlSet\services\HealthService\Parameters\PoolManager /v PoolLeaseRequestPeriodSeconds /t REG_DWORD /d 600 /f reg add HKLM\SYSTEM\CurrentControlSet\services\HealthService\Parameters\PoolManager /v PoolNetworkLatencySeconds /t REG_DWORD /d 120 /f
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2012 7:49pm

This error effectively shuts down all alerting, so when it appears, you will not know nor will your customers know as this can only be seen in the console and it NEVER emailed. So, you have no notification flow and all monitoring stops. This is a serious error that MS has no answer for. Additionally, if you over-ride it, it still comes back and notifications still die.
May 23rd, 2012 12:28pm

Adding myself to this thread in case MS ever answers. I never noticed this happening in my RC environment but it is happening with the "production" build. I have 4 servers in Hyper-V with a remote SQL instance. An answer from Microsoft would be great. This is holding up the roll out.
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2012 9:45am

I cannot deploy 2012 with this bug...If it didn't shut down monitoring and email alerts I could live with it but being that notifications STOP and you are blind to the meltdown this is a huge showstopper. SCOM is 100% broken when this alert happens and you get no Notification of it.
May 29th, 2012 9:52am

In digging a little deeper into the Operations Manager application logs I noticed an error 29181. It points to the DB being full. I believe that Operations Manager sets auto growth to none by default on the db install. At least it did for me. I used SQL Server Management Studio and set the growth on the Operations database to unrestricted. We'll see if that helps. Here is the alert context for your reference. System.Data.SqlClient.SqlException (0x80131904): Sql execution failed. Error 1105, Level 17, State 2, Procedure WorkItemMarkCompleted, Line 68, Message: Could not allocate space for object 'CS.WorkItem'.'PK_WorkItem' in database 'OperationsManager' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader() at System.Data.SqlClient.SqlCommand.EndExecuteNonQuery(IAsyncResult asyncResult) at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.NonQuerySqlCommandOperation.SqlCommandCompleted(IAsyncResult asyncResult)
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2012 10:32am

When I received this error, it was because my MGMT server was in maint mode. I put it in maint mode this morning to do patching on it, and i guess i set the time frame for longer than i thought. Once I took the mgmt server out of maint mode, I got flooded with about 25 alerts at once.
June 7th, 2012 4:06pm

We have had stability for a few days. The server seemed to be eating RAM, it seems there is a known memory leak issue with the SCOM 2012 console which had been left open on the server. I have been using the web console and RAM usage is a lot lower and have had no "All Management Servers Resource Pool Unavailable" for a few days. Fingers crossed.
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2012 4:09pm

We're getting this same problem in RTM. Fine for several weeks then all of a sudden everything is broken. Any ideas??? In addition to this, we're getting flooded with Event ID 20000's.
June 12th, 2012 9:56am

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

Other recent topics Other recent topics