[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1025
  • Last Modified:

SharePoint 2010 - MAManager.Initialize() error when doing full sync for user profile service

I have an issue doing a full import from Active Directory into SharePoint 2010 using the user profile syncronization application.

All of my services have started correctly, and when I do a full import it appears to have worked - however no user accounts have actually been imported.  When I have a look at it in the synchronization services manager I get the following error:

System.NotSupportedException: Specified method is not supported.
   at Microsoft.Office.Server.UserProfiles.MetaverseExtension.MAManager.Initialize()
   at Microsoft.Office.Server.UserProfiles.MetaverseExtension.MAManager.GetMAManager()
   at Microsoft.Office.Server.UserProfiles.MetaverseExtension.MVExtensionObject.Microsoft.MetadirectoryServices.IMVSynchronization.Provision(MVEntry mventry)

Any ideas?

thanks.
0
Scott_Gardner
Asked:
Scott_Gardner
  • 5
  • 3
1 Solution
 
Justin SmithSr. System EngineerCommented:
is everyting pretty much out of the box with the import?  are you just syncing your local domain?  what shows up in the ULS logs when you kick it off?  Is this RTM version of 2010?
0
 
Scott_GardnerAuthor Commented:
It is a standalone installation running on its on domain controller, (this is in a test environment). The syncronization is using the default settings when creating the connection. Crednetials are fine as I can see the AD tree in the config. There are no errors being displayed  in the windows event log only a warning for the FIMSyncronizationService:

The management agent "MOSSAD-SHAREPOINT.com AD" step execution completed on run profile "DS_FULLSYNC" with errors.
Additional Information
 Discovery Errors       : "0"
 Synchronization Errors : "7"
 Metaverse Retry Errors : "0"
 Export Errors          : "0"
 Warnings               : "0"
 
 User Action
 View the management agent run history for details.

In the FIM Management client it justs states the previous "Specified method is not supported." error against the 7 users it had found from AD.

The profile count in SharePoint is also not changing so it doesn;t look like it is a synchronisation error for just a specific field.

Thanks,


0
 
Justin SmithSr. System EngineerCommented:
what account are the two forefront services running as?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Justin SmithSr. System EngineerCommented:
Also, if this isnt' the RTM version, you probably had a BASIC install by default.  User Profile imports only work if it's a farm install.
0
 
Scott_GardnerAuthor Commented:
The two forefrontservices are running as user call spups (Ihave granted rights to create child objects on the domain and replicate changes within the directory.

Sorry with regards to the install type it is installed as a farm however the SQL Servers and all services run on the one box.This isn't an RTM version.

Thanks again
0
 
Justin SmithSr. System EngineerCommented:
If you install the beta on a Domain Controler, you don't have the option to do a farm install.  It will be basic by default.  Also, the Forefront services should start as the farm admin (db access acct).

I'm conviced your issue is the install.
0
 
Scott_GardnerAuthor Commented:
Highlighted the source of my problem. Will have to revisit the install.
0
 
Justin SmithSr. System EngineerCommented:
why the "B" grade?
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now