none
The current version of database is not compatible with the one expected by Forefront Identity Manager service

    Question

  • Our FIM recently went through a botched upgrade and now the service is unable to connect to the database.  The event log is flooded with Event 3.

    The current version of database is not compatible with the one expected by Forefront Identity Manager service. The current version of the database is : 1116. The expected version is : 1112.

    The Forefront Identity Manager Management Agent does not support the current Forefront Identity Manager Resource Management Service database version.
    Help would be very appreciated.  Thanks in advance!


    - Get on the floor, do that dinosaur

    Wednesday, July 31, 2013 4:41 PM

All replies

  • I would re-apply the FIM Service patch that you're trying to be on and that should upgrade the database.

    My Book - Active Directory, 4th Edition
    My Blog - www.briandesmond.com

    Wednesday, July 31, 2013 5:00 PM
    Moderator
  • I tried that and it rolls back after the service fails to start.  The install log says to check the install accounts permissions but I am using the FIM Admin service account.  

    - Get on the floor, do that dinosaur

    Wednesday, July 31, 2013 6:49 PM
  • Try launching the patch from an elevated command prompt with msiexec /p


    My Book - Active Directory, 4th Edition
    My Blog - www.briandesmond.com

    Wednesday, July 31, 2013 7:03 PM
    Moderator
  • I did  
    msiexec.exe /p FIMService_x64_KB2814853.msp /l*v C:\FIMAdminLog.log


    - Get on the floor, do that dinosaur

    Wednesday, July 31, 2013 7:12 PM
  • Can you paste the relevant chunk of the log?

    My Book - Active Directory, 4th Edition
    My Blog - www.briandesmond.com

    Wednesday, July 31, 2013 7:41 PM
    Moderator
  • yup

    MSI (s) (7C:54) [13:25:10:565]: PROPERTY CHANGE: Adding SetServiceRecoveryActions property. Its value is '"C:\Windows\system32\sc.exe" failure FIMService reset= 86400 actions= restart/6000/restart/6000/""/0'.
    Action ended 13:25:10: SetServiceRecoveryActionsProperty. Return value 1.

    and

    Error 1920. Service 'Forefront Identity Manager Service' (FIMService) failed to start. Verify that you have sufficient privileges to start system services.
    MSI (s) (7C:54) [13:26:21:100]: Product: Forefront Identity Manager Service and Portal -- Error 1920. Service 'Forefront Identity Manager Service' (FIMService) failed to start. Verify that you have sufficient privileges to start system services.
    

    and maybe

    MSI (c) (8C:50) [13:27:07:917]: Note: 1: 2262 2: Binary 3: -2147287038 
    Error 1920. Service 'Forefront Identity Manager Service' (FIMService) failed to start. Verify that you have sufficient privileges to start system services.
    MSI (s) (7C:48) [13:27:14:277]: I/O on thread 5296 could not be cancelled. Error: 1168
    MSI (s) (7C:48) [13:27:14:277]: I/O on thread 3264 could not be cancelled. Error: 1168
    MSI (s) (7C:48) [13:27:14:277]: I/O on thread 3652 could not be cancelled. Error: 1168
    MSI (s) (7C:48) [13:27:14:277]: I/O on thread 1832 could not be cancelled. Error: 1168
    MSI (s) (7C:48) [13:27:14:277]: I/O on thread 4664 could not be cancelled. Error: 1168
    MSI (s) (7C:48) [13:27:14:277]: I/O on thread 5460 could not be cancelled. Error: 1168
    MSI (s) (7C:48) [13:27:14:277]: I/O on thread 1272 could not be cancelled. Error: 1168
    MSI (s) (7C:48) [13:27:14:277]: I/O on thread 5748 could not be cancelled. Error: 1168
    MSI (s) (7C:48) [13:27:14:277]: I/O on thread 4036 could not be cancelled. Error: 1168
    MSI (s) (7C:48) [13:27:14:277]: I/O on thread 5904 could not be cancelled. Error: 1168
    MSI (s) (7C:54) [13:27:14:278]: Product: Forefront Identity Manager Service and Portal -- Error 1920. Service 'Forefront Identity Manager Service' (FIMService) failed to start. Verify that you have sufficient privileges to start system services.
    

    Again, I am using the FIM Admin account.


    - Get on the floor, do that dinosaur

    Wednesday, July 31, 2013 7:50 PM
  • Is there an ACL on the service that would remove rights to start it? You can do that.

    My Book - Active Directory, 4th Edition
    My Blog - www.briandesmond.com

    Wednesday, July 31, 2013 7:52 PM
    Moderator
  • No, theres no ACL on the service itself.  It is (or should be) starting with the FIM Admin account as well which is also a Domain Admin for troubleshooting purposes.  Does the account need special perms in the SQL database to start the service that may have been wiped during the failed upgrade? I'm reaching here, I know

    - Get on the floor, do that dinosaur

    Wednesday, July 31, 2013 8:18 PM
  • Did you backup the FIM Service DB? If so, can you just roll back to the pre-upgrade version, start the FIM Service again then re-apply the patch?


    Dave Nesbitt | Architect | Oxford Computer Group

    Thursday, August 01, 2013 9:44 AM
  • Unfortunately, no.  The DB was not backed up prior to the first attempt of applying the patch so I assume we are stuck with moving forward in finding a way to apply the patch successfully.  

    Unless, back to my original error where the database is looking for the wrong version, is there a way to correct that?  Does anyone know of a script/query that could either apply the correct DB version number to the DB, or change the version number that FIM is expecting to the version number of the DB?


    - Get on the floor, do that dinosaur

    Thursday, August 01, 2013 1:23 PM