Tag Info

New answers tagged

0

Check that Excel Calculation Services is started. Central Admin > Application Management >Manage services on server


-1

the problem is that the excel is to complex for showing.. try a simple excel sheet and it will work


0

The Double Encoding Bug has been fixed in the September 2014 CU of SharePoint 2013. Source: http://www.toddklindt.com/blog/Regressions/sp2013sep2014cu.aspx


1

Probably the "Double Encoding Bug". You can find a workaround here: http://thesharepointfarm.com/2014/06/workaround-ms14-022-double-encoding-bug/


0

We experienced a similar issue with a library migrated from our 2010 environment, I was able to edit the document with using office 2013, save the document back. Afterwards Office web word was able to edit the document....


0

There could be several reasons why you might be getting this issue , Make sure the owa is on the different server and properly joined to the sharepoint server . Create the owa farm and make sure the sharepoint server is in healthy state . I encountered this issue and i could observe that there was a security windows patch was being done on our servers ...


1

Before few days I was having same issue. Office web app was install correctly and every thing was done correctly. But still when I was trying preview any file I was getting error "Sorry we couldn't open this ..." Then I start digging ULS logs and I found SPWOPI is failing due to net tcp. So I did steps as below My first step was go on the both the ...


2

This behavior could be caused if you have your Alternative Access Mapping (AAM) Default Zone set to use protocol http while your OWA is set to use HTTPS. One solution I found is to change the Default Zone to use HTTPS. Change the Default Zone by going to Central Administration > Application Management > Configure Alternative Access Mapping > ...



Top 50 recent answers are included