Quantcast
Channel: Office 2013 and Office 365 ProPlus - Planning, Deployment, and Compatibility forum
Viewing all articles
Browse latest Browse all 3748

Extended logs for Office 365 repair operation ?

$
0
0

Hello,

I am deploying Office 365 in parallel of an Altiris Software virtualization solution.

Office 365 is deployed as a physical program but every time Visio starts, it makes a repair that is due to the virtualization packages that lie around.

Is there a way to know which file/reg key is causing the repair to happen ?

With Office 2010, there was such information in the events, telling exactly which file/key was causing the self-healing.

But with Office 365, is there a way to get such information ?

I already use extended logs, but there is very few information when the repair occur, indeed nothing about the cause of the repair:

10/31/2014 09:47:46.920 OFFICECL (0x788) 0xc28  Click-To-Run aox3p Verbose AppVEvents:: VirtualEnvironmentTerminated 
10/31/2014 09:47:57.653 OFFICECL (0x788) 0xd08  Click-To-Run aqdyh Verbose ProcessPool::CreateOMutex - Creating Mutex Global\ClickToRun_TaskIntegrateRepair_DoRepairForApp 
10/31/2014 09:47:57.653 OFFICECL (0x788) 0xd08  Click-To-Run aqo42 Medium TaskIntegrateRepair::DoRepairForApp: Starting repair for appID "Visio"... 
10/31/2014 09:47:57.653 OFFICECL (0x788) 0xd08  Click-To-Run ap6et Verbose TaskIntegrateRepair::RepairConfiguration: Starting CCS::Repair for appID "Visio"... 
10/31/2014 09:47:57.653 OFFICECL (0x788) 0xd08  Click-To-Run amcxp Verbose OISVAPI::ReIntegrateVirtualApplications: packageIdString = 9AC08E99-230B-47e8-9721-4577B7F124EA, versionIdString = 1A8308C7-90D1-4200-B16E-646F163A08E8

10/31/2014 09:55:53.708 OFFICECL (0x788) 0xd08  Click-To-Run ap6ev Verbose TaskIntegrateRepair::RepairConfiguration: CCS::Repair done. 
10/31/2014 09:55:53.708 OFFICECL (0x788) 0xd08  Click-To-Run ap6ew Verbose TaskIntegrateRepair::RepairCustomExtensionsAndMSIs: Repairing Custom Extensions and MSIs, licensingOnly=0... 
10/31/2014 09:55:53.708 OFFICECL (0x788) 0xd08  Click-To-Run aoh2j Medium ProcessSpawnerAdapter::SpawnProcessAndWait - Spawning process. Command: "C:\Program Files\Microsoft Office 15\root\integration\integrator.exe", Args: "/R /Extension /Msi PackageGUID="9AC08E99-230B-47e8-9721-4577B7F124EA" PackageRoot="C:\Program Files\Microsoft Office 15\root"" 
10/31/2014 10:00:39.438 OFFICECL (0x788) 0xd08  Click-To-Run aoh2k Verbose ProcessSpawnerAdapter::SpawnProcessAndWait - Process successfully created and completed. Command: C:\Program Files\Microsoft Office 15\root\integration\integrator.exe, Args: /R /Extension /Msi PackageGUID="9AC08E99-230B-47e8-9721-4577B7F124EA" PackageRoot="C:\Program Files\Microsoft Office 15\root" 
10/31/2014 10:00:39.438 OFFICECL (0x788) 0xd08  Click-To-Run apz3i Verbose TaskIntegrate::RunIntegrator: Successfully completed Extensions Repair. 
10/31/2014 10:00:39.438 OFFICECL (0x788) 0xd08  Click-To-Run ap6ex Verbose TaskIntegrateRepair::RepairCustomExtensionsAndMSIs: Custom Extensions and MSIs repair done 
10/31/2014 10:00:39.438 OFFICECL (0x788) 0xd08  Click-To-Run aqo43 Medium TaskIntegrateRepair::DoRepairForApp: Repair for appID "Visio" complete... 
10/31/2014 10:02:12.976 OFFICECL (0x788) 0xd08  Click-To-Run apvcy Medium ClickToRunData::GetConfigurationSetting - Failed to get value for VisioProRetail.MEDIATYPE. 

Many thanks


Viewing all articles
Browse latest Browse all 3748

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>