Project Pro 2013 client Deployment with Lync 2010 and Team Explorer Excel Issues Following

Question

Current machines are Office 2010 SP1 or SP2 32-bit
Just deployed Project 2013 Pro and Std to the existing machines that had Project 2010 Pro or Std.  We selected the full install since people use integration into different tools.
Results:
lync 2010 64-bit when attending a meeting prompted user to start using and download the Lync Web Component, which breaks features such as muting, etc.  
A repair sent to the workstations for Lync 2010 64-bit fixed that.
Team Explorer 2012 Export to excel from queries gives error Unable to cast COM object of type 'Microsoft.Office.Interop.Excel.ApplicationClass' 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: The interface is unknown. (Exception from HRESULT: 0x800706B5). 
Repair of Team Explorer, Office, Test Manager 2012, etc did not assist.  if we go into excel and connect to TFS, we can then retrieve the query data.  Just not from TFS exporting to excel.  Had to unload Project 2013, repair Office 2010
and rebooted with project off the machine and now it works.   It seems maybe the setup with the shared features and Office tools are breaking something?  We need the ability for VBA and .net functionality, but what could be breaking this?

Answer 1

Hi,
Your environment will support 32 bit of Project professional 2013 (x86) as you have Windows and Office of (X86).
You try to modify registry then you wont face issue.
 The issue when you hit a "1653" is that Windows
Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653"
error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
 these are the issues I've seen:
Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old. 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).
The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603
If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"logging"= "voicewarmup"
kirtesh