Office Automation App Fails On Office 365 Machines

I have an application that does COM automation with Excel.  I use Microsoft.Office.Interop.Excel from C#.
The application works fine if Office 2010 is installed.  On machines with Office 365 installed, I get the following error:
System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Office.Interop.Excel.Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{000208D5-0000-0000-C000-000000000046}'
failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).
Code is trivial to reproduce:
using System;
using System.Collections.Generic;
using System.Data;
using System.Diagnostics;
using System.IO;
using System.Runtime.InteropServices;
using System.Text;
using System.Threading;
using Excel = Microsoft.Office.Interop.Excel;
namespace TestExcel
    class Program
        static void Main(string[] args)
            // Start Excel and get Application object.
            Excel.Application excelApp = new Excel.Application(); // Fails here
            // Set some properties.
            excelApp.Visible = false;
            excelApp.DisplayAlerts = false;
            excelApp.Quit();
            Marshal.ReleaseComObject(excelApp);
Any ideas how to fix this?
Matt
Matt

Hi Matt.
Which version of COM do you reference?
If you reference version 15.0 in your application, I recommend that you could try this way:
1.Delete the Excel reference (Microsoft.Office.Interop.Excel). Version 15.0.
2.Add the Excel reference (older one. Version 14.0).
Hope that helps.
If your application still causes this error, please let me know.
Thanks.
George Hua
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Similar Messages

  • Office 2010 App-V on machine with Office 2013 installed

    Hi,
    After a migration to locally installed Office 2013 I need to restore access to Access 2010 to some users for a legacy app.  Ideally I want to use App-V.  I have made an App-V package of Access 2010 following the MS guidance.  It runs correctly
    but every time after running it, the next time you run an Office 2013 app it causes Office 2013 to perform a repair operation, this succeeds but has to be done every time the 2010 Access is run.  I can't find any reasons in the log files or in the event
    viewer, any ideas?
    Thanks 

    Thanks, I couldn't really find anything but it looks as though this could be just the way it is.
    from http://support.microsoft.com/kb/2784668
    When you start a version of Access on a computer that has multiple versions of Access installed, the Windows Installer may start, and
    a message that states that the Windows Installer is preparing to install Access may be displayed before Access starts.
    Every time that you start Access 2003, Access 2007, or Access 2010 after you use Access 2013, the Windows Installer repair operation registers
    that version of Access. Similarly, the Windows Installer repair operation registers Access 2010 every time that you start it after you use an earlier version of Access. This does not occur when you start Access 2002, nor does it occur when you start the same
    version of Access again. 
    Is this likely to also apply even when running App-V?

  • SharePoint 2013 - Office Web Apps - Internal and External Use

    I have successfully installed SharePoint 2013 and Office Web Apps on Azure VMs inside an Azure Virtual Network (IaaS model). Everyting is working well. However, my testing has shown that external users and internal users can't use Office Web Apps at the
    same time.
    Office Web Apps, installed on its own vm, accomodates an external and internal URL quite well. However, SharePoint 2013 appears to only allow one setting for WOPI Zone, either internal or external but not both. I've set the WOPI zone to Internal-HTTPS (Set-SPWOPIZone
    –Zone “internal-https”). OWA works just fine if accessed from inside the Azure Virtual Network. However, if I try to access from outside the Virtual Network, from the Internet, Office Web Apps fails. The exact oppisite is also true. I can set WOPI Zone to
    External-HTTPS and accessing from the Internet works fine, but accessing inside the Virtual Network fails.
    Am I missing something? I, obviously, want Office Webs Apps to function properly for both internal and external users simultaneously.
    I appreciate any help anyone can provide here.
    Glenn

    Hi Glenn,
    To have both the use of Internet and Internal available to your end-users, you first need to configure AAM setting. Open Central Administration > Application Management > Configure alternate access mappings. Let's say there is an existing web application
    named http://sharepoint and my end-users from local network are able to access it using the URL http://sharepoint (root site collection). Here you need to add the Internet URL by select the web application and click Edit Public URLs. Add the Internet domain
    to the web application, e.g http://sharepoint.abc.com. You don't necessarily have to edit binding setting in IIS. Before continuing next steps, make sure you are able to access http://sharepoint.abc.com from the Internet while being able to access http://sharepoint
    from local network (aka Internal).
    On the machine where Office Web App (OWA) Server 2013 is installed, open PowerShell to add OWA module and use the following command to re-create a new OWA server farm if you've completed configuring it previously.
    New-OfficeWebAppsFarm -InternalUrl "http://owa" -ExternalUrl "http://owa.abc.com" -EditingEnabled.
    In this case, I'm not using SSL certificate to encrypt data over the Internet. You can use Internet-public IP of the OWA server like -ExternalUrl "http://198.xxx.xxx.xx". Add CertifcateName parameter if you want to use whether CA-issued certificate
    or self-signed certificate.
    On your SharePoint machine, you need to re-bind all WFE machines to WAC farm using the cmdlet New-SPWOPIBinding. Next, you need to set the WOPI zone for both internal and external.
    Set-SPWOPIZone -zone "external-http"
    Note: I'm not all using certificate in my guidance. But the steps to have it configured is just to add more parameter. 
    I've recently successfully deployed OWA multi-server farm for both internal and internet uses for two big clients. In real-world scenario, ideally OWA should be published through firewall (Forefront UAG, TMG, F5...etc). Please let me know if you still have
    issues after following my steps. My email: [email protected]
    Regards,
    -T.s
    Thuan Soldier
    A 23-year-old man loving Microsoft technologies and making crazy ideas on business journey.
    SharePoint Vietnam |
    Blog | Twitter

  • 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

  • Office Web Apps (OWA) deployment and licensing

    Hi,
    Im trying to get some info about how to eventually purchase and install Office Web Apps (View only) for all Sharepoint-users in the farm. 
    As from 22/10 -14 OWA is no longer available for download from Microsoft Download Center.
    Source: Technet
    They're redirecting users to the Volume Licensing Service Center, but the link is dead.
    What i found searching is this page with lack of info: http://www.microsoftvolumelicensing.com/ProductPage.aspx?pid=387
    I feel stupid, but this page says nothing to me.
    Is there any obvious way to calculate the cost of OWA?
    Does OWA even cost if the organization is just going to View but not edit?
    From where should i get the installationpackage now when Microsoft Download Center got rid of it?
    Kr,
    Rasmus

    Hi,
    Office suite licenses(Standard or Pro Plus) are only required for those employees editing Office Web Apps documents.
    The Office Web Apps are included when you purchase Office Professional Plus 2013 or Office Standard 2013 licenses and allow you to
    view and edit Office files using the Office Web Apps Server.
    Office client suites are licensed per device. The primary user of a device licensed for this Office software is licensed for access to the online companion Office Web Apps from any device. In these situations, the primary user is enabled for remote online
    access through Office Web Apps.
    thanks
    diramoh

  • Office 365 instead of Office Web Apps server?

    We don't have an Office Web Apps server deployed. We'd really like to share Powerpoints in Lync with the full user experience, but we don't want to install a standalone server just for Office Web Apps since we wouldn't use it for anything else.  We
    use Office 365, is there a way to use an FQDN from Office 365 and point to that in topology builder as our Office Web Apps server?  We area always loading PowerPoint from the cloud anyways.  Is there any way to get around installing a stand alone
    OWAS server?
    Thanks,
    Brandon

    No as of today I believe that with Lync server 2013 on premise you do need office web app server on premise 
    Please remember, if you see a post that helped you please click ;Vote As Helpful" and if it answered your question please click "Mark As Answer" Regards Edwin Anthony Joseph

  • Microsoft Office Apps fail to work after 10.6.7 update

    Has anyone else's office apps failed to open after installing the OS update?
    This is a brand new iMac only 5 days old using office 2011 with current updates.
    Regards.
    Mike.

    After doing some Internet research and speaking with a second-level Apple tech, together we came up with the following solution.
    Shut down, then start in safe-mode (hold shift key while re-starting). This will clear the font cache and re-build it. After doing this, when I started Word 2004 it took some time, but it showed the following fonts as corrupt: APC Courier, Bastion, Chicago TU, Courier TU, Latinski - and indicated they should be removed. Word then started up even though I just clicked OK to those messages and didn't remove them. I then re-started Word and it came up normally even though those fonts are still in the font book. By the way, I have downloaded the freeware app "Fontnuke-1.17," but haven't used it yet. There is a shareware app, "Fontfinagler," which may also be useful if safe mode doesn't work for you.
    Branton
    California
    iMac 27 i7 with 250 GB SSD and 2 TB HD, 8 Gb RAM, 10.6.7, running Office 2004 for Mac

  • Installation of this package failed (Service Pack 2 for Microsoft Office Web Apps (KB2687470) 64-bit edition

    Hi there,
    On my SharePoint 2010 server I have Office Web Apps 2010 installed (NOT Microsoft Office).
    When I try to install OWA SP2 (KB2687470) I get this error:
    --- Logs show some errors at C:\Users\ext.magryan\AppData\Local\Temp\3\Wac Server Setup(2014062009365223A0).log
    Search "error" (32 hits in 1 files)
    C:\Users\ext.magryan\AppData\Local\Temp\3\Wac Server Setup(2014062009365223A0).log (32 hits)
    Line 352: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6025.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6025.1000, found product version 14.0.4763.1000.'
    Line 354: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6012.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6012.1000, found product version 14.0.4763.1000.'
    Line 356: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6014.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6014.1000, found product version 14.0.4763.1000.'
    Line 358: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6027.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6027.1000, found product version 14.0.4763.1000.'
    Line 360: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6022.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6022.1000, found product version 14.0.4763.1000.'
    Line 362: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6015.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6015.1000, found product version 14.0.4763.1000.'
    Line 403: MSI(ACTIONSTART): 'Action 9:36:56: SetSupportErrorTextRetail. '
    Line 404: MSI(INFO): 'Action start 9:36:56: SetSupportErrorTextRetail.'
    Line 405: MSI(INFO): 'Action ended 9:36:56: SetSupportErrorTextRetail. Return value 1.'
    Line 406: MSI(ACTIONSTART): 'Action 9:36:56: SetSupportErrorTextRetail_PERMISSION. '
    Line 407: MSI(INFO): 'Action start 9:36:56: SetSupportErrorTextRetail_PERMISSION.'
    Line 408: MSI(INFO): 'Action ended 9:36:56: SetSupportErrorTextRetail_PERMISSION. Return value 1.'
    Line 409: MSI(ACTIONSTART): 'Action 9:36:56: SetSupportErrorTextRetail_PROBLEM. '
    Line 410: MSI(INFO): 'Action start 9:36:56: SetSupportErrorTextRetail_PROBLEM.'
    Line 411: MSI(INFO): 'Action ended 9:36:56: SetSupportErrorTextRetail_PROBLEM. Return value 1.'
    Line 558: MSI(ERROR): 'Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:\Users\EXT~1.MAG\AppData\Local\Temp\3\Setup000023a0\SETUP.CHM.'
    Line 558: MSI(ERROR): 'Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:\Users\EXT~1.MAG\AppData\Local\Temp\3\Setup000023a0\SETUP.CHM.'
    Line 575: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_PROBLEM = If problem persists, contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, see C:\Users\EXT~1.MAG\AppData\Local\Temp\3\Setup000023a0\PSS10R.CHM.'
    Line 576: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_PERMISSION = Verify that you have sufficient permissions to access the registry or contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, see C:\Users\EXT~1.MAG\AppData\Local\Temp\3\Setup000023a0\PSS10R.CHM.'
    Line 577: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT = Contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, see C:\Users\EXT~1.MAG\AppData\Local\Temp\3\Setup000023a0\PSS10R.CHM.'
    Line 619: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PROBLEM_PRE = If problem persists, contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, see '
    Line 620: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PROBLEM_POST = .'
    Line 621: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PERMISSION_PRE = Verify that you have sufficient permissions to access the registry or contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, see '
    Line 622: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PERMISSION_POST = .'
    Line 623: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_PRE = Contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, see '
    Line 624: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_RETAIL_DEFAULT_POST = .'
    Line 625: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_OEM_DEFAULT = Contact your computer manufacturer's product support for assistance.'
    Line 626: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_OEM_DEFAULT_PERMISSION = Verify that you have sufficient permissions to access the registry or contact your computer manufacturer's product support for assistance.'
    Line 627: MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_OEM_DEFAULT_PROBLEM = If problem persists, contact your computer manufacturer's product support for assistance.'
    Line 629: MSI(INFO): 'Property(S): SecureCustomProperties = DIAGNOSE;DWLANGUAGE;ERRORSUPPORTTEXT;LAUNCHEDBYSETUPEXE;LOGVERBOSE;PIDKEY;SETUPHELPFILEDIR;SETUPINTLDLLDIRECTORY;SETUPPSSHELPFILEDIR;SETUPSUPPORTURL'
    Line 753: Error: Failed to configure: {90140000-1141-0409-1000-0000000FF1CE} ErrorCode: 1603(0x643).
    Line 753: Error: Failed to configure: {90140000-1141-0409-1000-0000000FF1CE} ErrorCode: 1603(0x643).
    Any help will be appreciated.
    Thanks.

    Did you install SharePoint 2010 SP1 (or preferably, SP2)?
    Foundation SP2:
    http://www.microsoft.com/en-us/download/details.aspx?id=39646
    Server SP2:
    http://www.microsoft.com/en-us/download/details.aspx?id=39672
    If you have SharePoint Foundation, use the Foundation SP2 link. If you have SharePoint Server, use the Server SP2 link. Install that first, then proceed with your OWA SP2 install.
    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.

  • Installing Office Web Apps Server 2013 fails with app-crash during install.

    Hi Folks,
    I am trying to install Office Web Apps Server 2013 with SP1 on Server 2012 R2.  The installation gets half way through then crashes (it just says a problem has occurred).
    The Event log only contains the message:-
     MsiExec.exe version .5.09....
    Faulting module name: Kernelbase.dll
    Exception Code 0x306d7363, Faulting process id: 0x774.
    Does anyone know how to install this product on Server 2012 R2?

    Hi,
    I’m afraid that this case is off-topic in this forum, About installation of Office Web Apps Server 2013, I suggest you posting your case to
    SharePoint 2013 - Setup, Upgrade, Administration and Operations .
    Regards,
    Marvin
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Office Web Apps Server - Access is denied

    Hello,
    I was able to create an Office Web Apps server and was able to create a new farm for that server all without any issues, everything works great.
    Unfortunately right after creating the farm, when attempting to run any other related powershell commands such as:
    Get-OfficeWebAppsFarm
    Remove-OfficeWebAppsFarm
    I get this error in powershell:
    Get-OfficeWebAppsFarm : Access is denied.
    At line:1 char:1
    + Get-OfficeWebAppsFarm
    + ~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Get-OfficeWebAppsFarm], SecurityAccessDeniedException
        + FullyQualifiedErrorId : System.ServiceModel.Security.SecurityAccessDeniedException,Microsoft.Office.Web.Apps.Adm
       inistration.GetFarmCommand
    Although everything is actually working on the server, I'd like to be able to use those other commands in the future so I can check configurations, use "Remove" for running updates, etc... Unfortunately it appears as though this Access is
    denied error may interfere with those activities.
    Has anyone seen this before?
    Thank you

    Hi,
    According to your post, my understanding is that you failed to run any other related powershell commands after creating the farm for Office Web Apps server.
    If the account trying to get  OfficeWebAppsFarm does not have local admin access on the machine you will simply get an “Access is denied”.
    Please make sure you have the permission to run the commands.
    More information:
    http://www.wictorwilen.se/office-web-apps-2013-securing-your-wac-farm
    Thanks,
    Linda Li                
    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]
    Linda Li
    TechNet Community Support

  • Office web apps server (2013) certificate issue

    If the name of the farm is different from the name of the individual office web apps server machine is there any way to deploy office web apps server with a single domain SSL certificate? 
    My office web apps server is working, but reporting itself unhealthy, apparently due to the fact that the SSL cert is for the name of the farm and that is different from the name of the machine. 
    Errors are 2004, 1004, 2156, 1156, "could not establish trust relationship for the SSL/TLS secure channel"
    Going to the farm's discovery URL in the browser works fine, but going to the machine name (plus /hosting/discovery) gives an SSL error because the name of the farm is not the same as the name of the machine. 
    Is there any way to make it use the farm's URL instead of the machine's URL in its own internal watchdog operations? Or any way to make it use a self signed certificate on the machine's URL for it's own health checks and still use the legitimate purchased
    SSL cert for user access? Or any other way you can think of to use a $5.99/yr single domain certificate instead of a $89.99/yr multiple domain certificate? 
    Bill Coulter

    I am experiencing this same issue.  The OWA server has sp1 installed.  In the OWA event logs I am getting health fails for 2 events and as best I can tell it seems to be related to this issue.
    We are also using a single godaddy certificate with a non machine name FQDN.  Both internal and external url's of the OWA farm are set to this same name.
    The problem only seems to occur with the 'Proofing Watchdog' (See events below).
    Has anyone got any update on whether this is supposed to be fixed ?
    <?xml version="1.0" encoding="utf-16"?>
    <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <HealthMessage>ProofingWatchdog reported status for Proofing in category 'PositiveWeb'. Reported status: Spelling attempt exception for "good": System.Net.WebException: The underlying connection was closed: Could not establish
    trust relationship for the SSL/TLS secure channel. ---&gt; System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
    <?xml version="1.0" encoding="utf-16"?>
    <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <HealthMessage>ProofingWatchdog reported status for Proofing in category 'NegativeWeb'. Reported status: Spelling attempt exception for "baad": System.Net.WebException: The underlying connection was closed: Could not establish
    trust relationship for the SSL/TLS secure channel. ---&gt; System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
       at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception 

  • 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 - "Could not find trace string in ULS logs" unhealthy?

    I have reviewed everything I could find on unhealthy WAC clusters as my problem seems unrelated to certificate or missing components.  I've already digested
    http://www.wictorwilen.se/office-web-apps-server-2013---machines-are-always-reported-as-unhealthy (Thanks Wictor).
    The particular configuration is an Office Web Apps 2013 ([X-OfficeVersion, 15.0.4551.1005]), running on top of Windows Server 2012, configured for http access (SSL offloaded NLB cluster) and finally linked to Exchange 2013, Lync 2013 and SharePoint
    2013.  Everything works as expected from client side after setting IIS ARR to handle all reverse proxy bits.
    FarmOU                            :
    InternalURL                       : https://officeapps.fqdn/
    ExternalURL                       : https://officeapps.fqdn/
    AllowHTTP                         : True
    SSLOffloaded                      : True
    CertificateName                   :
    EditingEnabled                    : True
    LogLocation                       : C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS
    LogRetentionInDays                : 7
    LogVerbosity                      : Unexpected
    Proxy                             :
    CacheLocation                     : C:\ProgramData\Microsoft\OfficeWebApps\Working\d
    MaxMemoryCacheSizeInMB            : 75
    DocumentInfoCacheSize             : 5000
    CacheSizeInGB                     : 15
    ClipartEnabled                    : False
    TranslationEnabled                : False
    MaxTranslationCharacterCount      : 125000
    TranslationServiceAppId           :
    TranslationServiceAddress         :
    RenderingLocalCacheLocation       : C:\ProgramData\Microsoft\OfficeWebApps\Working\waccache
    RecycleActiveProcessCount         : 5
    AllowCEIP                         : False
    ExcelRequestDurationMax           : 300
    ExcelSessionTimeout               : 450
    ExcelWorkbookSizeMax              : 50
    ExcelPrivateBytesMax              : -1
    ExcelConnectionLifetime           : 1800
    ExcelExternalDataCacheLifetime    : 300
    ExcelAllowExternalData            : True
    ExcelWarnOnDataRefresh            : True
    OpenFromUrlEnabled                : False
    OpenFromUncEnabled                : True
    OpenFromUrlThrottlingEnabled      : True
    PicturePasteDisabled              : True
    RemovePersonalInformationFromLogs : False
    AllowHttpSecureStoreConnections   : False
    Machines                          : {WAC15PD-02, WAC15PD-01}
    The problem however is an incessant logging on the WAC cluster nodes of event 1204,2204 followed almost immediately by 1004,2004.  This repeats every 4min or so...
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider
    Name="Office Web Apps Monitoring" />
      <EventID
    Qualifiers="0">1204</EventID>
      <Level>2</Level>
      <Task>1</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-02-04T20:49:37.000000000Z" />
      <EventRecordID>3043246</EventRecordID>
      <Channel>Microsoft Office Web Apps</Channel>
      <Computer>wac15pd-01.fqdn</Computer>
      <Security
    />
      </System>
    - <EventData>
      <Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported status: Could not find trace string in ULS logs in C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage>
    <ComponentOwner>ServicesInfrastructure</ComponentOwner>
    </HealthReport></Data>
      </EventData>
     </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider
    Name="Office Web Apps Monitoring" />
      <EventID
    Qualifiers="0">2204</EventID>
      <Level>2</Level>
      <Task>1</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-02-04T20:49:37.000000000Z" />
      <EventRecordID>3043247</EventRecordID>
      <Channel>Microsoft Office Web Apps</Channel>
      <Computer>wac15pd-01.fqdn</Computer>
      <Security
    />
      </System>
    - <EventData>
      <Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported status: Could not find trace string in ULS logs in
    C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage> <ComponentOwner>ServicesInfrastructure</ComponentOwner>
    </HealthReport></Data>
      </EventData>
      </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider
    Name="Office Web Apps Monitoring" />
      <EventID
    Qualifiers="0">1004</EventID>
      <Level>2</Level>
      <Task>10002</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-02-04T20:49:39.000000000Z" />
      <EventRecordID>3043266</EventRecordID>
      <Channel>Microsoft Office Web Apps</Channel>
      <Computer>wac15pd-01.fqdn</Computer>
      <Security
    />
      </System>
    - <EventData>
      <Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>AgentManagerWatchdog reported status for
    AgentManagerWatchdog in category 'Recent Watchdog Reports'. Reported status: Machine health is Unhealthy</HealthMessage> </HealthReport></Data>
      </EventData>
     </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider
    Name="Office Web Apps Monitoring" />
      <EventID
    Qualifiers="0">2004</EventID>
      <Level>2</Level>
      <Task>10002</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-02-04T20:49:39.000000000Z" />
      <EventRecordID>3043267</EventRecordID>
      <Channel>Microsoft Office Web Apps</Channel>
      <Computer>wac15pd-01.fqdn</Computer>
      <Security
    />
      </System>
    - <EventData>
      <Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>AgentManagerWatchdog reported status for
    AgentManagerWatchdog in category 'Recent Watchdog Reports'. Reported status: Machine health is Unhealthy</HealthMessage> </HealthReport></Data>
      </EventData>
      </Event>
    Further exploration of ULS log files (C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS) did not yield particularly much, except the following;
    02/04/2014 20:48:04.48  UlsControllerWatchdog.exe (0x1244)       0x0F60 Services Infrastructure        Uls Controller Watchdog        ajbam Assert 
     We're about to trace a string for category MsoSpUlsControllerWatchdog at level Info and we expect to find in the log later, but it appears that the category has been throttled. We will never be able to find the string and this watchdog will always fail.
    StackTrace:   at Microsoft.Office.Web.UlsControllerWatchdog.Program.CheckServiceInstance(ServiceInstance serviceInstance)     at Microsoft.Office.Web.Common.WatchdogHelperThreadManager.GetHealthResults(WatchdogExecutionContext
    context, ServiceInstance si)     at Microsoft.Office.Web.Common.WatchdogHelperThreadManager.WatchingThreadMethod(Object o)     at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback
    callback, Object state, Boolean preserveSyncCtx)     at System.Threading.ExecutionContext.Ru... 345fbec5-e958-4f1f-bf56-d65c1c0d472a
    02/04/2014 20:48:04.48* UlsControllerWatchdog.exe (0x1244)       0x0F60 Services Infrastructure        Uls Controller Watchdog        ajbam Assert 
     ...n(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)     at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()    
    at System.Threading.ThreadPoolWorkQueue.Dispatch()   345fbec5-e958-4f1f-bf56-d65c1c0d472a
    02/04/2014 20:48:05.52  UlsControllerWatchdog.exe (0x1244)       0x0F60 Services Infrastructure        Services Infrastructure Health adhog Unexpected Health report
    by UlsControllerWatchdog: Agent: UlsController, eventId: 1204, eventType: Error, categoryId: 1, eventMessage: <?xml version="1.0" encoding="utf-16"?>  <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">    <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported
    status: Could not find trace string in ULS logs in C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage>    <ComponentOwner>ServicesInfrastructure</ComponentOwner>  </HealthReport> 345fbec5-e958-4f1f-bf56-d65c1c0d472a
    02/04/2014 20:48:05.52  UlsControllerWatchdog.exe (0x1244)       0x0F60 Services Infrastructure        Services Infrastructure Health adhoh Unexpected Health report
    by UlsControllerWatchdog (persistent): Agent: UlsController, eventId: 2204, eventType: Error, categoryId: 1 345fbec5-e958-4f1f-bf56-d65c1c0d472a
    I suspect these might be related, but can't seem to find any logical explanation why this should cause the Get-OfficeWebAppsMachine to report HealthStatus of Unhealthy.  If related, is there a way to disable this check or remove throttling in a safe
    way?  Alternatively if this is some coding issue (I've not found any other blog/QA dealing with this particularly) it would be nice to get confirmation of this and potentially a fix/solution.
    Any help would be greatly appreciated. Thank you!

    Hi ChristiaanB,
    You get this ULS error because you change the log verbosity of the OWA farm. I wrote an article for this on my blog : OWA unhealthy uls issue
    Regards,
    Wes

  • PowerPoint presentations not working with Office Web Apps

         Hi,
         I have deployed Lync 2013 and Office Web Apps Server in order to share PowerPoint presentations. All te sharings are working fine (Desktop, Program, Whiteboard, Poll) but PowerPoint presentations.
         I have re-installed Office Web Apps Server several times but it doesn't work:
         Discovery URL is OK
         Event IDs in Lync Server Event Viewer are OK
         I have checked certificate and created it twice and that's not the problem (when tried to use a wrong certificate, the behaviour was different).
         Tried aspnet_regiis but didn't worked.
         Both Lync Server and Office Web Apps Server are updated.
         Servers are Windows Server 2008 R2 SP1.
         I have tested both Lync 2013 and Lync 2013 Basic clients but no one works.
         When I share a PowerPoint, I can see it follows the whole way through LyncShare, Lync Server and Office Web Apps Server. PowerPoint files get to Office Web Apps Server (different name but I can move then to other workstation and check
    they are the files shared).
         Clients begin showing a "Loading..." but end showing "Network connectivity lost or server too busy" (after 90 seconds more or less).
         If I get URL from Lync-UccApi-0:
         https://wacserver.domain/m/Presenter.aspx?a=0&amp;e=true&amp;WopiSrc=https%3A%2F%2Flyncpool.domain%2FDataCollabWeb%2Fwopi%2Ffiles%2F11-1-90C848&amp;access_token=AAMFEECCjUt7489YhSlhQY4GBWcGEIsJ8vG8JQH9w0g_TTTVe3aBEECCjUt7489YhSlhQY4GBWeCApwQgyBHjXVmSaUT70sAAlMNX4oAfTt5Nqgy5sJwqlLneNAxGYYIsFS5edC90AgIDURhdGFDb2xsYWJXZWI&amp;&lt;fs=FULLSCREEN&amp;&gt;&lt;rec=RECORDING&amp;&gt;&lt;thm=THEME_ID&amp;&gt;&lt;ui=UI_LLCC&amp;&gt;&lt;rs=DC_LLCC&amp;&gt;
         If I put this URL in the browser, it turns black and shows "Loading..." and, after a long while, "PowerPoint Web App...", but it remains in this state (loading) without working.
         In the Office Web Apps Server Event Viewer there are some errors related to other services I'm not using, as OneNote, or for Monitoring with the "PositiveDirect" and "NegativeDirect" tokens. Machine also answers it's
    Unhealthy, but as I have read, this is not a problem.
         In the ULS Logs I just see errors related to these events but logs for PowerPoint work fine. And IIS is answering with "200" (although there are a number of petitions that seem to be repeated:
    2013-12-02 16:23:15 WACSERVER_IP GET /m/getdata.ashx s=a%3D0%26WopiSrc%3Dhttps%253a%252f%252flyncpool.domain%252fDataCollabWeb%252fwopi%252ffiles%252f11-1-90C848%26access_token%3DAAMFEECCjUt7489YhSlhQY4GBWcGEBpfUkNifoaqnZCEMbqB4haBEECCjUt7489YhSlhQY4GBWeCApwQgyCHF8jSo70Xws4SrDZyRP3zgH8FZLobf75sHXgxfCmyK4YIxsoPfNC90AgIDURhdGFDb2xsYWJXZWI%26rec%3Dfalse%26thm%3D1%26ui%3Des-ES%26rs%3Des-ES%26%3D&n=-1&r=1386001395077
    443 - Client_IP Mozilla/4.0+(compatible;... 200 0 0 218
    2013-12-02 16:23:15 WACSERVER_IP GET /m/getdata.ashx s=a%3D0%26WopiSrc%3Dhttps%253a%252f%252flyncpool.domain%252fDataCollabWeb%252fwopi%252ffiles%252f11-1-90C848%26access_token%3DAAMFEECCjUt7489YhSlhQY4GBWcGEBpfUkNifoaqnZCEMbqB4haBEECCjUt7489YhSlhQY4GBWeCApwQgyCHF8jSo70Xws4SrDZyRP3zgH8FZLobf75sHXgxfCmyK4YIxsoPfNC90AgIDURhdGFDb2xsYWJXZWI%26rec%3Dfalse%26thm%3D1%26ui%3Des-ES%26rs%3Des-ES%26%3D&n=-1&r=1386001396078
    443 - Client_IP Mozilla/4.0+(compatible;... 200 0 0 203
    2013-12-02 16:23:17 WACSERVER_IP GET /m/getdata.ashx s=a%3D0%26WopiSrc%3Dhttps%253a%252f%252flyncpool.domain%252fDataCollabWeb%252fwopi%252ffiles%252f11-1-90C848%26access_token%3DAAMFEECCjUt7489YhSlhQY4GBWcGEBpfUkNifoaqnZCEMbqB4haBEECCjUt7489YhSlhQY4GBWeCApwQgyCHF8jSo70Xws4SrDZyRP3zgH8FZLobf75sHXgxfCmyK4YIxsoPfNC90AgIDURhdGFDb2xsYWJXZWI%26rec%3Dfalse%26thm%3D1%26ui%3Des-ES%26rs%3Des-ES%26%3D&n=-1&r=1386001397093
    443 - Client_IP Mozilla/4.0+(compatible;... 200 0 0 203
    2013-12-02 16:23:18 WACSERVER_IP GET /m/getdata.ashx s=a%3D0%26WopiSrc%3Dhttps%253a%252f%252flyncpool.domain%252fDataCollabWeb%252fwopi%252ffiles%252f11-1-90C848%26access_token%3DAAMFEECCjUt7489YhSlhQY4GBWcGEBpfUkNifoaqnZCEMbqB4haBEECCjUt7489YhSlhQY4GBWeCApwQgyCHF8jSo70Xws4SrDZyRP3zgH8FZLobf75sHXgxfCmyK4YIxsoPfNC90AgIDURhdGFDb2xsYWJXZWI%26rec%3Dfalse%26thm%3D1%26ui%3Des-ES%26rs%3Des-ES%26%3D&n=-1&r=1386001398093
    443 - Client_IP Mozilla/4.0+(compatible;... 200 0 0 218
    2013-12-02 16:23:19 WACSERVER_IP GET /m/getdata.ashx s=a%3D0%26WopiSrc%3Dhttps%253a%252f%252flyncpool.domain%252fDataCollabWeb%252fwopi%252ffiles%252f11-1-90C848%26access_token%3DAAMFEECCjUt7489YhSlhQY4GBWcGEBpfUkNifoaqnZCEMbqB4haBEECCjUt7489YhSlhQY4GBWeCApwQgyCHF8jSo70Xws4SrDZyRP3zgH8FZLobf75sHXgxfCmyK4YIxsoPfNC90AgIDURhdGFDb2xsYWJXZWI%26rec%3Dfalse%26thm%3D1%26ui%3Des-ES%26rs%3Des-ES%26%3D&n=-1&r=1386001399078
    443 - Client_IP Mozilla/4.0+(compatible;... 200 0 0 328
    2013-12-02 16:23:20 WACSERVER_IP GET /m/getdata.ashx s=a%3D0%26WopiSrc%3Dhttps%253a%252f%252flyncpool.domain%252fDataCollabWeb%252fwopi%252ffiles%252f11-1-90C848%26access_token%3DAAMFEECCjUt7489YhSlhQY4GBWcGEBpfUkNifoaqnZCEMbqB4haBEECCjUt7489YhSlhQY4GBWeCApwQgyCHF8jSo70Xws4SrDZyRP3zgH8FZLobf75sHXgxfCmyK4YIxsoPfNC90AgIDURhdGFDb2xsYWJXZWI%26rec%3Dfalse%26thm%3D1%26ui%3Des-ES%26rs%3Des-ES%26%3D&n=-1&r=1386001400076
    443 - Client_IP Mozilla/4.0+(compatible;... 200 0 0 234
    2013-12-02 16:23:20 WACSERVER_IP GET /m/getdata.ashx s=a%3D0%26WopiSrc%3Dhttps%253a%252f%252flyncpool.domain%252fDataCollabWeb%252fwopi%252ffiles%252f11-1-90C848%26access_token%3DAAMFEECCjUt7489YhSlhQY4GBWcGEBpfUkNifoaqnZCEMbqB4haBEECCjUt7489YhSlhQY4GBWeCApwQgyCHF8jSo70Xws4SrDZyRP3zgH8FZLobf75sHXgxfCmyK4YIxsoPfNC90AgIDURhdGFDb2xsYWJXZWI%26rec%3Dfalse%26thm%3D1%26ui%3Des-ES%26rs%3Des-ES%26%3D&n=-1&r=1386001401076
    443 - Client_IP Mozilla/4.0+(compatible;... 200 0 0 203
         It seems that something is not working between the clients and Office Web Apps Server. There is not a firewall and machines see each other. Certificate is accepted.
         I have tried so many thing but none of them worked.
         Does anybody have an idea?
         Thanks!

         Hi Thamara,
         There is a HLB but I thought of that and tested both: with HLB and pointing just a Front End, without HLB. In both cases, results were the same.
         I can access the Front End pool web services from the WAC server using the IE.
         I'm watching now this event:
    <?xml version="1.0" encoding="utf-16"?>
    <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <HealthMessage>BroadcastServicesWatchdog_Wfe reported status for BroadcastServices_Host in category '3'. Reported status: Contacting Participant.svc failed with an exception: The remote server returned an error: (404) Not Found.</HealthMessage>
    </HealthReport>
         Reading some posts, it's a known issue fixable by adding HTTP-Activation feature... in Windows 2012. I have a Windows 2008 and .NET Framework 4.5 is installed. I've tried to add HTTP-Activation feature from .NET Framework 3.5, but a number
    of format errors appear. I don't know how I could fix it in Windows 2008.
         In addition, as I'm making test for share PPT and they aren't finally showed, this error appears also:
    <?xml version="1.0" encoding="utf-16"?>
    <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <HealthMessage>PowerPointViewingServicesWatchdog_App reported status for PPTConversionService in category '0'. Reported status: AppManager: A request appears to be stuck in the queue. [State: ReadyToWork] [Start Time: 12/03/2013 10:35:07] [CorrelationId:
    ec4db345-0e8c-477e-ac0e-71afcb9a8efd] [DocId: https%3A%2F%2FLYNCPOOL.DOMAIN%2FDataCollabWeb%2Fwopi%2Ffiles%2F1-1-2BCF63F] [ClusterId: 0] [RequestId: 51e9263e-fc78-46b0-93ca-de48272dd2bc] [Current InProgress Queue Length: 4]</HealthMessage>
    </HealthReport>
         It seems that PPTs are being queued as they aren't actually showed.
         Does this give you any clue?
         Thank you very much.
         Kind regards.

  • Office 2013 updates fail on computers with Access 2013 installed

    I have about 10 workstations with the combination of Windows 7 enterprise 32 bit, Access 2013 and Office 2007 installed.
    SCCM offers up both Office 2007 and Office 2013 updates to these machines, but the Office 2013 updates, fail to install.
    The same thing happens when I go to Microsoft updates and manually install the required Office 2013 updates.
    I read that one of the updates required Office 2013 sp1.
    But when I downloaded it, it won't install:  KB2817430 "The expected version of this product was not found on the system."
    This is the second month I've had the failures. I removed KB2878316 and KB2889927 from my deployments and packages to stop repeated install attempts.
    But this month I've got a new on failing, KB2899493.
    Is there a way around this problem?

    Thanks, I couldn't really find anything but it looks as though this could be just the way it is.
    from http://support.microsoft.com/kb/2784668
    When you start a version of Access on a computer that has multiple versions of Access installed, the Windows Installer may start, and
    a message that states that the Windows Installer is preparing to install Access may be displayed before Access starts.
    Every time that you start Access 2003, Access 2007, or Access 2010 after you use Access 2013, the Windows Installer repair operation registers
    that version of Access. Similarly, the Windows Installer repair operation registers Access 2010 every time that you start it after you use an earlier version of Access. This does not occur when you start Access 2002, nor does it occur when you start the same
    version of Access again. 
    Is this likely to also apply even when running App-V?

Maybe you are looking for