ILM 2007 to FIM Sync Engine Upgrade
I am conducting a FIM Sync Engine upgrade at a customer at the moment and I receive the following error. Anyone come across this? Just checking here for completeness sake before we start potentially chatting to PSS. We have a ILM 2007 (3.3.1165.2) database. We moved the DB to a new clean x64 (Windows Serv 2008 Standard) and (SQL Server 2008 R2 Standard). Upgrading the DB with the legacy database gives the following error: "Error 25009.The Forefront Identity Manager Synchronization Service setup wizard cannot configure the specified database. Invalid column name 'object_type'. Anyone come accross this. The only reference I can find is that upgrades are only supported from 3.2.xxxx upwards....
March 28th, 2011 4:28pm

I haven't come across this myself, but I'm wondering if it's complaining about a metaverse attribute name? The reason I suspect this is that I have seen underscores causing errors/unexpected behaviour in FIM schema before. So to test my theory just now I tried creating a brand new "object_type" attribute in the FIM Sync Server metaverse, and sure enough, look what happened ... --------------------------- Synchronization Service Manager --------------------------- Update metaverse schema failed. Exception from HRESULT: 0x80040E14 --------------------------- OK --------------------------- This is obviously a bug, but you can possibly work around the problem by locating and renaming your MV attribute if this is the same error you're witnessing in the conversion stage. With RC0 I had a problem once when creating the FIM MA for the first time - again a clash of existing schema, where a site had an existing objectSID attribute which clashed (case only) with the new objectSid attribute the FIM MA was trying to create ...Bob Bradley, www.unifysolutions.net (FIMBob?)
Free Windows Admin Tool Kit Click here and download it now
March 28th, 2011 4:59pm

Almero, just a sanity check: did you have a look at this article ("Troubleshooting FIM Installation Error 25009") yet? It's not entirely the same error message, but maybe you could use some info of it (like using the verbose error log and SQL trace...) Kind regards, PeterPeter Geelen (Traxion) - Sr. Consultant IDA (http://www.fim2010.be) [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or "Helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]
March 28th, 2011 5:24pm

BTW, have you checked you've set the correct database compatibility level? (Cfr this post, but SQL 2008 compat level in your case). HTH, Peter Peter Geelen (Traxion) - Sr. Consultant IDA (http://www.fim2010.be) [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or "Helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
March 28th, 2011 5:34pm

Hey Peter I have plyed with the database compatibility level - tried backup / restore options. None worked. I tried older (pre-3.3.1165.2 upgraded) databases. No change. I am familier with the Error25009 article and none of those seem to apply here - the error code is just the same :) (apparently). I have asked the client to create a seperate environment so I can test some more over the next day or so. Due to time constraints we transported the config to a clean FIM Sync Engine now - re-importing all data. (As a backup plan). Would still like to get more info about this - so hope to test some more in dev environment. Could not see any significant error in SQL Profiler either just now, but will run a few more traces. Just wanted to see if any of guys spotted this as something you have seen before. A
March 28th, 2011 6:04pm

Hey gents, It appears that this is an known issue relating to version mismatches. Here is a KB relating to it. http://support.microsoft.com/kb/2352595 We are currently testing this in a dev environment. Will get back to you. Almero
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2011 8:36am

Hey there It is confirmed. The error ""Error 25009.The Forefront Identity Manager Synchronization Service setup wizard cannot configure the specified database. Invalid column name 'object_type'" is resolved by downloading the updated stand-alone installer in the KB2352595 article. http://support.microsoft.com/kb/2352595 Al
April 4th, 2011 2:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics