Microsoft Office WebApps Server

I have finished the initial installation of Microsoft Office WebApps and am receiving an HTTP Error 500.19 - Internal Server Error when I put the following in my browser http://servername/hosting/discovery.

I have followed the instructions found here up to this point and don't have an answer for this error.
http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx

Help!
Robert MohrAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mohit NairSenior AssociateCommented:
Hope you didnt install Office web apps on the server hosting Domain Controller. It wont work at all.
Run this command as this helps to register ASP.Net
%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir
0
Robert MohrAuthor Commented:
I did not. I did however install it on a server dedicated to just Office Web Apps for testing purposes. Having issue currently after attempting to run New-OfficeWebAppsFarm and PowerShell is telling me to install update KB2592525, however, it is already installed.
0
Robert MohrAuthor Commented:
I was able to get past the discovery piece and create the bindings between SharePoint 2013 and WebApps server. However, when I log into sharepoint and attempt to create or open a document such as excel I get a Server Error in '/x' Application. See attached image.
Any help on how to trouble shoot or anyone see this error?
2014-11-13-15-41-59.jpg
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Mohit NairSenior AssociateCommented:
This has been reported by quite a few users now.
Maybe the actual problem is DNS. The OfficeWebApp server(s) need to be able to resolve the URL to the SharePoint server(s). Add an “A” record in DNS that pointed to the SharePoint web server address

Reference article.
http://gavinmckay.wordpress.com/2014/04/04/sharepoint-2013-office-web-apps-permission-to-edit-this-notebook-error/
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Robert MohrAuthor Commented:
Still no answer on this thread. I am going to move forward with uninstalling both my web app server and sharepoint and installing the applications on servers mirroring OS and IIS versions (if possible for IIS).
0
Robert MohrAuthor Commented:
I added this to DNS. It did not solve the issue but was probably a good course of action.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.