If your environment has Office 2010 installed and you install parts of or all of Office 2013, for example Lync 2013, you will not be able to open or create a new Office document from the SharePoint document library. You will get a blank page displayed instead and may see the following URL links:
ms-word:nft|u|http://o15psvr:8080/Shared Documents/Forms/template.dotx|s|http://o15psvr:8080/Shared Documents
Excel Files : "ms-excel:ofv|u|http://sharePointDocumentlibraryURL"
This problem is related to the new Microsoft SharePoint Foundation Support for Office 2013. Office 2013 installs a new version that Office 2010 is not aware of. This causes a conflict and one of the Foundation Support tools needs to be removed. We generally recommend keeping the most recent SharePoint Foundation Support (2013) but if your environment has Office 2010 and Lync 2013, you will want to remove 2013 and keep the 2010 version.
To fix this issue, we need to do two things, we need to create an MSP file to remove the 2013 SharePoint Foundation Support, and then repair Office 2010.
Create a MSP file to remove SharePoint Foundation Support using the Office Customization Tool for Office 2013 (OCT):
1) Open the OCT tool for the Office version you wish to remove SharePoint Foundation services from. In this example it will be for Office 2013.
2) Path to “Set Feature installation state” on the left, expand Microsoft Office and expand Office tools.
3) Under “Microsoft SharePoint Foundation Support, click the drop down and set the sub tier Microsoft SharePoint Foundation Support to “Not Available, Hidden, and Locked” but keep Microsoft Web Access Datasheet Component turned on. You will see the letter “H” and “L” as well as a red “X” as shown in this example:
4) Save the MSP file and close the OCT
Running a Silent Repair of Office:
1) We will need access to Office source, so find your Office source files on the network.
2) Open the config.xml file located in the ProPlus.WW folder (If you are using a different SKU such as Office Standard, the config file will be located in the Standard.WW folder)
3) Change the first editable line in the config file to look like the following:
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes />
4) Save and close the Config file.
After applying the MSP file to remove SharePoint Foundation Support, run the following to repair Office:
“\\my-server\my-Office-2010-source\setup.exe” /repair ProPlus /config “my-Office-2010-source \proplus.ww\config.xml”
Automating this fix across your environment:
If you need to automate this across your environment there are a few ways you achieve this. You could use SCCM and schedule tasks to push out the MSP file first, then run the repair of Office 2010, or you could use a batch file to do the same thing.
Here is an example batch file that can be used to first install the MSP file, then trigger the repair of Office. (Always test scripts before deploying)
=================================
@echo off
:RUN
%windir%\system32\msiexec.exe /p \\<path to msp file>\my-file.msp
goto REPAIR
:REPAIR
“\\my-server\my-share\setup.exe” /repair ProPlus /config “\\my-server\my-share\proplus.ww\config.xml”
:END
Exit
================================
There are other ways to achieve this fix, but the biggest takeaway is to run the MSP file that removes SharePoint Foundation Support from Office 2013 first, then run a repair of Office 2010.