Removing schedule returns an error.

Can you tell me if the CSV connector is now rolled into the std broker install (like the placeholder connector). I tried installing the one in IDB-74 and it said a newer version was already installed.

If not, let me know where to get it.

Thanks

At QDET in a mirror production environment we recently saw an issue around the changes register of Identity Broker. A full import was running on a large connector (500000~ users) where 40 changes in the target system were present. The Identity Broker Changes Plug-in detected a change during the import process and kicked off two delta imports into FIM. Possibly due to poor infrastructure or heavy database server load, the delta imports failed - logs below:

Subsequent delta imports into FIM were successful, however, the import returned 0 results. This may suggest that the changes register is cleared regardless of the return state of a delta import. A full import into FIM was required to pick up the changed users.

Attempts to replicate this behaviour have so far been unsuccessful - the database is no longer timing out.

This is not a pressing issue as we have been unable to replicate yet (and may not be able to), but it would be worth investigating (for this or future versions) to prevent this from occurring again as the behaviour does incur operational intervention.

In IDaaS the full import of a chris21 connector is receiving an error as logged in the log file as follows. It seems to point to a problem with SQL Error code 40174.

The cause was identified as a result of throttling on Azure DB.

Solution: Increasing the DTU capacity on the DB in Azure.

Connector Processing started for connector chris21 - POS Form (page 15)",Normal
20151023,04:20:58,UNIFY Identity Broker,List,Information,Next chunk is [1000] sub total [19000]. Duration: 00:00:10.2657290,Normal
20151023,04:21:00,UNIFY Identity Broker,Change detection engine,Information,"Started processing changes register items.
Started processing changes register items for connector chris21 - POS Form.",Normal
20151023,04:21:01,UNIFY Identity Broker,Change detection engine,Information,"Changes register item processing completed.
Changes register item processing on connector chris21 - POS Form completed.  Duration: 00:00:01.1719116",Normal
20151023,04:21:07,UNIFY Identity Broker,Connector Processor,Information,"Connector processing failed.
Connector Processing page 15 for connector chris21 - POS Form failed with reason The service has encountered an error processing your request. Please try again. Error code 40174.
A severe error occurred on the current command.  The results, if any, should be discarded.. Duration: 00:00:09.7625532. 
Error details:
System.Data.SqlClient.SqlException (0x80131904): The service has encountered an error processing your request. Please try again. Error code 40174.
A severe error occurred on the current command.  The results, if any, should be discarded.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
   at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
   at System.Data.SqlClient.SqlDataReader.Read()
   at System.Data.Linq.SqlClient.ObjectReaderCompiler.ObjectReaderBase`1.Read()
   at System.Data.Linq.SqlClient.ObjectReaderCompiler.ObjectReader`2.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at Unify.Framework.Data.LinqWhereQuery`5.GetEnumerator()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at Unify.Product.IdentityBroker.EntityRepositoryExtensions.ConvertConnectorEntitiesWithRepositoryEntities(IEnumerable`1 connectorEntities, IMultiKey`1 schemaKey, IQueryable`1 sourceEntities, Guid connectorId, IEnumerable`1 originalEntities)
   at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetectionOnConnectorEntityPage(IEnumerable`1 connectorEntities, Int32& index, Int32 entitiesProcessedSoFar, IEntityChangesReportGenerator`2 reportGenerator)
   at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.<>c__DisplayClass3.<PerformChangeDetection>b__0(IEnumerable`1 page)
   at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.ThreadsafeItemEvaluator.Evaluate()
ClientConnectionId:abc9d8a7-32a0-402b-9273-7c87fc4223c4
Error Number:40197,State:3,Class:20",Normal
20151023,04:21:08,UNIFY Identity Broker,Connector Processor,Information,"Connector Processing started.
Connector Processing started for connector chris21 - POS Form (page 16)",Normal
20151023,04:21:08,UNIFY Identity Broker,List,Information,Next chunk is [1000] sub total [20000]. Duration: 00:00:10.5594588,Normal
20151023,04:21:17,UNIFY Identity Broker,List,Information,Next chunk is [1000] sub total [21000]. Duration: 00:00:08.7187876,Normal
20151023,04:21:23,UNIFY Identity Broker,Change detection engine,Error,"Change detection engine import all items failed.
Change detection engine import all items for connector chris21 - POS Form failed with reason An error occurred while evaluating a task on a worker thread.  See the inner exception details for information.. Duration: 00:06:12.2925941
Error details:
Unify.Framework.EvaluatorVisitorException: An error occurred while evaluating a task on a worker thread.  See the inner exception details for information. ---> System.Data.SqlClient.SqlException: The service has encountered an error processing your request. Please try again. Error code 40174.
A severe error occurred on the current command.  The results, if any, should be discarded.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
   at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
   at System.Data.SqlClient.SqlDataReader.Read()
   at System.Data.Linq.SqlClient.ObjectReaderCompiler.ObjectReaderBase`1.Read()
   at System.Data.Linq.SqlClient.ObjectReaderCompiler.ObjectReader`2.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at Unify.Framework.Data.LinqWhereQuery`5.GetEnumerator()
  at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at Unify.Product.IdentityBroker.EntityRepositoryExtensions.ConvertConnectorEntitiesWithRepositoryEntities(IEnumerable`1 connectorEntities, IMultiKey`1 schemaKey, IQueryable`1 sourceEntities, Guid connectorId, IEnumerable`1 originalEntities)
   at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetectionOnConnectorEntityPage(IEnumerable`1 connectorEntities, Int32& index, Int32 entitiesProcessedSoFar, IEntityChangesReportGenerator`2 reportGenerator)
   at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.<>c__DisplayClass3.<PerformChangeDetection>b__0(IEnumerable`1 page)
   at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.ThreadsafeItemEvaluator.Evaluate()
   --- End of inner exception stack trace ---
   at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.CheckForException()
   at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.WaitForAvailableThread()
   at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.Visit()
   at Unify.Product.IdentityBroker.RepositoryChangeDetectionWorkerBase.PerformChangeDetection(IEnumerable`1 connectorEntities)
   at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.ImportAllChangeProcess()
   at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.RunBase()
   at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
   at Unify.Product.IdentityBroker.ConnectorJobExecutor.<>c__DisplayClass29.<Run>b__27()
   at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal
20151023,04:21:34,UNIFY Identity Broker,Connector Processor,Information,"Connector processing success.
17625 entites in cumulative total. Current processing of page 16 for connector chris21 - POS Form processed 1175 entities, finding 1175 differences. Duration: 00:00:26.1862477. ",Normal
20151023,04:21:35,UNIFY Identity Broker,Change detection engine,Information,"Started processing changes register items.
Started processing changes register items for connector chris21 - POS Form.",Normal
20151023,04:21:37,UNIFY Identity Broker,Change detection engine,Information,"Changes register item processing completed.
Changes register item processing on connector chris21 - POS Form completed.  Duration: 00:00:02.0317620",Normal

In order to aid diagnosis of failing processes, I think it would be a good idea for there to be a configurable option to provide detailed diagnosis information at every interface boundary within Identity Broker.

By that, I mean every Identity Broker process that has interfaces should be able to have a decorator inserted to provide details information about the methods and data provided at each step of a process. This would prevent the kinds of Product Support issues where: "I can't really tell what's going on so I suspect something is wrong with Identity Broker".

After deploying UNIFY Identity Broker for Microsoft FIM v3.0.0 (x86).msi from https://unifysolutions.jira.com/wiki/display/SUBIDBFIM/Downloads and completing my IdB 3.0.6 DEEWR configuration, I was ready to create an instance of the IdB FIM xMA ...

After installing using the default options, I found that:

(b) Exported the "ILM xMA" file ... using the IdB Management studio my first choice was to select the third ILM 2 option (since this is the name that FIM was originally known). This was a mistake because the MA config pointed to a Unify.Adapters.* dll which I could not locate on the server. Figuring that the PDF and naming conventions were focused on ILM2007 FP1, I re-exported using this option and found this generated an MA config which referenced the same DLL deployed by this package (Unify.Framework.ILM2007FP1Adapter.dll). This means that either (a) there is a DLL which is missing from the install, or (b) the IdB console needs to be changed to remove the third option, or (c) the generated xMA is using the wrong DLL.

I believe we should actually retain the third option but rename it to FIM 2010 ... even if it generates a file of the same format as ILM2007 ... as it is going to confuse otherwise. If so the PDF file needs to be updated to accommodate all (3?) supported versions (maybe we need to lose MIIS SP2?).

This work may well have been earmarked for future attention, but I couldn't find anything in JIRA about this already.

When the relational connector is updated for the multivalue DN generator transformation, the changes register errors with the following:

When promote SAPPerson adaptor to SAP composite adaptor, an error is displayed to the browser:

System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at ASP._Page_Views_Adapter_Transformations_Transformations_cshtml.Execute() in c:\Program Files\UNIFY Solutions\Identity Broker\Web\Views\Adapter\Transformations\Transformations.cshtml:line 90
at System.Web.WebPages.WebPageBase.ExecutePageHierarchy()
at System.Web.Mvc.WebViewPage.ExecutePageHierarchy()
at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage)
at System.Web.Mvc.RazorView.RenderView(ViewContext viewContext, TextWriter writer, Object instance)
at System.Web.Mvc.BuildManagerCompiledView.Render(ViewContext viewContext, TextWriter writer)
at System.Web.Mvc.ViewResultBase.ExecuteResult(ControllerContext context)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResult(ControllerContext controllerContext, ActionResult actionResult)
at System.Web.Mvc.ControllerActionInvoker.<>c_DisplayClass1c.<InvokeActionResultWithFilters>b_19()
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilter(IResultFilter filter, ResultExecutingContext preContext, Func`1 continuation)
at System.Web.Mvc.ControllerActionInvoker.<>c_DisplayClass1c.<>cDisplayClass1e.<InvokeActionResultWithFilters>b_1b()
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList`1 filters, ActionResult actionResult)
at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)

Change detection and other logs using paging seem to start from page 2 - there is no page 1 in the log. See below for an example:

The last errored state of a connector is not cleared on start of that job. This means that if that job has errored before, when inactive the background-colour will be red.