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.

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.

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)

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...).

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.

A CSV connector configured to import a binary value fails with:

Change detection engine import all items for connector CSV Connector Example failed with reason Line 1 column 1 value of 010011010110000101101110 is not valid. Duration: 00:00:00.1406250

This was tried with a byte value, byte array value, binary value and base64 encoded string; all resulting with a message similar to the one provided above.

• Either the validator should be updated to handle string values
• Or an intermediate step is included where the CSV connector tries to parse the values retrieved based on the field ValueType, before creating with the Validator
• Otherwise, a more descriptive exception should be provided denoting that this connector doesn't support that value type.

Hi Guys,

I've been experiencing issues with the PowerShell connector in reporting export errors back to the MA. I'm using a try catch arrangement - with $components.Failures.Push($entity) however this does not appear to succeed in returning an error to the MA.

Attached is my current export script for Adds (Note that the reporting lines are commented out at the moment).

The MA in use is of the new Extensible Connectivity V2.0 type. It occurs to me that this may be similar to the issues we used to have on the IDB MA's with export errors being squashed if the 'Merge pending exports...' flag was not set correctly. However this setting is not present on the new MA type.

Issue is with this page: https://unifysolutions.jira.com/wiki/display/IDB305/Adapter+Engine+configuration

Namely (as per the comment I added there)

1) The Composite Adapter Configuration should also have its attributes documented (AdapterID and AdapterName at the very least are valid and I believe required)
2) The Composite Adapter also takes an image as a child element, which is also required.

The Time Offset transformation is limited to offsetting a timestamp by 23hrs 59mins and 59secs.

In the case of TAFE I am wanting to transform a date by 14 days (336 hours) which doesn't appear possible. I've looked at the Business Day Transformation however it only sets a flag rather than transforming the actual date/time.

I have installed Identity Broker Service v4.0 RTM x64 and Web Service v4.0 RTM x64. I have configure the for use with IIS as per https://unifysolutions.jira.com/wiki/display/IDB40/Configuring+for+use+with+IIS. When I browse to "http://localhost:8008/" I receive an error to add defaultRedirect="mycustompage.htm to the web.config file. I have add the line to the web.cnofig, run a IISRESET.

When I browse to "http://localhost:8008/" I receive the following error:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid. Detailed Error Information
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x8007000d
Config Error Configuration file is not well-formed XML
Config File \\?\D:\Program Files\UNIFY Solutions\Identity Broker\StandaloneWeb\web.config
Requested URL http://localhost:8008/
Physical Path
Logon Method Not yet determined
Logon User Not yet determined
Config Source
44:
45: <httpRuntime maxQueryStringLength="16384" />
46:
Links and More InformationThis error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
View more information »