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
Completed

Modify Connector schedules without disabling connector

Carol Wapshere 7 years ago updated by anonymous 7 years ago 2

It would be good to be able to modify IdB connector schedules without disabling the Connector. However as the main problem is the Adapter also gets disabled this may not be such a nuisance if that other suggestion is resolved.

Answer
anonymous 7 years ago

Adapter disabling connector part of this is fixed in v5.2.1.

0
Answered

Unify Idenity Broker v.5.0.4 RTM service stops after 3-5 mins with no error message

Anthony Soquin 7 years ago updated by anonymous 7 years ago 4

Hi Guys,

Just a quick question about Identity Broker 5.0.4. 
After 5 mins, the service shutdown with no error. Do you have an idea about the cause? 
There is nothing in the event viewer or in the log. I did some "import all" with no error.
Thanks in advance for your help.


Image 4529


UnifyLog20170828.csv

Answer
anonymous 7 years ago

This isn't a crash, something external is requesting that the service stops. Find the thing that's doing this and stop it from happening.

0
Completed

Schema provider checkboxes and UI cleanup

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

When a user clicks Request Schema, it's not obvious that the schema of the connected system is not shown. What is shown is a merge of the existing schema AND the schema of the connected system. This probably applies to all Connectors, but definitely on the Aurion one.

It's not clear that this is the behaviour.  

When I hit the button "Request Shema", I expect the modal popup to contain the actual schema of the system, not a merge. 

Then, when I hit "Continue with Schema", I expect the existing config to be merged.  Having both options would be even better.

Option 1) Continue with New Schema

Option 2) Continue with Merged Schema


Answer
anonymous 7 years ago

I've made this much more obvious (can see whether fields are new, intersect or existing), as well as update the button to show that the schemas are merged. Also added back in the checkboxes that went missing.

0
Answered

The target principal name is incorrect when accessing via IIS

Ben Parkinson 7 years ago updated 7 years ago 11

I am receiving an error on the standalone web component when trying to access it.

  • The site is installed and configured on IIS 7.5 per the instructions. 
  • Identity Broker is a base install also following the instructions.  
  • I can access the endpoints hosted on the Identity Broker server from the IIS server. 
  • The website is on port 8200 and shares the server with SharePoint and MIM Service & Portal. 
  • Identity Broker is on a separate server with just MIM Sync. 
  • The server also uses .NET4.6 (only mentioned here as I had issues with SharePoint).
  • I have tried enabling Anonymous Authentication over Windows Authentication and have also tried using the Identity Broker service account in the application pool. 
  • I've disabled Custom Errors to view the error, but have attached  Event Log item with the stack trace. 

It appears to be an authentication error, but I can't for the life of me work out where in the scheme of things it's coming from.

Broker Web Error.evtx

Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 14/08/2017 9:20:14 AM 
Event time (UTC): 13/08/2017 11:20:14 PM 
Event ID: 7a9e61eff31a4fedbcdbc46027dff770 
Event sequence: 2 
Event occurrence: 1 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/3/ROOT-1-131471400119122652 
    Trust level: Full 
    Application Virtual Path: / 
    Application Path: C:\inetpub\wwwroot\UnifyIdentityBroker\Identity Broker\StandaloneWeb\ 
    Machine name: IAM-DEV1-MIM2 
 
Process information: 
    Process ID: 5584 
    Process name: w3wp.exe 
    Account name: IIS APPPOOL\UNIFYIdentityBroker 
 
Exception information: 
    Exception type: HttpException 
    Exception message: The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate oXIwcKADCgEBomkEZ2BlBgkqhkiG9xIBAgIDAH5WMFSgAwIBBaEDAgEepBEYDzIwMTcwODEzMjMyMDE0WqUFAgMNka+mAwIBKakOGwxERVYuQ1NJUk8uQVWqGTAXoAMCAQGhEDAOGwxzYS11bmlmeS1pZGI='.
   at System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app)
   at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
   at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
   at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
   at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)
The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate oXIwcKADCgEBomkEZ2BlBgkqhkiG9xIBAgIDAH5WMFSgAwIBBaEDAgEepBEYDzIwMTcwODEzMjMyMDE0WqUFAgMNka+mAwIBKakOGwxERVYuQ1NJUk8uQVWqGTAXoAMCAQGhEDAOGwxzYS11bmlmeS1pZGI='.
Server stack trace: 
   at System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication(HttpWebRequest request, HttpWebResponse response, WebException responseException, HttpChannelFactory`1 factory)
   at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Unify.Framework.IStandardPostEngineCollector.RequiredSystemTypes()
   at Unify.Product.IdentityBroker.IdentityServiceClient.RequiredSystemTypes()
   at Unify.Connect.Web.ProfiledIdentityServiceClient.RequiredSystemTypes()
   at Unify.Connect.Web.MvcApplication.Application_Start()
The remote server returned an error: (401) Unauthorized.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
The target principal name is incorrect
   at System.Net.NTAuthentication.GetOutgoingBlob(Byte[] incomingBlob, Boolean throwOnError, SecurityStatus& statusCode)
   at System.Net.NTAuthentication.GetOutgoingBlob(String incomingBlob)
   at System.Net.NegotiateClient.DoAuthenticate(String challenge, WebRequest webRequest, ICredentials credentials, Boolean preAuthenticate)
   at System.Net.NegotiateClient.Authenticate(String challenge, WebRequest webRequest, ICredentials credentials)
   at System.Net.AuthenticationManagerDefault.Authenticate(String challenge, WebRequest request, ICredentials credentials)
   at System.Net.AuthenticationState.AttemptAuthenticate(HttpWebRequest httpWebRequest, ICredentials authInfo)
   at System.Net.HttpWebRequest.CheckResubmitForAuth()
   at System.Net.HttpWebRequest.CheckResubmit(Exception& e, Boolean& disableUpload)
 
 
Request information: 
    Request URL: http://localhost:8200/ 
    Request path: / 
    User host address: ::1 
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: IIS APPPOOL\UNIFYIdentityBroker 
 
Thread information: 
    Thread ID: 12 
    Thread account name: IIS APPPOOL\UNIFYIdentityBroker 
    Is impersonating: False 
    Stack trace:    at System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app)
   at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
   at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
   at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
   at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)
 
 
Custom event details:
Answer
anonymous 7 years ago

Hi Ben

This issue is a little tricky to troubleshoot as we've not seen this before and isn't something that can be reproduce in a test environment, but have something for you to try.

In both the Unify.Service.Connect.exe.config and the web.config files, find the system.serviceModel element and nested within that find <transport clientCredentialType="Windows" /> and change the Windows value to Ntlm. Restart the website and the IdB service.

Let us know of the outcome.

0
Fixed

LogWriter Object reference not set to an instance of an object.

Ben Parkinson 7 years ago updated by anonymous 7 years ago 11

Hi all,

I receivied the below error in the logs

The 'Error Email Log Writer' log writer - with an id of 'd807b535-f176-40f3-88bd-1105aaed5001' - has been disabled and will no longer actively write log entries. The configuration of this log writer may need to be updated. For more details please see, System.NullReferenceException: Object reference not set to an instance of an object. at Unify.Product.IdentityBroker.LDAPEngineTaskCompletedEvent.GetLogEntryData() at Unify.Framework.Notification.TaskEvent.GetLogEntry() at Unify.Framework.Notification.LogWriterSink.InnerNotify(ILogEntryNotification message) at Unify.Framework.Notification.LogWriterSinkBase.Notify(ILogEntryNotification message)

UNIFY Identity Broker Management Studio - v5.1.0 Revision #2

Answer
anonymous 7 years ago

Sorry Ben, the patch included a fix for an unrelated issue that would also require an update to another DLL. I've instead rolled the patch back to the RTM to remove unrelated changes. This should hopefully do the trick: Unify.IdentityBroker.LDAP.Engine.Notification.dll

0
Not a bug

The resource cannot be found - /Account/LogOn

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

Using

  • IdB service v4.1.5.5
  • IdB for Microsoft Active Directory 4.1.2.1
  • IdB for PeopleSoft Connector 4.1.0.0
  • IdB for FIM 4.0.0.3

* Note - About page incorrectly showing this: "UNIFY Identity Broker Management Studio, v0.0.5 Revision #5" ... can't explain this!

The following error is thrown when starting on the ABOUNT page (/About) and clicking on the Identity Btroker home page image to return to the dashboard.

The resource cannot be found. 
  Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly. 

 Requested URL: /Account/LogOn

The URL for this page is as follows:

http://localhost:8008/Account/LogOn?ReturnUrl=%2f

I am running IdB under IIS.  Navigating directly to the home page (by removing everything after the 8008 port number in the URL) also fails - only works after I put in a trailing ?, i.e.

http://localhost:8008/?

I am using a clean install of IdB 4.1, using the extensibility files from the (to be retired) existing v4.1.4 RTM version.

Answer
anonymous 7 years ago

Please try updating the authentication node in the web.config to:

<authentication mode="Windows" />

0
Answered

Reflection for adapter XXX failed with message One or more errors occurred

Bob Bradley 7 years ago updated by anonymous 7 years ago 2

Using IdB 5.0.5 Rev#0

I noted today that 2 adapters were both red on the dashboard.

Searching in the IdB logs via the console for the word "error" I could see earlier today that there were 8 occurrences of some sort of timeout siting "System.Threading.ReaderWriterLock.*.

Can you please spend a few minutes to check this out over a remote shared desktop to confirm that this is indeed the problem for which a patch has since become available whereby changelog access was causing record locking?

Answer
anonymous 7 years ago

Hi Bob,

This issue is unrelated to Delta Import timeouts on Identity Broker 5.1 Management Agents, as it occurs acquiring a lock for a different table. What is the impact of the issue? It looks like only one page of reflection fails at a time and subsequent pages continue to process normally, so the issue should be resolving itself.

0
Answered

Error during processing of SearchRequest targetting cn=changelog: Operation timed out

Bob Bradley 7 years ago updated by anonymous 7 years ago 3

The following 3 exceptions were logged today in the Application Event log for a failed MIM DI run profle against an IdB adapter:

<p style="margin-top:5pt;margin-bottom:5pt;font-family:Calibri;font-size:11.0pt"><span lang="en-US">Log Name:      Application</span><span lang="en-AU"><br>
</span><span lang="en-US">Source:       
FIMSynchronizationService</span><span lang="en-AU"><br>
</span><span lang="en-US">Date:         
5/07/2017 12:44:09 PM</span><span lang="en-AU"><br>
</span><span lang="en-US">Event ID:     
6110</span><span lang="en-AU"><br>
</span><span lang="en-US">Task Category: Management Agent Run Profile</span><span lang="en-AU"><br>
</span><span lang="en-US">Level:        
Warning</span><span lang="en-AU"><br>
</span><span lang="en-US">Keywords:     
Classic</span><span lang="en-AU"><br>
</span><span lang="en-US">User:         
N/A</span><span lang="en-AU"><br>
</span><span lang="en-US">Computer:     
AUHBSMIMWP0001.corp.qbe.com</span><span lang="en-AU"><br>
</span><span lang="en-US">Description:</span><span lang="en-AU"><br>
</span><span lang="en-US">The management agent "License Entitlements"
step execution completed on run profile "DI" but the watermark was
not saved.</span><span lang="en-AU"><br>
</span><span lang="en-US"> </span><span lang="en-AU"><br>
</span><span lang="en-US"> Additional
Information</span><span lang="en-AU"><br>
</span><span lang="en-US"> Discovery
Errors       : "0"</span><span lang="en-AU"><br>
</span><span lang="en-US"> Synchronization
Errors : "0"</span><span lang="en-AU"><br>
</span><span lang="en-US"> Metaverse Retry
Errors : "0"</span><span lang="en-AU"><br>
</span><span lang="en-US"> Export
Errors          : "0"</span><span lang="en-AU"><br>
</span><span lang="en-US"> Warnings               : "0"</span><span lang="en-AU"><br>
</span><span lang="en-US"> </span><span lang="en-AU"><br>
</span><span lang="en-US"> User Action</span><span lang="en-AU"><br>
</span><span lang="en-US"> View the
management agent run history for details.</span><span lang="en-AU"><br>
</span><span lang="en-US">Event Xml:</span><span lang="en-AU"><br>
</span><span lang="en-US"><Event xmlns="</span><a href="http://schemas.microsoft.com/win/2004/08/events/event"><span lang="en-US">http://schemas.microsoft.com/win/2004/08/events/event</span></a><span lang="en-US">"></span><span lang="en-AU"><br>
</span><span lang="en-US">  <System></span><span lang="en-AU"><br>
</span><span lang="en-US">    <Provider
Name="FIMSynchronizationService" /></span><span lang="en-AU"><br>
</span><span lang="en-US">    <EventID
Qualifiers="32768">6110</EventID></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Level>3</Level></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Task>1</Task></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Keywords>0x80000000000000</Keywords></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<TimeCreated SystemTime="2017-07-05T02:44:09.000000000Z"
/></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<EventRecordID>9375144</EventRecordID></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Channel>Application</Channel></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Computer>AUHBSMIMWP0001.corp.qbe.com</Computer></span><span lang="en-AU"><br>
</span><span lang="en-US">    <Security
/></span><span lang="en-AU"><br>
</span><span lang="en-US">  </System></span><span lang="en-AU"><br>
</span><span lang="en-US"> 
<EventData></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Data>License Entitlements</Data></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Data>DI</Data></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Data>0</Data></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Data>0</Data></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Data>0</Data></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Data>0</Data></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Data>0</Data></span><span lang="en-AU"><br>
</span><span lang="en-US"> 
</EventData></span><span lang="en-AU"><br>
</span><span lang="en-US"></Event></span></p>
<p style="margin-top:5pt;margin-bottom:5pt;font-family:Calibri;font-size:11.0pt"><span lang="en-US">Log Name:      Application</span><span lang="en-AU"><br>
</span><span lang="en-US">Source:       
FIMSynchronizationService</span><span lang="en-AU"><br>
</span><span lang="en-US">Date:         
5/07/2017 12:44:09 PM</span><span lang="en-AU"><br>
</span><span lang="en-US">Event ID:     
6803</span><span lang="en-AU"><br>
</span><span lang="en-US">Task Category: Management Agent Run Profile</span><span lang="en-AU"><br>
</span><span lang="en-US">Level:        
Error</span><span lang="en-AU"><br>
</span><span lang="en-US">Keywords:     
Classic</span><span lang="en-AU"><br>
</span><span lang="en-US">User:         
N/A</span><span lang="en-AU"><br>
</span><span lang="en-US">Computer:     
AUHBSMIMWP0001.corp.qbe.com</span><span lang="en-AU"><br>
</span><span lang="en-US">Description:</span><span lang="en-AU"><br>
</span><span lang="en-US">The management agent "License Entitlements"
failed on run profile "DI" because the server encountered errors.</span><span lang="en-AU"><br>
</span><span lang="en-US">Event Xml:</span><span lang="en-AU"><br>
</span><span lang="en-US"><Event xmlns="</span><a href="http://schemas.microsoft.com/win/2004/08/events/event"><span lang="en-US">http://schemas.microsoft.com/win/2004/08/events/event</span></a><span lang="en-US">"></span><span lang="en-AU"><br>
</span><span lang="en-US">  <System></span><span lang="en-AU"><br>
</span><span lang="en-US">    <Provider
Name="FIMSynchronizationService" /></span><span lang="en-AU"><br>
</span><span lang="en-US">    <EventID
Qualifiers="49152">6803</EventID></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Level>2</Level></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Task>1</Task></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Keywords>0x80000000000000</Keywords></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<TimeCreated SystemTime="2017-07-05T02:44:09.000000000Z"
/></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<EventRecordID>9375143</EventRecordID></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Channel>Application</Channel></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Computer>AUHBSMIMWP0001.corp.qbe.com</Computer></span><span lang="en-AU"><br>
</span><span lang="en-US">    <Security
/></span><span lang="en-AU"><br>
</span><span lang="en-US">  </System></span><span lang="en-AU"><br>
</span><span lang="en-US"> 
<EventData></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Data>License Entitlements</Data></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Data>DI</Data></span><span lang="en-AU"><br>
</span><span lang="en-US"> 
</EventData></span><span lang="en-AU"><br>
</span><span lang="en-US"></Event></span></p>
<p style="margin-top:5pt;margin-bottom:5pt;font-family:Calibri;font-size:11.0pt"><span lang="en-US">Log Name:      Application</span><span lang="en-AU"><br>
</span><span lang="en-US">Source:       
FIMSynchronizationService</span><span lang="en-AU"><br>
</span><span lang="en-US">Date:         
5/07/2017 12:44:09 PM</span><span lang="en-AU"><br>
</span><span lang="en-US">Event ID:     
6801</span><span lang="en-AU"><br>
</span><span lang="en-US">Task Category: Server</span><span lang="en-AU"><br>
</span><span lang="en-US">Level:        
Error</span><span lang="en-AU"><br>
</span><span lang="en-US">Keywords:     
Classic</span><span lang="en-AU"><br>
</span><span lang="en-US">User:         
N/A</span><span lang="en-AU"><br>
</span><span lang="en-US">Computer:     
AUHBSMIMWP0001.corp.qbe.com</span><span lang="en-AU"><br>
</span><span lang="en-US">Description:</span><span lang="en-AU"><br>
</span><span lang="en-US">The extensible extension returned an unsupported error.</span><span lang="en-AU"><br>
</span><span lang="en-US"> The stack trace
is:</span><span lang="en-AU"><br>
</span><span lang="en-US"> </span><span lang="en-AU"><br>
</span><span lang="en-US"> "Unify.Product.IdentityBroker.LdapOperationException:
Error during processing of SearchRequest targetting cn=changelog: Operation
timed out.</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.LdapConnection.SendRequest(ILdapRequest request)</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.LdapConnectionProxy.<SearchRequestPaged>d__9.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.ImportProxy.<GetChangedEntriesPaged>d__33.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.ExtensionMethods.Take[TSource](IEnumerator`1
source, Int32 count, IList`1& items)</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.ExtensionMethods.<Page>d__3`1.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.ImportProxy.Import(GetImportEntriesRunStep
importRunStep)</span><span lang="en-AU"><br>
</span><span lang="en-US">Forefront Identity Manager 4.3.2195.0"</span><span lang="en-AU"><br>
</span><span lang="en-US">Event Xml:</span><span lang="en-AU"><br>
</span><span lang="en-US"><Event xmlns="</span><a href="http://schemas.microsoft.com/win/2004/08/events/event"><span lang="en-US">http://schemas.microsoft.com/win/2004/08/events/event</span></a><span lang="en-US">"></span><span lang="en-AU"><br>
</span><span lang="en-US">  <System></span><span lang="en-AU"><br>
</span><span lang="en-US">    <Provider
Name="FIMSynchronizationService" /></span><span lang="en-AU"><br>
</span><span lang="en-US">    <EventID
Qualifiers="49152">6801</EventID></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Level>2</Level></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Task>3</Task></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Keywords>0x80000000000000</Keywords></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<TimeCreated SystemTime="2017-07-05T02:44:09.000000000Z"
/></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<EventRecordID>9375142</EventRecordID></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Channel>Application</Channel></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Computer>AUHBSMIMWP0001.corp.qbe.com</Computer></span><span lang="en-AU"><br>
</span><span lang="en-US">    <Security
/></span><span lang="en-AU"><br>
</span><span lang="en-US">  </System></span><span lang="en-AU"><br>
</span><span lang="en-US"> 
<EventData></span><span lang="en-AU"><br>
</span><span lang="en-US">   
<Data>Unify.Product.IdentityBroker.LdapOperationException: Error
during processing of SearchRequest targetting cn=changelog: Operation timed
out.</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.LdapConnection.SendRequest(ILdapRequest request)</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.LdapConnectionProxy.<SearchRequestPaged>d__9.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.ImportProxy.<GetChangedEntriesPaged>d__33.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.ExtensionMethods.Take[TSource](IEnumerator`1
source, Int32 count, IList`1& items)</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.ExtensionMethods.<Page>d__3`1.MoveNext()</span><span lang="en-AU"><br>
</span><span lang="en-US">   at
Unify.Product.IdentityBroker.ImportProxy.Import(GetImportEntriesRunStep
importRunStep)</span><span lang="en-AU"><br>
</span><span lang="en-US">Forefront Identity Manager 4.3.2195.0</Data></span><span lang="en-AU"><br>
</span><span lang="en-US"> 
</EventData></span><span lang="en-AU"><br>
</span><span lang="en-US"></Event></span></p>

This is the first time I've seen a timeout occur for a DI to the change log - is there something that can be set specifically to mitigate this?  So far indexing issues have impacted only full imports, but not deltas - and these are mitigated by daily index rebuilds.

Answer
anonymous 7 years ago

Hi Bob,

Which version of Identity Broker is installed, and do you have any patches installed for Unify.IdentityBroker.ChangeLog.Repository.Sql.dll? As of Identity Broker v5.1, there should no longer be any SQL locking around access to the changelog context. This change will also be included in an upcoming Identity Broker v5.0 release, although it is not present in the current v5.0.5 RC1.

0
Answered

Post-Provisioning in IdBPlus After Object Creation in Target?

Daniel Walters 7 years ago updated by anonymous 7 years ago 1

The documentation says that the post-provisioning task will run "after the new target entity is committed to the target entity space." This leads me to believe that the object might not actually be in the target connected system yet, it's only in the IdBPlus connector. If I, for example, ran a mailbox provisioning in post-provisioning task will the AD account definitely be there by the time post-provisioning runs?

Answer
anonymous 7 years ago

Hi Daniel,

Thanks for the great question! Yes, post-provisioning tasks run AFTER the entity has been pushed out to the target system. I'll update the documentation to make this point clearer.

0
Answered

Unable to cast object of type 'Unify.Product.IdentityBroker.RfcBulkUpdateResponse' to type 'Unify.Product.IdentityBroker.Rfc2251.IRfcRequest

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

Error being raised in IdB 5.1 not sure of the impact as yet.

Handling of LDAP Bulk Update request received from user mim on connection 127.0.0.1:55606 failed with error ""Unable to cast object of type 'Unify.Product.IdentityBroker.RfcBulkUpdateResponse' to type 'Unify.Product.IdentityBroker.Rfc2251.IRfcRequest'."". Duration 00:01:23.1812324.",Normal
20170630,05:43:41,UNIFY Identity Broker,LDAP Engine,Error,"An error occurred on client from 127.0.0.1:55606. More details:
Internal Server Error #11: System.InvalidCastException: Unable to cast object of type 'Unify.Product.IdentityBroker.RfcBulkUpdateResponse' to type 'Unify.Product.IdentityBroker.Rfc2251.IRfcRequest'.nformation,"Request to update entity to connector.
Request to update entities [Count:1] to connector SharePoint User Profile.",Normal
20170630,05:43:41,UNIFY Identity Broker,Connector,Information,"Update entities to connector completed.
Update entities 1 to connector SharePoint User Profile reported 1 entities saved. Duration: 00:00:00.5780823",Normal
20170630,05:43:41,UNIFY Identity Broker,Adapter,Informati
   at Unify.Framework.Auditing.AuditingExtensions.<>c__DisplayClass4_0.<TaskContinueWithExceptionPassthough>b__0(Task t)
   at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Unify.Product.IdentityBroker.LDAPConnection.<RespondToMessageAsync>d__33.MoveNext()",Normal
20170630,05:43:41,UNIFY Identity Broker,Adapter,Information,"Request to reflect change entities of the adapter.
Request to reflect change entities of the SharePoint Profiles (4e96758c-06c5-44dd-9f32-557b3e75d16f) adapter started.",Verbose
20170630,05:43:41,UNIFY Identity Broker,Changes register engine,Information,"Request to retrieve changes register context.
Request to retrieve changes register context started.",Verbose
Answer
anonymous 7 years ago

Hi Matt,

Thanks for raising this. In this case the error is legitimate, although there's a mistake in the reporting of the error which needs to be corrected. The attached Unify.IdentityBroker.LDAP.Engine.dll should correct the error reporting.

The actual error is due to the fact that Identity Broker failed to reply to an LDAP request because the connection was closed by the remote client, most likely because the remote client timed out.