- #Microsoft error reporting office 2013 install#
- #Microsoft error reporting office 2013 update#
- #Microsoft error reporting office 2013 windows#
This is a bit strange, if you look in the IIS for that specific for this file it is clearly there but if you try to browse to it you get a 404. Reported status: Contacting Participant.svc failed with an exception: The remote server returned an error: (404) Not Found. The second thing that I’ve seen is that (once you fix the certificate per above) the logs contains error messages that says it cannot access the Participant.svc file: BroadcastServicesWatchdog_Wfe reported status for BroadcastServices_Host in category ‘3’. This can be done either by removing all WOPI bindings and re-add them or by running the following command:
#Microsoft error reporting office 2013 update#
Once the machines are restarted you can go back to the logs and see if it now reports any issues and if everything is fine your machines should soon (it takes a couple of minutes) start reporting that they are Healthy.Īfter this you also need to update the WOPI Proof Key of your SharePoint farm(s), to avoid security errors when using Office Web Apps in SharePoint. Set-OfficeWebAppsFarm -CertificateName ""
Note that you need to restart all the servers in the farm once you have changed the certificate.
#Microsoft error reporting office 2013 install#
If you have an already existing farm and need to update the certificate you just install the certificate on all the machines (before doing anything else) and then use the following PowerShell command to configure the farm to use the new certificate, on one of the WAC machines. If you’re creating a new farm just proceed as normal with a certificate like this. In order to resolve this issue for the farm you have to create a new SAN certificamyte (or optionally a wildcard) containing the name of all the machines and the load balanced DNS entry. In order to test the endpoints of the different machines the watchdog processes cannot call the load balanced DNS entry () but instead has to call the individual machines, for instance – and the certificate is not valid for that DNS entry. If you take a closer look at the WAC logs you will see exceptions like this: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. But all the machines are reporting that they are Unhealthy. So you create a certificate for your WAC farm load balanced DNS address, for instance, install it on the WAC machines, set up the farm and everything looks fine. Especially Office Web Apps 2013, which sends the AuthN token in clear text over the wire. If you have been following the SharePoint 2013 space recently you should be pretty aware of that you should protect your server communication with SSL.
#Microsoft error reporting office 2013 windows#
One is related to certificates and the second is related to Windows Server 2012/IIS8 and WCF. Two common reasons for Unhealthy machinesĪs I said, most WAC farms I’ve seen are reporting all machines as Unhealthy and I’ve found two major reasons for this. In this log you will clearly see all the errors and be able to solve them, well at least most of them can be fixed by reading (and understanding) the log entry. You will find the logs under Applications and Service Logs > Microsoft Office Web Apps. You can see the Health reports in either the log files (SharePoint ULS Trace Log style) in your log directory on the WAC machines, but you might find it easier (and faster) to look in the Event Viewer of the machine. (Note: It will check all the reports from the last 10 minutes, so it is a slight delay in this status). If any of these watchdog process reports an error the machine is marked as Unhealthy. For instance it makes sure all the servers and service endpoints are responding, it checks if the proofing tools works by actually testing the service with a correctly spelled word and an incorrectly spelled word and so on.
These processes regularly check for issues with the different WAC services. The health reporting mechanism in Office Web Apps consists of a number of Watchdog processes (FarmStateManagerWatchdog.exe, ImagingWatchdog.exe etc). If you have installed and configured the farm according to the interwebs and/or official sources it is most likely that all your servers are reporting Unhealthy even though your WAC farm is running fine, from the end-user perspective.
0 kommentar(er)
