KMS_TS_featureImage.png' alt='Static Activation Key Technet - Apps' title='Static Activation Key Technet - Apps' />Microsoft Dynamics AX 2. Installation guide by ANEGIS Consulting Microsoft Dynamics Partner. Microsoft Dynamics AX 2. Installation guide   Published on Jan 6, 2. Owned and created by Microsoft Company. Programs To Clone Hard Drive. Published due to official Partnership marketing rights. VAMTProductKeys.png' alt='Static Activation Key Technet - Apps' title='Static Activation Key Technet - Apps' />Wictor Wiln Share. Point MCA, MCSM, MCM and MVP Office Web Apps Server 2. As you might have noticed I have somewhat fallen in love with Office Web Apps 2. WAC as we say now that weve gotten this close to each other. Its an amazingly well written server product with the good side benefit that it is also very usable for the end users. Even though me and WAC has been hanging around for a while and by now know each other pretty well, WAC has constantly been reporting that it is Unhealthy. And from what Ive seen, heard and experienced in the field I am not aloneOffice Web Apps 2. Health Reporting. Office Web Apps 2. WAC farm and its machines. You can at any time see the Health status of your machines by running the following Windows Power. Shell command Get Office. Web. Apps. Farm. Machines. If you have installed and configured the farm according to the interwebs andor 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. The health reporting mechanism in Office Web Apps consists of a number of Watchdog processes Farm. State. Manager. Watchdog. Imaging. Watchdog. These processes regularly check for issues with the different WAC services. 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. If any of these watchdog process reports an error the machine is marked as Unhealthy. Note It will check all the reports from the last 1. You can see the Health reports in either the log files Share. Point 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. You will find the logs under Applications and Service Logs Microsoft Office Web Apps. 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. Two common reasons for Unhealthy machines. As I said, most WAC farms Ive seen are reporting all machines as Unhealthy and Ive found two major reasons for this. One is related to certificates and the second is related to Windows Server 2. IIS8 and WCF. Correct WAC Farm certificate. If you have been following the Share. Point 2. 01. 3 space recently you should be pretty aware of that you should protect your server communication with SSL. Especially Office Web Apps 2. Auth. N token in clear text over the wire. So you create a certificate for your WAC farm load balanced DNS address, wac. WAC machines, set up the farm and everything looks fine. But all the machines are reporting that they are Unhealthy. 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 SSLTLS secure channel. Its not that strange actually. In order to test the endpoints of the different machines the watchdog processes cannot call the load balanced DNS entry wac. DNS entry. 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. If youre creating a new farm just proceed as normal with a certificate like this. A workspace that uses the Access database engine to access a data source. The data source can be an Access database file, an ODBC database, such as a Paradox or. How to troubleshoot HyperV guest installations and how to template a virtual machine to avoid future problems. Office clients use internet connectivity to perform activation, downloads, and online synchronization. Update your firewalls outbound allow lists for direct. Ba9GITab8/U5pek4AwWVI/AAAAAAAAIyo/Fk-HEH-yyfc/s1600/VisualStudioLicense.png' alt='Static Activation Key Technet - Apps' title='Static Activation Key Technet - Apps' />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 Power. Shell command to configure the farm to use the new certificate, on one of the WAC machines. Note that you need to restart all the servers in the farm once you have changed the certificate. Set Office. Web. Apps. Farm Certificate. Name wac. contoso. 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. After this you also need to update the WOPI Proof Key of your Share. Point farms, to avoid security errors when using Office Web Apps in Share. Point. This can be done either by removing all WOPI bindings and re add them or by running the following command Update SPWOPIProof. Key. WCF. svc endpoints not working on IIS8. The second thing that Ive seen is that once you fix the certificate per above the logs contains error messages that says it cannot access the Participant. Broadcast. Services. WatchdogWfe reported status for Broadcast. ServicesHost in category 3. Reported status Contacting Participant. Semantics Palmer Pdf'>Semantics Palmer Pdf. Best Cms Cctv Programs there. The remote server returned an error 4. Not Found. There are other similar error messages. 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 4. Heres a good way to test if youre suffering from this issue without reading any logs Invoke Web. Request https wacserver. AnonymousBroadcast. Ping. Tip this command andor URL is a very good way to use in your monitoring software or load balancer to check if the WAC farmmachine is up and running. If you receive a HTTP status equal to 2. When you installconfigure IIS8 on Windows Server 2. Tech. Net and trying to do a minimal installation with as little Server features installed as possible you are most likely not installing the HTTP Activation for. NET Framework 4. 5 WCF Services. In order for IIS to understand. Static file handler, you need to install this Feature on your WAC machines. It can be done using the Add Roles and Features Wizard as shown above or using the following Power. Shell command. Note that it will at the same time install two other dependent features. Add Windows. Feature NET WCF HTTP Activation. If youre installing a WAC machine from scratch your Power. Shell command should look like follows on Windows Server 2. Import Module Server. Manager. Required Features. Add Windows. Feature NET Framework 4. Core,NET Framework 4. ASPNET,. Web Mgmt Console,Web Common Http,Web Default Doc,Web Static Content,. Web Filtering,Web Windows Auth,Web Net Ext. Web Asp Net. 45,Web ISAPI Ext,. Web ISAPI Filter,Web Includes,Ink. And. Handwriting. Services, NET WCF HTTP Activation. Recommended Features. Add Windows. Feature Web Stat Compression,Web Dyn Compression. Once the feature is installed, there is no need for any server restart, you should see that your machines are reported as Healthy. Remember it can take up to 1. You can sometimes speed up the health reporting a bit by restarting the WAC Service Restart Service WACSMIf they are no reported as Healthy then you have another issue. Check the logs again, fix it, report to me what you did and why and Ill update this post. Another note, you might not see the same status on all WAC machines when you inspect the health status for each machine. WAC machines are not constantly talking to each other, it may take a while before the synchronize. You can always log in to each and every WAC machine and run the following cmdlet to get the actual value of that specific machine Get Office. Web. Apps. Machine. Repairing an Office Web Apps Farm. There is a Power. Shell cmdlet in Office Web Apps 2. Repair Office. Web. Apps. Farm. This command is sounding way better than it actually is. It will not repair anything, it will remove all Unhealthy servers, and nothing more.