Translation Service 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 the Translation Service application.
Table 10. Translation Service events
Event ID | Description | Cause and Resolution |
---|---|---|
47001 |
The Translation Service is starting. |
|
47002 |
The Translation Service was started. %1 |
|
47003 |
The Translation Service is stopping. |
|
47004 |
The Translation Service was stopped. |
|
47005 |
Unexpected exception occurred in the Translation Service. Message: %1 Stack: %2 |
|
47006 |
The Translation Service is running under an account that is not authorized to connect to the server. |
|
47007 |
Unable to load the application manifest file from the installation directory. File: %1 |
CAUSE: Either the file has been deleted or the service account does not have permissions to read from the installation directory or the file has been corrupted. RESOLUTION: Verify that the file exists. If it does not, reinstall the application. If it does exist, verify that the service account has permissions to read the file. If the service account has read permissions on the file, then it is corrupted and you should reinstall the application. |
47008 |
Unable to compile the application manifest file from the installation directory. File: %1 Errors: %2 |
CAUSE: The file has been corrupted and contains errors. RESOLUTION: Reinstall Office Communications Server. |
47009 |
Unable to start Translation Service. Exception: %1 |
|
47010 |
This rule, and any profiles which reference it, will not be used. Rule (friendly) name: %1 Rule distinguished name: %2 Invalid field(s): %3 |
CAUSE: The translation rule contains one or more invalid field values. |
47011 |
These two rules, and any profiles which reference them, will not be used. First rule (friendly) name: %1 Second rule (friendly) name: %2 Distinguished name: %3 |
CAUSE: Two translation rules contain identical distinguished name field values. |
47012 |
This profile will not be used. Profile name: %1 Invalid field: %2 |
CAUSE: This profile contains an invalid field value. |
47013 |
These profiles will not be used. First profile name: %1 Second profile name: %2 |
CAUSE: These two profiles contain identical name fields. |
47014 |
All configuration data was successfully loaded. |
|
47015 |
All configuration data was loaded, but some bad data was detected and will not be used. |
CAUSE: Review preceding event log entries for more detail. |
47016 |
An unexpected exception occurred while loading configuration data. Exception: %1 Stack: %2 |
|
47017 |
An exception occurred during a regular expression replace operation. Rule name: %1 Rule pattern expression: %2 Rule translation expression: %3 Called phone number: %4 Exception: %5 |
RESOLUTION: Verify rule pattern and translation expressions. |
47018 |
The translation result is not a valid phone number format. Rule name: %1 Rule pattern expression: %2 Rule translation expression: %3 Called phone number: %4 Translation result: %5 |
CAUSE: A normalization rule is incorrect and the resulting translated number is not a valid phone number. RESOLUTION: Verify rule pattern and translation expressions. |
47019 |
The translation result exceeds the maximum acceptable length of 256 characters. Rule name: %1 Rule pattern expression: %2 Rule translation expression: %3 Called phone number: %4 Translation result: %5 |
RESOLUTION: Verify rule pattern and translation expressions. |
47020 |
A request for the default location profile failed because a default was not set. User %3 requested the default location profile, but a default has not been configured. It is likely this problem affects other users as well. In the past %1 minutes, %2 attempts to get the default location profile failed. |
CAUSE: Office Communications Server clients that are enabled for Unified Communications may request the details of their default location profile, but the pool has not been configured with a default location profile. RESOLUTION: Use the Voice tab on the Front End Properties (pool level) to select a default location profile for the pool. |
47021 |
Multiple requests for the default location profile failed because a default was not set. At least %1 different users have requested a default location profile in the last hour. This may represent an issue that is not specific to individual users. This message will not be repeated again for %2 hours even though the problem may persist. |
CAUSE: Office Communications Server clients that are enabled for Unified Communications may request the details of their default location profile, but the pool has not been configured with a default location profile. RESOLUTION: Use the Voice tab on the Front End Properties (pool level) to select a default location profile for the pool. |
47022 |
A request for the specific location profile failed because the profile is not known. User %1 requested an unknown location profile named '%2'. This location profile name may have been specified in group policy or selected by some other means available to the user. Location profile requests that fail for this user will not be reported again for another hour. |
CAUSE: Office Communications Server clients that are enabled for Unified Communications may request the details of a specific location profile based on group policy settings or based on user selection. RESOLUTION: Review group policy settings for this user and ensure the specified location profile has been defined in the system. |
47023 |
Multiple requests for the default location profile failed because a default is not defined. At least %1 different users have requested an unknown location profile in the last hour. This may represent an issue that is not specific to individual users. This message will not be repeated again for %2 hours even though the problem may persist. |
CAUSE: Office Communications Server clients that are enabled for Unified Communications may request the details of a specific location profile based on group policy settings or based on user selection. RESOLUTION: Review group policy settings and ensure the specified location profiles are defined in the system. |
47024 |
The Translation Service application was disabled. |
|
47025 |
The Translation Service application was enabled. |
|
See Also
Other Resources
VoIP Components
Normalization Rules
Creating and Configuring Location Profiles