Last post Mar 08, 2010 04:55 PM by ft_alex
Mar 02, 2010 08:14 PM|ft_alex|LINK
When trying to install all in the Exchange Provisioning Configuration group for HMC 4.5, it fails on Initialize Exchange 2007 OAB Resource Manager. There is nothing in the event log on MPS01, but MPS02 has a 5134 event ID from the Provisioning Engine. The
Resolution of execute statements failed from a procedure=main namespace=request executing procedure=Initialize namespace=Exchange 2007 OAB Resource Manager. Check Event Viewer for additional namespace load errors.
There are no other errors in the event log. Not quite sure what to do. I've rebooted the servers. I have not tried rebooting AD, MPS, and Exchange though. Only MPS.
This is on Procedure W08-DWHE.94: To configure Hosted Exchange Provisioning. Any ideas?
Mar 03, 2010 08:58 AM|ehlo250|LINK
If you're familiar with using TraceView to collect trace information from MPS, then you could get more information about exactly where the error is occurring in the process. Drill down into each nested request until you find the one that returned the error
and also should show what the error is. That information would be very helpful in helping you determine the problem.
Mar 03, 2010 10:15 AM|PowerK6|LINK
Open MPS Deployment Tool.
In the Requirements Status pane, expand Hosted Exchange, and then right-click the
Exchange Provisioning component.
Find Exchange 2007 OAB Resource Manager, and then right click to select Uninstall, then
Go to DWHE.94 again.
Mar 03, 2010 11:33 AM|ft_alex|LINK
Unfortunately, uninstalling and reinstalling the OAB Resource Manager did not clear the error.
In TraceView, I've added all the provisioning servers in options, but when I click Start Tracing then click on Start Deployment in the deployment tool, then go back to TraceView, it says "No stack traces" in the left pane. Is there something I'm missing?
Is there a procedure filter file I should be adding?
Mar 03, 2010 11:58 AM|DmitriG|LINK
TraceView, it says "No stack traces" in the left pane
Sometimes TraceView starts to work only after re-installation.
Also, on Action History tab in Deployment Tool, you can find MPS response for Exchange 2007 OAB Resource Manager::Initialize execution.
Mar 03, 2010 01:45 PM|ft_alex|LINK
Here is the Action Failure Details from the Action History window:
Message: <errorContext description="Resolution of execute statements failed from a procedure=main namespace=request executing procedure=Initialize namespace=Exchange 2007 OAB Resource Manager. Check Event Viewer for additional namespace load errors." code="0xc220140e"
I'm re-installing TraceView now to see if that helps with that issue. Should I try re-installing the deployment tools as well?
Mar 03, 2010 02:36 PM|DmitriG|LINK
Should I try re-installing the deployment tools as well?
Open Provisioning Manager and check that namespace "Exchange 2007 OAB Resource Manager" exists.
Mar 03, 2010 02:58 PM|ft_alex|LINK
Re-installing TraceView didn't change anything as far as its operation.
Provisioning Manager does list OAB Resource Manager.
Mar 03, 2010 05:11 PM|ft_alex|LINK
Would installing 4.5 UR 6 help maybe? Or is that something I don't want to do until everything is successfully deployed in MPS?
All of the Exchange servers in the environment are SP1 UR9 - Would that be causing problems?
Mar 03, 2010 09:49 PM|PowerK6|LINK
On MPS server, check C:\ConfigShare\log\Exchange 2007 OAB Resource Manager_Initialize on Exchange 2007 OAB Resource Manager_Initialize datexxxx.log
Or using Initialize.xml under C:\Program Files\Microsoft Hosting\Provisioning\Samples\Exchange 2007 OAB Resource Manager
provtest Initialize.xml /x2
See what you get.
Mar 03, 2010 11:23 PM|ft_alex|LINK
Same error. In the log and when I run provtest.
Mar 04, 2010 12:25 AM|ft_alex|LINK
Is it possible this is being caused by a corrupt configuration database?
Mar 04, 2010 12:27 AM|PowerK6|LINK
Can you please use the Deployment Tool to verify that the Namespaces you are missing/not installed?
Mar 04, 2010 12:40 AM|ft_alex|LINK
I do not have the following installed:
All under Customer Directory Integration, Data Hosting, Office Communications Server Services Hosting, Sharepoint Server Services Hosting, and Web Hosting.
Mar 04, 2010 01:07 AM|PowerK6|LINK
Deployment Tool->Hosted Exchange->Exchange Provisioning component.
Right click any item, like Exchange 2007 OAB Resource Manager, select Verify all MPF namespaces, start Deployment.
Mar 04, 2010 01:23 AM|ft_alex|LINK
MPF Engine Hotfix says Not assigned. When I try to assign it to any of the servers, the assign button is greyed out. If I try to uninstall it, there are a lot of namespaces it wants to uninstall (all of them, I believe). So I try to uninstall all of them,
but it says that the Registry Provider namespace cannot be uninstalled until the MPF Engine Hotfix is operational.
Mar 04, 2010 07:35 AM|PowerK6|LINK
MPS Engine Hotfix - KB939216, open Add/Remove Programs to check, if installed, you can ignore it.
check your MPSPrivAcct account, make sure it will not expired.
check Exchange 2007 Management Tools installed correctly on your MPS server.
Did you open Automatic Update and keep your server updated?
If you installed KB968930, uninstall it, reboot MPS server and retry. if not work, go to
http://blogs.msdn.com/mkostersitz/default.aspx, check the hotfix list, uninstall hotfixes which not on the list.
Mar 04, 2010 03:33 PM|ft_alex|LINK
KB939216 is installed- I tried forcing a not installed state on the MPF Engine Hotfix, then reinstalling, made not difference.
MPSPrivAcct is set to never expire.
Exchange 2007 Management Tools seems to have installed correctly, it will open up just fine and can see all servers.
I have had Automatic Updates notify of new updates and have kept it up to date. However, I forgot to install Exchange 2007 SP1 UR9 after installing management tools, so I did that, then restarted both MPS01 and MPS02. Still nothing.
I am currently going through the list of hotfixes to see if I have any installed that are not supported.
Thank you for all of the help you have given me so far, it is very appreciated. Hopefully we can figure this one out!
Mar 05, 2010 02:05 AM|ft_alex|LINK
I uninstalled all unsupported hotfixes on all servers. I'm still getting the error. I'm starting to feel like I'm going to have to start over. Is there a way to do that for just the provisioning servers? Or does it do too much to Active Directory to risk
Mar 05, 2010 10:15 AM|DmitriG|LINK
In the Provisioning Manager, when you browse Exchange 2007 OAB Resource Manager namespace, do you see Initialize procedure on the right panel?
Mar 05, 2010 02:28 PM|ft_alex|LINK
I do, yes. I've edited the XML to have the correct FQDN to the primary domain controller as well.
One interesting thing that I've noticed, is that sometimes when trying to initialize, it will fail with the error almost immediately, and other times it will run for about 2-3 minutes before it fails.
Mar 05, 2010 04:01 PM|DmitriG|LINK
other times it will run for about 2-3 minutes before it fails
It happens when Provisioning Engine COM application working process is starting. It takes a time to load all XMLs with namespace definitions and parse them.
Do you see Event ID 5134 (see your initial post) on both servers or only on MPS02?
Mar 05, 2010 04:10 PM|ft_alex|LINK
Thanks for the quick reply. I'm only seeing it on MPS02. But it's not accompanied by any other errors.
Mar 05, 2010 05:03 PM|DmitriG|LINK
Try to shutdown MPS02 and execute procedure again.
Mar 05, 2010 05:32 PM|ft_alex|LINK
With MPS02 turned off, I'm still getting the same failure and NOW I'm getting the 5134 event ID on MPS01.
Mar 06, 2010 03:48 PM|ft_alex|LINK
I think I'm just going to wipe everything and start over. Can I not use the monitoring and reporting for this? This is just a sandbox deployment for developers to work with, so is the monitoring and reporting completely necessary? Also, can I get away with
one MPS server instead of the two?
Mar 06, 2010 09:49 PM|PowerK6|LINK
Monitoring and reporting is not a necessary component, you can skip it. MPS02 is not necessary, either. Even you can consolidate MPS01 and MPSSQL01 into one same box.
Mar 08, 2010 04:55 PM|ft_alex|LINK
Not sure what happened during my first attempt, but I stayed up all weekend starting from scratch, and all of the initializing tasks worked. I'm just going through the Configure Resource Management process now. Everything is looking good. Thank you for all
your help! It's a shame the solution was to start completely over.