locked
User Profile Synchronization error MOSS MA not found

Answers

All replies

  • Hi

    I had this problem and found that the Forefront Identity Management Service was not running I went into Start -> Administrator Tools -> Services and started it and everything worked !

    Regards

    Nigel
    Tuesday, February 23, 2010 11:55 AM
  • The two FIM services should and will start on their own if everything is setup properly - they should not be started manually.

    Umit, you need to tell us what "MOSS MA" is.  That must be something specific to your farm or something you've named?  Let us know what that is.  One tip I can give for configuring the User Profile Sync is to be sure that you're logged in as the service account that will be running that service app.  Also, be sure that service account is a local admin on the box where you're starting the service.
    SharePoint Architect || My Blog
    • Proposed as answer by André Rentes Friday, October 22, 2010 12:28 PM
    Wednesday, February 24, 2010 4:15 AM
  • Hi Clayton

    MOSS MA is setup by the User Profile system - I had the same message.

    This is the corresponding ULS Log Entry :-

    LoadConnections failed trying to fill the connections list. Most likely during RetriveResources because of permissions --- {1}.  Available parameters: System.ServiceModel.EndpointNotFoundException: Could not connect to http://sps2010rc:5725/ResourceManagementService/MEX. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.3.3:5725.  ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.3.3:5725     at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)     at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& sock... affaead0-7be6-4fb3-8df1-b41aa16d0193
    02/23/2010 11:13:44.79* w3wp.exe (0x1634)                        0x0F60 SharePoint Portal Server       User Profiles                  d3b3 High     ...et, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)     --- End of inner exception stack trace ---     at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)     at System.Net.HttpWebRequest.GetRequestStream()     at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()     --- End of inner exception stack trace ---    Server stack trace:      at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()     at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)     at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)     at System.ServiceModel.Channels.RequestChannel.Request... affaead0-7be6-4fb3-8df1-b41aa16d0193
    02/23/2010 11:13:44.79* w3wp.exe (0x1634)                        0x0F60 SharePoint Portal Server       User Profiles                  d3b3 High     ...(Message message, TimeSpan timeout)     at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown at [0]:      at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)     at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)     at System.ServiceModel.Description.IMetadataE... affaead0-7be6-4fb3-8df1-b41aa16d0193
    02/23/2010 11:13:44.79* w3wp.exe (0x1634)                        0x0F60 SharePoint Portal Server       User Profiles                  d3b3 High     ...xchange.Get(Message request)     at Microsoft.ResourceManagement.WebServices.MetadataClient.Get(String dialect, String identifier)     at Microsoft.ResourceManagement.WebServices.Client.ResourceManagementClient.SchemaManagerImplementation.RefreshSchema()     at Microsoft.ResourceManagement.WebServices.ResourceManager.get_SchemaManager()     at Microsoft.ResourceManagement.WebServices.ResourceManager..ctor(String typeName, LocaleAwareClientHelper localePreferences, ContextualSecurityToken securityToken)     at Microsoft.Office.Server.UserProfiles.ConnectionManager.LoadConnections() . affaead0-7be6-4fb3-8df1-b41aa16d0193
    02/23/2010 11:13:44.79  w3wp.exe (0x1634)                        0x0F60 SharePoint Portal Server       User Profiles                  a3xu High     ConnectionManager.LoadConnections(): Could not find MOSS MA despite being marked as fully configured, was it deleted? affaead0-7be6-4fb3-8df1-b41aa16d0193

    Regards

    Nigel

    Wednesday, February 24, 2010 6:46 AM
  • Hi everyone,

    I can confirm that the resolution to this issue is to restart the following services:

    - Forefront Identity Manager Service 
    - ForeFront Identity Manager Synchronization Service

    Through Services in Administrative Tools (or services.msc in Run command).


    Cheers,
    Tommy
    • Proposed as answer by Tommy Segoro Thursday, February 25, 2010 8:25 AM
    • Unproposed as answer by Stanfford Liu Monday, December 6, 2010 3:33 AM
    • Marked as answer by Tracyp - MSFT Wednesday, December 15, 2010 11:47 PM
    • Unmarked as answer by GuYuming Friday, March 16, 2012 5:18 AM
    Thursday, February 25, 2010 8:24 AM
  • Please don't propose your own reply as an answer.  If the OP says it fixes his problem, then he will mark it as such.


    SharePoint Architect || My Blog
    Thursday, February 25, 2010 8:40 AM
  • I was getting this error on the RTM version - where I didn't get it on the beta.

    The ForeFront Identity Manager Synchronization Service was started, but the Forefront Identity Manager Service was not

    I know I'm not supposed to do this, and I know it is supposed to start automatically, but manually starting the ForeFront Identity Manager Service allowed me to create the new connection.

    I'm guessing this could have something to do with this machine previously running the Beta - which I uninstalled first. Not a bit deal for me. This is just a "play" server.

    Brad Thurber

    Thursday, April 29, 2010 12:04 PM
  • Hi Tommy,

    I had the same issue and your solution solved my issue

    Thanks,

    Rosaline

    Thursday, May 13, 2010 2:55 PM
  • Same issue here and starting the FIM Service solved my issue. 

    Thanks!

    Tuesday, May 18, 2010 6:59 PM
  • I had this problem, and the Forefront Identity Manager Service was not started. I started it and restarted ForeFront Identity Manager Synchronization Service. That solved the issue!


    Tihomir Ignatov
    Friday, May 21, 2010 3:07 PM
  • Hi,

    When I try to start the serviceForeFront Identity Manager Synchronization Service,It gives ther error that the ForeFront Identity Manager Synchronization Service is unable to start  error 2 the specified file not found.

    can any body help on this

    Thanks,

    gs

    Thursday, June 3, 2010 11:46 AM
  • Worked for me as well. It happend out of nowhere, weird.

    Monday, June 21, 2010 4:55 PM
  • Clayton is correct.  There should be no need to start the FIM services manually.

    I've documented a step by step guide that should hopefully help you in visualizing the User Profile Service Application setup using the least privilege model...

    http://sharepointgeorge.com/2010/configuring-the-user-profile-service-in-sharepoint-2010/


    Blog: http://sharepointgeorge.com Twitter: http://twitter.com/georgekhalil
    Monday, June 21, 2010 9:34 PM
  • This happened to me too when I used PowerShell to configure my sync with our AD that has a different NETBIOS name. FIM service was stopped for no reason and I had to manually start it. All is well now.

    I like how Clayton the MVP tells us not to manually start the service, yet that is the solution that works for everyone. Can't argue with results.

    Wednesday, August 4, 2010 9:35 PM
  • Hi

    The best source of how to install and configure the User profile service is @harbars article :-

    http://www.harbar.net/articles/sp2010ups.aspx

    http://harbar.net/archive/2010/05/10/sharepoint-2010-user-profile-sync-amp-reboots.aspx

    Nigel

     

     

    Thursday, August 26, 2010 9:21 AM
  • Hi all,

    Both my 'Forefront Identity Manager Service' and 'Forefront Identity manager Sychronisation service' are started already (automatically, not by me), but I still get the 'MOSS MA not found' error.

    I tried to restart the above 2 services but the same error still occured.

    Any idea ? Thanks.

    Friday, September 24, 2010 5:42 AM
  • Hi all,

    Both my 'Forefront Identity Manager Service' and 'Forefront Identity manager Sychronisation service' are started already (automatically, not by me), but I still get the 'MOSS MA not found' error.

    I tried to restart the above 2 services but the same error still occured.

    Any idea ? Thanks.


    I ahve the same issue !!! both are started, but MOSS AM error is coming !
    Monday, October 11, 2010 11:23 AM
  • Hi

    Have you installed the following :-

  • KB 2352346 - SharePoint Foundation 2010
  • KB 2352342 - SharePoint Server 2010

    If not install them and try again following Spencer Harbar's instructions (including the re-boots !)

    Also if you could include the errors in the ULS Log around this issue this would also help us diagnose the issue.

    Regards

    Nigel

Monday, October 11, 2010 11:36 AM
  • Hi Also - If you perform a restart of the Server and again, the ForeFront service does not start, use the Services and modify the properties to set the Startup type to be 'Automatic (Delayed Start)' See if that works. Regards Nigel
    Monday, October 11, 2010 11:40 AM
  • Clayton is corret we should not start FMI services manually. I had this problems and read the link bellow that provides full information about profile sync. My problem was the user that did not have permission.

    http://technet.microsoft.com/en-us/library/ee721049.aspx#

    I stoped the service User Profile Synchronization Service and start it again logged in with an farm account. Automatically the FMI services will be started and everything will works well.


    André Rentes
    • Proposed as answer by TimDev Tuesday, November 2, 2010 8:00 PM
    Friday, October 22, 2010 12:33 PM
  • Under "Service Applications", click on "Manage services on server".

    Then start the "User Profile Synchronization Service".  (you should stop it if it is already started. {This is how to do a service reset.})

    Select the "User Profile Application" and enter in the "Service Account Name and Password"

    IMPORTANT STEP:

    NOTE: If SharePoint Central Administration is deployed on the same machine, you MUST recycle Internet Information Services (IIS) after provisioning the User Profile Synchronization Service.

    In other words, just run IISRESET and both Forefront IM services start right up.

    SharePoint Architect/Developer: Timothy Murray


    Software Engineer
    Tuesday, November 2, 2010 8:02 PM
  • Thanks ,

    Its work for me.


    Thanks, Sachin Jagtap
    • Proposed as answer by Sachin Jagtap Monday, December 6, 2010 9:32 PM
    Monday, December 6, 2010 9:32 PM
  • I enabled both of these services and I am still getting the error message
    Tuesday, December 14, 2010 10:43 PM
  • Wednesday, December 15, 2010 9:39 AM
  • Hi all,

    Both my 'Forefront Identity Manager Service' and 'Forefront Identity manager Sychronisation service' are started already (automatically, not by me), but I still get the 'MOSS MA not found' error.

    I tried to restart the above 2 services but the same error still occured.

    Any idea ? Thanks.


    I have the same problem if you find how to solve it please reply to me or any one knows the solution for that problem..
    I am too late but i will never give up
    Sunday, January 9, 2011 12:59 PM
  • Hi all,

    I had same issue, that has been resloved after started stated services.

     

    Thanks,

    Manas Mondal

    Saturday, January 22, 2011 8:37 AM
  • For the Moss MA not found issue please refer my blog

    http://aurramu.blogspot.com/2011/02/moss-ma-not-found-in-sharepoint-2010.html

     

    • Proposed as answer by The Eagle Wednesday, March 2, 2011 7:34 AM
    Friday, February 4, 2011 11:22 AM
  • For the Moss MA not found issue please refer my blog

    http://aurramu.blogspot.com/2011/02/moss-ma-not-found-in-sharepoint-2010.html

     


    I read your blog as you suggested.I have the Forefront two services started already.About solution 2 I will try it and I realy wish it will be that easy...
    I am too late but i will never give up
    Sunday, February 6, 2011 2:12 PM
  • Thanks Tommy.

     

    Restarting Forefront services fixed the error.

    Thanks,

    Kavita

    Wednesday, February 16, 2011 6:47 PM
  • For the Moss MA not found issue please refer my blog

    http://aurramu.blogspot.com/2011/02/moss-ma-not-found-in-sharepoint-2010.html

     


    I solved my problem using your solution 2 and a Microsoft Hotfix.

    If someone find my post helpful please click the reputation yellow arrow on the left or mark as answer.


    I am too late but i will never give up
    Wednesday, March 2, 2011 7:33 AM
  • I restarted the 2 Forefront services as suggested and it removed the MOSS MA error. I was logged in as the service administrator for these services. The services did not start on their own initially.
    Thursday, March 3, 2011 11:50 PM
  • Restarting the services didn't work.

    I got this "MOSS MA not found" when adding an AD connection to the UserProfileConfigManager using PowerShell.
    ULS it showed:
    LoadConnections failed trying to fill the connections list. Most likely during RetriveResources because of permissions --- {1}. Available parameters: Microsoft.ResourceManagement.WebServices.Client.PermissionDeniedException: Access to the requested resource(s) is denied

     I fixed the error by running the "Add AD connection to UserProfileConfigManager" as farm account.

    Or, much eseier, add the 'installer' acocunt to "User Profile Service Application" Administrators section with 'Manage Profile' permissions. Also perform an iisreset to let the security changes come through. Maybe wait even a few minutes before giving it a try.

    Regards Koen

    Blog: http://kvdlinden.blogspot.com
    Follow me at: http://twitter.com/#!/kvdlinden



    Friday, April 1, 2011 7:14 AM
  • I fixed it by stop the User Profile Synchronization service in Central Administration -> Manage Services on Server and restart it. Please take a look at http://cid-6f40fb61d28cf147.office.live.com/view.aspx/Technology/MOSS%20MA%20Not%20found%20error%20when%20create%20new%20synchronization%20connection.docx for detail.

    • Marked as answer by GuYuming Monday, June 20, 2011 1:25 AM
    Wednesday, April 20, 2011 5:05 AM
  • Can anyone tell me where the MOSS MA should be created? I know how FIM works but the Management Agent should be created automatically. Restarting the User Profile Synchronization Service worked for me but in the past I haven't had to do this. From the looks of it the MA only got created once I created the synchronization connection, not when I restarted the service. I guess I'd like to know where the process failed in order to avoid it in future....

    Thursday, April 21, 2011 11:59 AM
  • also, check your proxy settings your UPS service user :)
    Thursday, May 12, 2011 12:46 PM
  • Thank you Nigel your solution is the best after searching for a long time trying to make sure that forfront is working properly and making sure that every thing is OK with our Active directory. I should tried your solution first. many thanks.
    Saturday, June 18, 2011 11:52 AM
  • Thanks GuYuming.  This fixed it for me, I'd even restarted the server before restarting this service and specifically restarting the service fixed it.
    Friday, July 1, 2011 2:09 PM
  • Moderator, please unmark this as the answer, as if SharePoint configuration is correct it manages the FIM services completely. We are NOT suppose to be changing the FIM services manually through services.msc, we are only suppose to have SharePoint change them.

    Linda Chapman | SharePoint Consultant | My Blog: http://LindaChapman.BlogSpot.com | http://www.linkedin.com/in/LindaChapman

    Thursday, March 15, 2012 4:40 PM
  • Actually "MOSS MA" is a SharePoint error, that you will get in some configurations of a farm. It is just not consistent. In some configurations it will just fail but not show the error.

    Linda Chapman | SharePoint Consultant | My Blog: http://LindaChapman.BlogSpot.com | http://www.linkedin.com/in/LindaChapman

    Thursday, March 15, 2012 4:42 PM
  • The issue is it is not supported by Microsoft to manually change those FIM services. If you configure UPA and UPS properly you will not get this error.

    Linda Chapman | SharePoint Consultant | My Blog: http://LindaChapman.BlogSpot.com | http://www.linkedin.com/in/LindaChapman

    Thursday, March 15, 2012 4:47 PM
  • You were right Nigel! It has worked out for me :)

    Friday, March 23, 2012 2:39 PM
  • Restarting the services didn't work for me. However, I solved my problem!

    I went to the logs (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS) and found the correlation ID given by the error.

    I then realized that it was a FIREWALL issue!!! Ports 5725, 5726 weren't opened on the application server (we use host based firewall via GPOs) where the FF services run.

    Opened the firewall and everything went as smooth as silk!

    Cheers!


    • Edited by Audiolomb Monday, April 16, 2012 4:26 PM
    Monday, April 16, 2012 4:21 PM
  • Tuesday, April 17, 2012 10:54 AM