Overview

The purpose of this wiki page is to cover a very unique installation issue that I encountered today when installing the FIM Synchronization Service and using an existing database from MIIS 2003 SP2 ( 3.2.559 ).  This may be a one off, but I also believe that it should be documented for us all to know about here.

Problem Statement

You decide to upgrade Microsoft Identity Integration Server 2003 Service Pack 2 ( MIIS 2003 SP2 ( 3.2.559 ) using a Microsoft SQL Server 2000 Service Pack 4 ( SQL Server 2000 SP 4 ) backend database server to Microsoft Forefront Identity Manager 2010 ( 4.0.2592 ) with a Microsoft SQL Server 2008 server. 

You backup the MIIS 2003 database ( MicrosoftIdentityIntegrationServer ) and restore the database to the SQL Server 2008 server as FIMSynchronizationService.

You open a Command-Prompt, by right clicking on Command-Prompt and selecting Run As Administrator.  You navigate to the location of the installation media, and execute it with the MSIEXEC.EXE command-line to obtain a Windows Installer Verbose Log File. 

You receive the following installation error message.

Windows Installer Error message

Error 25009.

The Forefront Identity Manager Synchronization Service setup wizard cannot configure the specified database. CONDITIONAL failed because the following SET options have incorrect settings: 'ARITHABORT'.

Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations.

MSI (s) (E0!84) [14:41:30:998]:

Product: Forefront Identity Manager Synchronization Service -- Error 25009.

The Forefront Identity Manager Synchronization Service setup wizard cannot configure the specified database. CONDITIONAL failed because the following SET options have incorrect settings: 'ARITHABORT'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations.

CustomAction ConfigDB returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Action ended 14:41:30: InstallFinalize. Return value 3.

Cause

The SQL Server Compatibility Level was set to SQL Server 2000 (80).

Resolution

Set the SQL Server Compatibility Level to SQL Server 2008 ( 100 )

Run the installation again

APPENDIX A - How to check the SQL Server Compatibility Level

  1. Open SQL Server Management Studio, and connect to the SQL Server hosting the existing FIMSynchronizationService database
  2. Right mouse click on the FIMSynchronizationService database
  3. From the context menu, select Properties
  4. In the Properties Windows, select Options
  5. Review Compatibility Level Drop down

 


See also