Bugs
0
Fixed
Generated xMA cannot be created in FIM
Matthew Clark 13 years ago
in UNIFYBroker/Microsoft Identity Manager
•
updated by anonymous 6 years ago •
5
Generated management agents cannot be created successfully in FIM. The MA is visible in the drop down on the Create Management Agent screen, but attempting to configure it results in an "8023090D" error. No other information is available in the Windows event log.
8023090D.png
Customer support service by UserEcho
The problem was found to be a return in the XSLT, creating an illegal character next to the attribute name. Fixed, tested and closed.
Reopening - MA could be configured, but throws the following error when attempting to finalize the creation of the management agent:
The server encountered an unexpected error while performing an operation for the client.
"BAIL: MMS(6756): cdext.cpp(412): 0x80070057 (The parameter is incorrect.): Invalid element: MAConfig
BAIL: MMS(6756): xstack.cpp(402): 0x80070057 (The parameter is incorrect.)
BAIL: MMS(6756): xparse.cpp(428): 0x80070057 (The parameter is incorrect.)
ERR: MMS(6756): configxml.cpp(993): Exec XML: invalid element <apply-rules-subtype> value
reevaluate-flow-connectors
encountered
BAIL: MMS(6756): configxml.cpp(994): 0x80070057 (The parameter is incorrect.)
BAIL: MMS(6756): xstack.cpp(528): 0x80070057 (The parameter is incorrect.)
BAIL: MMS(6756): xparse.cpp(528): 0x80070057 (The parameter is incorrect.)
BAIL: MMS(6756): configxml.cpp(269): 0x80070057 (The parameter is incorrect.)
BAIL: MMS(6756): runconfig.cpp(2261): 0x8023062e (The specified XML has an invalid format.)
BAIL: MMS(6756): runconfig.cpp(832): 0x8023062e (The specified XML has an invalid format.)
BAIL: MMS(6756): runconfig.cpp(569): 0x8023062e (The specified XML has an invalid format.)
BAIL: MMS(6756): runconfig.cpp(445): 0x8023062e (The specified XML has an invalid format.)
BAIL: MMS(6756): mastate.cpp(1857): 0x8023062e (The specified XML has an invalid format.)
BAIL: MMS(6756): server.cpp(1029): 0x8023062e (The specified XML has an invalid format.)
This was found again to be a problem with spacing in the management agent. Once the management agent was created, any further operation results in a stopped-extension-dll-instantiation exception.
The instantiation exception was thought to be an issue with the FIM Portal configuration on the machine (see
IDB-197) as the portal threw errors at the same time the management agent was changed. The FIM Portal issues have been resolved, but this error message is still appearing.The adapter did not have the proxy assembly properly embedded. The app.config was also no longer correct. Tested in FIM with both endpoints, with Identity Broker logs showing an attempt to import/export was made. Issue closed.