Hi, It seems that every time we attempt to patch FIM Service with Roll Up, the following error message appears: The database upgrade tool has encountered errors when upgrading the database. The Error Messages: Execute SQL : The upgrade tool has rolled back. The sql transaction running the script PreProcess0027.sql failed. Exception: System.Data.SqlClient.SqlException: Cannot insert the value NULL into column 'DataTypeKey', table 'FIMService.fim.MembershipConditionStatement'; column does not allow nulls. UPDATE fails. The statement has been terminated. 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.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.IdentityManagement.DatabaseUpgrade.Program.ExecuteSqlScript(SqlConnection connection, String sqlFile, Boolean embeddedAsResource, Boolean continueOnError) Execute SQL : The upgrade tool has rolled back. The sql transaction running the script Upgrade0027.sql failed. Exception: System.Data.SqlClient.SqlException: Invalid column name 'TabularFunctionValueKey'. Invalid column name 'TabularFunctionValueKey'. Invalid column name 'TabularFunctionValueKey'. Invalid column name 'TabularFunctionValueKey'. 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.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.IdentityManagement.DatabaseUpgrade.Program.ExecuteSqlScript(SqlConnection connection, String sqlFile, Boolean embeddedAsResource, Boolean continueOnError) Execute SQL : The upgrade tool has rolled back. The sql transaction running the script PostProcess0027.sql failed. Exception: System.Data.SqlClient.SqlException: Invalid object name 'fim.MembershipConditionStatementString'. Optimizing membership condition statement string literals ... 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.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.IdentityManagement.DatabaseUpgrade.Program.ExecuteSqlScript(SqlConnection connection, String sqlFile, Boolean embeddedAsResource, Boolean continueOnError) Anyone would have any idea? Thank you.

L Ali, Hopefully you opened a ticket with support. Did you ever get it resolved? It sounds like something was wrong with your ForefrontIdentityManager Database.David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

Hello, i am also looking for a solution of this error, as we currently have the same issue within out development environment, another (nearly identical) environment does not have this problem, and hotfix installed properly. regards Peter

This is a known issue that will be fixed in the upcoming May 2012 hotfix for FIM 2010.

We actually had this issue. We had to install the previous hotfix and then install rollup 2. We wasted 2 days on this. Very lame.