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.
Isolated Storage issues prevent service from starting
The Identity Broker service is currently failing to start, Rev 389, running the 32-bit service:
Application: Unify.Service.Connect32.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IsolatedStorage.IsolatedStorageException
Stack:
at System.IO.IsolatedStorage.IsolatedStorage.InitStore(System.IO.IsolatedStorage.IsolatedStorageScope, System.Type)
at System.IO.IsolatedStorage.IsolatedStorageFile.GetStore(System.IO.IsolatedStorage.IsolatedStorageScope, System.Type)
at Unify.Service.IdentityBrokerService32..ctor(System.IO.DirectoryInfo)
at Unify.Service32.ConnectServiceBootStrap.Main()
The error is occurring on an attempt to retrieve the isolated storage file. Of note is that the 64-bit installer attempts this in the OnStart() method of the service, whereas the 32-bit attempts this in the service constructor.
IdB service crashing when running imports from remote FIM server
Everything working fine until today. Last major change was on the 25/09/2012 when the WofG->Health connection was introduced.
Today since lunchtime the IdB service keeps crashing.
In the System Event log:
Log Name: System Source: Service Control Manager Date: 3/10/2012 12:17:12 PM Event ID: 7034 Task Category: None Level: Error Keywords: Classic User: N/A Computer: PRDAPP119VS.act.gov.au Description: The UNIFY Identity Broker v3.0.6 service service terminated unexpectedly. It has done this 1 time(s).
In the Application Event log at the same time:
Log Name: Application
Source: Microsoft-Windows-MSDTC Client 2
Date: 3/10/2012 12:17:12 PM
Event ID: 4879
Task Category: CM
Level: Warning
Keywords: Classic
User: N/A
Computer: PRDAPP119VS.act.gov.au
Description:
MSDTC encountered an error (HR=0x80000171) while attempting to establish a secure connection with system PRDAPP119VS.
The server it is failing to establish a secure connection with is in fact itself.
There have been no further MSDTC errors but IdB no longer works. I can start the service but as soon as I try to run an Import from the WofG FIM server IdB on the Health server crashes immediately with the same error in the System event log.
Restarting the DTC service does not help.
Allow GeneralizedTime formatted dates to be read back into Identity Broker
As part of IDB-125, the GeneralizedTime format is successfully generated by the compliant LDIF adapter for DateValue and TimestampValue types. The .NET DateTime conversion does not recognize this format, and fails to convert the value to the respective value type when reading LDIF back in. These validators must be updated to support this format.
Request to retrieve DN generation configuration continuously logged.
Adapter request to retrieve DN generation configuration adapter space. Adapter request to retrieve DN generation configuration from adapter space 27e24050-eb57-4f35-a725-30509f996262.
Is continuously being logged to the IDB logs.
This will probably be the result of the LoggingLevel being to high.
Log intermittedly used by another process
During an export of 3000 users to Identity Broker, the following error appeared 4 times in the Event log. This can be seen on Test1 14/12/11 4:28:04pm, 4:31:59pm, 4:37:15pm, 4:43:14pm
Error occurred in module: Logging
Unable to log, exception as follows:
System.IO.IOException: The process cannot access the file 'C:\Program Files\UNIFY Solutions\Identity Broker\Services\Logs\UnifyLog20111214.csv' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding)
at System.IO.File.InternalAppendAllText(String path, String contents, Encoding encoding)
at Unify.Framework.Logging.CsvLogWriter.WriteLogEntryBase(ILogEntry logEntry, String filePath)
at Unify.Framework.Logging.CsvLogReaderWriter.WriteLogEntryBase(ILogEntry logEntry, String filePath)
at Unify.Framework.Logging.FileLogWriterBase.WriteLogEntryBase(ILogEntry logEntry)
at Unify.Framework.Logging.LogWriterBase.WriteLogEntry(ILogEntry logEntry)
IdB for FIM ECMA feature request: replay import (LDIF) file
With the ECMAs for FIM that I've written myself, one of the most useful features I was able to easily implement was the ability to set an ECMA parameter that would allow me to reprocess the last full import (LDIF in this case) file generated by either the ECMA full or delta import. I know that when FIM R2 comes this appears to change the paradigm, but nonetheless with the time that it takes me to construct a full import file before I can test my FIM solution in a lab, the ability to replay import files this way would be very handy. An added spin-off for this was to be able to replay production-generated LDIF files in a lab environment for analysis - something that proved crucial for me @ CSODBB in both troubleshooting and testing.
Enable Replay Option.png
Adding field to connector schema cached in IE6
Adding field to connector schema cached in IE6, as same field attempted to add on different requests for IE6; whereas in chrome this could be added fine.
On reflection: Byte array contains invalid string characters
Create an Adapter for Adv_Worx_Person successfully with now additional transformation, Run "Generate Change Token" and there are 290 Pending Changes but 0 Processed Entity Count.
Check the log files and found the following error:
Request to reflect change entities of the adapter. Request to reflect change entities of the Adv_Worx_Person (7fb73121-2311-4dfd-ad8f-ef1512ffc9fb) adapter errored with message: Byte array contains invalid string characters.. Duration: 00:00:00.2812421 Error details: System.Exception: Byte array contains invalid string characters. at Unify.Product.IdentityBroker.Asn1OctetStringBase.StringValue() at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext() at System.Linq.Enumerable.First[TSource](IEnumerable`1 source) at Unify.Product.IdentityBroker.LDAPChangeAdd.Format() at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext() at System.String.Join(String separator, IEnumerable`1 values) at Unify.Product.IdentityBroker.ChangeReportToChangeLogAdapter.<HandleAdds>d__2f.MoveNext() at Unify.Product.IdentityBroker.ChangeReportToChangeLogAdapter.<Transform>d__0.MoveNext() at System.Linq.Buffer`1..ctor(IEnumerable`1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source) at Unify.Product.IdentityBroker.Adapter.ReflectChanges() at Unify.Product.IdentityBroker.AdapterNotifierDecorator.ReflectChanges() at Unify.Product.IdentityBroker.ReflectAdapterOnChangeDueJob.<RunBase>b__0(IOperationalAdapter adapter)
screenshot-2.png
Unify.IdentityBroker.LDAP.Shared.dll
Identity Broker 32 bit debug not set to x86
When attempting to save InnerRange Insight Agent configuration I receive the following error.
Was this the COM reference you mentioned the other day Adam van Vliet?
System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Retrieving the COM class factory for component with CLSID {0B4EDEFE-EE24-4796-87B3-EC5EF6DF50FD} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {0B4EDEFE-EE24-4796-87B3-EC5EF6DF50FD} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). at Unify.Product.IdentityBroker.InsightAgent..ctor(IInsightAgentInformation information) at Unify.Product.IdentityBroker.InsightAgentFactory.CreateComponent(IAgentConfiguration factoryInformation) at Unify.Product.IdentityBroker.AgentEngine.<>c__DisplayClassa.<Add>b__9() at Unify.Product.IdentityBroker.AgentEngine.<>c__DisplayClass1.<ConfigurationChange>b__0() at Unify.Framework.ExtensionMethods.WaitOnMutex(Mutex mutex, Action work) at Unify.Product.IdentityBroker.AgentEngine.Add(IAgentConfiguration agent) at Unify.Product.IdentityBroker.IdentityServiceCollector.AddAgent(AgentRemotingConfiguration agent) at SyncInvokeAddAgen...).
Unify.Service.Connect32.Debug.exe
Unify.Service.Connect32.exe
Connector scheduled import not clearing old records
It has come to our attention that the Relief Staff Adaptor/Connector is (on the majority) adding new relief assignments, but is not dropping them from groups on the next day when they are not scheduled. It appears to only be a problem with the groups, not an issue with eMinerva permissions.
We have confirmed the Oracle View is reading correctly. If we clear the connector, then run an import it is reading correctly.
I also had an issue where one staff member was not processed on a Delta Import, it took a Full Import to bring it through to ILM.
This (non-scheduled staff not removed) happened last week as well. You will not be able to do testing until tomorrow as I have cleared the connector already. Dev is not suited to this testing as it will not contained Relief Schedules for today.
.jpg
Connector Search showing 7 Relief Staff @ School 401.jpg
UnifyLog20120314.csv
Customer support service by UserEcho
