Identity Broker Forum

Welcome to the community forum for Identity Broker.

Browse the knowledge base, ask questions directly to the product group, or leverage the community to get answers. Leave ideas for new features and vote for the features or bug fixes you want most.

0
Answered

Boolean Constant attribute appears as String in connector space

Matthew Woolnough 7 years ago updated by anonymous 7 years ago 13

As shown in the image below, Boolean constant appears as a string in the Connector Space. 



Image 4169

Answer
anonymous 7 years ago

Without knowing what sharing exists in MIM between MAs for identical object types and attributes, it seems you have a bug on your hands. You've demonstrated that we are reporting the correct type to MIM and that MIM is capable of understanding the schema correctly, but for some reason with that name it's stuck thinking it's a string. You'll have to either raise a support ticket with Microsoft, or stick to the changed field name and move on.

0
Fixed

Identity Broker Service 5.1 Installation/Upgrade Setup Wizard Ended Prematurely

Aneesh Varghese 8 years ago updated by anonymous 7 years ago 11

Identity Broker Service Installation/upgrade Setup Wizard Ended Prematurely. Here are the version details:

Current Version • Identity Broker Service v4.1.4 RTM x64

Target Version

• Identity Broker Service v5.1.0.2 RTM x64

Please see the attached screenshots.

Image 4148

Image 4147

Answer
anonymous 8 years ago

Service just started fine. Indeed it is strange why the installer failed for the very first time. I will let you know if I see the similar behavior in the next environment (UAT).  So for now, it can be closed. Thanks for your help. Cheers 

0
Answered

Unify.Service.Connect.exe using large amounts of RAM and unresponsive

Matthew Woolnough 8 years ago updated by anonymous 7 years ago 37

The Unify Service.Connect process is currently using 786084KB RAM and is unresponsive.  It's not writing to Logs and restarting the service has not killed the process. 


PS C:\Unify> Get-Process -Name Unify.Service.Connect

Handles  NPM(K)    PM(K)      WS(K)     CPU(s)     Id  SI ProcessName
-------  ------    -----      -----     ------     --  -- -----------
 209907    5995  2926564     786084  10,599.94  23692   0 Unify.Service.Connect


Answer
anonymous 7 years ago

I have not seen this issue since the last update. Not sure why that is. No significant changes to the environment have occurred. Probably best to close it & Ill re-open if it arises again .

0
Fixed

DataTables warning: table id=Logs - Invalid JSON response

Matthew Woolnough 8 years ago updated by anonymous 8 years ago 7

Clicking on the last page of Logs often throws the following error:


---------------------------
Message from webpage
---------------------------
DataTables warning: table id=Logs - Invalid JSON response. For more information about this error, please see http://datatables.net/tn/1
---------------------------
OK  

---------------------------

The user cannot access that page. 

Answer
anonymous 8 years ago

Hi Matthew, I believe I was able to track down and fix this issue. If you're able to test please take a look at:

Unify.Framework.Logging.Writer.dll

0
Answered

Change Core Log location

Matthew Woolnough 8 years ago updated by Adam van Vliet 7 years ago 2

Core Logs are being written to C:\Program Files\UNIFY Solutions\Identity Broker\Services\Logs There doesn't seem to be a place to do this in the UI.

Answer
anonymous 8 years ago

Hi Matt,

This location currently can't be changed. If you need to log to a different directory, you can create another CSV log writer configured to log to the desired directory. Alternatively, you could try replacing the C:\Program Files\UNIFY Solutions\Identity Broker\Services\Logs directory with a symbolic link to the desired directory.

0
Fixed

Schema Provider errors with "Value cannot be null. Parameter name: key"

Matthew Woolnough 8 years ago updated by anonymous 8 years ago 1

On some of the other connectors when I attempt to request schema, I get the error "Value cannot be null. Parameter name: key".

Answer
anonymous 8 years ago

Please extract Web.zip and follow the folder hierarchy to update ApplySchemaProvider.cshtml

0
Fixed

Adapter object doesn't have corresponding object in Connector resulting in "duplicate-objects error"

Tom Parker 8 years ago updated by anonymous 8 years ago 4

This is related to http://voice.unifysolutions.net/topics/2674-idb-51-returning-duplicate-objects-that-only-exist-once-in-the-adapterconnector/ although the bug is now exhibiting new characteristics and the work around is no longer working.

Image 4007

Drilling down on one of these records we can see that they exist twice in IdB adaptor but only once in the connector:

Image 4008

Image 4009

The second entry in the adaptor was once correct but has since been removed from the source system (as this is to do with student enrollments that's a normal procedure). According to Andrew Silcock's notes in the linked job, previously the entries only existed in the adaptor once.



0
Declined

Cannot create a DN in the format UID=-12345

Bob Bradley 8 years ago updated by anonymous 8 years ago 4

It would be great to be able to extend the definition of a valid IdB DN to include the "-".

The following error is raised when attempting to export a new record to an underlying SQL entity via IdB4:

Log Name:      Application
Source:        FIMSynchronizationService
Date:          13/04/2017 3:07:52 PM
Event ID:      6801
Task Category: Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CENTRELINK-FIM.unifyfim.unifytest.local
Description:
The extensible extension returned an unsupported error.
 The stack trace is:
 
 "System.Exception: Error occurred when attempting to save entity with distinguished name

UID=-281283620

Error:

1 items failed schema validation during Adapter operation.  Check log for validation errors.
   at Unify.Product.IdentityBroker.Adapter.GetReverseTransformedEntities(IEnumerable`1 entities)
   at Unify.Product.IdentityBroker.Adapter.AddEntities(IEnumerable`1 entities, EntityToConnectorEntityBridge[]& backwardAdapterEntities)
   at Unify.Product.IdentityBroker.Adapter.AddEntities(IEnumerable`1 entities)
   at Unify.Product.IdentityBroker.AdapterNotifierDecoratorBase`1.AddEntity(IAdapterEntity entity)
   at Unify.Product.IdentityBroker.AdapterNotifierDecoratorBase`1.AddEntity(IAdapterEntity entity)
   at Unify.Product.IdentityBroker.LDIFAdapterBase.HandleExportAdd(IAdapter adapter, IAdapterEntitySaveChange pendingAdd)
   at Unify.Product.IdentityBroker.LDIFAdapterBase.ExportChanges(ExportedLDIFForAdapter exportedLdifForAdapter)
   at SyncInvokeExportChanges(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
   at Unify.Product.IdentityBroker.IdentityBrokerManagementAgentProxy.ExportEntry(ModificationType modificationType, String[] changedAttributes, CSEntry csentry)
   at Unify.Product.IdentityBroker.IdentityBrokerManagementAgent.ExportEntry(ModificationType modificationType, String[] changedAttributes, CSEntry csentry)
Forefront Identity Manager 4.0.3732.2"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="FIMSynchronizationService" />
    <EventID Qualifiers="49152">6801</EventID>
    <Level>2</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-13T05:37:52.000000000Z" />
    <EventRecordID>2307483</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CENTRELINK-FIM.unifyfim.unifytest.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>System.Exception: Error occurred when attempting to save entity with distinguished name

UID=-281283620

Error:

1 items failed schema validation during Adapter operation.  Check log for validation errors.
   at Unify.Product.IdentityBroker.Adapter.GetReverseTransformedEntities(IEnumerable`1 entities)
   at Unify.Product.IdentityBroker.Adapter.AddEntities(IEnumerable`1 entities, EntityToConnectorEntityBridge[]& backwardAdapterEntities)
   at Unify.Product.IdentityBroker.Adapter.AddEntities(IEnumerable`1 entities)
   at Unify.Product.IdentityBroker.AdapterNotifierDecoratorBase`1.AddEntity(IAdapterEntity entity)
   at Unify.Product.IdentityBroker.AdapterNotifierDecoratorBase`1.AddEntity(IAdapterEntity entity)
   at Unify.Product.IdentityBroker.LDIFAdapterBase.HandleExportAdd(IAdapter adapter, IAdapterEntitySaveChange pendingAdd)
   at Unify.Product.IdentityBroker.LDIFAdapterBase.ExportChanges(ExportedLDIFForAdapter exportedLdifForAdapter)
   at SyncInvokeExportChanges(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
   at Unify.Product.IdentityBroker.IdentityBrokerManagementAgentProxy.ExportEntry(ModificationType modificationType, String[] changedAttributes, CSEntry csentry)
   at Unify.Product.IdentityBroker.IdentityBrokerManagementAgent.ExportEntry(ModificationType modificationType, String[] changedAttributes, CSEntry csentry)
Forefront Identity Manager 4.0.3732.2</Data>
  </EventData>
</Event>

I don't see why this should be an invalid DN - e.g. it is perfectly acceptable in ADLDS.

The reason for wanting to do this was in a test scenario where I need to enforce uniqueness so I don't clash with an existing range of identities - so flipping the sign was the simplest way to achieve this.

In the end I was able to come up with another way of generating a unique ID, but I thought this deserved consideration anyhow.

Answer
anonymous 8 years ago

Closed, not enough information provided.

0
Not a bug

BadImageFormatException on service startup

Matthew Woolnough 8 years ago updated by anonymous 8 years ago 4

Attempting new install of IdB 5.1 on Windows 2016. Installing Aurion connector 5.0.1 and trying to create the agent. The configuration section of the Agent is missing.

Error below is seen in logs:

20170502,22:32:16,UNIFY Identity Broker,Service Engine,Warning,"An error occurred whilst coordinating the plug-in engine. The error was:
System.BadImageFormatException: Could not load file or assembly 'file:///C:\Program Files\UNIFY Solutions\Identity Broker\Services\Unify.Service.Connect32.exe' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'file:///C:\Program Files\UNIFY Solutions\Identity Broker\Services\Unify.Service.Connect32.exe'

How can I get the configuration section displayed so I can configure it?

Answer
anonymous 8 years ago

That gets logged with Verbose logging - there's nothing actually wrong. It may be fixed in v5.2.

To use v5.1 you'll have to install a v5.1.x connector.

0
Answered

MA stopped-extension-dll-exception

Eddie Kirkman 8 years ago updated by anonymous 7 years ago 3

Our Identity broker MA is failing on its Delta Imports with the ever helpful "stopped-extension-dll-exception" error.

From Event Viewer, I get:

The extensible extension returned an unsupported error.
The stack trace is:

"Unify.Product.IdentityBroker.LdapOperationException: Error during processing of SearchRequest targetting cn=changelog: Operation timed out while waiting for message queue with id of 10. ---> System.OperationCanceledException: Operation timed out while waiting for message queue with id of 10.
at Unify.Product.IdentityBroker.LdapConnection.GetMessage(Int32 messageId)
at Unify.Product.IdentityBroker.SearchRequest.Send(Func`2 send, Func`2 recv)
at Unify.Product.IdentityBroker.LdapConnection.SendRequest(ILdapRequest request)
--- End of inner exception stack trace ---
at Unify.Product.IdentityBroker.LdapConnection.SendRequest(ILdapRequest request)
at Unify.Product.IdentityBroker.LdapConnectionProxy.<SearchRequestPaged>d__8.MoveNext()
at Unify.Product.IdentityBroker.ImportProxy.<GetChangedEntriesPaged>d__30.MoveNext()
at System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()
at Unify.Product.IdentityBroker.ExtensionMethods.Take[TSource](IEnumerator`1 source, Int32 count, IList`1& items)
at Unify.Product.IdentityBroker.ExtensionMethods.<Page>d__3`1.MoveNext()
at Unify.Product.IdentityBroker.ImportProxy.Import(GetImportEntriesRunStep importRunStep)
Forefront Identity Manager 4.3.2266.0"

Apart from the fact that there was a dll exception, any idea what this is about or where to look for more useful information? I am seeing nothing with any errors in the IdB logs.

Answer
anonymous 7 years ago

Please try with the patch from http://voice.unifysolutions.net/topics/2672-delta-import-timeouts-on-identity-broker-51-management-agents/ (Unify.IdentityBroker.ChangeLog.Repository.Sql.dll - for the appropriate version of Identity Broker).