Here is yet another of those Microsoft Identity Manager installation errors that doesn’t give you much information and when looking for a resolution you can’t find an exact match through Dr Google.

Nearing the end of the Microsoft Identity Manager Service and Portal installation you receive the “The Microsoft Identity Manager server database could not be successfully populated” error.

Looking into the installation log (which I’m in the good practice of always initiating when doing an installation of the MIM Service/Portal these days eg. msiexec /i “e:\Service and Portal\Service and Portal.msi” /l*v c:\temp\install.log )  didn’t give up much information at all. Fatal Error. Dialog created.

Looking at the server that the installation was being done on I could see that it was being spanked. This server is for a customers development environment, hosted in Azure but also done rather frugally (my Virtual Machine was running, SQL, MIM Sync, all the dependencies for the MIM Portal and then the MIM Service/Portal itself). FWIW the initially provisioned VM was an Azure DS1v2 server. Seems a character may have got lost in the VM request where an Azure DS11v2 server would have been more appropriate.

I re-sized the Azure VM and actually chose to go with an Azure DS3v2 VM size. I kicked off the Microsoft Identity Manager Service & Portal installation again and ….

….. SUCCESS.

Hope this helps someone else who may find themselves in a similar position.

Follow Darren on Twitter @darrenjrobinson

Category:
FIM, Identity and Access Management
Tags:
, ,

Join the conversation! 6 Comments

  1. I have faced this before and I needed to install SQL Server 2012 Native Client on the Portal, which is Prerequisite for the install. But never tried it on Azure. But thanks for the input.

    Reply
    • Yes. I already had the SQL Native Client installed as that’s tripped me up before. It’s one of my Pre-req’s in my checklist.

      Reply
  2. Thank you! Had the exact same issue in Azure. This solved days of agony.

    Reply
  3. Thanks! I followed your tip and it worked. I chose to resize down after the installation to save a few $ on my test installation.

    Reply
  4. Hi, may I check with you what is the actual size required? I’m working on a VM created on VirtualBox locally and I had this error as well… My VM still has 26GB out of 50GB free…
    Appreciate any help.. Thanks!

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: