Skip to content

Installing Office Web Apps in a Standalone SharePoint 2010 environment

November 27, 2009

I recently set up a new VM (on a Hyper-V host) with Windows Server 2008 R2 for the purpose of evaluating SharePoint Server 2010 beta. This is a single server, standalone environment – domain controller, SQL server 2008 and SharePoint Server 2010 all on one VM.

Here are the resources I read through (I obviously didn’t read one of them well enough, you’ll understand later) to get set for installing SP Server 2010 beta and Office Web Apps beta in this standalone environment. These references contain download links and product keys too should you need them. (Deploying Office Web Apps)

After installing all prerequisites for SharePoint 2010 (including SQL 2008 SP1, CU2 and CU3) I set out to install SharePoint 2010. Now, if you read through the TechNet resource on deploying Office Web Apps, you’ll see that there is a wee bit of Powershelly stuff you’ll need to do to activate and start the Office Web App services and to create the service apps and proxies. This needs to be done only if you run the SharePoint post-setup configuration wizard as part of your SharePoint 2010 installation. I was keen to avoid this, hence here are the steps I followed to get everything up and running:

  1. Ran prerequisite installer from SharePoint 2010 setup to ensure I hadn’t missed any prereqs
  2. Ran SharePoint Server 2010 OfficeServer.exe setup (using complete installation option to be able to use full blown SQL 2008)
  3. REMOVED TICK from “Run the SharePoint Products and Technologies Configuration Wizard now” box. (Do not run the config wizard at this time unless you want to manually active Office Web Apps using Powershell)
  4. Ran Office Web Apps WcServer.exe setup
  5. Once the setup is finished, the “Run the SharePoint Products and Technologies Configuration Wizard now” box should be ticked. Click close to start the wizard and run through
  6. Ran Farm configuration wizard from Central Administration

All done! Well, kind of. I happily went and created my first site collection, uploaded a Word document and tried to open it up to test Office Web Apps. Word Web App launched and appeared to be OK, but after several minutes of SharePoint “processing” my document I got an error that read: “Word Web App cannot open this document because the server is still processing the document. Please try again later.”

OK. So tried an Excel document – that opened fine. Unsurprisingly really because Excel has it’s own web services which have been around since MOSS 2007. Then tried a Powerpoint document and I got a different error, something along the lines of “network connection interrupted” which didn’t make any sense. At first I thought it might have been a resourcing issue, so I turned off a couple of VMs and allocated some more RAM to this one, same problem though.

So after SEVERAL hours of looking through event logs, Googling, looking in every dark corner of Central Administration, testing and retesting, I decided to re-read through the deployment instructions. In Jie Li’s article (3rd link in the above list), under step 11 we have the following note:

If you are trying to use Office Web Applications on DC (Office Web Application need to be installed seperately, like a language pack or an update. Please also note that Office Web Application cannot be installed on Windows 7), then the following commands need to be run to make the services work. Please note that in different languages, Service Application names could be localized. You can find them out by Get-SPServiceApplication, and then change the names in the script as necessary.

$e = Get-SPServiceApplication | where {$_.TypeName.Equals("Word Viewing Service Application")}
$e.WordServerIsSandboxed = $false

#(Please use the below script for PowerPointServiceApplication - You need to enter "Y" for the answer of each cmd)
Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedViewing $false
Get-SPPowerPointServiceApplication | Set-SPPowerPointServiceApplication -EnableSandboxedEditing $false

In the server’s c:\windows\system32\inetsrv\config\applicationHost.config
Add the line below in the end of the dynamicTypes.
<add mimeType=”application/zip” enabled=”false” />


I had initially not seen this as I was using the TechNet article as my reference for installing Office Web Apps. So, because my server is also a domain controller I ran the Powershell commands and just like magic, Office Web Apps worked. Albeit a little slowly at first (possibly because I only have 3 GB RAM allocated to this server – don’t laugh) but after installing Silverlight it is nice and quick.

Issue resolved, I can now continue to play with SP2010.

30 Comments leave one →
  1. November 28, 2009 2:03 am


    Great post! I have added it to SharePoint Buzz’s SharePoint 2010 Beta Installation Roundup!

  2. November 28, 2009 11:58 am

    Awesome, thanks for doing that! And thanks for the feedback 🙂

  3. December 3, 2009 1:38 pm

    Hi Kylie, thanks for commenting on my thread on MSDN. Turned out that my problem was that I was running the site on port 888 instead of port 80. I think that if you create a site on a different numbered port you will see the error.

  4. December 3, 2009 2:44 pm

    Hi Tim, good to hear that you got it working. Strange that two very different problems surfaced identical errors though huh.

  5. December 6, 2009 1:57 am

    Another interesting insight. If the Jie Li changes are applied after the creation of a site, the errors will persist, even if the site is on port 80. I found that to get the Office Web App viewers to work, I had to re-create the site. It does not sound like you had this issue though.

  6. AOM permalink
    December 23, 2009 7:42 am

    After some research, i found that there is no other case like mine.
    I had installed the Sharepoint 2010 and started worked on it, and then after a week i tried to install the Office Web Apps, but i only can get the Excel functional.
    When i open a document it appears the error: Word Web App encountered an unexpected error.
    A powerpoint it appears: PowerPoint Web App encountered an error. Please try again.

    How can i get this thing working. My VM has the Sharepoint, Sql Server 2008, Windows Server R2.

    Any Help?


    • December 27, 2009 12:16 pm

      @AOM – Have you run the Powershell commands to activate the Office web apps services?

      The instructions below can also be found at: – this needs to be done if you have run the SharePoint config wizard prior to installing Office Web Apps.

      Activate the Office Web Apps services and feature by using Windows PowerShell

      When activating Office Web Apps using Windows PowerShell, you can perform the following steps on a stand-alone SharePoint Foundation server or from any SharePoint Foundation server in a server farm.

      Manually performing these steps by using Windows PowerShell is required only if you installed SharePoint Foundation and ran PSConfig on a stand-alone server before you installed Office Web Apps. Or, you must perform these steps if you installed SharePoint Foundation and ran the Farm Configuration Wizard on a farm server before you installed Office Web Apps. If you doubt your SharePoint configuration and Office Web Apps activation, you can check the state of each service and service application in the Manage services on server and Manage service applications pages in SharePoint Central Administration. If none of the Office Web Apps services are running, or the service applications do not exist, then you have confirmed that you must perform the following steps.
      To run scripts in Windows PowerShell, you must set the execution policy to run scripts unrestricted.

      Set Windows PowerShell script execution policy
      Click Start, point to All Programs, point to Windows PowerShell, right-click Windows PowerShell, and then click Run as administrator.

      In the Windows PowerShell console, at the command prompt, type set-executionpolicy unrestricted, and then press ENTER.

      Start the service instances

      A service instance provides the physical location for a service application. For each server you want to run the Office Web Apps service applications; you must start the service instances. Start the service instances by running the following script in Windows PowerShell:

      $machinesToActivate = @(“contosoapp1″,”contosoapp2”)
      $serviceInstanceNames = @(“Word Viewing Service”, “PowerPoint Service”,
      “Excel Calculation Services”)
      foreach ($machine in $machinesToActivate) {
      foreach ($serviceInstance in $serviceInstanceNames){
      $serviceID = $(Get-SPServiceInstance | where
      {$_.TypeName -match $serviceInstance} | where
      {$_.Server -match “SPServer Name=”+$machine}).ID
      Start-SPServiceInstance -Identity $serviceID
      Create the service applications and the service application proxies

      After the service instances have been started, the service applications and the service application proxies which connect the Web front-ends to the service applications must be created. Create the service applications and the service application proxies by running the following script:

      $appPool = Get-SPIisWebServiceApplicationPool
      –Name “SharePoint Web Services Default”
      New-SPWordViewingServiceApplication –Name “WdView” –AppPool $appPool |
      New-SPWordViewingServiceApplicationProxy –Name “WdProxy”
      New-SPPowerPointServiceApplication –Name “PPT” –AppPool $appPool |
      New-SPPowerPointServiceApplicationProxy –Name “PPTProxy”
      New-SPExcelServiceApplication –Name “Excel”
      -SPIisWebApplicationPool $appPool |
      Activate the Office Web Apps feature on all site collections

      Office Web Apps require that the Office Web Apps feature be activated on every site collection for which the Web apps will be available. Activate the Office Web Apps feature for all site collections by running the following script:

      $webAppsFeatureId = $(Get-SPFeature -limit all | where {$_.displayname
      -eq “OfficeWebApps”}).Id
      Get-SPSite –limit ALL |foreach{
      Enable-SPFeature $webAppsFeatureId –url $_.URL }

  7. April 13, 2010 9:27 pm

    dear all i’m trying to install office web apps but it asks for a key..

    in the download link :

    in the instructions: it says

    Customers who wish to install the Office Web Apps (Beta) should click “download” above, and save the file locally. For detailed instructions as to how to install and activate the Office Web Apps (Beta)​, including the necessary product key please see Deploy Office Web Apps
    but i can’t find any key in this link of deploy office web apps !
    can anyone help me with this?

    • Prashanth permalink
      April 23, 2010 2:21 am

      Hi, the product key is BQDC3-93DMP-HGJB2-MFFV8-622QJ.
      Hope it works for you.

      • Mudas permalink
        July 26, 2010 6:53 pm

        Hello Prashanth,

        i tried the key you gave me but it’s not working, can you give me another one if you have any. FYI i am installing office web app beta version.

        thank you for any help.

  8. April 13, 2010 10:38 pm

    i’m trying to install now office web apps but it needs key..

    and i can’t find it here

    as it was sying it’s here

    • April 18, 2010 9:14 pm

      Did you manage to get this working? I was thinking that maybe they have revoked the web apps beta and removed the key since we’re days away from the RTM now.

  9. Fred Morrison permalink
    April 26, 2010 10:39 am

    I’m using the RTM editons of SharePoint Server 2010 and Office 2010 Premium Plus even with all the “tricks” document in this post, can only get the document to render in the browser, but cannot Open with Word without getting the following error:

    Word experienced an error trying to open the file.

    My environment is a virtual machine with 4096MB of RAM, SQL Server 2008 SP1 + CU6, Windows Server 2008 R2 (fully patched through April 2010 “patch Tuesday”). It’s a domain controller (naturally, because I’m doing all my training/experimentation with it), if that matters.

    Clearly, Microsoft has a LOT MORE work to do before Office Web Apps can be considered “ready”.

    • May 8, 2010 6:06 pm

      So your Office Web Apps is actually working if the document is rendering in the browser but you’re getting the error when trying to open the file from SharePoint in the client/desktop application?

      This issue is unlikely to be related to Office Web Apps (since you say it does open in the browser hence office web apps is working fine and this must be a client issue). I have encountered this issue (or something similar) before with documents not opening in the client application.

      Check out this post for some possible solutions:

      It can also be caused by having different versions of Office installed (could even be if you have Office 2010 installed but still have say SharePoint designer 2007 on your machine). If this is the case you could remove all instances of Office on the client machine (including SPD and any other non-standard office apps you may have like Visio, Project etc) and then reinstall Office 2010.

  10. Uma permalink
    July 12, 2010 2:54 pm

    Have anyone tried installing Office Web Application 2010 in Sharepoint Standard Edition?

  11. Mudas permalink
    July 26, 2010 6:56 pm

    Hello All,

    guy i need the link to download Office web app and the working product key.

    kindly help me as i am testing the whole new range of Office 2010, sharepoint 2010 & office web app.

    thank you for any help.

  12. Woksal permalink
    October 12, 2010 7:55 pm

    thank you so much for this post! saved me a lot of time!

  13. March 30, 2011 5:11 am

    I followed the guidelines presented here and elsewhere and was not successful.

    We have a SharePoint 2010 standalone server that is a DC. It is also host to SQL 2008 R2. SharePoint works fine otherwise but we can’t get Office Web Apps to work properly. For Word and Power Point we can select to edit or view in a browser and it works oaky. Excel documents do not view or edit in a browser. One Note only gives an option to check the document out.

    If it is possible to configure Office Web Apps to work with the configuration we have, I’d really like to hear from someone who has done it. We may be able to pay a reasonable fee for someone to do this.

    • June 2, 2011 11:11 pm

      Did you ever get this sorted? Do you get an error when trying to view Excel docs?

  14. Kelly permalink
    March 31, 2011 9:02 am

    So the office web apps seems to be set up correctly on my server, but I keep getting this error ‘Network connectivity has been lost. Check your network connection or try again later’ when trying to view a document online. Any ideas what the problem is??

    • June 2, 2011 11:14 pm

      Sounds similar to the issue that I had prior to running the Powershell commands – I take it you’ve done this? I also found that after installing Silverlight it performed a lot better, so if it is timing out, that might be worth a try too.

  15. June 8, 2011 9:04 pm

    Good article and tim’s comment is what solved it for me. Create a new site, and office web apps works 🙂

  16. January 26, 2012 11:10 pm

    Thanks for this…

    Heads up if your server has in the past been a domain controller but you have DCPROMO out a server you still need to use this ! spent ages ignoring these type of articles thinking that as my server wasn’t a domain controller it was not applicable.



  17. May 17, 2012 1:48 am

    Hi Kylie, how can I follow you ? Liked your post very much.. great work done..

  18. May 17, 2012 1:50 am

    Hi Kylie, How can I follow your posts ? Very nice written thnks..


  1. SharePoint 2010 Office Web Apps on a single server SharePoint Foundation --> Issues and Fixes - Dirk Van den Berghe SharePoint Blog
  2. Configure Office Web Apps for Sharepoint 2010 with DC | Articles Review
  3. Installing Office Web Apps in a Standalone SharePoint 2010 environment « Experience & Solution 410
  4. Installing Office Web Apps in a Standalone SharePoint 2010 environment « Geek’s the new black « Network and System Blog

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: