Robert Mohr
asked on
Office WebApps Server Error in '/x' Application
I am getting the following error when I attempt to open any MS Office Document within our SharePoint 2013 Foundations site. Help!
See Image for Runtime Error. It occurs on the web page.
2014-11-13-15-41-59.jpg
See Image for Runtime Error. It occurs on the web page.
2014-11-13-15-41-59.jpg
ASKER
Dan -
Thank-you for your help with this!
Where is the config file located? I attempted to do research (google) with no luck. I logged into IIS but I'm not sure where to go.
In regards to where the application resides, I entered the URL of the file and it still gave the same error
URL of file was http://<servername>/Shared%20Docu ments/test .xlsx?Web= 1
Couple things to note -
When I deployed the single server office web apps server to use HTTP, I entered this line into PowerShell
New-OfficeWebAppsFarm -InternalURL "http://<servername>" -AllowHttp -EditingEnabled
When running above PowerShell command, I get a notice that says "You should only do this if users of this office web apps server have licenses that permit editing using office web apps." I went ahead and chose "Yes" even though I'm not sure what that means. Everyone has a copy of Office on their machines.
It's also worth noting that I received positive installation verification when entering the following link into a browser http://servername/hosting/discovery after I set up the webapps farm.
Here is configuration information -
Thoughts?
Thank-you for your help with this!
Where is the config file located? I attempted to do research (google) with no luck. I logged into IIS but I'm not sure where to go.
In regards to where the application resides, I entered the URL of the file and it still gave the same error
URL of file was http://<servername>/Shared%20Docu
Couple things to note -
When I deployed the single server office web apps server to use HTTP, I entered this line into PowerShell
New-OfficeWebAppsFarm -InternalURL "http://<servername>" -AllowHttp -EditingEnabled
When running above PowerShell command, I get a notice that says "You should only do this if users of this office web apps server have licenses that permit editing using office web apps." I went ahead and chose "Yes" even though I'm not sure what that means. Everyone has a copy of Office on their machines.
It's also worth noting that I received positive installation verification when entering the following link into a browser http://servername/hosting/discovery after I set up the webapps farm.
Here is configuration information -
My webapps server is Server 2008R2 (IIS 7)
SharePoint server is Server 2012R2 (IIS 8)
I'm considering putting SharePoint on Server 2008R2 so there's is a closer match with server and IIS.
My version of is SharePoint 2013 Foundations
I'm using this TechNet article to set up my webapps server. http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx
Thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Dan
Thanks for assisting finding webconfig file(s).
No luck on that change however. The webconfig files on the SharePoint server had
I have rebooted both my WebApps Server and my SharePoint Server.
Any further insight?
Thanks for assisting finding webconfig file(s).
No luck on that change however. The webconfig files on the SharePoint server had
<customErrors mode="On">
which I then changed to
<customErrors mode="Off">
I searched the WebApps server to see if the config file there even had <customErrors mode="Off"> and it had no customErrors line.I have rebooted both my WebApps Server and my SharePoint Server.
Any further insight?
ASKER
It may be worth noting that when I now go to
http://<servername>/hosting/disco very
that I get a 404 error and the configuration verification page does not show. Augh!!!!!
http://<servername>/hosting/disco
that I get a 404 error and the configuration verification page does not show. Augh!!!!!
ASKER
Scratch that last comment please. No 404.
ASKER
This helped find the path to a webconfig file. thank-you!
Open in new window
to this:
Open in new window
Or, if you do not want to do this, logon to the server where this application lives and try to go to the URL which is giving you the error.
Please post the error full text of the error message.
Dan