0
Fixed

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

Ben Parkinson 3 years ago updated by anonymous 3 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

Affected Versions:
Fixed by Version:

Answer

Answer

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

Under review

Hi Ben, could you please let me know what version of Identity Broker you're running?

Fixed

Hi Ben,

Could you please try placing the following DLL into the Services directory of the Identity Broker installation, restart the service and then re-enable the log writer? Unify.IdentityBroker.LDAP.Engine.Notification.dll

Let us know if the error resurfaces with this patch in place.

Hi,

The new DLL has been applied by the customer per instructions from Corey Curtis; however, the customer is now receiving the following error (sorry it's cut off, that's all I've received from him). 

Would it be possible that by restarting the service, the underlying initial problem has surfaced as opposed to the introduction of the DLL given there's barely any code change?


An error occurred on client from 127.0.0.1:58313. More details:

Internal Server Error #11: System.MissingMethodException: Method not found: 'Void Unify.Product.IdentityBroker.HandleSchemaRequestNotificationFactory..ctor(System.String, System.String)'.

   at Unify.Product.IdentityBroker.SchemaRequestHandlerFactory.CreateNotificationFactory(IRfcLdapMessage message, IRequestHandlerFactoryInformation factoryInformation)

   at Unify.Product.IdentityBroker.LDAPConnection.<RespondToMessageAsync>d__33.MoveNext()

Answer

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

Client has reported the following error has occurred multiple times overnight overnight:

An error occurred on client from 127.0.0.1:55396. More details:
  
Internal Server Error #11: System.MissingMethodException: Method not found: 'Void Unify.Product.IdentityBroker.HandleSchemaRequestNotificationFactory..ctor(System.String, System.String)'.
   at Unify.Product.IdentityBroker.SchemaRequestHandlerFactory.CreateNotificationFactory(IRfcLdapMessage message, IRequestHandlerFactoryInformation factoryInformation)
   at Unify.Product.IdentityBroker.LDAPConnection.<RespondToMessageAsync>d__33.MoveNext()

Hi Matt,

Please make sure that the latest copy of the DLL is placed in the Services directory and that the other is removed entirely - note that renaming it is insufficient, at the very least you need to change the file extension but preferably just remove it entirely.

Hi Curtis,

Thanks for the feedback. After working with the client to ensure the old DLL was removed and the correct fresh one was applied, the client has not received any additional errors over the weekend. He is happy to mark this as resolved.

Excellent, thanks for the update.

Just following up to advise the customer has reported it is now all working. Thanks very much guys.

Excellent, thanks for the follow up.