I switched to excel services from office web app, and i want to revert my changes. remove-spwopisupressionSetting doesnt work!

I originally had excel web app working on prem, but since it didn't support powerview I tried my luck with excel services.
I switched to excel services by using the new-SPWOPISuppressionSetting cmdlet.
I figured to return to excel web app, I would just use the remove-SPWOPISupressionSetting cmdlet, but I removed the suppression setting and even reboot the server and it's still using excel services!
What do I have to do at this point, reinstall office web app completely? Its still working for word and powerpoint, why didn't it take back over for excel? Any tips?
Thanks

Hi,
From your description, my understanding is that you want to
remove the suppression settings for excel.
I could try these point below:
1.
Test the issue with another browser.
2.
Test the issue with another computer.
3.
Try to clear the cookie of your browser and test your issue.
4.
Try restart the IIS with command iisreset.
Please try command
Get-SPWOPISuppressionSetting to get
all the suppression settings on the current SharePoint farm to check if the excel is suppressed or not. You could refer to this article:
https://technet.microsoft.com/en-us/library/jj219445.aspx.
As word and PowerPoint work well, you could try command
Remove-SPWOPISuppressionSetting -Extension "XLSX" -Action "view" that you could refer to this article:
https://technet.microsoft.com/en-us/library/jj219452.aspx?f=255&MSPPError=-2147217396.
Best Regards,
Vincent Han
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Similar Messages

HT201272 used 2 days for download 1 magazine, it has been bad service from AIS ebook app and Matichon app.(download on high speed internet)

used 2 days for download 1 magazine, it has been bad service from AIS ebook app and Matichon app.(download on high speed internet)

iOS 6 came out a couple of days ago, so Apple's servers have probably been busy as a result of people downloading it

Printing Word documents to PDF from Office Web Apps Server 2013 yields inaccessible PDF files

I have Office Web Apps Server 2013 SP1 with March 2015 CU applied. The version shows up as "15.0.4569.1506" using Todd Klindt's
method. When anonymous users view the Word documents online through the Office Web Apps, they have an option to print them to PDF. The PDF file that gets generated as a result isn't accessible
(i.e. it isn't WCAG-compliant). using Adobe Acrobat Pro to check it I can see that it is missing tags, for example. The source Word document was made fully accessible from the point of view of Microsoft Office accessibility tools.
When viewing the same document in Word Online in Office 365, I get an extra option "Download as PDF". The PDF document produced is accessible. If I save a Word 2013 document as a PDF from within the Word editor, it also generates accessible
PDF.
I was wondering if the reason for the accessibility problem that I have misconfigured my on-premises Office Web Apps, or perhaps the accessibility compliance isn't built in yet. If the latter is true, I was wondering if someone could indicate whether
or not this is on the list of upcoming CUs.
thanks in advance.

Just check my WAC install, no this is likely an Office online only feature, at least at this point in time.
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.

How to get error information back from Office Web Apps server?

I'm developing a web application with an embedded Word iframe that interfaces with an Office Web Apps server; I am trying to implement the MS-FSSHTTPB protocol for my WOPI server.
More details here. When I send a bad response back to the OWA server it stops making requests to the WOPI server and sends the following error message back to the browser client: "Sorry, there was a problem and we can't open this document. If this
happens again, try opening the document in Microsoft Word."
Is there a way I can get additional information about what went wrong so that I can correct it?

Yes, this is closely related to SharePoint.
I'm trying to embed a Word editor in our web app. The Word iframe is served from the OWA server. It typically communicates with a SharePoint server to receive information about the document its trying to display.
I'm trying to implement the SharePoint portion. The servers communicate via the MS-FSSHTTPB protocol (among others) which I'm struggling to implement. When I send a response to the OWA server that it doesn't like then it stops replying. I'm wondering how
I can retrieve the exact error the occurred.
I believe I originally posted this question to Open Specifications > SharePoint Server Protocols.

Office Web Apps and Forms Based Authentication

Is it possible to use Office Web Apps Server 2013 to give external SharePoint Foundation 2013 clients access to Office documents in a View only capacity?
Does FBA work with Office Web Apps or would external users have to at least have a Windows CAL in AD if we are just using SharePoint Foundation?

Hi,
It may be possible.
Here are some links for your situation:
http://technet.microsoft.com/en-us/library/ff431682(v=office.15).aspx
http://blogs.technet.com/b/office_web_apps_server_2013_support_blog/archive/2014/03/20/office-web-apps-2013-errors-previewing-viewing-editing-documents-when-using-fba-in-the-extended-zone-but-not-the-default-zone.aspx
http://technet.microsoft.com/en-us/library/ee806890(v=office.15).aspx
Office Web Apps can be used only by SharePoint 2013 web applications that use claims-based authentication.
There is a known issue when using Office Web App in the extended zone with FBA, but not the default zone. Please configure FBA authentication in the Default zone in case of that.
Hope it helps.
Regards,
Rebecca Tu
TechNet Community Support

OWA 2013: Insecure Content javascript error in Google Chrome when attempting to launch Edit in Excel from Office Web Apps 2013

I'm unable to launch an excel file in the Client App from OWA using google chrome. I am able to open the excel file in the web application, but when clicking "Edit Workbook" and selecting "Edit Excel" the file never opens.
Opening developer mode shows a javascript error. This error comes back as:
[blocked] The page at 'https://owa.mysite.com/x/_layouts/xlviewerinternal.aspx?ui=en%2DUS&r…g%2Fsites%2Fmiketest%2Ftestlib%2FForms%2FAllItems%2Easpx&wdEnableRoaming=1' was loaded over HTTPS, but ran insecure content from 'ms-excel:ofv|u|https://intranet.mysite.org/sites/miketest/testlib/SitePageVerification.xlsx':
this content should also be loaded over HTTPS.
Both sites are using https, so I'm unsure what the error is about. Any ideas?

Hi Michael,
According to your description, my understanding is that you got an error when you tried to edit excel in client application with Chrome.
Per my knowledge, when you open or edit documents(from SharePoint library) in client application, it requires Open Documents ActiveX controls. Open Documents ActiveX controls limitations on browsers which do not support ActiveX. Currently only 32-bit versions
of Internet Explorer support this functionality. So , for resolving your issue, I suggest you use IE 32-bit.
More indormation, please refer to the link below:
http://technet.microsoft.com/en-us/library/cc263526.aspx
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Issue with office web apps sorry, there was a problem and we can't open this document.

Hi All,
i am having issue when trying to open the word file using office web apps farm. i have multi-tier farm (2 wfe, 2 apps and 2 owa). is that something wrong with certificate or the way AAM configured. Can anyone give me some direction please?

Hi,
According to your description, my understanding is that you failed to open the word file using office web app.
Please open the word file using office web app in other SharePoint sites and test whether this issue occurs. Also, please test whether all words have this issue.
Please reset IIS on the OWA server.
Please disconnect the SharePoint Farm from Office Web Apps and reconnect it. Then check the WOPIZone and TMG server.
Please created certificate for your PC and update mappings of IP addresses.
Some useful posts for your reference:
https://social.technet.microsoft.com/Forums/office/en-US/fdbf2198-5a62-422a-9015-a65599eabeb5/office-web-apps-2013-sorry-there-was-a-problem-and-we-cant-open-this-document-if-this-happens?forum=sharepointadmin
https://social.technet.microsoft.com/Forums/office/en-US/154e9673-8227-4913-9f2a-97677e4c5314/sorry-there-was-a-problem-and-we-cant-open-that-document?forum=sharepointadminprevious
http://sharepoint.stackexchange.com/questions/66013/a-problem-with-a-websites-security-certificate-for-apps
Best Regards,
Dean Wang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Office web apps without excel

Hi,
If office web app is installed in my environment but I do not have excel calculation service running then can I open and edit excel files ?

Office Web Apps 2010 supports Excel files via Excel Web Access (EWA). It only supports the XLSX file type, though (that is Office 2007 and newer). It does not support XLS, like Excel Calc Services does.
Trevor Seward
Follow or contact me at...
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 2013 + could not establish trust relationship

We currently have a three tier SharePoint 2013 Farm:
1. Web Front End Server (Server 2008 R2 Enterprise) - Servername: TEST2SP013.domain.dom
2. Central Admin Server (Server 2008 R2 Enterprise) - Servername: TEST2SPCA013.domain.dom
3. SQL Server (Server 2012 Datacenter) - Servername: TESTSQL012.domain.dom
All Machines are in the same IP/Subnet.
We are trying to setup a new server (Server 2012 R2 Datacenter) (Servername: TEST022.domain.dom) to run Office Web Apps 2013 in our TEST environment to test the system before rolling in production and have had issues throughout the entire process.
The technet articles we have used are:
http://technet.microsoft.com/en-us/library/jj219435.aspx
http://technet.microsoft.com/en-us/library/ff431687.aspx
http://technet.microsoft.com/en-us/library/jj219627.aspx
We finally have what I thought was a correct setup but anytime we try to edit or view a word, excel, powerpoint document within SharePoint 2013, we receive "Sorry, there was a problem and we can't open this document. If this happens again, try opening
the document in Microsoft Word."
We found a few How-To Setup Office Web Apps sites where other people provided step-by step instructions:
blogs.msdn.com/b/sowmyancs/archive/2012/10/29/install-configure-amp-monitor-office-web-apps-2013-for-sp-2013.aspx
http://www.wictorwilen.se/office-web-apps-2013-securing-your-wac-farm
http://blogs.technet.com/b/justin_gao/archive/2013/06/30/configuring-office-web-apps-server-communication-using-https.aspx
We reviewed the ULS logs and found the following error:
02/14/2014 13:38:40.24 w3wp.exe (0x1C04)                       0x1BB4 Office Web Apps
WAC Hosting Interaction       adhsk Unexpected WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.UnexpectedErrorException: HttpRequest failed ---> Microsoft.Office.Web.Apps.Common.HttpRequestAsyncException:
No Response in WebException ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate
is invalid according to the validation procedure.     at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)     at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)     --- End of
inner exception stack trace ---     at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)     at Microsoft.Office.Web.Apps.Common.Ht... 7bed0d51-511d-4541-a059-e2f72942e617
None of the article provide specific step-by-step instructions with using HTTPS in a test environment specifically when it comes to Self-Signed Certs through Active Directory Certificate Services.
We tried creating a Self-Signed Cert through IIS on the Office Web Apps Box which did not work.
We tried creating a Cert through Active Directory Certificate Services which did not work.
We tried adding the Cert through Central Admin > Security > Manage Trust which did not help.
We verified "get-spwopizone" is set to internal-https
We can access the Web Apps https://test022/hosting/discovery site and view the XML with no issue on any machine on our network.
We added our domain to the list of approved domains that can use Office Web Apps as well as add "Domain Users" as the security group that can "EDIT" Office Documents through Office Web Apps.
After each step, we tried performing either a system reboot or IIS Reset on the Office Web Appcs and WFE box.
My Question is how do we generate a certificate (either self-signed through IIS on the Office Web Apps Box or through AD) that will allow this application to work? I read that the Fully Qualified Domain Name needs to be in the SAN field of the Cert but when
we request it, I have no way of entering this information. I tried following http://technet.microsoft.com/en-us/library/ff625722 to manually request a certificate with a Custom SAN but that did not work either.
I am assuming the certificate issue is with the New Office Web Apps box. Is this correct?
-Chris

If internal cert then you will have to add certificate from OWA to tursted certificates in each sharepoint server plus add the certificate from central admin in Sharepoint through manage trust. Also you will need to install p7b file (file that contains
path to root certificate to verify each intermediate certificate) for internal cert to each sharepoint server to not get certificate error.
sachin

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 - Best Practice for App Pool Security Account?

Guys,
I am finalising my testing of Office Web Apps, and ready to move onto deploying it to my live farm.
Generally speaking, I put service applications in their own application pool.
Obviously by doing so this has an overhead on memory and processing, however generally speaking it is best practice from a security perspective when using separate accounts.
I have to create 3 new service applications in order to deploy Office Web Apps, in my test environment these are using the Default SharePoint app pool.
Should I create one application pool for all my office web apps with a fresh service account, or does it make no odds from a security perspective to run them in the default app pool?
Cheers,
Conrad
Conrad Goodman MCITP SA / MCTS: WSS3.0 + MOSS2007

i run my OWA under it's own service account (spOWA) and use only one app pool. Just remember that if you go this route, "When
you create a new application pool, you can specify a security account used by the application pool to be either a predefined Network Service account or a managed account. The account must have db_datareader, db_datawriter, and execute permissions for the content
databases and the SharePoint configuration database, and be assigned to the db_owner role for the content databases." (http://technet.microsoft.com/en-us/library/ff431687.aspx)

Office Web Apps 2013 with SharePoint 2013 Server

Hi All,
I have installed a separate server for Office Web Apps 2013 on Windows Server 2012 VM. I have followed TechNet's article on
Deploying Office Web Apps Server & exactly followed steps.
On SharePoint Server 2013 (Windows Server 2012), I followed TechNet’s article on
Configure Office Web Apps for SharePoint. The Office Web Apps on SharePoint 2013 environment works for
Excel document that shows “View in Browser” but
no Preview.
However, PowerPoint and Word documents doesn’t show “View in Browser”. I thought Internet Explorer 10 has some issue with Office Web Apps and checked on Chrome and results were same.
On SharePoint Server 2013 environment, I have configured 3 services applications, MMS, UPS and Excel Service.
1.) Do I need any other service applications to be enabled for OWA 2013?
I read number of blogs,
Installing Office Web Apps Server for SharePoint 2013 (Steve Mann),
Install Office Web Apps 2013 with SharePoint 2013 (Max Melcher) and Spence Harbar
(Enabling Office Web Apps Preview editing with SharePoint 2013). and all these blogs give more or less same steps that I have followed.
Strange thing is that Excel documents on my SharePoint 2013 sites are working but neither word or PowerPoint documents are not showing option for “View in Browser”.
I am using HTTP and not HTTPS.
2. Can someone please advice how could I solve the Office Web Apps 2010 on Word and PPT?
3. How to can enable preview for Excel, Word and PPT documents.
Thanks you.
Regards,
Aroh
Aroh Shukla

Hi Inderjeet and Olafur,
Thanks for your reply.
@Inderjeet: That site collection feature on SP2010 works on our production environment but on SP2013 site collection there is no OWA feature. Microsoft recommends to have a separate OWA2013 server and what I create
a separate VM for OWA2013 server.
@Olafur: Your suggestion looks spot on. The OWA server does show the discovery:
Our SP2013 development server has limited RAM (4GB) and it think is causing the issue.
Let me check if increasing RAM solves the issue.
Thanks again for your suggestions. (Interjeet and Olafur).
--Aroh
Aroh Shukla

SharePoint 2013 Anonymous (public) site and Office Web Apps Server 2013 issue with download.aspx

Our organization has a public facing anonymous site in SharePoint 2013 which allows access to documents (docx) in a library. ViewFormsLockdown is activated as we present the documents via CQWP / custom template. We are combating the usual
issue of multiple login prompts when using Internet Explorer when a user accesses said document. We also have tried using the Word Viewer (view only mode) from Office Web Apps Server 2013 which works well, but ...
the problem stems from the fact that users can go the file menu from the word view and choose to download the document (which is what we want), unfortunately it looks like the link redirects via /_layouts/15/download.aspx which also presents a login
prompt. Much has been written out there about doing direct links for documents via /_layouts/download.aspx to address multiple login prompts when the document is opening in word (from IE).
I've tried nearly every combination of recommendations (disabling client integration, browser file handling (permissive/strict), ViewFormsLockdown feature, web.config modifications with options and propfind verbs and more) all to varying levels of success,
but never totally getting rid of the prompt. It has been stated that because the downloads.aspx inherits from Microsoft.SharePoint.ApplicationPages.Download this will not allow anonymous access. We really want to use the word view from the Office
web app and have the file download functionality work from the menu there ... can anyone suggest an alternate fix? I might be wishing but will appreciate any guidance offered ...
cheers,
Dean
some reference links (but not all) for various things we've tried:
http://mohitvash.wordpress.com/2013/06/18/sharepoint-download-a-file-programatically/
http://blog.sharedove.com/adisjugo/index.php/2012/09/29/open-sharepoint-files-in-edit-mode-from-client-applications-and-not-read-only/
http://stackoverflow.com/questions/375390/office-documents-prompt-for-login-in-anonymous-sharepoint-site
http://yalla.itgroove.net/tag/anonymous-access/
Glifnard

I'm glad to here that the problem has been fixed. Thank you for sharing your experience here, it will be helpful to other community members who have similar questions.
Cheers,
Steve Fan
TechNet Community Support

Office Web Apps - Office Web Apps was unable to find the specified certificate

Hello,
Let me start by saying I did not see a forum listed for Office Web Apps and figured the SharePoint forum would be the second best place to post this. With that said, here's my issue...
I installed OWA 2013 on a Windows Server 2012 (not R2) VM and installed all the prereqs as described here: http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx Since this is a test environment, I'm planning on using a self-signed
cert which appears to be supported based on info found here: http://technet.microsoft.com/en-us/library/2e147f11-6f47-46bc-90bf-b2f179958d11(v=office.15)#certificate.
I created the cert using the following command:
New-SelfSignedCertificate -DnsName owa.test.local -CertStoreLocation cert:\LocalMachine\My
I then edited the cert's properties in the Cert Manager MMC snap-in and added a friendly name of "2014_OWA_Cert". I then proceeded to try and create the OWA farm by running:
New-OfficeWebAppsFarm -InternalUrl "https://owa.test.local" -CertificateName "2014_OWA_Cert" -EditingEnabled
This produces the following error:
New-OfficeWebAppsFarm : Office Web Apps was unable to find the specified certificate.
At line:1 char:1
+ New-OfficeWebAppsFarm -InternalUrl "https://owa.test.local" -CertificateNa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (:) [New-OfficeWebAppsFarm], ArgumentException
+ FullyQualifiedErrorId : CertificateNotFound,Microsoft.Office.Web.Apps.Administration.NewFarmCommand
What gives?

Hi Waqas
Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
Issue #3 in the above blog link does not reflect the same error I see on my servers.
I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
If you added domains to the Allow List by using the
New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
New-OfficeWebAppsHost cmdlet.
I have not added any domains to the Allow list so this did not help either. Should I add the domain?
Any further help with this is much appreciated.
Thanks again.
Yoshi

Office Web Apps - Preview Sharepoint 2010 documents in Sharepoint 2013 Search Results

Hi,
We have a Sharepoint 2013 search site collection. The content sources for the Search service application includes some Sharepoint 2010 sites. We also have Office Web Apps server deployed. When searching for documents, the OWA preview works for all the document
in local sharepoint 2013 farm. However document preview doesn't work for documents in the sharepoint 2010 farm.
Any idea why this happens?
Regards,
Muthu

Could you please elaborate more on open url / please give us some syntax how to use that is display template?
When we use open url do we still need to install office webapps in the 2010 environment?

I switched to excel services from office web app, and i want to revert my changes. remove-spwopisupressionSetting doesnt work!

Similar Messages

Maybe you are looking for