Troubleshooting FIM Portal Issues
Due to my SharePoint experience I got stuck putting up FIM Portal at a client site. I started digging into FIM Portal, FIM Service and FIM Sync. FIM Sync reminds me a little of my BizTalk days. The whole product is interesting, you have pay close attention to details otherwise things do not work 
I setup 2 labs to test various scenarios involving different FIM components. My deployment path included 2 WSS Servers (FIM Portals load balanced), both running FIM Service, separate FIM Sync Server and a common SQL Cluster for all FIM components.
I am posting on the issues you run into when adding a new WSS server to the Farm and here are the issues I ran into and the resolution:
1) Only add/install FIM Service to the 2nd WSS Server. No need to install or add the FIM Portal feature.
2) The 2 FIM WSPs found in solution management through CA should get deployed to the second WSS server as soon as the timer job executed to synchronize the web application(s) and solutions (WSPs) to the newly added server. If WSPs don’t get installed on the 2nd SharePoint server you will receive some weird SharePoint errors.
3) Make sure the firewalls between the servers are off if the WSPs aren’t getting deployed to the new WSS Server.
4) If the problems with bringing up the FIM Portal site persist then you can try to do a REPAIR on the first server which will retract the WSPs and deploy them again GLOBALLY (to all WFE servers in the Farm) by removing and adding the FIM Portal solution pack.
5) The other major thing that needs done is changing the FIM Service URL in the second WSS Server’s web.config file found in %INETPUBDIR%\inetpub\wwwroot\wss\VirtualDirectories\. The way SharePoint works is once the 2nd WSS Server comes online (added to the Farm through the PSConfig tool) the timer jobs in SharePoint starts deploying the Web Application to the second server. In the process the same web.config file from the 1st WSS Server gets deployed to the 2nd WSS Server but it has the first server’s FIM Service URL.
The config entry to change in the web.config file is the following and it needs to have the 2nd server in :
<resourceManagementClient resourceManagementServiceBaseAddress="http://:5725″ timeoutInMilliseconds=”60000″ />
NOTE: The above is true is if you followed the deployment path of 2 WSS Servers (FIM Portals load balanced) and both to run the FIM Service.
Thats it folks!
