Office Web Apps broken in IE11 after CU installation

We just installed the Oct 2013 CU and during testing found that Word and PowerPoint Office Web Apps now do not work in IE11 only. IE 8-10, Firefox, Chrome, and Safari all still display documents fine using Office Web Apps. Excel Web App doesn't display
an error, but it also seems to have issues and doesn't always display the ribbon menu with IE11 only.
The error being displayed is "Sorry, we ran into a problem"
Does anyone have any ideas on what is causing or has seen a similar issue?
Thanks.
Nick Hurst

There are posts about problems with SP & IE 11 all over the place. It's a known issue. Most of the problems can be solved by changing the compatability mode in IE. Here's some links you can check out:
http://corypeters.net/2013/10/sharepoint-and-internet-explorer-11/
http://sharepointthing.wordpress.com/2013/10/09/problem-with-sharepoint-2013-and-internet-explorer-11/
http://community.office365.com/en-us/forums/685/t/211953.aspx
cameron rautmann

Similar Messages

Office web apps feature not working after setup and configuration?

Hi I have installed the SP1 update and since then my office web apps features are not coming up in SharePoint. After running the updates and attaching the farm back i see the bindings and settings are applied but somehow the office web apps features are
not coming up in SharePoint. Can someone let me know what might be the issue?

Did you delete and recreate the WAC farm after you updated?
See: https://technet.microsoft.com/en-us/library/jj966220.aspx
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Office Web App 2013 : Compatibility issue after opening a word document with image from sharepoint 2013

Hi,
Uploaded a word doucment in sharepoint 2013 and When we open it in WebApp2013 then following compatibilty warning is reflecting.
"Compatibility Mode Functionality is currently limited"
how to supress this warning message ?
Thanks.
raj

Hi,
As I understand, you would like to insert document preview in Iframe, here is an article which describe about Document preview function for your reference:
http://community.obilogic.co.uk/blogs/teamblog/archive/2014/01/23/sharepoint-2013-custom-callout-with-file-preview.aspx
Regards,
Rebecca Tu
TechNet Community Support

Office Web App Feature doesn't exist in Site Collection Features

Hi
I have Installed Office 2010 professional
and then SharePoint Server 2010 64 bit and then Office Web App 2010 .
But After Creating the First Library and try to open office files (work , excel ....) It Cannot open , Only Excel Sheets can be Edited on the the Browser
Only .
I have make sure that the services is started , But I try to find Office web apps Feature on site collection feature , but i didn't find it ,
I think that office web app isn't compatible with the sharepoint but i don't know how to get It .
what can I do ?
Thanks for attention .

HI,Ensure that the service below are started on the server.
Excel Calculation Services, PowerPoint Service, and
Word Viewing Service, Check the below link that gives more details on configuration of office web app in 2010.
http://expertsharepoint.blogspot.de/2014/10/deploy-office-web-apps-installed-on.html
Anil Avula[MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

Office Web Apps Error after SP 2013 September 2014 CU

Hello Everyone,
I have a single front end and single SQL server for my SharePoint 2013 deployment. I also have Office Web Apps setup and running. However after installing SP 1 and the latest September 2014 CU it appears our users are seeing the below prompt
when open a Word doc in Office Web Apps.
However I am finding that if they use IE 9 or 10 and even Firefox everything works normal. This appears to be affecting just Word.
As for my Office Web Apps server it is still at Version 15.0.4420.1017 (RTM)
If I need to update my Office Web Apps server what order should i do. SP1, July, then Sept?
Thanks,
Ian...

You need to apply office web app update.
It should be in below order.
Office web app Sp1
September 2014 update
If this helped you resolve your issue, please mark it Answered

Office Web App error - unable to open PDF after multiple trials

Hi, we are using Office Web App server 2013 on win server 2012 (NO Sharepoint installed) to preview files (doc, docx, pdf, xls, xlsx, ppt, pptx), OWA is set as http, wopihost
is http as well under different from HTTP80, HTTP809 application pool
File conversion if fine for small files and large files to some point - we can process same large pdf (100MB) 30-50 times, but after that there is a message
"Sorry, Word Web App ran into
a problem opening this document. To view this document please open it in Microsoft Word."
Server has plenty of free space, PerfMon
does not show spikes, no memory spikes in Process Manager. ULS logs do not provide any good info either...
No errors in event log under Applications,
System, or Microsoft Office Web Apps sections.
That error will be shown if we process
the same file. if try to process different file it works fine (again - few dozen times), but if after that I try to process first file - it shows error again.
Documents
are located on the same server as OWA installed, same machine has wopi site in non owa application pool (from Microsoft demo
- C#)
The only resolution i found is to reset
WAC server from PowerShell or restart IIS - after that it starts to process original file...
If I just recycle OWA application pools
- HTTP80, HTTP809 it does not help. (tried to change Recycling condition in IIS for those pools - it slightly improves situation but does not resolve).
I can reproduce such pattern with different file types, it just matter of number of hits.
Same error present if we use OWA and wopi on machine as https with certificate.
We use VerboseEx option for logging - no errors in ULS log files, but multiple Sync exiting
early records similar to
Sync exiting early: LastSyncTime = 09/16/2014 14:52:07
at Microsoft.Office.Web.Apps.Environment.WacServer.ACacheableFarmStateObject.Sync(Boolean force)
at Microsoft.Office.Web.Apps.Environment.WacServer.AFarmSettings.TryGetSettingValue[T](String settingName,
T& value, Boolean shouldProcessValue)
at Microsoft.Office.Web.Apps.Environment.WacServer.WSConfigAdapter.TryGetValue[T](String settingName,
T& value)
at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter.GetAgentUri(WebAgentProperties
agentProperties, String machineName, String fqdn)
at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter.UpdateServiceList()
at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter.FindAllServiceInstances()
at Microsoft.Office.Web.Common.ServiceInstanceFinder.RefreshList(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback
callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback,
Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
---------------------------------There are some paired records
Cached service list has 39 service instances before the update
Cached service lists has 39 service instances after the update
So it goes as follows: OWA processing all formats fine, after trying same 100mb pdf file 50 times (it is possible to get same error with docx, just bigger number of trials) it does not process that pdf file, but processes others.
After IIS reset it works as usual again. After trying another 100mb pdf file 50-60 times OWA stops to process that another file... We are expecting large number of hits and resetting IIS every 30min is not a good solution...
Any help will be appreciated.
Thank you

Hi ,
Thank you for your post.
Whether the issue occurs with different file types or only the PDF.
Based on your description, when you reset WAC server from PowerShell or restart IIS, the issue is solved temporarily.
I recommend that you check the application account, re-enter the account, then reset the IIS.
whether the issue occurs with different file types or only the PDF.
In addition, please check if the link is useful:
http://stevemannspath.blogspot.jp/2013/04/sharepoint-2013-pdf-support-and.html
Best Regards,
Lisa Chen

Office Web Apps KeyNotFound Exception After December CU

After applying the December CU to my WAC 2013 farm, documents will no longer open in browser from SharePoint. The install went smooth. I followed the instructions to remove the hosts from the farm, install the update and recreate the farm. The
secondary server joined the farm without any errors. When I try to open a document from a SharePoint site, I see the following errors in the logs on the WAC hosts:
ServiceInstanceFinderAdapter.FindAllServiceInstances() threw an exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Collections.Generic.KeyNotFoundException: The given key was not
present in the dictionary.
at Microsoft.Office.Web.Apps.Environment.WacServer.AFarmTopology.GetMachine(String machineName)
at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter..ctor()     -
-- End of inner exception stack trace ---
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at Microsoft.Office.Web.Common.EnvironmentAdapters.HostEnvironment.LoadAdapterInstance(AdapterLoadInformation adapterInfo, Boolean readAppConfigOnly)
at Microsoft.Office.Web.Common.EnvironmentAdapters.HostEnvironment.AdapterLoadInformation`1.<>c__DisplayClass17.<BuildInstance>b__16()
at System.Lazy`1.CreateValue()
at System.Lazy`1.LazyInitValue()
at Microsoft.Office.Web.Common.EnvironmentAdapters.HostEnvironment.get_ServiceInstanceFinderAdapter()
at Microsoft.Office.Web.Common.ServiceInstanceFinder.RefreshList(Object state)
I can't find any online documentation about this error in a post update scenario. Any ideas on my next steps?
Thanks

Remove the WOPI binding from SharePoint, remove each OWA server from the farm (and the farm itself), then just recreate the setup. It looks like it is missing a machine name in the farm.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Office Web Apps is not working

Hi,
We have tried to deploy Office Web Apps Server but, after a number of tests, we haven't been able to view PowerPoint presentations. We tested "everything" but it didn't work.
Finally, to simplify and focus the problem, we just deployed Office Web Apps Server "on its own", that is: just Internal URL, HTTP, Open From URL Enabled and sharing docs from a shared folder in the same server. So we have:
\\wacserver\share\<Docs> (Excel, Word and PowerPoint)
http://wacserver
They work both "/hosting/discovery" and "/op/generate.aspx".
If we try to view Excel doc, it works. If we try to view Word or PowerPoint, id doesn't work.
For PowerPoint, it appears the PowerPoint Web Apps frame (FILE, START SLIDE SHOW, SLIDE - OF -, NOTES...) and, in the center, an animation
"PowerPoint Web App .....". After a couple of minutes, it stops with "Either you've lost network connectivity or our server is to busy to handle your request".
What we have seen from different sources:
FIDDLER
======
/op/view.aspx?... Response 200
/p/PowerPointFrame.aspx?... Response 200
/p/imagehandler.ashx?... Response 202
13 petitions to /p/ppt/view.svc/jsonAnonymous/GetPresentation Response 200
PROCESS MONITOR
==============
There were some folders and registry keys Network Service was trying to access with ACCESS DENIED response. We gave it permissions and they disappeared.
SYSTEM is trying to access some registry keys (SpellingWcfprovider.exe => HKU\S-1-5-18, ImagingService.exe => HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options, and 2 or 3 more). It gets an ACCESS DENIED
but SYSTEM, we have checked, has "Full control" permissions in those keys or folders.
These errors appear by Office Web Server running itself, although we are not making a PowrPoint file request.
ULS
===
Several times, it tries to find the PowerPoint presentation in the caché, doesn't find it, manage to get it but, when trying to put it in the cache, it receives a disk space error:
Determined file name [PowerPoint.pptx] from [\\wacserver\share\PowerPoint.pptx]
AFileFetcher: Starting Unc download at [\\wacserver\share\PowerPoint.pptx]
Begining UNC Download for [\\wacserver\share\PowerPoint.pptx]
Reading next block of bytes for [\\wacserver\share\PowerPoint.pptx]
End reading block of bytes for [\\wacserver\share\PowerPoint.pptx]
Reading next block of bytes for [\\wacserver\share\PowerPoint.pptx]
End reading block of bytes for [\\wacserver\share\PowerPoint.pptx]
AFileFetcher: Done downloading file. [\\wacserver\share\PowerPoint.pptx]
Downloaded file from final URL [\\wacserver\share\PowerPoint.pptx] with SHA256 [Y/whX0EzCZJQdHym/OPrMdrNVg0h8SwrC0TehaKIQdU=]
AFileFetcher: Will cache web file info to memory cache. [\\wacserver\share\PowerPoint.pptx]
Starting WriteStreamToDiskCache
Creating channel to DiskCache: http://wacserver:809/diskcache/DiskCache.svc
MachineTransfer [SourceMachine:wacserver, SourceMachineVersion:15.0.4543.1000, TargetMachine:wacserver, TargetMachineVersion:15.0.4551.1011, Method:DiskCacheService.PutCacheData]
PutCacheData: [167F6AC792AE9B53BEA7CD135A35C18F0710CF5916C49DD5804C9E29CF9149CA55D1C8D1AD526B45B91801E1502B2BCD, d1c8d155-52ad-456b-b918-01e1502b2bcd, 50758, wacserver]
PutCacheData: Writing to C:\ProgramData\Microsoft\OfficeWebApps\Working\d\1CA\167F6AC792AE9B53BEA7CD135A35C18F0710CF5916C49DD5804C9E29CF9149CA55D1C8D1AD526B45B91801E1502B2BCD
Not enough disk space to write. Sleeping once.
Not enough disk space to write. Giving up.
PutCacheData Response: [False]
The cache folder has enough disk size and PowerPoint.pptx file is just 30 KB.
It repeats this flow 3 times (as for the first HTTP requests).
During the 2 minutes test (until it fails) there are 14 traces like:
Failed to create process object for pid 7780 with exception System.ArgumentException: Process with an Id of 7780 is not running. at System.Diagnostics.Process.GetProcessById(Int32 processId) at Microsoft.Office.Web.Common.RequestPipe.ProcessManager.TryGetProcessObject(Int32
pid).
We have tried a number of things but none has worked. The farm has just one server and it says ist's unhealthy. We have Windows Server 2008 R2 SP1. We have read some ways to fix the health, like HTTP Activation feature, but it only works
for Windows Server 2012 as fas as we know.
Has anybody experienced something like this or have a posible solution? Office Web Apps Server should be so easy to deploy but we have spent a lot of time with this.
Thank you very much. Your help will be very appreciated.
Kind regards.

Hi John,
According to your description, my understanding is that you cannot view the PowerPoint files in Office Web Apps in SharePoint.
Was there any error when you view the PowerPoint files in Office Web Apps?
You can troubleshoot the error following the link below:
http://technet.microsoft.com/en-us/library/ff431687.aspx#tshoot
I also recommend to re-configure SharePoint to use the Office Web Apps Server to see if the issue still occurs.
http://technet.microsoft.com/en-us/library/ff431687.aspx#ConfigureMain
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Sorry, something went wrong - Open Office File from Search Results Page with Office Web Apps

Hi,
I'm getting "Sorry, something went wrong" error when I'm trying to open any office document from inside Search Results Page with Office Web Apps, the same error is appearing in the document preview as well.
The error in SharePoint logs says that the file cannot be found.
Please note that this error is coming only when the "Filename" of the document is not written in English (in my case its written with Arabic characters).
If I try to open it from the document library, its opening properly with no errors.
The only difference between two URLs (document URL in Search Results and in Document Library) is the value for "sourcedoc" attribute;
In the case of Search Results page, the filename in "sourcedoc" attribute is kept as is with Arabic characters.
While in the Document Library, the filename in "sourcedoc" attribute is converted into different characters (something like: "B9%D9%85%D9%8").
Anybody have an idea on how to overcome this issue, implement a workaround or modify the "sourcedoc" behavior?
Thanks in Advance.
Hamza AlSughier

Dear Wendy,
Thanks for your efforts, I already tried your last suggestion before, but this didn't solve my problem.
Actually my end users are accessing this portal using ADFS and HTTPS.
Finally I got this solved, I have done below to get my overall solution working perfectly:
- First I have configured Windows Authentication and ADFS Authentication on the same zone which is the default zone.
- The issue when opening office documents with Arabic file name has disappeared as a result of first change.
- Then I have faced an issue where we are not able to crawl content under Default zone, however we have to do so, after too many efforts, I found that its related to the Load-balancer/proxy, I have made the crawler server
to crawl himself (http://CrawlServerName:PortNumber).
- Also a change on Alternate Access Mapping was needed, I have set one of the extended zones (which is running Windows Authentication only) as Internal URL for the Default Zone, and this is was the URL I used for Crawling.
I have configured Server Name Mappings to make sure we got proper URLs in Search Results.
- Then we faced another issue, which is Authentication selection on login page (How to bypass this page, and authenticate using ADFS auto), I used this solution (Set Custom Sign In Page):
http://0ut0ftheb0x.wordpress.com/2014/01/04/skip-the-authentication-selection-page-at-_logindefault-aspx-in-a-mixed-authentication-environment/.
- I faced one more issue as a result of above workaround; Sign Out functionality wasn't working well; users get logged in automatically whenever I click on Sign Out. I solved this by modifying the "Sign Out" Control under _layouts;
I made it to redirect users to ADFS Sign Out Page instead of SharePoint Sign Out Page (I know its not recommended, but I don't have any other option).
Hamza AlSughier

SharePoint 2013 and MS Office Web Apps - error in sharepoint's url calls OWAps

I have new SharePoint 2013 Server farm and one dedicated Office Web Apps (OWAps) server.
This farm is placed in one domain (Acompany.local). There is other domain BCompany.local whitch has both trusted to first domain (two diffirent forests, two company's branches).
Users from second domain BCompany.local well see intranet portal, build in sharepoint in the first domain (url like http://intranet.Acompany.local).
But, when they try to use OWAps, f.e. whatching preview or try to open docs for edit in browser - they see error in frame.
I'm looked it in google chrome's developer tools and find' that sharepoint use wrong url to call OWAps - like http://owaps/... instead of http://owaps.Acompany.local/...
When I created new office web app farm by:
New-OfficeWebAppsFarm -InternalURL "http://owaps.Acompany.local" - ExternalURL "http://owaps.Acompany.local" -AllowHttp -EditingEnabled
And in sharepoint farm new SWOPI binding by:
New-SPWOPIBinding -ServerName "http://owaps.Acompany.local" -AllowHTTP
Get-SPWOPIBinding tell that all SWOPI bindings are http://owaps.Acompany.local, but in devtools I continue to see wrong http://owaps/... url
Any idea to fix this behavior?

The reason WAC is recommended to be installed on a dedicated server is that it recreates the IIS sites/settings. This is why you're seeing the setting reset itself after restart.
What I'd probably recommend is creating a script that queries the WAC URL on a regular basis.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Office Web Apps Server - Access is denied

Hello,
I was able to create an Office Web Apps server and was able to create a new farm for that server all without any issues, everything works great.
Unfortunately right after creating the farm, when attempting to run any other related powershell commands such as:
Get-OfficeWebAppsFarm
Remove-OfficeWebAppsFarm
I get this error in powershell:
Get-OfficeWebAppsFarm : Access is denied.
At line:1 char:1
+ Get-OfficeWebAppsFarm
+ ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-OfficeWebAppsFarm], SecurityAccessDeniedException
    + FullyQualifiedErrorId : System.ServiceModel.Security.SecurityAccessDeniedException,Microsoft.Office.Web.Apps.Adm
   inistration.GetFarmCommand
Although everything is actually working on the server, I'd like to be able to use those other commands in the future so I can check configurations, use "Remove" for running updates, etc... Unfortunately it appears as though this Access is
denied error may interfere with those activities.
Has anyone seen this before?
Thank you

Hi,
According to your post, my understanding is that you failed to run any other related powershell commands after creating the farm for Office Web Apps server.
If the account trying to get OfficeWebAppsFarm does not have local admin access on the machine you will simply get an “Access is denied”.
Please make sure you have the permission to run the commands.
More information:
http://www.wictorwilen.se/office-web-apps-2013-securing-your-wac-farm
Thanks,
Linda Li
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Linda Li
TechNet Community Support

Office Web Apps Server IIS site disappeared?

I deployed an Office Web Apps server on a dedicated VM to be used for Lync 2013. After the initial installation / set up, I confirmed the discovery URL. It worked fine.
However, after one point in time, PowerPoint Presentations stopped working. When trying to share a PPT presentation, the Lync client popped up a message saying "Sorry, we couldn't upload <ppt file name> because we're having trouble connecting
to the service. If this keeps happening, try contacting your support team". I've done many many Lync and Office Web Apps install myself previously, and never had a message pop up like the one I saw in this case.
I tried going to the Web Apps discovery URL again, and it didn't get anywhere. I got on the Web Apps server and all the IIS sites were wiped.
I tried uninstalling the Office Web Apps server and reinstalling, but from that point on, IIS sites for Web Apps just would not appear under IIS manager.
Has anyone had similar issue with Office Web Apps?
Thanks,
Andrew Shin, TechNet Forum replies

Hello,
Maybe the windows update is active and configured to Automatically download and installed update of Office Web Apps and this behavior just breaking your setup.
Try
remove the farm of WAC
Install SP1
and start new deployment of farm.
Link SP1
http://www.microsoft.com/en-us/download/details.aspx?id=42547
How update your farm Office Web Apps
http://technet.microsoft.com/en-us/library/jj966220(v=office.15).aspx
Hugs[]s
Robson Hasselhoff - Follow me @Robk9e

Office Web Apps server / Lync server 2013

Hi I have installed a Lync 2013 Server and Office Web Apps Server. Configured Lync topology, Office Web Apps farm and certificates.
However when i start the services i get this error message in the log saying Office Web Apps discovery failed.
Event ID: 41033
Description:
Office Web Apps Server (WAC) discovery failed, PowerPoint content is disabled.
Attempted Office Web Apps Server discovery Url:
Received error message: Invalid Uri syntax for WAC configuration
The number of retries: 1,
Cause: Office Web Apps Server may be unavailable or network connectivity may have been compromised.
Resolution:
Check HTTPS connectivity from this box to the Office Web Apps Server deployment using the discovery Url.
I can access the OWAS server Url from Lync Server
Connecting to the HTTPS discovery URL is working fine, and brings up the XML-page (after i click "show all content").
The two servers are located on the same internal network, DNS resolves fine both ways, and no firewall rules blocks any connections between the two. Can anyone please help me figure this out?
Only identical problem found online is here (Invalid Uri syntax for WAC configuration):
http://blogs.technet.com/b/dodeitte/archive/2012/09/10/office-web-apps-server-amp-lync-server-2013.aspx
He resolved the problem by assigning a new OAuthTokenIssuer certificate. This however did not fix the problem in my case.
Regards
Sverre A. Veel

Hi,
In addition, please make sure you have restarted front end and office web apps server after reissuing the certificate.
Kent Huang
TechNet Community Support

Office Web Apps Server 2013 / Real-Time co-authoring

Hello,
In general, I would like
to ask the development team or product
manager SharePoint /Office web Apps.
As you already know in the cloud
product version introduces new features. Such as
authoring and other unlike on-premises version . This link demonstrate it.
http://blogs.office.com/2013/11/06/collaboration-just-got-easier-real-time-co-authoring-now-available-in-office-web-apps/ .
Please tell me the plans or roadmaps for the implementation
of these functions in the server version. Or Microsoft
has no plans to develop this area?

great, and as i said, we are working to keep parity, but there are still many features which are technically considered in preview in the O365 environment. after several months, depending on stability, feedback, and whether the feature fits well with
the product, it may either be tested to go into on-prem farms and come out of preview or be dropped altogether (auto-hosted apps).
This feature is definitely one that is key to the future of the product, but there isn't a timeline on when it will come to onprem. there ia a lot of additional testing before anything can be integrated to on-prem as the environments have many
more variables than the rather rigid architecture at O365, as well as the fact that the o365 farms have many of the preview features and so then anything to go into a feature for on-prem needs to be re-vetted in farms without those extras and checked for dependencies
(not normally an issue, but still part of the process).
Christopher Webb | Microsoft Certified Master: SharePoint 2010 | Microsoft Certified Solutions Master: SharePoint Charter | Microsoft Certified Trainer| http://tealsk12.org Volunteer Teacher | http://christophermichaelwebb.com

Office Web Apps - "Could not find trace string in ULS logs" unhealthy?

I have reviewed everything I could find on unhealthy WAC clusters as my problem seems unrelated to certificate or missing components. I've already digested
http://www.wictorwilen.se/office-web-apps-server-2013---machines-are-always-reported-as-unhealthy (Thanks Wictor).
The particular configuration is an Office Web Apps 2013 ([X-OfficeVersion, 15.0.4551.1005]), running on top of Windows Server 2012, configured for http access (SSL offloaded NLB cluster) and finally linked to Exchange 2013, Lync 2013 and SharePoint
2013. Everything works as expected from client side after setting IIS ARR to handle all reverse proxy bits.
FarmOU                            :
InternalURL                       : https://officeapps.fqdn/
ExternalURL                       : https://officeapps.fqdn/
AllowHTTP                         : True
SSLOffloaded                      : True
CertificateName                   :
EditingEnabled                    : True
LogLocation                       : C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS
LogRetentionInDays                : 7
LogVerbosity                      : Unexpected
Proxy                             :
CacheLocation                     : C:\ProgramData\Microsoft\OfficeWebApps\Working\d
MaxMemoryCacheSizeInMB            : 75
DocumentInfoCacheSize             : 5000
CacheSizeInGB                     : 15
ClipartEnabled                    : False
TranslationEnabled                : False
MaxTranslationCharacterCount      : 125000
TranslationServiceAppId           :
TranslationServiceAddress         :
RenderingLocalCacheLocation       : C:\ProgramData\Microsoft\OfficeWebApps\Working\waccache
RecycleActiveProcessCount         : 5
AllowCEIP                         : False
ExcelRequestDurationMax           : 300
ExcelSessionTimeout               : 450
ExcelWorkbookSizeMax              : 50
ExcelPrivateBytesMax              : -1
ExcelConnectionLifetime           : 1800
ExcelExternalDataCacheLifetime    : 300
ExcelAllowExternalData            : True
ExcelWarnOnDataRefresh            : True
OpenFromUrlEnabled                : False
OpenFromUncEnabled                : True
OpenFromUrlThrottlingEnabled      : True
PicturePasteDisabled              : True
RemovePersonalInformationFromLogs : False
AllowHttpSecureStoreConnections   : False
Machines                          : {WAC15PD-02, WAC15PD-01}
The problem however is an incessant logging on the WAC cluster nodes of event 1204,2204 followed almost immediately by 1004,2004. This repeats every 4min or so...
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Office Web Apps Monitoring" />
<EventID
Qualifiers="0">1204</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-02-04T20:49:37.000000000Z" />
<EventRecordID>3043246</EventRecordID>
<Channel>Microsoft Office Web Apps</Channel>
<Computer>wac15pd-01.fqdn</Computer>
<Security
/>
</System>
- <EventData>
<Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported status: Could not find trace string in ULS logs in C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage>
<ComponentOwner>ServicesInfrastructure</ComponentOwner>
</HealthReport></Data>
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Office Web Apps Monitoring" />
<EventID
Qualifiers="0">2204</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-02-04T20:49:37.000000000Z" />
<EventRecordID>3043247</EventRecordID>
<Channel>Microsoft Office Web Apps</Channel>
<Computer>wac15pd-01.fqdn</Computer>
<Security
/>
</System>
- <EventData>
<Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported status: Could not find trace string in ULS logs in
C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage> <ComponentOwner>ServicesInfrastructure</ComponentOwner>
</HealthReport></Data>
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Office Web Apps Monitoring" />
<EventID
Qualifiers="0">1004</EventID>
<Level>2</Level>
<Task>10002</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-02-04T20:49:39.000000000Z" />
<EventRecordID>3043266</EventRecordID>
<Channel>Microsoft Office Web Apps</Channel>
<Computer>wac15pd-01.fqdn</Computer>
<Security
/>
</System>
- <EventData>
<Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>AgentManagerWatchdog reported status for
AgentManagerWatchdog in category 'Recent Watchdog Reports'. Reported status: Machine health is Unhealthy</HealthMessage> </HealthReport></Data>
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Office Web Apps Monitoring" />
<EventID
Qualifiers="0">2004</EventID>
<Level>2</Level>
<Task>10002</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-02-04T20:49:39.000000000Z" />
<EventRecordID>3043267</EventRecordID>
<Channel>Microsoft Office Web Apps</Channel>
<Computer>wac15pd-01.fqdn</Computer>
<Security
/>
</System>
- <EventData>
<Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>AgentManagerWatchdog reported status for
AgentManagerWatchdog in category 'Recent Watchdog Reports'. Reported status: Machine health is Unhealthy</HealthMessage> </HealthReport></Data>
</EventData>
</Event>
Further exploration of ULS log files (C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS) did not yield particularly much, except the following;
02/04/2014 20:48:04.48 UlsControllerWatchdog.exe (0x1244)      0x0F60 Services Infrastructure       Uls Controller Watchdog       ajbam Assert
We're about to trace a string for category MsoSpUlsControllerWatchdog at level Info and we expect to find in the log later, but it appears that the category has been throttled. We will never be able to find the string and this watchdog will always fail.
StackTrace:   at Microsoft.Office.Web.UlsControllerWatchdog.Program.CheckServiceInstance(ServiceInstance serviceInstance)     at Microsoft.Office.Web.Common.WatchdogHelperThreadManager.GetHealthResults(WatchdogExecutionContext
context, ServiceInstance si)     at Microsoft.Office.Web.Common.WatchdogHelperThreadManager.WatchingThreadMethod(Object o)     at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback
callback, Object state, Boolean preserveSyncCtx)     at System.Threading.ExecutionContext.Ru... 345fbec5-e958-4f1f-bf56-d65c1c0d472a
02/04/2014 20:48:04.48* UlsControllerWatchdog.exe (0x1244)      0x0F60 Services Infrastructure       Uls Controller Watchdog       ajbam Assert
...n(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)     at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch() 345fbec5-e958-4f1f-bf56-d65c1c0d472a
02/04/2014 20:48:05.52 UlsControllerWatchdog.exe (0x1244)      0x0F60 Services Infrastructure       Services Infrastructure Health adhog Unexpected Health report
by UlsControllerWatchdog: Agent: UlsController, eventId: 1204, eventType: Error, categoryId: 1, eventMessage: <?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">    <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported
status: Could not find trace string in ULS logs in C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage>    <ComponentOwner>ServicesInfrastructure</ComponentOwner> </HealthReport> 345fbec5-e958-4f1f-bf56-d65c1c0d472a
02/04/2014 20:48:05.52 UlsControllerWatchdog.exe (0x1244)      0x0F60 Services Infrastructure       Services Infrastructure Health adhoh Unexpected Health report
by UlsControllerWatchdog (persistent): Agent: UlsController, eventId: 2204, eventType: Error, categoryId: 1 345fbec5-e958-4f1f-bf56-d65c1c0d472a
I suspect these might be related, but can't seem to find any logical explanation why this should cause the Get-OfficeWebAppsMachine to report HealthStatus of Unhealthy. If related, is there a way to disable this check or remove throttling in a safe
way? Alternatively if this is some coding issue (I've not found any other blog/QA dealing with this particularly) it would be nice to get confirmation of this and potentially a fix/solution.
Any help would be greatly appreciated. Thank you!

Hi ChristiaanB,
You get this ULS error because you change the log verbosity of the OWA farm. I wrote an article for this on my blog : OWA unhealthy uls issue
Regards,
Wes

Office Web Apps broken in IE11 after CU installation

Similar Messages

Maybe you are looking for