When ADO.Net is used to connect to a SQL store, the only "Windows Integrated Security" option available for a windows service is to use the windows service account itself. This is overly restrictive, especially for DET where there are a number of XMAs connecting to SQL databases with credentials other than the FIM sync service, which is also used as the Event Broker 2.3 service account. This has been achieved through using a SQL.Data.Sqlclient connection in lieu of ADO.Net ... as per this TechNet article: http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnectionstringbuilder.aspx ... and as explained in this 3rd party tutorial: http://www.dotnetperls.com/sqlclient

I am completing the FIM specs for an install and all FIM software requirements need .NET 3.5 (or 3.5.1) (well the install guide says .NET 3.0 for servers other than the Sync server)

Question - I see that EB V3.0 requires .NET 4.0 which means collocated on a FIM Server will require .NET 4.0

Please confirm

TIA

Based on the Event Broker license request instruction client's site code is required.

I would like to know where I can obtain the client's site code for AHG so that I can in request for the Event Broker license for their Dev/UAT environment deployment?

In addition, based on my understanding of the Event Broker lincense request instruction

• When the client purchased Event Broker do they do not automatically get an Event Broker license as part of the product delivery.
• Thus the client will need make a request for an Event Broker license whether directly to licensing@unifysolutions.net.

If I understanding this process correctly then do I need to wait for the client to initiate this request before I can lodge an Event Broker license request in the Jira system?

Thank you.

We have a job that runs every 10 Minutes every day. We set it up NOT to run between 22:00:00 and 06:00:00 on the day(s) of Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday .
This time exception does not work on Sunday. The job start running at 00:07 in the middle of another job and continues ALL Sunday.

How can we fix that?
We are running version FIMEventBroker 3.1.0

Regards,

Meni Ariely

I perform the following steps and result in the below error.

1 - Create ADDS Agent
2 - Create an Operation List named "Test Outgoing".
3 - Add Check Operation and select Outgoing Pending Operation Operation, click Create.
4 - Select ADDS MA as the Management Agent and click Create.
5 - Click the Edit Check Operation for this newly create Check Operation. The below error occurred/displayed.

Error
System.NullReferenceException: Object reference not set to an instance of an object.
at ASP._Page_Views_Operation_Index_cshtml.<>c__DisplayClass1.<RenderGroups>b__0(TextWriter __razor_helper_writer) in c:\Program Files\UNIFY Solutions\Event Broker\Web\Views\Operation\Index.cshtml:line 39
at ASP._Page_Views_Operation_Index_cshtml.Execute() in c:\Program Files\UNIFY Solutions\Event Broker\Web\Views\Operation\Index.cshtml:line 19
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)

Henry reported that he got the above exception when clicking on the Create Agent (http://<EvB server>:8081/Agents page) due to IIS' "request filtering module" which I can only guess has been activated as a result of a recent Windows Update (???). When Henry reported the problem I tried for myself in my own lab environment and sure enough the same page (http://127.0.0.1:8081/Agents/Create/Unify.EventBroker.Agent.AD) was dispayed with the following error summary:

HTTP Error 404.7 - Not Found
The request filtering module is configured to deny the file extension.

Henry explained that he was able to selectively remove the filter, but I can only presume that this will be affecting EVERYONE now that this feature appears to have been activated in my lab without me even realizing it. We probably need to (a) add some extra doco in the troubleshooting section, (b) add something in the prerequisites section to ensure people avoid this in the first place, and (c) look at a way of automating the removal of this filter as part of the installation???

Migrate all Identity Broker installer improvements (Log, Patches, WCF, ASP.NET temp, log on as service, start service, ect).

Original issue description:

FIM Event Broker tries to log to C:\Program Files\UNIFY Solutions\Event Broker\Services\Logs, but does not create the directory. Update the installer to create the directory.

v3.0 and v3.1 have already been done, ie the prerequisite pages have been updated for both the log directory issue and the creation of WCF end-point issue.

The titles and descriptions share the Create/Update text. This is fine in the titles, but it could be lower case in the description of an operation or an agent. For example:

A feature is requested to support sites where UNIFY websites are hosted under IIS to be accessible externally to the hosting server - whereby a visual way of differentiating one site from another is required (DEV from TEST, DEV from PROD, etc.).

An approach has been implemented at one site by simply appending the following text to the site.css file - giving the effect of a different colour for the navbar background for DEV and TEST sites (PROD remains as per default installation):

/* Differentiate DEV from TEST and PROD */
.navbar { background-color: #ccff99 !important; background-image: none !important; }
/* Differentiate TEST from DEV and PROD */
/*.navbar { background-color: #ffffcc !important; background-image: none !important; }*/