Issue : Could not find MOSS MA despite being marked as fully configured, was it deleted?
An issue with SharePoint 2010’s Synchronization Connections within User Profile Synchronization Service that prevented me from adding any new User profile connections
When I attempted to re-add the Synchronization connection I was presented with this error:
SP Error:
MOSS MA Not Found 80b81e6c-2cbe-41ce-a144-197d4f6cf14b
An issue with SharePoint 2010’s Synchronization Connections within User Profile Synchronization Service that prevented me from adding any new User profile connections
When I attempted to re-add the Synchronization connection I was presented with this error:
SP Error:
MOSS MA Not Found 80b81e6c-2cbe-41ce-a144-197d4f6cf14b
We tried
the following actions:
1.
Disabled User Profiles Sync Services
2.
iisreset /noforce
3. Restart
User Profile Synchronization Services in order for the FIM services to restart
automatically – confirmed by opening services.msc and checking FIM services.
4. Checked
in miisclient.exe Management Agents >
ILMA > Properties > Connect to db > http://localhost:5725
5. Checked
Firewall - disabled
6. Checked
for Web proxies
7. Take
user profile database backups from Qual Farm
8.
Restored into Prod farm
9. Edit the web.config of the central admin web
application on Server
a. Add the below lines directly above the
</configuration> tag
<system.diagnostics>
<trace
autoflush="true"/>
<sources>
<source name="System.Net"
maxdatasize="1024">
<listeners>
<add
name="MyTraceFile"/>
</listeners>
</source>
<source name="System.Net.Sockets"
maxdatasize="1024">
<listeners>
<add
name="MyTraceFile"/>
</listeners>
</source>
<source name="System.Net.Cache"
maxdatasize="1024">
<listeners>
<add
name="MyTraceFile"/>
</listeners>
</source>
</sources>
<sharedListeners>
<add name="MyTraceFile"
type="System.Diagnostics.TextWriterTraceListener"
initializeData="D:\temp\System.Net.log"/>
</sharedListeners>
<switches>
<add name="System.Net" value="Verbose"
/>
<add name="System.Net.Sockets" value="Verbose"
/>
<add name="System.Net.Cache" value="Verbose"
/>
<add name="System.Net.HttpListener" value="Verbose"
/>
<add name="Microsoft.ResourceManagement"
value="Verbose" />
</switches>
</system.diagnostics>
Note: Log file location can
be modified
b. Replace the following lines
<system.net>
<defaultProxy />
</system.net>
with
<defaultProxy>
<proxy bypassonlocal="true"
usesystemdefault="false" />
</defaultProxy>
Created
new user profile service with using restored databases
10. Started User profile services in
Application server and observed that the problem still persists
11. Changed Server provision from
Application server to Web frontend server
12. Repeated 10Th step in WEF
server and observed that the same problem
13. Referred our document steps (what we
provided to Microsoft while opening MS ticket) and repeated same steps in
Application server
14. After that User profile connection
has been created without any error and it worked.
15 Deleted new user profile application
service and used old user profile service and tried to create new the
connection again – it worked
16 Run full sync jobs.
After applying this action
plan we managed to fix this issue in Prod farm.
