- UNIFYNow Forum
-
Questions
0
Answered
EB FIM agent failing with "Invalid namespace"
A fresh installation of EB 3.0.0. SQL is local with only the Default instance. The customer has installed EB using the FIM Sync service account which is a local administrator and a member of the FIMSyncAdmins group. We also have the same config in Dev which worked fine.
The FIM Agent fails with "Invalid namespace". I search jira for this message but couldn't find anything. Do you know what it means?
Note: customer wants to test update to 3.2.0 on this server which is why we've installed an older version.
Customer support service by UserEcho
Hey Carol,
I don't believe this is an Event Broker specific error - this is likely an error when attempting to connect to the FIM WMI interface. Ensure Event Broker is configured correctly to the FIM instance, ensuring "Local" is selected if EB is installed on the same machine. Otherwise, see http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/a3c552e3-ca18-4f8f-b399-86f07240b5ed for potential WMI issues.
Matt
Please note the change in issue type.
Yes somehow the MIIS WMI namespace was missing from the FIM server. The thread you posted contained several possible answers - it was the last one that helped me.
1.Click Start, select All Programs, select Accessories, right-click Command Prompt, and then click Run as administrator. This will bring up Administrator: Command Prompt.
2.Type wmimgmt.msc and hit Enter. This will bring up WMI Control.
3.Right-click WMI Control (Local) and then click Properties. This will bring up WMI Control (Local) Properties.
4.Click on the Security tab.
5.Expand the root namespace and verify MicrosoftIdentityIntegrationServer is missing.
6.Close WMI Control (Local) Properties and then close WMI Control (Local).
7.Return to the Administrator: Command Prompt.
8.Navigate to the FIM 2010 Synchronization Service Bin folder.
9.Run the following command: regsvr32 /s mmswmi.dll.
10.Run the following command: mofcomp mmswmi.mof.
11.Run the following command: net stop winmgmt.
12.Run the following command: net start winmgmt.
What step #12 above doesn't say is that the extra services that had to be stopped (dependencies to restart WMI) all need manual restarting (step #13):