MIM Event Broker Forum
Welcome to the community forum for MIM Event 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.
Operation lists do not seem to be firing as expected
Description
Some scheduled Operation Lists do not seem to be running, and there is no feedback in the logs pertaining to the cause of the issue.
Affected Software
- MIM Event Broker
Symptom
MIM Event Broker displays the operation list as running, however, the list is not executing contained operations.
Resolution
This behaviour is due to the problematic operation list being contained in an exclusion group and is attempting to run whilst another member is already operating. Ensure that operation list schedules are planned appropriately such that unexpected blocking does not occur. See Schedules for further details.
Multiple Portal updates not triggering operation lists
Description
Successive updates to the MIM Portal results in operation lists configured with the MIM Event Broker Changes Activity to fire on the first update, blocking execution of subsequent calls to MIM Event Broker.
Affected Software
- MIM Portal
- MIM Event Broker
Symptom
After a large number of changes occur in the MIM Portal in succession, the Portal logs show that the workflow has successfully run each time. However, some changes may have been missed as they were processed after the import had completed.
Resolution
In order to ensure an optimal configuration for the Portal Workflow, please follow the recommendations made in the activity's Usage Considerations.
The service will not start because a port is in use
Description
MIM Event Broker service cannot be started, and a System.Exception: Port X is in use
message appears in the Windows Event Viewer. With the default configuration, this message will read System.Exception: Port 8080 is in use
.
Affected software
- MIM Event Broker
Symptom
- The MIM Event Broker service cannot be started on a machine due to a port exception.
Solution
This issue usually occurs because the web engine is attempting to host MIM Event Broker on a port that is already in use when the service is started.
Possible steps to resolve:
- Verify the web engine is not attempting to use a port that is known to be in use by another application.
- A web browser may still be listening to the MIM Event Broker port even after the service has been stopped, and as such, the web browser instance must be closed to completely clear the port for re-use (not just an FIM Event Broker tab, for instance).
- Restart the DNS service, as this has been known to hold on to ports.
- If that does not resolve the issue, execute the following command
netstat -aon | findstr :8080
(replacing8080
with the appropriate port number)- The number on the right is a process id - look at the task manager and try and find this id.
- If possible, close or restart the process with the id that was found.
- Use the command
tasklist
to match the id with the process name.
The current identity does not have write access
Description
The MIM Event Broker management studio cannot be accessed and is instantly redirected to the default ASP.net error page. Subsequently an exception is displayed in the FIM Event Log Viewer that details that The current identity does not have write access to '%.NET Installation Directory%\Framework/x64|Version|\Temporary ASP.NET Files
.
Affected software
- FIM Event Broker
Symptom
The MIM Event Broker management studio cannot be accessed and a warning similar to the following exception can be seen in the Windows Event Viewer:
... Exception information: Exception type: HttpException Exception message: The current identity (ExampleDomain\ExampleUser) does not have write access to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files'. at System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) at System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags, PolicyLevel policyLevel, Exception appDomainCreationException) ...
Solution
This problem may occur when an a particular user does not have the required permissions to write to the Temporary ASP.NET Files
directory of the host machine.
For more information on the Temporary ASP.NET Files
directory see http://msdn.microsoft.com/en-us/library/ms366723.aspx
To give the particular user the required permissions, open command prompt and redirect to the directory that holds the Temporary ASP.Net Files directory; which should subsequently be by default:
cd C:\Windows\Microsoft.NET\Framework64\v4.0.x\
And execute the following command, making sure to replace |SPECIFIC_USER| with the desired Service Account.
aspnet_regiis -ga "|SPECIFIC_USER|"
The service will not start due to a lack of permissions to create a WCF end-point
Description
MIM Event Broker service will not start and the following exception can be seen in the Windows Event Viewer Unify.Framework.UnifyServerStartException: The request to create a WCF end-point for Event Broker has failed due to lack of permissions to create a WCF end-point with the specified namespace
.
Affected Software
- MIM Event Broker
Symptom
The MIM Event Broker service cannot be started and the following details can be seen in the Windows Event Viewer:
Service cannot be started. Unify.Framework.UnifyServerStartException: The request to create a WCF end-point for Event Broker has failed due to lack of permissions to create a WCF end-point with the specified namespace. In order to give permissions for the end-point to be opened, run the Windows Command Prompt as administrator and run the following command: netsh.exe http add urlacl url=http://+:|PORT|/ user=|USERNAME| For more information search for information on the inner exception provided to this exception message. ---> Unify.Product.EventBroker.UnifyStartupException: The request to create a WCF end-point for Event Broker has failed due to lack of permissions to create a WCF end-point with the specified namespace. In order to give permissions for the end-point to be opened, run the Windows Command Prompt as administrator and run the following command: netsh.exe http add urlacl url=http://+:|PORT|/ user=|USERNAME| For more information search for information on the inner exception provided to this exception message. ---> System.ServiceModel.AddressAccessDeniedException: HTTP could not register URL http://+:59990/EventBroker/EventBrokerManagementStudio.svc/. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details). ---> System.Net.HttpListenerException: Access is denied at System.Net.HttpListener.AddAllPrefixes() at System.Net.HttpListener.Start() at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen() --- End of inner exception stack trace --- at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen() at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener) at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback) at System.ServiceModel.Channels.HttpChannelListener.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at Unify.Product.EventBroker.EventBrokerEngine.Start() --- End of inner exception stack trace --- at Unify.Product.EventBroker.EventBrokerEngine.Start() at Unify.Framework.UnifyEngine.Start()
Solution
This issue occurs because the Service account does not have sufficient permissions to create a WCF end-point on the specified port (by default this is 59990).
To provide the service account with the required permissions enter the following into command-prompt.
netsh.exe http add urlacl url=http://+:DESIRED_PORT/ user=DESIRED_SERVICE_ACCOUNT
Other solutions include:
- Changing the service account to an account that has the required permissions - specifically if the original service account should not be able to host services on specific ports.
- Changing the port to one that the original service account supports - specifically if the service account cannot/should not be changed.
The service will not start due to a Management Object provider error
Description
MIM Event Broker service cannot be started, and a System.Management.ManagementException: Provider failure
message appears in the Windows Event Viewer.
Affected software
- MIM Event Broker
Symptom
The MIM Event Broker service cannot be started on a machine due to a provider error.
Solution
This issue usually occurs because of an issue with the WMI provider.
Restarting the WMI service or the machine itself should resolve the issue. If not, follow the following instructions on Regasm.exe
http://msdn.microsoft.com/en-us/library/tzat5yw6.aspx for System.Management.Instrumentation.dll
, as mentioned on http://msdn.microsoft.com/en-us/library/bb961987.aspx.
Management studio redirects to a default ASP.net error page
Description
Although the service has started correctly - the MIM Event Broker management studio site cannot be accessed, and is instantly redirected to a default ASP.net error page.
Affected software
- MIM Event Broker
Symptom
The MIM Event Broker management studio cannot be accessed.
Solution
This problem may be due to a number of minor ASP.NET specific issues; refer to one of the following corresponding pages based on the exception details displayed in the Windows Event Viewer.
The service will not start due to an out of memory exception
Description
The MIM Event Broker service cannot be started, and a System.Management.ManagementException: Out of memory
message appears in the Windows Event Viewer.
Affected software
- MIM Event Broker
Symptom
The MIM Event Broker service cannot be started on a machine due to an out of memory exception.
Solution
This issue usually occurs because of a known issue with the win32_service WMI provider on Windows Server 2008 R2. More information can be found here.
Restarting the WMI service or the machine itself should resolve the issue.
Management Studio fails to load due to missing write access
Description
Browsing to Management Studio when fails with an error, stating that the identity account does not have write access to C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files.
Affected Software
- MIM Event Broker
- IIS
Symptom
The following error appears when browsing to Management Studio:
Event code: 3005 Event message: An unhandled exception has occurred. Event time: 12/04/2012 12:33:37 PM Event time (UTC): 12/04/2012 2:33:37 AM Event ID: 2c9910b1222346b3bd5c3b519d3d5fe7 Event sequence: 1 Event occurrence: 1 Event detail code: 0 Application information: Application domain: ef0bce15-1-129786716158618250 Trust level: Application Virtual Path: / Application Path: D:\UNIFY Solutions\Event Broker\Web\ Machine name: FIMSERVER Process information: Process ID: 1196 Process name: Unify.Service.Event.exe Account name: Customer\fimsyncuser Exception information: Exception type: HttpException Exception message: The current identity (Customer\fimsyncuser) does not have write access to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files'. at System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) at System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags, PolicyLevel policyLevel, Exception appDomainCreationException)
Resolution
This is due to the network identity having insufficient access for ASP.NET. Verify that the user, group, and/or application pool identity being used have write access to this folder. Refer to http://www.iis.net/learn/get-started/planning-for-security/understanding-built-in-user-and-group-accounts-in-iis and Isolating Applications under http://technet.microsoft.com/en-us/library/dd163542.aspx for more information on appropriately configuring these accounts.
Licence has expired and Event Broker is no longer operational
Description
A set of key features of MIM Event Broker has become non-operational if it is either unlicensed or its license expires. Additionally, some licenses limit MIM Event Broker functionality.
Affected software
- MIM Event Broker.
Symptom
When attempting unlicensed activity in an MIM Event Broker instance, behaviour similar to the following will be exhibited:
Unlicensed activities includes:
Symptom | Cause |
---|---|
Unable to start the scheduler | The MIM Event Broker service is unlicensed. |
Unable to execute operation lists | The FIM Event Broker service is unlicensed. |
Only a certain number of agents can be created | The current license limits the number of agents. |
Only a certain number of a specific type of agents can be created | The current license limits the number of allowable agent types. |
Some operations can be created whilst others cannot | The current license has either a _Whitelist_ or _Blacklist_ restricting the allowable types of operations. |
Solution
A new license will need to be ordered. To order an FIM Event Broker license please see How to Request a MIM Event Broker License
Customer support service by UserEcho