Inbound Routing Events Related to Enterprise Voice
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
The following table lists Office Communications Server events that are related to inbound routing.
Table 8. Inbound routing events
| Event ID | Description | Cause and Resolution |
|---|---|---|
45001 |
The Inbound Routing Application is starting. |
|
45002 |
The Inbound Routing Application was started. |
|
45003 |
The Inbound Routing Application is stopping. |
|
45004 |
The Inbound Routing Application was stopped. |
|
45005 |
Unexpected exception occurred in the Inbound Routing Application. |
|
45006 |
Unable to load settings from configuration file. |
CAUSE: The inbound routing application is incorrectly configured, or the program does not have permission to read the configuration file. RESOLUTION: Verify that the RTCSRV service account has read permission on the InboundRouting.exe.config file in the installation directory. |
45007 |
Exception occurred while processing request. |
|
45008 |
The routing script '<script_name>' version '<version_number>' was successfully loaded from <script_location>. |
|
45009 |
Unable to load the application manifest file from the installation directory. |
CAUSE: The file has been deleted, or the RTCSRV service account does not have permission to read from the installation directory, or the file is corrupted. RESOLUTION: Verify that the file exists. If it does not, reinstall $(SERVER_PRODUCT_GENERICNAME_STR). If the file does exist, verify that the RTCSRV service account has permission to read the file. If the RTCSRV service account has read permission on the file, then the file is corrupted, and you should reinstall $(SERVER_PRODUCT_GENERICNAME_STR). |
45010 |
Unable to compile the application manifest file from the installation directory. |
CAUSE: The file is corrupted. RESOLUTION: Reinstall $(SERVER_PRODUCT_GENERICNAME_STR). |
45011 |
Inbound Routing Application is waiting for the $(SERVER_PRODUCT_GENERICNAME_STR) to start. |
CAUSE: The inbound routing application is not active until it can connect to $(SERVER_PRODUCT_GENERICNAME_STR). You may or may not see this event, depending on whether $(SERVER_PRODUCT_GENERICNAME_STR) is slow to start. RESOLUTION: None, unless you see this event multiple times, in which case you should examine the event logs to determine why the $(SERVER_PRODUCT_GENERICNAME_STR) has not started. |
45012 |
Inbound Routing Application is running under an account that is not authorized to connect to the server. |
CAUSE: The RTCSRV service account is not a member of the RTC Server Applications local group. RESOLUTION: Reinstall $(SERVER_PRODUCT_GENERICNAME_STR). |
45013 |
Inbound Routing Application is unable to load routing script defined in the InboundRouting.exe.config |
|
45015 |
Unable to open event '<event_ID>'. Internal error. |
|
45016 |
<Application_name> application is enabled. |
|
45017 |
<Application_name> application is disabled. |
|
45018 |
The script used when user has not published routing data was not found in the configuration or failed to load. |
RESOLUTION: Correct the configuration file, and resolve any previous errors related to script loading. |
45019 |
User <SIP URI> provided a routing document with errors. Default call handling was applied instead. Issues with this user's routing documents will not be reported again for another hour. |
CAUSE: A new or experimental user agent may have published a routing document with errors. RESOLUTION: Replace the user agent that published the defective configuration. |
45020 |
User <SIP URI> provided a routing preamble that references an unknown built in script. Missing script name=<script_name> version=<version_number>. Issues with this user's routing publication will not be reported again for another hour. |
CAUSE: A new or experimental user agent may have been deployed that does not match the server version or routing scripts enabled on the server. RESOLUTION: Add the missing script to the server, or replace the user agent that is attempting to use the missing script. |
45021 |
Multiple users have routing rules that are not understood by the server. |
CAUSE: A new or experimental user agent may have been deployed or server configuration changes may have created a mismatch with existing user agents. RESOLUTION: Add the missing script to the server, or replace the user agent that is publishing the routing document. |
45022 |
A voice call to user <SIP URI> failed because it is not possible to determine the user's Unified Communications (UC) policy. |
|
45023 |
Multiple users have a badly formatted Unified Communications policy. |
|
45024 |
Missed call notifications cannot be sent. |
CAUSE: The Exchange Unified Messaging server may be experiencing an issue. RESOLUTION: Examine the event logs on the indicated Exchange Unified Messaging server to determine the cause of the issue. |
45025 |
An attempt to use the following Exchange Unified Messaging server for a missed call notification succeeded: <Exchange_UM_Server>. Any previous errors have been resolved. |
|
45026 |
A missed call notification could not be generated because the template '<template_name>' is not supported by any of the Exchange Unified Messaging servers in dial plan <dialplan_name>. Failure occurrences: <number_of_failures>, since <date/time>. |
CAUSE: A new routing script may have been deployed that requests a template that is unavailable on the deployed Exchange Unified Messaging servers. RESOLUTION: Upgrade the Exchange Unified Messaging servers, remove the script, or modify the script to use an available template. |
45027 |
A server supporting template '<template_name>' was found in dial plan <dialplan_name>. Any previous errors have been resolved. |
|
45028 |
A missed call notification could not be generated. |
CAUSE: Dial plan <dialplan_name> does not have any Exchange Unified Messaging servers defined. Failure occurrences: <number_of_failures>, since <date/time>. RESOLUTION: Check the configuration for this dial plan and point it to appropriate Exchange Unified Messaging servers. |
45029 |
An Exchange Unified Messaging server was found for dial plan <dialplan_name>. |
|
45030 |
A missed call notification could not be generated for user <SIP_URI> because the assigned dial plan <dialplan_name> is not known. Issues with this user's dial plan will not be reported again for another hour. |
CAUSE: The dial plan is no longer defined, or permission to access Active Directory objects may not be granted to this process. RESOLUTION: Assign the user to a new dial plan, or adjust the permissions on AD DS. |
45031 |
A missed call notification could not be generated because the user has an unknown Exchange Unified Messaging dial plan. |
CAUSE: A dial plan may have been removed or disabled, or permission to access Active Directory objects may not be granted to this process. RESOLUTION: Assign the user to a new dial plan, or adjust the permissions on Active Directory. |
45032 |
The forwarding URI '<SIP_URI>' for contact <contact_name> is not a valid SIP URI. |
CAUSE: The forwarding URI value stored in the otherIpPhone attribute for this contact is not a valid SIP URI. RESOLUTION: Correct or remove the value from AD DS. |
45033 |
Multiple users have an invalid static forwarding URI. |
CAUSE: A faulty script or tool may have been used to set Active Directory attributes. RESOLUTION: Correct or remove the value from AD DS. |
45034 |
An attempt to send diagnostics information failed. |
|
45035 |
An attempt to send diagnostics information succeeded. |
|