SharePoint 2010 Install Error

I had previously installed SharePoint with Office Web Apps using an Enterprise license, but for whatever reason the customer decided to go with a Standard license instead. I uninstalled SP, but then when attempting to reinstall, this error came up: “The install in progress conflicts with a previously installed Microsoft Office 2010 Server product.”

Here are the things I had to do to get it to go away:

1) Uninstall Office Web Apps
2) Reboot
3) Backup the registry.
4) Go into the registry to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and run a search for “Office Web” and “Sharepoint” delete any keys found.
5) Reboot

I was then able to install SharePoint again.

Later after talking with a colluge he offered this advice:

Find the UninstallString value and copy out the data by double-clicking or right-clicking and selecting Modify. Open a command prompt as Administrator and paste the value for each key you find. This will force Windows to run an Uninstall instead of ripping out the key manually.

Install Office Web Apps on SharePoint 2010

Installing Office Web Apps on SharePoint 2010

 
Activity 1: Obtain the Media

The best bet is to do a search to find the latest version. Here is a link to the current one:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=27d81b1c-18ae-4983-8e1c-224bb747eb99&displaylang=en 

Activity 2: Evaluate the State of SharePoint
Step 1) If this is an existing SharePoint 2010 installation, delete the existing Excel Service.
 1) Open Central Administration.
 2) Click Application Management.
 3) Under Service Applications, click Manage Service Applications.
 4) Click in the blank area to the right of the Excel Services Application to highlight it.
 5) Choose Delete from the Ribbion.
               
Step 2) Give your service application pool account Full Control of C:\Windows\Temp
 
Step 3) Ensure your service application pool account has db_owner on the content databases in SQL.
 1) Start SQL Server Management Studio
 2) Expand Security -> Logins
 3) Locate the service application pool user and right-click to get to Properties.
 4) Select User Mapping
 5) Find the Content Databases. Typically they are WSS_Something_Content
 6) Click the CheckBox next to each one and Check db_owner under roler membership.
 
Step 4) Ensure your SharePoint Farm account has db_owner on the PerformancePoint Service database
 1) Start SQL Server Management Studio
 2) Expand Security -> Logins
 3) Locate the farm account user and right-click to get to Properties.
 4) Select User Mapping
 5) Find the PerformancePoint Service Databases. Typically it is named PerformacePoint Service_GUID
 6) Click the CheckBox next to each one and Check db_owner under roler membership.
 
 
Activity 3: Run Setup
Step 1) Run Office Web Apps Setup.exe
 
Step 2) Enter the product key.
 
Step 3) The installation will run and then ask you to run the SharePoint product configuration wizard. Launch the Config wizard located at Start -> Programs -> Microsoft SharePoint 2010 Products -> SharePoint 2010 Products Configuration Wizard and let it run.
 
Activity 4: Start Services
Step 1) Open Central Administration. If you are asked to run the configuration wizard select No, I will configure everything myself.

Step 2) Click Application Management.

Step 3) Click Manage Services on Server.

Step 4) Start the Word Viewing Service and PowerPoint Service.
 
Activity 5: Provision Service Applications
Step 1) Click Application Management.

Step 2) Click Manage service applications.

Step 3) Click New and select Word Viewing Service.

Step 4) Give the service a name like Word Viewing Service.

Step 5) Click Use existing application pool and select “SharePoint Web Services” from the drop down.

Step 6) Click Ok

Step 7) Repeat this process for PowerPoint, and Excel.

Step 8) Run an IISRESET.
 
Activity 6: Enable Office Web Apps Site Feature
Step 1) Browse to the site collection in Internet Explorer.

Step 2) Site Actions -> Site Settings -> Site Collection Administration -> Site collection features.

Step 3) Click Activate next to Office Web Apps.
 
If server is a Active Directory domain controller:
Please do note that Office Web Apps is not supported on a DC. So this configuration should be avoided if possible. 
 
If the server is a DC an additional script needs to be run to active the features. Open the SharePoint 2010 power shell and run the following script:
 
$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
 
(OPTIONAL) Found this on a blog while troubleshooting, unfortinuately I no longer have the direct link, but I have never had to use it. It may come in handy:
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” />
 
After the above is done run IISRESET.

iPad Blogging

I decided to really put iPad blogging to the test today. I’m sitting out in an area with no public WiFi around, using only a non-3G iPad, and no external keyboard. Since there is no WiFi around, my connection is being powered by a rooted HTC Hero, which is nice, because it saved me paying extra for the iPad and it’s AT&T data plan. The Hero is 3G only, but it’s plenty for blogging and email. One thing I noticed right away is that HTML markup sucks without a keyboard. To make a “<p>” you have to go into the secondary symbol screen, back to alpha, then back to the a secondary symbol screen. To much clicking around in my opinion. Referencing images is a bit of a pain to. If you need a link, say from a page on the web, you have to suspend your editor, load Safari, copy the link, suspend Safari, re-load the editor and paste it in. Again, to much clicking. IOS 4 should some of this, so I’m looking forward to it. So, although some work arounds and extra steps are needed, blogging on a non 3G iPad works fairly well.