I am having various issues that seem to spawn from having O365 (C2R) and Visio 2013 Standard Volume (MSI) installed on the same computer. I have put a great deal of time and research into resolving this to no avail.
I have determined the solution is to install O365 as an MSI or Visio as C2R. However, I cannot find an MSI installer for O365. That leaves installing Visio as a C2R, which is plausible using ODT.
So, I downloaded the latest ODT (15.0.4747.1000) and followed various guides to setup the installation. My configuration file is as follows:
<Configuration> <Add SourcePath="%userprofile%\desktop\Office Issues" OfficeClientEdition="32" > <Product ID="VisioStdVolume"> <Language ID="en-us" /> </Product> </Add> <!-- <Updates Enabled="TRUE" UpdatePath="\\Server\Share\" /> --> <Display Level="FULL" AcceptEULA="TRUE" /> <Logging Level="Full" Path="%userprofile%\desktop\Office Issues\Logs" /> <!-- <Property Name="AUTOACTIVATE" Value="1" /> --> </Configuration>
From an elevated command prompt, I run the following command to download:
setup /download configuration.xml
Once that has finished, I then run the following command to install:
setup /configure configuration.xml
The above commands and configuration file, paired together do nothing except generate a UAC prompt and create the following log file:
Timestamp Process TID Area Category EventID Level Message Correlation 08/26/2015 16:39:17.175 SETUP (0x470) 0x1694 Click-To-Run amaxp Medium BaseConfigure::TryGetConfiguration: EULA's have been accepted. 08/26/2015 16:39:17.178 SETUP (0x470) 0x1694 Click-To-Run aoh85 Medium AdminConfigure::HandleStateAction: Configuring an install/crosssell scenario. 08/26/2015 16:39:17.178 SETUP (0x470) 0x1694 Click-To-Run amb0r Medium BlockVolumeInstall::HandleStateAction: No console to write to. Creating one here. 08/26/2015 16:39:17.178 SETUP (0x470) 0x1694 Click-To-Run amb0s Medium BlockVolumeInstall::HandleStateAction: Freeing newly created console window. 08/26/2015 16:39:17.179 SETUP (0x470) 0x1694 Click-To-Run aoh72 Medium ExitBootStateMachine::HandleStateAction: Bootstrapper workflow exiting with result: 0x0 08/26/2015 16:39:17.179 SETUP (0x470) 0x1694 Click-To-Run Telemetry aoh9z Medium AdminBootstrapper::Main: Installation came back with -2147467259. 08/26/2015 16:39:17.181 SETUP (0x470) 0x1694 Logging Liblet aqc99 Medium Logging liblet uninitializing.
I can get this whole process to work if I use the product ID "VisioStdRetail". Except that when I try to enter my key, Visio informs me it is a volume license key and will not work on the version of Visio I have installed.
I have read places that confirm the product ID "VisioStdVolume" as well as "VisioProVolume" no longer function with the configure switch but does with the packager switch. I can confirm that the packager switch does take me a step farther, and generates a package. This is great, but we do not have a virtual application environment set up to utilize this method.
So, by this point you may have already guessed it.. but... My issue is that I cannot get O365 and Visio to coexist on my computer! I need both of these programs installed and functioning properly (I have both installed, but Microsoft doesn't support it and for me it is not functioning). Is there any way to make this work?