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?

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.

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

This is still a problem in RTM version. Argh.

We have the same issue SCOM 2012 RTM. any ideas?

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.

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.

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)

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.

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.

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.

Hey everybody ! I have the same problem and i just resolve it by re-enter the credential of the scom manager and administrator in the Run As Accounts Settings. Tell me if for you it's ok ! Regards !

Hi, I have this problem too, i need to reboot the SCOM server and this resolve the issue. However after a few days the problem would come back again, is there a permanent solution to this problem? Thank Li Liang

Hi, I got the same problem too several days ago. Running SCOM 2012 RTM for over 2 months now. First I checked if the SCOM database is configured with no "AutoGrowth" feature, and indeed this is the case, so I thought if I enable AutoGrowth then issue may be fixed. Especially when I checked the size of SCOM database - it was exactly 20GB and 10GB for transaction log. But then I said: wait a second, I probably don't have so many servers to fill up 20GB of data. So generated report for disk space usage (in SQL 2008 R2 it is easy task) and I saw that only 10-15 is used inside this 20GB file, the rest was empty. So basically SCOM pre-allocated 20GB and disabled auto-growth but still there is a plenty unused space. Then I tried solution with 2 registry keys. Instead of restarting service for me it was easier to reboot the whole server. And guess what? Problem disappeared. So for me the registry solution definitely worked. Make sure that you populate registry keys properly, in some documents there may be mistakes. Here is the right configuration for those keys: Interesting enough that Microsoft created KB article for this issue but it is no longer available, even if I login with Premier account. But if you search for it using Google you can preview it - quality is not that good, but still there is a proof that this article existed. Not clear why Microsoft removed it. They are doing funky things lately :-) You can see that the solution from this article is to add 2 registry keys, so this solution worked for me, and I hope will work for other people. Just don't forget to restart SCOM server and allow few minutes to settle down. I think I did receive few alerts after reboot, but after several minutes they all disappeared and never came back. By the way, when this issue existed, I noticed significant increase of false alerts for network devices like Printers and Switches that were reported as Not Responding for SNMP Ping, and now I don't get these alerts any more. What is interesting it was many devices all together and then after few minutes they were disappearing. Now I know they were false alerts and this is all because of the bug in SCOM 2012. Well, I still love SCOM 2012. It is much better!!! Good luck!