SharePoint 2010 Office Web Apps on a single server SharePoint Foundation –> Issues and Fixes

I finally found some time to get the Office Web Apps working on one of my servers running SharePoint Foundation 2010 beta

This is the server that I had upgraded from WSS 3.0 etc. As you may recall, I had completely uninstalled my SharePoint 2010 Foundation and WSS 3.0 after successfully having upgraded my WSS 3.0 site collection to SharePoint 2010. This enabled me to have a “clean” installation of Foundation. After all that,  I decided to give Office Web Apps a try. The installation went smoothly and after running psconfig, all service applications were up and running.

So I gave it a try and as expected it did not work….bummer … That was some weeks ago. I finally found the time to get this fixed. I googled around a bit and found an article by Kylie Richardson.

She had run into the same issue I had, where the Word Viewer refused to render the document. Apparently this is an issue if you are running SharePoint Foundation on a Domain Controller. The system I am running is running so much more than that :)

In my case the solution did not work. I got error messages in the eventlogs stating that my Excel services and Word Services were not properly registered in the Config database.

Finally I decided to follow Kiley’s article all the way where she installed Foundatation and Office Web Apps before running the SharePoint 2010 Products and Configuration Wizard to create the farm.

The steps I took:

  • took a backup of my site collection
  • uninstalled Office Web Apps
  • then uninstalled SharePoint Foundation 2010
  • reinstalled SharePoint Foundation 2010 without running SharePoint 2010 Products and Configuration Wizard
  • reinstalled Office Web Apps
  • ran SharePoint 2010 Products and Configuration Wizard
  • restored my site collection
  • executed the suggested commands by Kylie:

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

#(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” />

IISRESET

So there I was with my completely reinstalled SharePoint Foundation

Cool. So now Office Web Apps works…..or NOT!

After having doen all these actions, it still didn’t work. I remebered for Excel Services that you need to configure the Trusted File Locations, so I went to the Service Applications, Selected Excel Services and added a trusted file location for my site collection –> No Luck, still didn’t work.

At this point I went back to basic troubleshooting…Eventlog and bam! There was an error indcation that my SharePoint Farm Service account was unable to open my content database, which was not there before having reinstalled everything. As a fix I added my SharePoint Farm Service account in the permissions of my content database and voila, Office Web Apps works!

As it turns out, I am using different accounts for my Application Pools as everyone should and the Excel Services and Word Viewing Service seem to use the default SharePoint Farm Service account for accessing the content.

So again, nice to know, isn’t it ? [:D]

SharePoint 2010 beta error: Retrieving the COM class factory for component with CLSID {BDEADF26-C265-11D0-BCED-00A0C90AB50F} failed due to the following error: 800703fa

So I ran into this issue after having installed my SharePoint 2010 farm with 3 servers. At first I did not want to spend a lot of time troubleshooting this and I solved it be reprovisioning my Central Admin which solved the issue. However one day later, the issue was back. after further investigatioàn this time I got an error indicating:

–> Retrieving the COM class factory for component with CLSID {BDEADF26-C265-11D0-BCED-00A0C90AB50F} failed due to the following error: 800703fa

When performing an IIS reset, the error disappears. You could schedule a iisreset, but hey let’s try to fix this. My good friend Google, found the solution on the blog of Kasper de Jonge.

(http://business-intelligence.kdejonge.net/sharepoint-2010-beta-error-retrieving-the-com-class-factory-for-component-with-clsid-bdeadf26-c265-11d0-bced-00a0c90ab50f-failed-due-to-the-following-error-800703fa)

The solution:

Go to IIS Manager, select the Application Pool for your central administration web  application and click Advanced settings, change the value for “Load User Profile” to “true”

 

Thanks Kasper for this one [:D]

Revert a SharePoint 2010 site to the WSS3.0/MOSS2007 Look after Visual Upgrade

This question came up in one of my comments recently and I wanted to find out if it was even possible to reveert the look back of a SharePoint 2010 site that has been upgraded from WSS 3.0 or MOSS2007

Thanks to Corey Roth and a comment on his post about I found out the following:

“In SharePoint 2010, there is the concept of a UI Version and it has a value of 3 or 4.  When you upgrade your existing site, it will leave you at Version 3 which looks just like WSS3.  However, you have the capability to upgrade to the new SharePoint 2010 visualizations which is version 4.  If the administrators have the options enabled, you can change your UI version using the UI itself.  It provides the capability to run on Version 3 but get a preview of 4 and then ultimately they can convert to version 4 completely.  However, you may want to do this programmatically or you may want to revert back to version 3 after you have turned off preview mode.  “

So there are already two possible ways of doing it:

1. Using Code: (thanks to Corey Roth)

using (SPSite siteCollection = new SPSite(“http://server/site“))
{
    SPWeb site = siteCollection.OpenWeb()
    {
        site.UIVersion = 3;
        site.UIVersionConfigurationEnabled = true;
        site.Update();
    }
}

2. Using Powershell: (thanks to Tobias Zimmergren)

$site = Get-SPSite(“http://portal“)
$web = $site.OpenWeb()
$web.UIVersion = 3
$web.Update()
$web.Dispose()
$site.Dispose()

Tip of the day: The best way for finding your downloads on microsoft.com/downloads –> USE GOOGLE !!

This is my frustration of the week!

Don’t you just hate it when you are on the nice Microsoft Download Center www.microsoft.com/downloads website, that when you search for a download, like Sharepoint Language Pack, that you get a blank page? Well I do!

I blame it on Bing….

 That’s why I decided to kill my Bing ringtones from my cell phone and use Google by default for my Microsof Download searches