Software Exchange Resource Manager

SoftwareExchange Resource Manager
Frequently Asked Questions

General Licensing Permissions Scheduling Installation / Migration


Events are not firing and there are DCOM errors in the Windows Application Event Log. Why is that?
Exchange Resource Manager requires that the ERM Service Account is granted the "Log on as a batch job" right in the effective policy settings of the server running ERM. This happens automatically when ERM is installed, but if these rights are superceded by a Group Policy Object (GPO) it may cause ERM not to function. DCOM errors indicating an authentication failure are often seen in the Windows Application Event Log when meeting requests are sent to ERM-managed mailboxes given this scenario. In some cases, ERM may work for a period of time and then stop working at the point the inherited GPO is applied. See Microsoft KB article 312497 for more information on this requirement (http://support.microsoft.com/default.aspx?scid=kb;en-us;312497).
I changed a recurring meeting, but when the updated meeting request was declined, my meeting disappeared. What happened?
ERM uses the same functionality as MS Exchange so that if a user reschedules a resource and that request is declined (for whatever reason), MS Exchange will then delete the original meeting scheduled for the resource.
I do not receive a response when I cancel a meeting, and the meeting appears in a cancelled state rather than being removed from the resource calendar. What’s going on?
A refresh of the Exchange cache is necessary after managing a resource in order for the “Send As” rights granted to the Service Account to take effect. By default, this occurs every two hours. Any cancellations that occur after the Exchange cache has refreshed should occur normally.
ERM-managed resources simply stopped processing meeting requests.
Ensure that the password for the ERM service account is still valid. Attempt to verify the ERM service account from the ERM Mailbox Browser by clicking Edit -> Product Configuration -> Service Account tab -> Verify. Correct any pop up errors.
Resources stopped responding to meeting requests every two days. ERM has to be un-installed and re-installed to fix the problem.
Check the System Event Log for DCOM errors with an event ID of 10004. Ensure that the ERM service account has “log on as a batch job” user rights in the effective local security policy setting for the server.
None of the resources residing on a particular mailbox store respond to meeting requests. When the inbox of an ERM-managed resource is viewed, the event sinks (items with a subject of “ERMEventRegItemSync” or “ERMEventRegItemAsync”) are visible. The application event log has a EXOLEDB errors with a source of 116 every time the server is rebooted or the Exchange Information Store is restarted.
This is due to a problem with the mailbox store containing the resource mailboxes. Refer to the resolution steps in the following article: http://support.microsoft.com/default.aspx?scid=kb;en-us;316622. Either fix the existing store as described in the article or created a new store and move the resource mailboxes to newly created store.
ERM retains cancelled meetings on the resource calendar with the word “Cancelled:” pre-pended to the subject of the meeting and no response is sent to the meeting organizer.
The ERM Service account requires “Send As” rights to the resource account in order to correctly process cancelled meetings. ERM grants these rights as part of the management process, but it can take up to 2 hours for the new rights to take effect, since a refresh of the Exchange cache is necessary. Verify that the ERM Service account is granted “Send As” rights to the resource account (properties -> Security tab) in Active Directory Users and Computers. Allow two hours after management for these rights to take effect.
markermarkermarkermarker
Simpler-Webb
1717 W. 6th St.
Suite 140
Austin, TX 78703
Phone
Local: (512) 322-0071
Toll Free: (800) 808-3083
Fax
(512) 322-0074
Newsletter
Get valuable insight delivered straight to your inbox

 
 Security code