Issues accessing and writing to logs

Beau Harrison (Software Developer) 3 years ago updated by anonymous 3 years ago 1


A number of issues may be encountered when attempting to access or write to the main Identity Broker logs.

Affected Software

  • FIM Event Broker


A variety of error messages can be produced when FIM Event Broker is unable to successfully access its logging directory. The following error messages may appear on pages and in the Windows Event log:

System.NullReferenceException: Object reference not set to an instance of an object.
at ASP._Page_Views_Error_Index_cshtml.Execute() in c:\Program Files\UNIFY Solutions\Event Broker\Web\Views\Error\Index.cshtml:line 10
at System.Web.WebPages.WebPageBase.ExecutePageHierarchy()
at System.Web.Mvc.WebViewPage.ExecutePageHierarchy()
at System.Web.WebPages.StartPage.ExecutePageHierarchy()
at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage)
at System.Web.Mvc.ViewResultBase.ExecuteResult(ControllerContext context)
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.InvokeActionResultWithFilters(ControllerContext controllerContext, IList`1 filters, ActionResult actionResult)
at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)


These error messages may appear differently, but they can be attributed to similar causes. If any issues either reading or writing to the main FIM Event Broker log occurs, please consider the following:

  • Ensure that the main Logs directory exists in the FIM Event Broker Services directory
  • If using IIS, ensure that any application pool accounts have sufficient access to the contents of the directory