Migrating from ILM to FIM All the existing ILM data are in FIM. When attempt to create FIM Service Management Agent, on the Update MV schema step, and click Next, the following error occur – ‘ Modify mv data fails: Exception from HRRESULT: 0x80040E14’. what would cause it? Thank you

Assuming you've upgraded the ILM database to FIM already without issue. Assuming you're install the FIM Service and Portal, and are now trying to create your first FIM MA. Are you getting the error when creating the FIM MA?CraigMartin Edgile, Inc. http://identitytrench.com

Yes, didn't have issue upgrade the ILM database, installed FIM sync service, service and portal on a Windows 2008 Server R2 Enterprise. tried to create our first FIM MA, and got error - ‘ Modify mv data fails: Exception from HRRESULT: 0x80040E14’ Application Log: The server encountered an unexpected error while performing an operation for the client. "ERR: MMS(1900): sql.cpp(5583): Query ({call mms_CorrectMvAttributesLength}) performed with error ERR: MMS(1900): sql.cpp(5636): ALTER TABLE ALTER COLUMN pwdException failed because one or more objects access this column. ERR: MMS(1900): sql.cpp(5644): hrError: 0x80040e14, dwMinor: 4922 ERR: MMS(1900): sql.cpp(5799): SQL error: 42S03, native: 4922 ERR: MMS(1900): sql.cpp(5636): The statistics 'pwdException' is dependent on column 'pwdException'. ERR: MMS(1900): sql.cpp(5644): hrError: 0x80040e14, dwMinor: 5074 ERR: MMS(1900): sql.cpp(5799): SQL error: 42S03, native: 5074 BAIL: MMS(1900): sql.cpp(7250): 0x80040e14 BAIL: MMS(1900): sql.cpp(7054): 0x80040e14 BAIL: MMS(1900): sproc.cpp(3831): 0x80040e14 BAIL: MMS(1900): session.cpp(453): 0x80040e14 BAIL: MMS(1900): server.cpp(2630): 0x80040e14 Forefront Identity Manager 4.0.2592.0"

OK, I was going to suggest you try this: Using PowerShell to do a FIM MA account configuration quick test But the ERR looks more like a problem Brad Turner ran into pre-RTM. AFAIK that bug was fixed. Are you on the latest FIM bits?CraigMartin Edgile, Inc. http://identitytrench.com

I installed the latest FIM 2010 Synchroization Service Update KB978864, and still getting the same error.

If I see a BAIL: message from ILM/FIM, I call PSS. Please let us know when/how your issue is resolved. -Jeremy

Our custom attribute type (from ILM) isn't compatible with FIM, throwing error while FIM try to update the schema for the frist time. We delete the SQL statistics for those attributes in FIMSynchronizationService database, and it works now.

Can you tell me what table is holding these stats? Granted I could look through them all but was curious if you knew right off hang. Thanks!!