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.
Additional display information if a connector would never run
If a connector has been configured with a schedule that would never run, it would be good to have some additional feedback on this on the connector page. The only way you can see if this is the case is if you mouseover the little clock on the home page. It would be good if some additional UI feedback is given, either in the form of:
- Information on the schedule display stating that a particular schedule would never run
- An alert to the home page that such a configuration exists
- A header on the connector page stating the connector won't run
- A combination of these
Feedback on schema validation to be improved
In testing for IDBCHRS-34, it has been found that some instances of the Chris21 connectors were correctly committing entities to the database, while some are not. Debugging shows that the connector is correctly pulling entities from the target system, meaning these are being lost before committing to the database.
UPDATE: This was found to be an issue with schema validation causing the commit to fail on the "IncludeItem" step. However, the feedback to the user at the moment is insufficient, and you can only find this by viewing the Identity Broker logs. The following should be added:
- A warning message should be raised and displayed on the statistics page - for v4.0, this should point the user to the logs. A larger set of work would be to collect all the entities that failed validation and display this following an import.
- Raise an alert with the alert engine
- The following error message should be updated to include the schema key for readability and ease of use, rather than the Entity Id:
The entity 55d751c6-0409-4bc0-9e09-1302e715feef on the f3df77ea-0084-4480-84a7-02125264899d connector Chris21 DET failed validation 3 times for the following reasons: detbirdate is a required field and is not present.; detsex is a required field and is not present.; detterdate is a required field and is not present.
Schema Validation Message.png
Cannot delete Join mappings on idB4.1
When attemping to delete join mappings on idb4.1 I receive "The resource cannot be found"
Currently unable to configure joins without this ability
error1.png
Error2.png
Connector full import synchronization aborts encompassing transaction against large number of deletes (> 500,000 entities)
A connector full import/sync that results in a large number of deletions (> 500,000) will abort its respective encompassing TransactionScope.
The following was additionally observed when the TransactionScope was observed to abort:
- When debugging, the TransactionScope itself is registered as complete. (TransactionScope::complete = true)
- From this, it can be potentially inferred that the problem itself happens either on the MSDTC or SQL Server end - as far as the IdB application is concerned, the TransactionScope completed.
- The exception was thrown during IDB ChangeDetection.
- If debugging, ensure that break on all exceptions is enabled.
- During the import, in the respective SQL traces, a substantial number of entries were logged with the following EventClass and ApplicationName.
EventClass: Lock:Timeout ApplicationName: .Net SqlClient Data Provider
Stack empty exceptions from full imports
With the latest build of Framework, the following error appears when trying to run an adapter full import using ECMA 1:
Stack empty
at System.Collections.Generic.Stack`1.Pop()
at Unify.Framework.Collections.GenericStack`1.Pop() in c:\workspaces\DEV\FrameworkCore\Source\Collections\Unify.Framework.Collections\Collections\GenericStack.cs:line 71
at Unify.Framework.Collections.Scope`1.Dispose() in c:\workspaces\DEV\FrameworkCore\Source\Collections\Unify.Framework.Collections\Scope\Scope.cs:line 79
at Unify.Framework.Notification.ProcessScope.Dispose() in c:\workspaces\DEV\FrameworkCore\Source\Notification\Unify.Framework.Notification.Core\ProcessScope.cs:line 59
at Unify.Framework.Notification.TaskNotifier`1.Dispose() in c:\workspaces\DEV\FrameworkCore\Source\Notification\Unify.Framework.Notification.Core\TaskNotifier_T.cs:line 80
at Unify.Framework.Notification.NotificationEnumerableExtensions.<>c_DisplayClass3`1.<Notify>b_2() in c:\workspaces\DEV\FrameworkCore\Source\Notification\Unify.Framework.Notification.Core\NotificationEnumerableExtensions.cs:line 62
at Unify.Framework.Collections.EnumerableExtensions.<ActionOnLast>d__17`1.MoveNext() in c:\workspaces\DEV\FrameworkCore\Source\Collections\Unify.Framework.Collections\Collections\EnumerableExtensions.cs:line 261
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()
at System.Linq.Enumerable.<ConcatIterator>d__71`1.MoveNext()
at Unify.Framework.IO.LDIFComponentFileGenerator`1.GenerateFile(TextWriter writer, IEnumerable`1 entries) in c:\workspaces\DEV\FrameworkCore\Source\IO\Unify.Framework.IO.LDIF\LDIFComponentFileGenerator.cs:line 46
at Unify.Product.IdentityBroker.LDIFAdapterBase.<>c_DisplayClass14`1.<CreateLDIFComponentStream>b_13(Stream stream) in S:\Hg\Product\IdentityBroker\IdentityBroker\Source\Adapter\Unify.IdentityBroker.Adapter.Remoting\LDIFAdapterBase.cs:line 399
at Unify.Framework.IO.LazyEvaluationStream.Evaluate(Object obj) in c:\workspaces\DEV\FrameworkCore\Source\IO\Unify.Framework.IO\LazyEvaluationStream.cs:line 124
This is appearing in the serialization/ECMA 2 branch, but may also be occurring in default.
Relational transformation contributions do not seem to be flagging changes
Relational transformation contributions do not properly seem to be detecting changes. With the following configuration, I modify the value posnumber which has been added to the adapter via a relational transformation. However, no changes are flagged for the adapter following change detection, even though 1 change is picked up by the change reports. This is because FindBaseEntities in RelationalTransformationContribution is returning no entities following the Zip statement, even though the changes are correctly passed to the method.
Moreover, where I have had other relational changes being picked up, it seems that these are the result of simpler transformations such as Time Offset.
Unify.Product.IdentityBroker.AdapterEnginePlugInKey.extensibility.config.xml
Unify.Product.IdentityBroker.ConnectorEnginePlugInKey.extensibility.config.xml
Memory leak during connector operation
The Identity Broker service requires profiling. After leaving three connectors running (one of which is producing 3000 schema validation errors each run every 30 seconds), the console is up to 635MB in a matter of minutes, and still climbing.
No adapters are running. The configuration is connecting to a Chris21 DET form (3000 entities, all failing validation), Chris21 DDS form (588 entities, all succeeding), and a CSV connector (failing due to missing file).
Is Operative Flag transformation does not render correctly
The following transformation in EDIT mode:
appears inconsistent with the way it is rendered in VIEW mode:
Suggestion is that the top line in VIEW mode should appear as follows:
IF [hireDate] <= @NOW && [terminationDateOffsetHours] >= @NOW
IsOperativeFlag.Edit.png
IsOperativeFlag.View.png
IdB 4.0.0.3 service cannot start.
Following error occurs when starting IdB service.
---------------------------
Services
---------------------------
Windows could not start the UNIFY Identity Broker v4.0.0 RTM service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.
---------------------------
OK
---------------------------
Two additional error message is logged in Event Viewer:
=================Error One===================
Log Name: Application
Source: .NET Runtime
Date: 31/10/2012 4:07:01 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: FIMDEVSVC01.education.vic.gov.au
Description:
Application: Unify.Service.Connect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeInitializationException
Stack:
at Unify.Service.ConnectServiceBootStrap.Main()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-10-31T05:07:01.000000000Z" />
<EventRecordID>1983</EventRecordID>
<Channel>Application</Channel>
<Computer>FIMDEVSVC01.education.vic.gov.au</Computer>
<Security />
</System>
<EventData>
<Data>Application: Unify.Service.Connect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeInitializationException
Stack:
at Unify.Service.ConnectServiceBootStrap.Main()
</Data>
</EventData>
</Event>
=================Error One===================
=================Error Two===================
Log Name: Application
Source: Application Error
Date: 31/10/2012 4:07:01 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: FIMDEVSVC01.education.vic.gov.au
Description:
Faulting application name: Unify.Service.Connect.exe, version: 4.0.0.3, time stamp: 0x504eab1b
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17932, time stamp: 0x503285c2
Exception code: 0xe0434352
Fault offset: 0x000000000000caed
Faulting process id: 0x990
Faulting application start time: 0x01cdb7258fb5990c
Faulting application path: C:\Program Files\UNIFY Solutions\Identity Broker\Services\Unify.Service.Connect.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: cd706c6b-2318-11e2-acf5-0050568b6a1c
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-10-31T05:07:01.000000000Z" />
<EventRecordID>1984</EventRecordID>
<Channel>Application</Channel>
<Computer>FIMDEVSVC01.education.vic.gov.au</Computer>
<Security />
</System>
<EventData>
<Data>Unify.Service.Connect.exe</Data>
<Data>4.0.0.3</Data>
<Data>504eab1b</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.17932</Data>
<Data>503285c2</Data>
<Data>e0434352</Data>
<Data>000000000000caed</Data>
<Data>990</Data>
<Data>01cdb7258fb5990c</Data>
<Data>C:\Program Files\UNIFY Solutions\Identity Broker\Services\Unify.Service.Connect.exe</Data>
<Data>C:\WINDOWS\system32\KERNELBASE.dll</Data>
<Data>cd706c6b-2318-11e2-acf5-0050568b6a1c</Data>
</EventData>
</Event>
=================Error Two===================
Additional, there is only one .dll file under C:\Program Files\UNIFY Solutions\IdentityBroker\Services\. The name is "CassiniDev4-lib.dll"
The IdentityBroker service will not start due to an 'IsolatedStorageException: Unable to determine application identity of caller' exception.
A determination may be necessary for the correct course of action with regards to the exception:
System.IO.IsolatedStorage.IsolatedStorageException occurred
Message=Unable to determine application identity of the caller.
Source=mscorlib
StackTrace:
at System.IO.IsolatedStorage.IsolatedStorage.InitStore(IsolatedStorageScope scope, Type appEvidenceType)
at System.IO.IsolatedStorage.IsolatedStorageFile.GetStore(IsolatedStorageScope scope, Type applicationEvidenceType)
at Unify.Console.Program.Main() in S:\hg\Product\IdentityBroker\Master-T\Source\Service\Unify.Console.Connect\Program.cs:line 26
InnerException:
This exception is encountered while debugging the IdentityBroker service in its current state.
A temporary workaround has been encountered whereby the the IsolatedStorageFile of the IdentityBrokerServiceEngine is changed to:
IsolatedStorageFile.GetMachineStoreForAssembly();
but a determination will need to be made as to whether this is correct and what implications it has with regards to the IdentityBroker service.
Customer support service by UserEcho
