You’d think by now Microsoft would have stopped hard-coding its products to expect the US date format “MMDDYY”, but apparently the team behind Office Online Server 2016 are still holding out – and as a result you might find your OOS farm remains steadfastly “Unhealthy”, despite your best efforts.
If you’re not in the US (i.e. are running a different time and date format) and none of Wictor Wilén’s many fixes have borne fruit, try this one.
The telltale sign this time is the presence of one or both of these events in the Applications and Services Logs / Microsoft Office Web Apps event log, spewing forth roughly every 4 minutes:
41268:
<HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'.
Reported status: Likely caused by shipping osipartner outputs from somewhere other than a devmain checkpoint.
Trace string is found but the format is not correct in C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.
The following fields has the wrong format or content: [ Timestamp ].</HealthMessage>
Continue reading ‘Non-US dates make for Unhealthy OOS Farms’ »
