I'm installing/configuring FIM, and am using 4 machines: 1. Portal 2. Service 3. Service DB 4. Sync service/db I've installed all the pieces to FIM across the machines. After installing, should I have been able to access the Portal with any users, including the user who installed the Portal? Is there a way to test that my installations were successful? I am now creating the FIM Service MA (ADMA created just fine). On the second screen, it asks for Server, Database, FIM Service base address, and the account information. All of them are pretty easy to figure out, except the FIM Service base address. If we separated the Portal, Service, and Service DB, what address do we use - what is this value asking for? I've tried all 3, but each of them give me an error 'Failed to retrieve the Schema'. Is there a port that isn't open somewhere? Is there a problem with how everything is installed, given that I've never been able to access the Portal? So far the event logs haven't given any helpful information.

The adres should point to the 2. Service machine. During installation you can open de specific ports 5725 and 5726 for authentication. Can you telnet from the 4. Sync service/db to the 2. Service on the specific port 5725? Need realtime FIM synchronization? check out the new http://www.traxionsolutions.com/imsequencer that supports FIM 2010 and Omada Identity Manager real time synchronization!

Hi There, The information for setting up the FIM MA is: SQL Server -> Address or resolvable SQL Server Name FIM Service -> That would be where you have installed the FIM Service itself which is, in your example, box 3. This is in the form of a URL like http://Server3:5725 Account -> Commonly when people are creating the FIM Service a mistake is made with the account that is set up for the MA. When setting up the FIM Service, it asked for the service account of the synchronization account. You had to type it in as Domain\Account. This is the account credentials you should use within the MA setup as it has special permissions in the FIM database. Quite often in my set ups, you'll see service accounts named FIMSE (sync engine), FIMMA (FIM MA) and FIMSvc (FIM Service) set up and used for each of the discrete tasks. Schema discovery issues in the MA are usually caused by not being able to connect to SQL properly with the service account. As the read operations are done directly from the database itself. It does also check connectivity to the web service as well and would throw an error if it unable to connect. Thanks B

I thought it was probably the service address - that made the most sense. I opened those ports during the service installation and I see the two Inbound rules on the 2. Service machine. However, I'm trying to run a telnet ("o <servername> 5725") from the sync machine and it doesn't connect: Could not open connection to the host, on port 5725: Connect failed Also, when I installed the service I gave it the servicema account for FIM Management Agent Account, which is the same account I'm trying to use to create the Service MA now. I do see the servicema account in the FIM database.

I tried every combination I could think of yesterday, but apparently I didn't try using IP addresses for both the server and the service base address. I didn't get an error this time when I clicked Next. Looks like I'm able to get to the next step now. Thanks for the clarification!