Last post Jul 09, 2009 03:15 PM by DmitriG
Jun 19, 2009 10:37 PM|beyondit|LINK
When executing the CreateMailbox.xml script, I am receiving the error "E_BLOCKMODEL_NO_RANKED_RESOURCES_FOUND." Also, I have paste the exact error from the command
line below. I read that there is a bug in HMC 4.5, whereby dynamicQuota may cause this error at http://forums.asp.net/t/1428786.aspx and the organization affected dynamic quota is set to true
(<dynamicQuota>1</dynamicQuota>). Therefore, my intuition tells me the organization is lacking some resource, however, I am unable to pin point it and asking for your assistance.
<errorSource namespace="Exchange 2007 Resource Manager"
<errorSource namespace="Hosted Email 2007"
<errorSource namespace="Hosted Email 2007"
Hosted Email 2007
HMC 4.5 mps SoapException Password CreateUserRequestData CreateUserRequest
Jun 22, 2009 10:11 AM|kiphup|LINK
You should deploy HMC RU3. That HMC 4.5 bug you are referring to is in RU2.
Jun 22, 2009 10:17 AM|beyondit|LINK
Do you know where I might be able to download HMC 4.5 Update 3? Unfortunately, we don't have a premiere support contract :(
Jun 22, 2009 12:21 PM|PowerK6|LINK
Seems this issue was already fixed in RU2?
This update rollup fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
The CreateMailbox procedure in the Hosted Email 2007 Namespace fails with an error message that resembles the following:E_BLOCKMODEL_NO_RANKED_RESOURCES_FOUND
Jun 23, 2009 01:40 AM|beyondit|LINK
Might you have any input as to how I can trace why it is giving this error? Any thoughts are appreciated.
Jun 24, 2009 11:27 AM|PowerK6|LINK
According to this post, seems the real reason is lack of OAB server.
And please also check your organization/plan resource allocation. Better you can post your TraceView result.
Oh, one more thing, make sure you follow RU2 steps correctly, or it's not a truely rollup update.
Jul 02, 2009 10:54 AM|PowerK6|LINK
Make sure you have run follow steps:
Note: In addition to the steps for deploying this in the article, you may also want to run the following as well which was left out.
Initialize the Namespaces that you re-installed, initialize the following,
Hosted Active Directory
Initialize Hosted Active Directory
Hosted Exchange - Exchange Provisioning Configuration
Initialize Exchange 2007 OAB Resource Manager
Initialize Hosted Email 2007
Initialize Hosted Unified MEssaging 2007
Initialize Managed EMail 2007
16. On the MPSSQL server or servers, run the KB959196.msi file to install the MPS Resource manager Database Function Update tool.
Jul 03, 2009 02:54 AM|beyondit|LINK
I have tried all as you have mentioned above, however, I am still getting the same error. On another note, recently we upgraded our entire Exchange Enviornment to Windows Server 2008 whereby we added all new servers and incremented the hostname (e.g. exmbxclus01
to exmbxclus02), and removed the old exchange servers from from the enviornment. The reason I stated this is when I was running the traceview, I saw commands with the old exmbxclus01 hostname being used.
When we added all the new servers, I ran the appropiate scripts (e.g. AddOABServer.XML) to get them added. Also, I was able to move the Organization's OAB server to the new server using deallocating, then reallocating the OAB server, however, I was unsure
how to do this for the Mailbox server. One thing to note is we were recieving the error in question prior to this upgrade, however, I wanted to mention this as when I executed initialized the namespaces above, it may have fixed the problem and now we have
a new problem.
When I ran traceview, it timesout, therefore, I was unable to provide the trace. Can you let me know what I need to do in order to remove exmbxclus01 from the resources? I tried and althought it executed successfully, it is still showing both exmbxclus01
and exmbxoab01 as the organization's assigned resources (even though I successfully change the Organization's OAB server using the Exchange 2007 OAB Resource Manager scripts).
Also, I found that the database is still showing resources being used on exmbxclus01 despite we moved the mailboxes to the new mailbox server.
Jul 03, 2009 10:24 AM|DmitriG|LINK
Looks like you screwed ResourceManager DB. You didn't update DB with new mailbox locations. Plus, you removed old Exchange servers from environment, but records about them still in RM DB. These record tight to Exchange server/database objects in AD. If RM
can't map DB record to objects in AD it can't work.
You have to repair/rebuild RM DB. Prepare you credit card and call MS PSS.
Jul 04, 2009 12:04 AM|beyondit|LINK
I tested with creating a new organization, and was able to subscribe to all services, as well as create email accounts, OCS users, sharepoint sites etc. without any problem. All new organizations are using the new resources we added without any error.
The problem I am having only affects 1 organization, which is the firstOrganization we created.
Somewhere in the ResourceManager DB or AD it is mapping the firstOrganization to exmbxclus01, however, if I can change this, it would be sufficient. As for the old servers remaining, I was able to remove the old OAB server from the firstOrganization, and
assign firstOrganiztion to it the new OAB server.
I've been up and down the Resource Manager Database, it doesn't seem to complicated, but I have yet to find any document how it maps organization's to the mailbox cluster server. Is that done in the Resource Manager database or in AD?
Also, I fogot to mention that the hotfix you recommended to run on the mpssql server was not included in Rollup 2, however, Rollup 3. Where might i got about obtaining that from? I always see people asking, and the only reply I've seen so far is that you
have to have Premier support to get it. Is Rollup 3 available online?
Lastly, as for prepare the credit card for Microsoft, I called in hope to get support and all I got was a quote for $56,000.00 USD for 1 year of Premier support which was not affordable to us at the moment. Is there another pay-by-hour or pay-by-incident
you are aware of?
Jul 09, 2009 03:15 PM|DmitriG|LINK
Since it is only one org it is lot easier ;-)
Use procedures Exchange 2007 Resource Manager::DeallocateMailbox, DeallocatePublicFolder, and DeallocateOrganization to deallocate your organization's resources from old server. Than use AllocateOrganization, AllocatePublicFolder, and AllocateMailbox in
explicit mode (specifying mailbox database and server names) to allocate resources on new server back to organization.
To check what is owned by organization now, you can use next procedures from the same namespace "Exchange 2007 Resource Manager":