none
FIM Service Management Agent: Server -Stopped

    Question

  • Hiii

    I trying to run the FIM Service MA it receiving an error "FIM Service Management Agent: Server -Stopped' while running Full Import and Export..after researching this error it MS Forums I got to this link

    http://social.technet.microsoft.com/wiki/contents/articles/11331.troubleshooting-fim-r2-stopped-server-error-on-the-fim-service-management-agent.aspx

    In this link it says Run the Sync.ClearExport stored procedure  i couldn't find the navigation to do this.

    Any help will be appreciated!!

    Thanks

    Wednesday, August 28, 2013 4:34 PM

All replies

  • It's on the FIMService database. You may have checked the FIMSynchronizationService database instead.

    Thanks,

    Sami

    Wednesday, August 28, 2013 5:20 PM
  • I don't see it in them

    Wednesday, August 28, 2013 5:29 PM
  • Strange. Here's the proc. I'm assuming you are in a dev environment... Messing around with the FIM databases is not supported. But if you are in a dev env, this might help you.

    If not, you might want to look into running a repair of the FIM Service to see if it will bring the procedure back. (Take a back up first, of course.)

    USE

    [FIMService]


    GO



    /****** Object:  StoredProcedure [sync].[ClearExport]    Script Date: 08/28/2013 12:36:58 ******/


    SET

    ANSI_NULLS ON

    GO

    SET

    QUOTED_IDENTIFIER ON

    GO

    CREATE

    PROCEDURE [sync].[ClearExport]

        @trace         

    BIT             = NULL


    AS


    --********************************************************

    --*                                                      *

    --*   Copyright (C) Microsoft. All rights reserved.      *

    --*                                                      *

    --********************************************************


    BEGIN


       

    SET NOCOUNT ON;


       

       

    EXECUTE [fim].[AssertTransactionalContext]@requireTransaction = 0;

       

       

    BEGIN TRANSACTION


           

    EXECUTE [sync].[DoClearExport]@trace = @trace;


       

    COMMIT TRANSACTION

    END

    GO

    Wednesday, August 28, 2013 5:38 PM
  • Unfortunately this is in Prod Environment not sure if I can execute this....

    Thanks

    Wednesday, August 28, 2013 5:59 PM
  • Uday,

    This SPROC might not be there if this is not R2. What version of FIM are you using. The 2nd number will tell you if you are using R2, so 4.1.x is R2, 4.0.x is pre-R2. That article you refer to is for R2, not all of those steps would necessarily apply if using pre-R2 version.......

    Wednesday, August 28, 2013 6:38 PM
  • Hi Glenn-

    I'm using FIM 2010  V4.0.36.6.2, will there be a separate instructions to fix this on  FIM 2010?

    Thanks

    Thursday, August 29, 2013 9:20 AM
  • I've restarted FIM Sync server & FIM Server and rebooted machine and found event id:6324 ailed to connect to the database.... I've verified permissions it looks good on sql server.

    Any Idea what am I missing?


    "BAIL: MMS(1696): storeimp.cpp(234): 0x80004005 (Unspecified error)
    ERR: MMS(1696): server.cpp(373): Failed to connect to the database FIMSynchronizationService on HPVCPFIM02
    BAIL: MMS(1696): server.cpp(374): 0x80004005 (Unspecified error)
    BAIL: MMS(1696): server.cpp(3862): 0x80004005 (Unspecified error)
    BAIL: MMS(1696): service.cpp(1539): 0x80004005 (Unspecified error)
    ERR: MMS(1696): service.cpp(988): Error creating com objects. Error code: -2147467259. This is retry number 0.
    BAIL: MMS(1696): clrhost.cpp(224): 0x80131022 
    BAIL: MMS(1696): scriptmanagerimpl.cpp(7678): 0x80131022 
    BAIL: MMS(1696): server.cpp(251): 0x80131022 
    BAIL: MMS(1696): server.cpp(3862): 0x80131022 
    BAIL: MMS(1696): service.cpp(1539): 0x80131022 
    ERR: MMS(1696): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 1.
    BAIL: MMS(1696): clrhost.cpp(224): 0x80131022 
    BAIL: MMS(1696): scriptmanagerimpl.cpp(7678): 0x80131022 
    BAIL: MMS(1696): server.cpp(251): 0x80131022 
    BAIL: MMS(1696): server.cpp(3862): 0x80131022 
    BAIL: MMS(1696): service.cpp(1539): 0x80131022 
    ERR: MMS(1696): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 2.
    BAIL: MMS(1696): clrhost.cpp(224): 0x80131022 
    BAIL: MMS(1696): scriptmanagerimpl.cpp(7678): 0x80131022 
    BAIL: MMS(1696): server.cpp(251): 0x80131022 
    BAIL: MMS(1696): server.cpp(3862): 0x80131022 
    BAIL: MMS(1696): service.cpp(1539): 0x80131022 
    ERR: MMS(1696): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 3.
    BAIL: MMS(1696): service.cpp(1002): 0x80131022 
    Forefront Identity Manager 4.0.3606.2"
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="FIMSynchronizationService" />
        <EventID Qualifiers="49152">6324</EventID>
        <Level>2</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-08-28T00:12:40.000000000Z" />
        <EventRecordID>6522320</EventRecordID>
        <Channel>Application</Channel>
        <Computer>HPVCPFIM02.ihtech.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>BAIL: MMS(1696): storeimp.cpp(234): 0x80004005 (Unspecified error)
    ERR: MMS(1696): server.cpp(373): Failed to connect to the database FIMSynchronizationService on HPVCPFIM02
    BAIL: MMS(1696): server.cpp(374): 0x80004005 (Unspecified error)
    BAIL: MMS(1696): server.cpp(3862): 0x80004005 (Unspecified error)
    BAIL: MMS(1696): service.cpp(1539): 0x80004005 (Unspecified error)
    ERR: MMS(1696): service.cpp(988): Error creating com objects. Error code: -2147467259. This is retry number 0.
    BAIL: MMS(1696): clrhost.cpp(224): 0x80131022 
    BAIL: MMS(1696): scriptmanagerimpl.cpp(7678): 0x80131022 
    BAIL: MMS(1696): server.cpp(251): 0x80131022 
    BAIL: MMS(1696): server.cpp(3862): 0x80131022 
    BAIL: MMS(1696): service.cpp(1539): 0x80131022 
    ERR: MMS(1696): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 1.
    BAIL: MMS(1696): clrhost.cpp(224): 0x80131022 
    BAIL: MMS(1696): scriptmanagerimpl.cpp(7678): 0x80131022 
    BAIL: MMS(1696): server.cpp(251): 0x80131022 
    BAIL: MMS(1696): server.cpp(3862): 0x80131022 
    BAIL: MMS(1696): service.cpp(1539): 0x80131022 
    ERR: MMS(1696): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 2.
    BAIL: MMS(1696): clrhost.cpp(224): 0x80131022 
    BAIL: MMS(1696): scriptmanagerimpl.cpp(7678): 0x80131022 
    BAIL: MMS(1696): server.cpp(251): 0x80131022 
    BAIL: MMS(1696): server.cpp(3862): 0x80131022 
    BAIL: MMS(1696): service.cpp(1539): 0x80131022 
    ERR: MMS(1696): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 3.
    BAIL: MMS(1696): service.cpp(1002): 0x80131022 
    Forefront Identity Manager 4.0.3606.2</Data>
      </EventData>
    </Event>

    Thursday, August 29, 2013 1:37 PM
  • I would look at SQL server logs. I would think the above errors should generate something on the SQL side for this.
    Monday, September 02, 2013 3:33 PM
  • HI Glenn -

    Thanks for you reply..

    When I trigger FI for FIM MA  I see the below sql errors

    Log Name:      Application

    Source:        MSSQLSERVER

    Date:         

    Event ID:      17310

    Task Category: Server

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      FIM01

    Description:

    A user request from the session with SPID 115 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="MSSQLSERVER" />

        <EventID Qualifiers="49152">17310</EventID>

        <Level>2</Level>

        <Task>2</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2013-08-29T15:06:47.000000000Z" />

        <EventRecordID>323420485</EventRecordID>

        <Channel>Application</Channel>

        <Computer>FIM01</Computer>

        <Security />

      </System>

      <EventData>

        <Data>115</Data>

        <Binary>9E430000140000000B00000048005000560043005000460049004D0030003100000000000000</Binary>

      </EventData>

    </Event>

    Wednesday, September 04, 2013 9:29 AM
  • Uday,

    This still points to SQL issues. Please check the SQL server logs, the actual SQL service has log mechanism. You can see this by going to SQL Management Studio and choose management from the navigation bar and choose logs, it will show you logs from last several days(or weeks), I would that this should show something from the time that you saw the above event log errors.

    Saturday, September 07, 2013 6:15 AM
  • Glenn-

    I did some more troubleshooting by refreshing schema of FIMMA and updating the password of FIMMA Account during this process I see an error/Event ID 6331 I followed an article where it says to provide permission to 'BIN' folder, I did that but still no go there is another article referring to this Event 6331 "[Troubleshooting] Refresh Schema on FIM MA fails: Event ID 6331  where it says to swap the version number in 'miisserver.exe.config' file, before I would do this I would like to confirm from the FIM Experts will there be any addition issues if this didn't work by swapping versions? or there is no harm in doing this.

    Thanks

    Wednesday, September 11, 2013 9:35 AM
  • Do you not see the sync.ClearExport above sync.ConcludeExport (see below)? I cannot make out the sproc above sync.ConcludeExport in your screen clipping.

    sync.ClearExport

    Running this stored procedure for the error you described has helped me in the past. If it turns out you do have this stored procedure, I suggest following the steps in the link you provided. If you don't have the proper rights to execute this sproc, then perhaps a member of your DBA team with permissions to the FIMService database can execute it for you.

    Wednesday, September 18, 2013 5:31 PM