SharePoint 2013 disable Save/ Share or Print option in Office Web Apps for PDF and Word Docs

Hi,
How can we disable Save/ Share or Print option in Office Web Apps for Word and PDF files.
Regards,

Rights Management Server/Service
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

Similar Messages

  • Hp officejet pro 8610 prints solid black on scanned pdf and word doc pictures

    -HP Officejet Pro 8610
    -problem printing scanned pdf document and word doc. photos
    -My new HP Officejet Pro 8610 printed a newly scanned pdf document as an all black picture. I then printed a saved word documtent from my iMac which included a small picture. The document print was acceptable, but the picture was solid black. There were no error messages. These were, my initial tests, to check this new printer.

    Hey there @TM-10 
    Welcome to the Community
    I read through your post about your new Officejet 8610 scanning a document to your computer and printing out all black. I have a couple ideas for you to try.
    Try the steps in this guide: Unexpected Scan Output Using HP Scan Application for HP Multifunction Printers When Using OS X v10.9...
    Press the Power button to turn on the product.
    With the product turned on, disconnect the power cord from the rear of the product.
    Unplug the power cord from the wall outlet.
    Wait at least 15 seconds.
    Plug the power cord back into the wall outlet.
    Reconnect the power cord to the rear of the product.
    If the product does not turn on by itself, press the Power button to turn it on.
    Ensure the printer is plugged in directly to the wall outlet, avoiding power bars and surge protectors. This ensures the printer is receiving full power and may help.
    Good luck
    R a i n b o w 7000I work on behalf of HP
    Click the “Kudos Thumbs Up" at the bottom of this post to say
    “Thanks” for helping!
    Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

  • Since upgrading to Lion OS, Firefox (6.0.2) will not allow the print option in Preview (5.5) for PDFs. The Rainbow wheel turns until I eventually force close.

    I cannot print wirelessly to printer or to Evernote, etc. Print option will not work. If I use Safari, the PDF will print.

    Most likely culprits are one of these:
    com.vmware.kext.vmnet          0073.02.98
    com.vmware.kext.vmioplug          0073.02.98
    com.vmware.kext.vsockets          90.1.5
    com.vmware.kext.vmci          90.1.1
    Boot into safe mode, put the machine to sleep, wait about 10 minutes, wake it, and see if the issue persists. If not, dump vmware, restart normally, and repeat the sleep/wake steps.
    See
    What is a kernel panic,
    Technical Note TN2063: Understanding and Debugging Kernel Panics,
    Mac OS X Kernel Panic FAQ,
    Resolving Kernel Panics, and
    Tutorial: Avoiding and eliminating Kernel panics for more details.

  • Office web app 2013 file not found

    Hi,
    Trying to access a document preview from sharepoint 2013 i get "file not found" from the office web app server.
    In the OWA server uls logs I can see a messege "disk cache file not found" so i looked at the cachelocation and the renderinglocalcachlocation
    directories and i can only find the doc preview files in the renderinglocalcachlocation dir.
    I also made sure the identity of openfromurlhost and openfromurlweb application pools have access to this documend and i
    run the openfromurlenable command.
    any ideas ?
    thanks.

    Hi,
    Try the following:
    1- https://support.office.com/en-nz/article/Configure-disk-based-cache-settings-75429eaf-893a-4a27-bca7-bf75497091de
    2-adding OWA
    url to the "Trusted Sites".
    3-Make sure you have followed the instructions for OWA installation configurations
    http://blogs.msdn.com/b/uksharepoint/archive/2013/08/06/scripted-installation-of-sharepoint-2013-and-office-web-apps-server-from-the-field-part-4.aspx
    Kind Regards,
    John Naguib
    Technical Consultant/Architect
    MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation
    Please remember to mark your question as answered if this solves your problem

  • 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

  • Open Documents with Office Web App - SharePoint 2013

    We have configured Office Web App for our SharePoint 2013 Farm and in Site settings, Site Collection Features,  have disabled "Open Documents in Client Applications by Default" . Out of 15 sites, all documents in 13 sites open in Office
    Web App. One of the 2 sites where the document still open using Client Application is a Wiki site.
    Advanced propertied for the libraries settings has been set to "Use the server default (Open in the browser)". Anything else to check to open documents in Office Web App?
    Thanks
    MP

    Hi,              
    As I understand, you encountered the issue when you want to open documents with Office Web App.
    Check things below:
    1. In the library setting->advanced setting, you can choose the open in the browser to see if the same situation will occur.
    2. Check if you have not enable the Open Documents in Client Applications by Default feature.
    If you choose Activate to enable the Open in Client feature (documents will open in the client application), or
    Deactivate to disable the Open in Client feature (documents will open in the browser).
    You can go to Site setting->site collection administration->site collection feature->Open
    Documents in Client Applications by Default to set the feature.
    The article below is about how to set the default open behavior for browser-enabled documents.
    https://technet.microsoft.com/en-us/library/ee837425(v=office.15).aspx
    The article below is about how to configure office web apps for SharePoint 2013.
    Configure Office Web Apps for SharePoint 2013
    Best regards
    Sara Fan
    TechNet Community Support

  • Office web apps Server for Sharepoint 2013

    Hello,
    I used the following article to install office web apps server and hook it up to a test sharepoint server:
    http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx. The OWAS service was verified as working by loading:
    https://owas.companyname.com/hosting/discovery
    For the sharepoint configuration phase, the following commands were run on the sharepoint machine:
    1) New-SPWOPIBinding -ServerName "owas.companyname.com"   -- (owas.companyname.com) is the host name of the owas server)
    2) Get-SPWOPIZone
    3) Set-SPWOPIZone -zone "external-https"
    However, office documents are still launching in the desktop office applications, not in the browser. Any ideas of what else I may need to do?
    thanks,
    Sherazad

    Hi  ,
    According to your description, my understanding is that you fail to configure Office Web Apps for your SharePoint 2013.
    How about run Get-SPWOPIZone? If you can get a result, it says that your  SharePoint  have connected with Office Web Apps.
    Then you can run below command to  change the zone to internal-https.
    Set-SPWOPIZone -zone "internal-https"
    Reference:
    http://technet.microsoft.com/en-us/library/ff431687(v=office.15).aspx 
    http://stevegoodyear.wordpress.com/sharepoint-2013-build-guide/office-web-apps-2013-server-install-and-configuration/
    Thanks,
    Eric
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
    contact [email protected]
    Eric Tao
    TechNet Community Support

  • Office Web Apps 2013 - Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word

    Hello
    I had configured Office Web Apps for SharePoint 2013 which was working fine for about 2 months until this morning.
    The error message I get for WORD, PDF and Excel files is:
    The ULS logs on the WFE give me this:
    WOPI (CheckFile) Proof Data: AccessToken Hash '1572676699' [1054 bytes], URL
    01/08/2014 11:01:58.01*    w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              afk59    Monitorable   
    WOPI                              agxqc    Medium      WOPI Signature verification
    attempt failed with public key 01/08/2014
    11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              agxqc    Medium      WOPI
    Signature verification attempt failed with public key
    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              agxqb    Medium      WOPI
    Signature verification attempt failed - no public key    e75ead18-af27-4d44-ba50-b38b408011e8
    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              ahdzz    Monitorable    WOPI
    Proof: All WOPI Signature verification attempts failed    e75ead18-af27-4d44-ba50-b38b408011e8
    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              ag7pj    Unexpected    WOPI
    (CheckFile) - Invalid Proof Signature for file Letterhead Template.docx  url: http://site.contoso.com/_vti_bin/wopi.ashx/files/9c5d0d7077aa43e9a9538c02deb57580?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOi
    The ULS Logs on my Office Web Apps server gives me this:
    Error message from host: Verifying signature failed, host correlation:     d197d187-ef9d-42f6-ae4f-c4b8199c1078
    WOPICheckFile,WACSERVER FileNotFound
    WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.FileUnknownException: WOPI 404
    Any idea what may have caused this issue all of a sudden?
    Thank you.
    Yoshi

    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

  • Exchange 2013 OWA published through TMG: Unable to preview documents with Office Web App server

    We configured our Exchange 2013 servers to use Office Web App for document previews on OWA. Everything works fine internally, and externally also when we access OWA directly. But when from an outside network we open a OWA session through TMG and try to preview
    a document, we get the error "Sorry we cannot open this document, an error occured . . ."
    Did anyone experience such an issue ?
    Thanks,
    Antonio

    Hello,
    Since directing accessing OWA from CAS is fine and the issue only occur when involving TMG, I think the issue is more related to TMG settings. Please find more efficient support
    via our TMG forum:
    http://social.technet.microsoft.com/Forums/en-US/Forefrontedgegeneral/threads
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • 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

  • 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.

  • Using Office Web Apps Server 2013 without SharePoint, Lync, or Exchange

    I'm trying to use the Office Web Apps Server 2013 as an online viewer of Office documents (using the Online Viewer). I've set up a New-OfficeWebAppsFarm with editing disabled, no UNC paths, and an external URL with SSL Offloaded to my Load balancer.
    I don't want to use it with SharePoint, Lync or Exchange. Just use it to view documents online (similar to Google Docs Viewer).
    However, when I point the Office Web Apps Server to a remote file online (e.x. a DOC hosted on a website), I get an error opening it.
    I've checked the health statuses of my OWA Servers, and it says Healthy.
    When I check the Event viewer of my OWA Server, I see 501 WOPI errors:
    Could not contact WOPI End Point. Error details - 'NotImplemented url - https://sample-owa-url.com/oh/wopi/files/@/wFileId?wFileId=http%3A%2F%2Fwww%2Eimr%2Esandia%2Egov%2Fimrtemplate%2Edoc&access_token=1&access_token_ttl=0'.
    It seems OWA is trying to connect to the path /oh/wopi/files....  but the server is responding NotImplemented.
    What do I have to get this to work?
    Thanks for any help!

    Did you ever find an answer? I have the exact same Issue.
    I have 2 WAC servers behind a load balancer with SSL offloaded to the LB. Both servers report healthy with Get-OfficeWebAppsMachine
    Works fine with SharePoint 2013.
    When I use it with a remote file, served using HTTP with no authentication (anonymous), I get a generic "Sorry there was a problem and we can't open this document..." error.
    In the ULS and event viewer, I see the WOPI error and 501 which basically says:
    Could not contact WOPI End Point. Error details - 'NotImplemented url - https://sample-owa-url.com/oh/wopi/files/@/wFileId?wFileId=http%3A%2F%2Fwww%2Blah%2Ecom%2FWordDocument%2Edocx&access_token=1&access_token_ttl=0'.
    I also sometimes see this:
    <HealthMessage>WordViewerWfeWatchdog reported status for WebWordViewer in category 'WfeRedirect'. Reported status: /default.aspx returned a 404, which means that we didn't have where to redirect.</HealthMessage> 
    The very interesting part s that I have a dev server, with OWA (WAC) installed, thats not going through a LB and does not use SSL, that works just fine with the same public url word document.

  • Office Web Apps 2013 - Word app not working on Sharepoint 2013 but Excel does

    Hi there!
    We had some problems with Office Web Apps 2013 not working with Lync, and the status of OWA was unhealty so we decided to install some updates for OWA.
    We have downloaded November 2013 update for OWA.
    We found out a guide for putting updates on OWA and done this steps:
    * Remove-OfficeWebAppsMachine
    * Installed the november update
    * Restarted OWA server
    * ran: New-OfficeWebAppsFarm -InternalUrl https://owasrv.domain.local -ExternalURL
    https://owasrv.domain.local -CertificateName "certname" -AllowHttp  -EditingEnabled
    * Restart-Service WACSM
    - checked in IIS in the bindings if the site useses the correct certificate
    Then we went on Sharepoint 2013 and ran some commands:
    * Remove-SPWOPIBinding –All:$true
    * New-SPWOPIBinding -ServerName owasrv.domain.local
    * Set-SPWOPIZone –zone “external-https”
    Now here are the funny things:
    * Excel word app on Sharepoint 2013 works
    * Word APP not working (screenshot)
    * Lync 2013 powerpoint still not working (screenshot)
    * status of OWA is healthy
    bostjanc

    Hi,
    The Friendly name field must be unique within the Trusted Root Certificate Authorities store.  In -CertificateName, enter the friendly name you gave your
    certificate earlier.
    Validate the configuration by navigating to the discovery URL of the Office Web Apps server.  Like
    https://xxx/hosting/discovery
    Meanwhile, the issue is related to Lync, I recommend to you to post the question on Lync Server for further discussion via the link below.
    http://social.technet.microsoft.com/Forums/en-US/home?forum=ocsclients
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction
    with us. Thank you for your understanding.
    Tracy Cai
    TechNet Community Support

  • SharePoint 2013 cannot view PDF documents in mobile browser with office web apps

    Hi,
    I'm receiving the following error when viewing SharePoint 2013 PDF documents in a mobile browser after clicking on the filename:
    "Viewing of .pdf files has been disabled in Microsoft Word Mobile Viewer. Please get in touch with your helpdesk."
    My Question
    Is viewing PDF documents in mobile browsers with Office Web Apps SP1 actually supported?  If so, how can I enable it?  I've already have pdf viewing working in non-mobile browsers. Word documents open just fine on mobile browsers too.
    I'm getting conflicting answers for pdf mobile viewing support from various sources:
    You've got Microsoft toting that they've added in PDF viewing on any device for Office Web Apps
    http://blogs.office.com/2013/07/03/pdfs-in-the-word-web-app/
    A MS support person saying saying it is not supported
    http://blogs.technet.com/b/office_web_apps_server_2013_support_blog/archive/2013/12/31/enabling-pdf-previews-in-document-libraries-with-office-web-apps-2013-in-sharepoint-2013-open-link-does-not-work-from-preview.aspx
    Another person implying that it should work because you can disable pdf browsing for mobile browsers only
    http://blogs.technet.com/b/office_resource_kit/archive/2013/07/24/control-whether-pdfs-open-in-word-web-app-or-the-default-pdf-reader.aspx
    What I've tried
    When I started looking into this there was a mobile WOPI entry:
    Application     : WordPdf
    Extension       : PDF
    ProgId          :
    Action          : mobileView
    IsDefaultAction : False
    ServerName      : 20SP8
    WopiZone        : internal-http
    I tried experimenting with tweaking this binding by changing the DefaultAction to true, and even removing it altogether via:
    Get-SPWopiBinding -Action "MobileView" -Application "WordPDF" | Remove-SPWopiBinding -Confirm:$false
    But I still get the same message.
    I removed all the WordPdf bindings and re-added them via:
    New-SPWOPIBinding –ServerName "<myserver>" –Application "WordPDF" -AllowHTTP
    No dice.  In fact the mobileview binding doesn't even come back... but I guess that is a different issue altogether.
    Version
    SharePoint 2013 (SP1)
    Office Web Apps Server (SP1)
    Farm Setup
    Internal facing only
    2 front end servers, 1 app server, 1 office web apps server

    I think the PDF support, if it exists, in only in Office 365. Always remember that the Office 365 and on premises versions will never be in sync. On premise is updated using periodic service packs and Office 365 has continuous updates. (I've heard every
    10 days.)
    In my Office 365 / IE 10 tests, the PDFs open in the browser's default PDF viewer, in my case FoxIt Reader. So I can't prove one way or the other about support in Office Web Apps.
    Mike Smith TechTrainingNotes.blogspot.com

  • SharePoint 2013 - Office web apps intermittent issue

    From past few weeks we are seeing issue while opening the documents from sites error message says “Sorry something went wrong + An unexpected error occur on the Server”.  This happens with individual users accounts(Since it is
    expected behavior with Service account for Office web Apps). After identifying on which server we are seeing the issue we are performing the
    IIS reset on that effected Server and then issue will resolve but after a week or 10 days this is repeated again.    If anyone has seen this issue in(SP2013+OWA) please share your inputs for permanent fix.
    Subhash

    Hi Cristian,
    Below is the Log file. Please refer.
    08/06/2014 11:41:09.73 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache air4a Monitorable Token Cache: Failed to get token from distributed cache for '0).w|s-1-5-21-2146773085-903363285-719344707-1611799'.(This
    is expected during the process warm up or if data cache Initialization is getting done by some other thread). ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.73 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache air4b Monitorable Token Cache: Reverting to local cache to get the token for '0).w|s-1-5-21-2146773085-903363285-719344707-1611799'. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation Application Authentication aiv3c Exception System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Configuration.ConfigurationChannelFactory`1[Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract],
    cannot be used for communication because it is in the Faulted state.     at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposed()     at System.ServiceModel.ChannelFactory.EnsureOpened()    
    at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.GetInternalAppStsChannel()     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.<>c__DisplayClass2.<RequestSelfIssuedToken>b__0()    
    at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.RequestSelfIssuedToken(RequestApplicationSecurityToken rst)
    StackTrace:  at onetnative.dll: (sig=6aba1f5f-ccc4-4590-af00-b8ffe7fe99a0|2|onetnative.pdb, offset=28BE6) at onetnative.dll: (offset=152A9) ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation Unified Logging Service c91s Monitorable Watson bucket parameters: Microsoft SharePoint Foundation 4, ULSException14, 269cd32d "sharepoint foundation",
    0f001144 "15.0.4420.0", b2c61fc4 "system.servicemodel", 0400766f "4.0.30319.0", 51d7762b "fri jul 05 18:43:07 2013", 000000e4 "000000e4", 00000063 "00000063", 96a3e724 "communicationobjectfaultedexception",
    00215742 "aiv3c" ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation Application Authentication agmxo Exception System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Configuration.ConfigurationChannelFactory`1[Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract],
    cannot be used for communication because it is in the Faulted state.     at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposed()     at System.ServiceModel.ChannelFactory.EnsureOpened()    
    at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.GetInternalAppStsChannel()     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.<>c__DisplayClass2.<RequestSelfIssuedToken>b__0()    
    at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.RequestSelfIssuedToken(RequestApplicationSecurityToken rst)    
    at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.RequestRawLoopbackToken(OAuth2EndpointIdentity endpointIdentity, JsonWebSecurityToken onBehalfOf, String applicationContext)     at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri
    endpointAddress, SPIdentityContext identityContext, String applicationContext, DateTime& validTo) StackTrace:  at onetnative.dll: (sig=6aba1f5f-ccc4-4590-af00-b8ffe7fe99a0|2|onetnative.pdb, offset=28BE6) at onetnative.dll: (offset=152A9) ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation Unified Logging Service c91s Monitorable Watson bucket parameters: Microsoft SharePoint Foundation 4, ULSException14, 269cd32d "sharepoint foundation",
    0f001144 "15.0.4420.0", b2c61fc4 "system.servicemodel", 0400766f "4.0.30319.0", 51d7762b "fri jul 05 18:43:07 2013", 000000e4 "000000e4", 00000063 "00000063", 96a3e724 "communicationobjectfaultedexception",
    0018c5ce "agmxo" ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation WOPI ajc39 Unexpected WOPIFrame - Unhandled exception: System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Configuration.ConfigurationChannelFactory`1[Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract],
    cannot be used for communication because it is in the Faulted state.     at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposed()     at System.ServiceModel.ChannelFactory.EnsureOpened()    
    at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.GetInternalAppStsChannel()     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.<>c__DisplayClass2.<RequestSelfIssuedToken>b__0()    
    at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at Microsoft.SharePoint.IdentityServices.SPApplicationSecurityTokenServiceClient.RequestSelfIssuedToken(RequestApplicationSecurityToken rst)    
    at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.RequestRawLoopbackToken(OAuth2EndpointIdentity endpointIdentity, JsonWebSecurityToken onBehalfOf, String applicationContext)     at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri
    endpointAddress, SPIdentityContext identityContext, String applicationContext, DateTime& validTo)     at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueLoopbackTokenString(Uri endpointAddress, SPUser user,
    String applicationContext, DateTime& validTo)     at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPWeb web, Guid uniqueId, String proofKeyId, SPUrlZone zone, SPBasePermissions perms, Boolean hasEditLicense, Int64& ttl)    
    at Microsoft.SharePoint.Utilities.SPWOPIHost.GetAccessToken(SPFile file, String proofKeyId, SPUrlZone zone, Int64& ttl)     at Microsoft.SharePoint.Utilities.SPWOPIHost.GetWOPITargetInternal(HttpContext httpContext, SPWeb web, Object&
    spPrimeObject, SPWOPIAction& requestedAction, SPRegionalSettings spSettings, String& wopiAppUrl, String& wopiFavIconUrl, String& wopiAccessToken, Int64& wopiAccessTokenTtl, String& errorMessageToDisplay, String& redirectUrl)    
    at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoadHelper(WOPIFrame frame)     at Microsoft.SharePoint.ApplicationPages.WOPIFrameHelper.OnLoad(WOPIFrame frame) ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation General aat87 Monitorable An error has occurred on the server. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache ah24q Unexpected SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts are present in the farm. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache ah24w Unexpected Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedViewStateCache'
    - Exception 'System.InvalidOperationException: SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm.     at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()'. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:09.78 w3wp.exe (0x1688) 0x4764 SharePoint Foundation General ajb4s Monitorable ViewStateLog: Failed to write to the velocity cache: Documents/Srikanth_excel test.xlsx&action=default ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:19.97 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache ah24q Unexpected SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts are present in the farm. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:19.97 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache ah24w Unexpected Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedLogonTokenCache'
    - Exception 'System.InvalidOperationException: SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm.     at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()'. ccecab9c-73c6-e096-b4ac-251e2bb15206
    08/06/2014 11:41:19.97 w3wp.exe (0x1688) 0x4764 SharePoint Foundation DistributedCache air4g Monitorable Token Cache: Failed to initialize SPDistributedSecurityTokenCache  Exception: 'System.InvalidOperationException:
    SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm.     at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()     at Microsoft.SharePoint.DistributedCaching.SPDistributedCache..ctor(String
    name, TimeSpan timeToLive, SPDistributedCacheContainerType containerType, Boolean encryptData)     at Microsoft.SharePoint.IdentityModel.SPDistributedSecurityTokenCache..ctor(String name, TimeSpan timeToLive, SPDistributedCacheContainerType
    containerType, Boolean encrptyData, TimeSpan minimumTokenExpirationWindow)     at Microsoft.SharePoint.IdentityModel.SPDistributedSecurityTokenCacheInitializer.Init(Object state)'. ccecab9c-73c6-e096-b4ac-251e2bb15206

Maybe you are looking for

  • Ipad losing network connection--why?

    Ipad I has started losing connection to home network (ATT Uverse) in past few weeks after several years of no such problems. Have not recently upgraded anything. Have not noted same problem with IMac, which also is on same WiFi connection. Has happen

  • Can we edit simultaneously in Pages for iCloud and Pages for OS X?

    I know that it's possible for multiple users to edit a document in Pages for iCloud (beta). But what happens if one user is using Pages for iCloud, and another person is editing the same document in Pages for OS X? Will the changes be updated in real

  • Epson R1800 prints too dark with PS CS5

    I have been using Photoshop since version 2.5 updating each version. I have a trial version of PS CS5 12.0.1.  I have been trying to print from it but have been unable to get anything other than dark prints.  I have carefully checked everything, used

  • Problems with text in overlays

    Hi All and sorry if this is a basic question, but really rushed to meet a client's deadline. I created a simple SD menu at 16x9. My client wants the entire title of the video tracks highlighted when the pointer rolls over it or selects it. Problem is

  • Photoshop Elements Version  4 Help

    I have version 4 and up until 2 weeks ago it was working fine but now every time I try to open it  I get the message "Attempt to access invalid address". Then I click 'ok' and it says "It may still be loading or waiting for a response from you". I ha