Topic Last Modified: 2010-11-11
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
- From the Operations Console, double-click this alert, and then
click the General tab. Review the description of the alert
that includes the variables specific to your environment.
- From the Operations Console, double-click this alert, and then
click the Alert Context tab. Review the logged events that
meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
^(49|96)$ |
Event Source |
MSExchange OWA |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Client Access/Outlook Web Access |
Rule Name |
The WebReady Document Viewing worker application can't be found. |
Explanation
This Error indicates that the WebReady Document Viewing service did not open an attachment as a Web page. WebReady Document Viewing lets users access file attachments in Microsoft Office Outlook Web App. Users can access common file types such as Microsoft Word documents even if the application is not installed. The event may occur if one or more of the following conditions are true:
- The value of
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{F7CC98B4-F6F5-489D-98EB-000689C721DE}\LocalServer32\(Default)
is empty. Alternatively, the file referenced by this registry key
is incorrect.
- The TranscodingService.exe file is missing from the computer
that is running the Client Access server role.
User Action
To resolve this error, follow one or more of these steps:
- Verify that the correct value exists for the registry specified
in the Explanation.
- In Registry editor, under the registry subkey
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{F7CC98B4-F6F5-489D-98EB-000689C721DE}\LocalServer32,
double-click the registry key (Default).
- In Value data, verify that the value specified is a path
of the TranscodingService.exe file. The default location of the
file and the registry key value is C:\Program
Files\Microsoft\Exchange
Server\V14\ClientAccess\owa\bin\DocumentViewing\TranscodingService.exe.
- In Registry editor, under the registry subkey
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{F7CC98B4-F6F5-489D-98EB-000689C721DE}\LocalServer32,
double-click the registry key (Default).
- Verify that the TranscodingService.exe file exists in the
location that is specified in the registry. If it does not exist,
copy that file from the
\Setup\ServerRoles\ClientAccess\owa\bin\DocumentViewing folder on
the Exchange Server 2010 DVD, and then paste it to the
Client Access server. The default location to replace the file on
the client Access server is C:\Program Files\Microsoft\Exchange
Server\V14\ClientAccess\owa\bin\DocumentViewing.
- Remove and then re-install the Client Access server role. For
more information about how to modify server roles, see Modify or
Remove Exchange 2010.
- Contact a Microsoft Support professional to resolve this issue.
To contact a Microsoft Support professional, visit the Exchange Server Solutions Center. In the navigation
pane, click Assisted Support Options and use one of the
assisted support options to contact a Microsoft Support
professional. Because your organization may have a specific
procedure for directly contacting Microsoft Technical Support, be
sure to review your organization's guidelines first.
For More Information
If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.