I have tried to do User Profile Synchronization. The status did not change from “Synchronizing” for more than 10 hrs.
I found the following errors in the logs:
UserProfileApplication.SynchronizeMIIS: Unexpected exception: System.ServiceModel.EndpointNotFoundException: Could not connect to http://sp2010index:5725/ResourceManagementService/MEX. TCP error code 10061: No connection could be made because the target machine actively refused it xxx.xx.x.xxx:xxxx. ---> 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 xxx.xx.x.xxx:xxxx at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 tim... 6d0e9ede-b3cf-45ac-9c4a-c5800216a178
After starting the “Forefront Identity Manager Service”, the exception disappeared. This can be started through services.msc
After starting the servide, the User Profile Sync worked and the Audiences compiled too..
My coloeague Dave suggested that it is a better practice to stop and start "User Profile Synchronization Service" from Central Admin as opposed to starting the “Forefront Identity Manager Service”, manually.
I found the following errors in the logs:
UserProfileApplication.SynchronizeMIIS: Unexpected exception: System.ServiceModel.EndpointNotFoundException: Could not connect to http://sp2010index:5725/ResourceManagementService/MEX. TCP error code 10061: No connection could be made because the target machine actively refused it xxx.xx.x.xxx:xxxx. ---> 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 xxx.xx.x.xxx:xxxx at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 tim... 6d0e9ede-b3cf-45ac-9c4a-c5800216a178
After starting the “Forefront Identity Manager Service”, the exception disappeared. This can be started through services.msc
After starting the servide, the User Profile Sync worked and the Audiences compiled too..
My coloeague Dave suggested that it is a better practice to stop and start "User Profile Synchronization Service" from Central Admin as opposed to starting the “Forefront Identity Manager Service”, manually.
No comments:
Post a Comment