Tuesday, January 29, 2013 7:26 PM
Im setting up a lab environment. I have installed SCSM DW and console, did pritty much what Carol did in this blogpost: http://www.wapshere.com/missmiis/installing-reporting-for-fim-r2
At the stage where Im gonna add FIM Reporting I get a error saying I have to install the KB2561430. This i apparently a hotfix for SCSM 2010 SP1. So, Im not able to install this hotfix in my environment since im running SCSM 2012.. Any ideas ? Im stuck.
Wednesday, February 06, 2013 8:29 PM
I got the same problem. I thought that FIM R2 with SP1 supports SCSM 2012 as written:
- Support for Windows Server 2012 has been added.
- Support for SQL Server 2012 has been added.
- Support for SCSM 2012 has been added.
What on earth is going on here Microsoft? We're all siting ducks here.
Sunday, February 10, 2013 8:47 PMAnyone from Microsoft who can help us here??
Wednesday, February 20, 2013 12:26 PM
Did you install SCSM 2012 SP1? I just want to see if it might be that FIM 2010 R2 SP1 only supports SCSM 2010 RTM. I'm getting the same issue in my lab. I've installed SCSM 2012 SP1.
Wednesday, February 20, 2013 12:32 PMCorrection SCSM 2010 RTM = SCSM 2012 RTM
Wednesday, February 20, 2013 12:59 PM
Looks like in the release notes http://technet.microsoft.com/en-us/library/jj863245(v=ws.10).aspx You should do an upgrade of SCSM. Just worried that it doesn't work from the install files on a fresh SCSM 2012 and this means you need to install on Windows 2008 R2 first, Then upgrade SCSM to 2012 and then upgrade to Windows 2012 OS.
I haven't tested the above yet but this is not a good solution.
Going to see if I can find a Microsoft resource to assist.
Wednesday, February 27, 2013 11:29 PM
Possible solution is:
FROM MS:There’s been some chatter on this topic internally and I have two pieces of information to share. Firstly a mismatch of versions between SCSM and SCDW can cause this check to fail, so be sure that both the SM instance(s) and the DW are running the same build.If the check still fails there is a workaround. A command line installation will work. If you have installed FIM and are enabling reporting be sure to utilise the EXISTINGDATABASE=1 option. If it’s a clean installation just do it as you would normally and the check will be skipped and the installation will succeed.
Thursday, February 28, 2013 7:29 PM
Yes thanks I've also logged a call and did a quick wiki on installing everything on Windows 2012, SQL 2012 and SCSM 2012 SP1:
Tuesday, March 19, 2013 6:11 AMCould you share what the command line install would be if you were trying to do a change rather than a new install to add the reporting feature?
Tuesday, March 19, 2013 7:54 AMJust add EXISTINGDATABASE=1 in your command line
Wednesday, March 20, 2013 2:25 PM
When I try and install it via command line I get this error 'another version of this product is already installed'. I currently have the portal and fim service installed and trying to add the third part - reporting. Does this look like the correct command line?
msiexec /i "<D:\Service and Portal\Service and Portal.msi>" ADDLOCAL=CommonServices,WebPortals SQMOPTINSETTING=0 SQLSERVER_SERVER=wgsql3 SQLSERVER_DATABASE=FIMService EXISTINGDATABASE=1 MAIL_SERVER=smtp.walshgroup.com MAIL_SERVER_USE_SSL=1 MAIL_SERVER_IS_EXCHANGE=1 POLL_EXCHANGE_ENABLED=1 /L*v C:\fimservicelog.txt