I ran the same New-OfficeWebAppsFarm script that I have been running for the installation/upgrades for years, so at first I thought it was the latest CU.
After installing the upgrade, I ran the following script to get the new WAC Server Version to make sure I was on the right version:
However, the version number did not return. From within SharePoint, I received a Server Error message, saying "We're sorry. An error has occurred. We've logged the error for the server administrator" This message was in the wopi frame, but would be seen within the WAC farm by going to https://wac.domain.com
Now the interesting part was that I was able to get content back from going to wopi-discovery: (http://wac.domain.com/hosting/discovery).
Looking at the Event Viewer, I was getting Application Error and .NET Runtime errors for the different application Watchdog.exe. At this point, I enabled verbose logging on the server.
I once again tried to open up the servicebusy.htm page, then opened up the ULS logs. I was able to find an Unexpected Error:
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.
ServiceInstanceFinder has no data because of an adapter exception, throwing exception to terminate process
I did a quick search and found a blog post on OOS which had the same issue (https://social.technet.microsoft.com/Forums/office/en-US/96dd1ac1-1173-47c3-bdc5-29ac0fd9f722/oos-2016-server-error-were-sorry-an-error-has-occurred-weve-logged-the-error-for-the-server?forum=OfficeOnlineServer). Basically, if the server name is not in all capitol letters, it doesn't work. To fix this, I ran a a script to update 3 registry values to update the Computer Name to all CAPS.
I opened up the servicebusy.htm page again and the expected error was returned:
I then stop my verbose logging by running the following:
Now, when I run the following script:
I get the expected results:
At least it is an easy fix...
I also tested this on a base image of WAC plus Service Pack 1, and same issue persisted.



Hats off to your presence of mind..I really enjoyed reading your blog. I really appreciate your information which you shared with us.
ReplyDeleteMS office course in chennai
This is good knowledge gaining article. This post is really the best on this valuable topic.
ReplyDeletesoftware development company in delhi
Want to know what is the best spy app for monitoring your child’s phone remotely? There is no need to explore so many applications one by one by yourself to find the best one. Simply stop over https://www.toptrackingapps.com/ and you will get a list of the leading tracking and monitoring apps for both iPhone and Android phone. Compare them and prefer the most suitable one.
ReplyDeleteKeep in mind, every one of your endeavors will end up waste if your expert looking site doesn't have an expert looking versatile form. Https://Owdt.com
ReplyDeleteVery useful and interesting information. Thank you for posting.
ReplyDelete"At least it is an easy fix..." - perfect, thanks!
ReplyDeleteThanks for Sharing This Article.It is very so much valuable content.
ReplyDeletevé máy bay vietnam airlines đi quảng châu
vé máy bay đi quảng châu
bay từ tphcm sang thượng hải mất bao lâu
giá vé máy bay đi anh vietnam airlines
vé máy bay 2 chiều đi mỹ
vé máy bay từ texas về việt nam
Greaat post
ReplyDeleteThanks for sharing this troubleshooting experience. Issues with Office Web Apps and SharePoint can be frustrating, especially when documents suddenly stop rendering inside the WOPI frame with a generic server error. Debugging through Event Viewer and ULS logs is often the only way to uncover the real cause. It’s interesting how something as small as a server-name configuration detail can trigger the problem. Technical posts like this are very useful for administrators managing SharePoint environments. Learning how to promote such technical guides through a digital marketing course can also help reach a wider developer community.
ReplyDeleteThanks for sharing this troubleshooting guide. Issues with Office Web Apps 2013 and SharePoint integration can be tricky, especially when server configuration or environment settings cause unexpected errors. Debugging through logs and checking farm configuration is often the key to identifying the real problem. In some cases, even small configuration details like server naming can lead to errors in the WAC farm environment. Developers interested in building stronger technical skills can also explore **Java course Chennai**, **Python course**, **Data Science course**, **Data Analyst course**, **Full Stack Development**, and **UI/UX course** from Login360 to expand their programming and technology knowledge.
ReplyDelete