none
FIM2010R2 PowerShell Connector - Create new MA gives error E_MMS_SCHEMA_CLASS_NOT_FOUND RRS feed

  • Question

  • When i try to create a new Powershell MA (Microsoft) i manage to get the schema from my Powershell script and can select an anchor to use sucessfully, but at the end i Always gets this error and i have tried to use the scripts from following link http://technet.microsoft.com/en-us/library/dn640417(v=ws.10).aspx but Always the same error, and i also enabled logging but this gave no more info.

    Log Name:      Application
    Source:        FIMSynchronizationService
    Date:          2014-03-19 11:12:13
    Event ID:      6306
    Task Category: Server
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      {Fim Server}
    Description:
    The server encountered an unexpected error while performing an operation for the client.
     
     "BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\maxml\cdext.cpp(416): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xstack.cpp(405): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xparse.cpp(436): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\server\schema\schema.cpp(1619): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\maxml\compmap.cpp(155): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\maxml\compmap.cpp(453): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xsimple.cpp(842): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xstack.cpp(540): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xparse.cpp(544): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xsimple.cpp(334): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\maxml\compmap.cpp(344): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\server\mastate\mastate.cpp(10645): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    ERR_: MMS(4436): d:\bt\25920\private\source\miis\server\mastate\mastate.cpp(13144): Error creating MA component mappings object: 0x80230914
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\server\mastate\mastate.cpp(13164): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\server\mastate\mastate.cpp(1724): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\server\server\server.cpp(1090): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    Forefront Identity Manager 4.1.3508.0"
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="FIMSynchronizationService" />
        <EventID Qualifiers="49152">6306</EventID>
        <Level>2</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-03-19T10:12:13.000000000Z" />
        <EventRecordID>110463</EventRecordID>
        <Channel>Application</Channel>
        <Computer>{FIM Server}</Computer>
        <Security />
      </System>
      <EventData>
        <Data>BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\maxml\cdext.cpp(416): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xstack.cpp(405): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xparse.cpp(436): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\server\schema\schema.cpp(1619): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\maxml\compmap.cpp(155): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\maxml\compmap.cpp(453): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xsimple.cpp(842): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xstack.cpp(540): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xparse.cpp(544): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\xmlpe\xsimple.cpp(334): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\shared\maxml\compmap.cpp(344): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\server\mastate\mastate.cpp(10645): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    ERR_: MMS(4436): d:\bt\25920\private\source\miis\server\mastate\mastate.cpp(13144): Error creating MA component mappings object: 0x80230914
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\server\mastate\mastate.cpp(13164): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\server\mastate\mastate.cpp(1724): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    BAIL: MMS(4436): d:\bt\25920\private\source\miis\server\server\server.cpp(1090): 0x80230914 (E_MMS_SCHEMA_CLASS_NOT_FOUND)
    Forefront Identity Manager 4.1.3508.0</Data>
      </EventData>
    </Event>


    Ulf Lindström

    Wednesday, March 19, 2014 10:20 AM

Answers

  • Ok, I got some info on this.

    1. Set “Distinguished Name Style” in capabilities to “LDAP” 

    2. Remove the DN component mapping in the "Configure Provisioning Hierarchy" screen.

    This will help to create the connector successfully”

    For the other “Distinguished Name Style” in capabilities ("None" and "Generic") it looks like there need to be some work from the product team.

    Thursday, March 27, 2014 11:58 AM

All replies

  • Hi!

    I just wanted to tell you I have the same problem, both with our code witch we have been running for months now with the Beta version and when we try to use the Example code from Technet.

    I have registered a case with MS on this 2 days ago and will update you when it's sovled.

    /Robert

    Wednesday, March 19, 2014 7:57 PM
  • Just got the following info and I have also verified it.

    The following parameters witch is sent to the scripts has been changed.

    $types -> $schema

    $credential -> $psCredential

    $parentNode -> $hierarchyNode

    /Robert

    Friday, March 21, 2014 9:30 AM
  • Thanks!

    But did this helped? i tried to change the scripts i have, but no change
    this is what i understand has been changed

    :GetSchema
    param(   
        [System.Collections.ObjectModel.KeyedCollection[[string], [Microsoft.MetadirectoryServices.ConfigParameter]]]
        $ConfigParameters,
        [PSCredential]
        $psCredential
    )

    :importData
    param(   
        [System.Collections.ObjectModel.KeyedCollection[[string], [Microsoft.MetadirectoryServices.ConfigParameter]]]
        [ValidateNotNull()]
        $ConfigParameters,
        [Microsoft.MetadirectoryServices.Schema]
        [ValidateNotNull()]
        $schema,
        [Microsoft.MetadirectoryServices.OpenImportConnectionRunStep]
        $OpenImportConnectionRunStep,
        [Microsoft.MetadirectoryServices.ImportRunStep]
        $GetImportEntriesRunStep,
        [PSCredential]
        $psCredential
    )


    Ulf Lindström


    Friday, March 21, 2014 10:39 AM
  • It seems right.

    But as I said this was not the solution for creating the MA just a note for Changes they made that are not in documentation.

    Friday, March 21, 2014 11:56 AM
  • Ok, I got some info on this.

    1. Set “Distinguished Name Style” in capabilities to “LDAP” 

    2. Remove the DN component mapping in the "Configure Provisioning Hierarchy" screen.

    This will help to create the connector successfully”

    For the other “Distinguished Name Style” in capabilities ("None" and "Generic") it looks like there need to be some work from the product team.

    Thursday, March 27, 2014 11:58 AM
  • Thanks!

    That did the trick i got it up and running, Now i just have to get my remote script to work.


    Ulf Lindström

    Thursday, March 27, 2014 1:58 PM
  • Robert;

    Thank you for your post, I had the same Error as you did E_MMS_SCHEMA_CLASS_NOT_FOUND

    I also resolved it by setting the DN style to LDAP and removing the DN component per your post.

    Thank you for posting that work around! 

    -Jonathan


    • Edited by jmanley WI Friday, April 18, 2014 3:01 PM
    Friday, April 18, 2014 3:00 PM