Hi all,

I hope you can help me with this issue. We have a FIM 2010 R2 Sync Engine, Service and Portal running. Now I'm trying to run to install SP1 for that but it fails.

 

• FIM Sync Engine is no problem and patches correctly to R2 SP1
• FIM Service and Portal ends prematurly during the upgrade, leaving the database corrupted(version-1) etc.

I've run an MSI verbose logging, but that doesnt help much:

-------------------------------------------------------------------------------------------------

MSI (c) (E0:70) [10:59:25:371]: Transforming table Binary.

MSI (c) (E0:70) [10:59:25:371]: Note: 1: 2262 2: Binary 3: -2147287038
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 UpgradeDatabase, location: C:\Program Files\Microsoft Forefront Identity Manager\2010\Service\Microsoft.IdentityManagement.DatabaseUpgrade.exe, command: /ConnectionString:"Data Source=XXXX;Initial Catalog=FIMService;Integrated Security=SSPI;Pooling=true;Connection Timeout=225" /FimServiceAccountName:"XXXX" /FimServiceDatabaseName:"FIMService"
MSI (s) (44:94) [10:59:28:877]: 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 UpgradeDatabase, location: C:\Program Files\Microsoft Forefront Identity Manager\2010\Service\Microsoft.IdentityManagement.DatabaseUpgrade.exe, command: /ConnectionString:"Data Source=XXXXX;Initial Catalog=FIMService;Integrated Security=SSPI;Pooling=true;Connection Timeout=225" /FimServiceAccountName:"XXXXXX" /FimServiceDatabaseName:"FIMService"

Action ended 10:59:28: InstallExecute. Return value 3.

Rollback starts from here.

-------------------------------------------------------------------------------------------------

I've found the following in the Microsoft.IdentityManagement.DatabaseUpgrade_tracelog.txt and I guess this is what goes wrong:

-------------------------------------------------------------------------------------------------

Microsoft.ResourceManagement Verbose: 0 :  Executing Batch #: 1
    DateTime=2013-11-14T13:00:10.2511860Z
Microsoft.ResourceManagement Verbose: 0 : --********************************************************
--*                
    DateTime=2013-11-14T13:00:10.2511860Z
Microsoft.ResourceManagement Verbose: 0 : Out-of-box object import : Completed processing pre object import file DisableUsageKeywordCheck.sql.
    DateTime=2013-11-14T13:00:10.2570456Z
Microsoft.ResourceManagement Verbose: 0 : Out-of-box object import : Started processing object import file ConfigurationChange1113Attribute.xml.
    DateTime=2013-11-14T13:00:10.2580222Z
Microsoft.ResourceManagement Verbose: 0 : PlatformBasics is starting. IsService = 'False'.
    DateTime=2013-11-14T13:00:11.0822726Z
Microsoft.ResourceManagement Verbose: 0 : Application Registered as ServiceId '2', ServicePartitionId '2'.
    DateTime=2013-11-14T13:00:11.1564942Z
Microsoft.ResourceManagement Verbose: 0 : Request '' status was updated in-memory from 'NotFound' to 'Validating'.
    DateTime=2013-11-14T13:00:11.7063200Z
Microsoft.ResourceManagement Verbose: 0 : Request created: 'Create Resource:  'Deferred Evaluation' Request'
    <RequestParameter xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:type="CreateRequestParameter"><Calculated>false</Calculated><Target>35c27ca4-3925-468e-8e10-e68b5882b6b4</Target><PropertyName>UsageKeyword</PropertyName><Value xsi:type="xsd:string">Microsoft.ResourceManagement.WebServices</Value><Operation>Create</Operation></RequestParameter>
    <RequestParameter xmlns:xsi="http:
    DateTime=2013-11-14T13:00:13.0325428Z
Microsoft.ResourceManagement Verbose: 0 : Entered RequestDispatcher with Request Object; RequestIdentifier '60f2fc53-de87-4837-8139-9f3efcec3b06'.
    DateTime=2013-11-14T13:00:13.0462152Z
Microsoft.ResourceManagement Verbose: 0 : Add request '60f2fc53-de87-4837-8139-9f3efcec3b06' to cache with RequestStatus 'Validating'.
    DateTime=2013-11-14T13:00:13.0510982Z
Microsoft.ResourceManagement Information: 1 : RequestDispatcher enter processing pipeline;  RequestIdentifier '60f2fc53-de87-4837-8139-9f3efcec3b06'; Operation 'Create'; Object 'Resource'; RequestStatus 'Validating'.
    DateTime=2013-11-14T13:00:13.0530514Z
Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier '60f2fc53-de87-4837-8139-9f3efcec3b06' for a 'Create' operation on object 'Resource' with RequestStatus 'Validating'.
    DateTime=2013-11-14T13:00:13.0550046Z
Microsoft.ResourceManagement Information: 1 : ManagementPolicy: EvaluatingRights
    DateTime=2013-11-14T13:00:13.0579344Z
Microsoft.ResourceManagement Information: 1 : ManagementPolicy: RightsEvaluated
    DateTime=2013-11-14T13:00:17.4897452Z
Microsoft.ResourceManagement Verbose: 0 : Request '60f2fc53-de87-4837-8139-9f3efcec3b06' status was updated in-memory from 'Validating' to 'Validated'.
    DateTime=2013-11-14T13:00:17.4897452Z
Microsoft.ResourceManagement Verbose: 0 : Request '60f2fc53-de87-4837-8139-9f3efcec3b06' updates have been persisted to permanent storage.
    DateTime=2013-11-14T13:00:17.5854520Z
Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier '60f2fc53-de87-4837-8139-9f3efcec3b06' for a 'Create' operation on object 'Resource' with RequestStatus 'Validated'.
    DateTime=2013-11-14T13:00:17.5864286Z
Microsoft.ResourceManagement Verbose: 0 : Executing initial authentication.
    DateTime=2013-11-14T13:00:17.5893584Z
Microsoft.ResourceManagement Verbose: 0 : Request '60f2fc53-de87-4837-8139-9f3efcec3b06' status was updated in-memory from 'Validated' to 'Authenticating'.
    DateTime=2013-11-14T13:00:17.5893584Z
Microsoft.ResourceManagement Verbose: 0 : Request '60f2fc53-de87-4837-8139-9f3efcec3b06' status was updated in-memory from 'Authenticating' to 'Authenticated'.
    DateTime=2013-11-14T13:00:17.5893584Z
Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier '60f2fc53-de87-4837-8139-9f3efcec3b06' for a 'Create' operation on object 'Resource' with RequestStatus 'Authenticated'.
    DateTime=2013-11-14T13:00:17.5903350Z
Microsoft.ResourceManagement Verbose: 0 : Request '60f2fc53-de87-4837-8139-9f3efcec3b06' status was updated in-memory from 'Authenticated' to 'Authorized'.
    DateTime=2013-11-14T13:00:17.5971712Z
Microsoft.ResourceManagement Verbose: 0 : RequestDispatcher is processing RequestIdentifier '60f2fc53-de87-4837-8139-9f3efcec3b06' for a 'Create' operation on object 'Resource' with RequestStatus 'Authorized'.
    DateTime=2013-11-14T13:00:17.5981478Z
Microsoft.ResourceManagement Information: 1 : WS: Action.Create.Execute.Enter
    DateTime=2013-11-14T13:00:17.6010776Z
Microsoft.ResourceManagement Error: 3 : Reraised Error 50000, Level 16, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 50000, Level 16, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 547, Level 16, State 1, Procedure UpdateResource, Line 220, Message: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ObjectValueBoolean_BindingInternal". The conflict occurred in database "FIMService", table "fim.BindingInternal".
    DateTime=2013-11-14T13:00:18.0327348Z
Microsoft.ResourceManagement Error: 3 : Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Data.SqlClient.SqlException: Reraised Error 50000, Level 16, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 50000, Level 16, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 547, Level 16, State 1, Procedure UpdateResource, Line 220, Message: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ObjectValueBoolean_BindingInternal". The conflict occurred in database "FIMService", table "fim.BindingInternal".
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader()
   at Microsoft.ResourceManagement.Data.DataAccess.ProcessRequest(RequestType request)
   --- End of inner exception stack trace ---
    DateTime=2013-11-14T13:00:18.0405476Z

-------------------------------------------------------------------------------------------------

 

• I have admin rights in SQL, Sharepoint etc. Account belongs to the FIM administrators group.
• I performed an upgrade from 2010 to 2010 R2 with the same account last week.
• Sync Engine upgrades succesfully
• I've run the following match:

select * from FIMService.fim.BindingInternal INNER JOIN FIMService.fim.AttributeInternal on FIMService.fim.BindingInternal.AttributeName=FIMService.fim.AttributeInternal.Name

All BindingInternal AttributeNames are present in AttributeInternal Names.

Any of you has experienced this before?

Kind regards, Robin

• Edited by Robin Gaal Thursday, November 14, 2013 3:17 PM

Those where custom made scripts by microsoft specific for our database (we uploaded the complete SQL db to them). Let me see if I can find anything for you.. It's such a long time ago.

Well i've found the script. Its full with GUID's so I'm affraid it's not going to work for your specific installation (since your guids might be diffrent) and again it was a point solution for our specific corrupted DB problem. I would not advice you to run the script since it might make it even worse if you don't know what your doing. If you really insist I will post them so you can study them, but i do NOT advice you to run them.