TROUBLESHOOTING: Failed to retrieve schema or cannot connect to database while creating a FIM MA

TROUBLESHOOTING: Failed to retrieve schema or cannot connect to database while creating a FIM MA

PROBLEM STATEMENT

You recently installed FIM 2010 Update 2 (4.00.3606.2) with a SQL Server 2008 R2 backend.  Everything seems good.  You then attempt to create a FIM Service Management Agent.  You receive an error message “Failed to retrieve schema” or “Cannot connect to Database”.

CAUSE

The cause of this issue is that the .NET Framework v4.0 is not installed on the FIM Synchronization Service. 

RESOLUTION

In this case, there are two possible solutions for this problem.

#1

è Install the Microsoft .NET Framework v4.0

#2

  1. On the FIM Synchronization Service Machine, Stop the FIM Synchronization Service
  2. Navigate to %programfiles%\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin
  3. Edit the miiserver.exe.config file
  4. In the <startup> section, swap the order of the supportedRuntime

FROM

  <startup useLegacyV2RuntimeActivationPolicy="true">

    <supportedRuntime version="v4.0.30319"></supportedRuntime>

    <supportedRuntime version="v2.0.50727"></supportedRuntime>

  </startup>

TO

  <startup useLegacyV2RuntimeActivationPolicy="true">

    <supportedRuntime version="v2.0.50727"></supportedRuntime>

    <supportedRuntime version="v4.0.30319"></supportedRuntime>

  </startup>

  1. Save the miiserver.exe.config file
  2. Start the FIM Synchronization Service
  3. Create the FIM Service Management Agent

 

SEE ALSO

 

Leave a Comment
  • Please add 4 and 4 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
Page 1 of 1 (1 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
  • Brilliant. Exactly the same issue. Spent an hour troubleshooting rights and sql before i saw it.

  • This solution not working :(

  • Fernando Lugão Veltem edited Revision 1. Comment: added toc and tags

  • Please note that we have found some instances where installing the .NET Framework 4.0 does not work around this issue.  The second option to work around this problem has worked in every known instance of the problem to date.

Page 1 of 1 (4 items)