FIM Service database could not be successfully deployed. Error: Timeout Expired

I had a simmilar issue as per http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/b2de9b59-0ce4-4c9b-bfec-95662a4aa373.

The setup is on a LAB environment with AD, SQL 2008 R2, Exchange 2010 and the FIM server is on different servers. FIM Synchronization completed succesfully on the same server and there is no connection problem with SQL.
The FIM Server details:
OS:Windows Server 2008 R2 SP1,
SQL Native Client 2008 R2 is install
SQL Envirinment:
OS:Windows Server 2008 R2 SP1,
SQL 2008 R2

The Installation account of the "FIM Service & Portal" is the FIM Service account and have SYSADMIN rights on SQL,

There is a mailbox for the FIM service account and it can access owa. The EWS certifacte was aso added to "Trusted People - Local Computer". The FIM Service and Portal Setup run and then give the following errors:

The first error screen:


The second error screen:


After the setup has performed a rollback the following error is found in the Application Log:
Product: Forefront Identity Manager Service and Portal
-- Error 1722. There is a problem with this Windows Installer package. A
program run as part of the setup did not finish as expected. Contact your
support personnel or package vendor. Action DeployAndPopulateDatabase,
location: C:\Windows\Installer\MSI40E7.tmp, command: installApp=FIM
action=DeployAndPopulateDatabase databaseName=FIMService
namespaceName="fim" datFilesInstallDir="C:\Program
Files\Microsoft Forefront Identity Manager\2010\Service\Data"
sqlserverName=****sql01.***.***.com FIMServiceAccountDomain=tlab
FIMServiceAccountName=fimsvc SyncServiceAccountDomain=****
SyncServiceAccountName=fimma RunningUserDomain=**** RunningUserName=FIMsvc RunningUserEmail=CreateDatabase=True

This is the same as "Yoann-78" posted on, but the FIM Service account does have a mailbox and it does show in AD.

I Got a workaround on this issue:

I got FIM Portal & Service installed using SQL locally on the server. I have made a backup of the database and restore it to the SQL Cluster. I could then install FIM Portal & Service by selecting using the existing database, but could not install FIM Portal & Service by selecting creates a new database. I have set the SQL Timeout to "0" (Unlimited) and we still encountered the issue.
Anybody any ideas for what we can check to see why the database are not being created with the installation?

I could also successfully install FIM Portal & Service on the SQL Cluster in the PRoduction environment, so the issue is with Lab's SQL Cluster envorinmnet configuration but we could not troubleshoot the issue anymore as we were on a scheduled timeline to complete the project.