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

Office 365 error 259-4 when installing newer Project on top of older ProPlus

$
0
0

Hello,

I am encountering a problem in the following circumstances:

- I install Office 365 ProPlus using version 15.0.4649.1003

- Then I try to install Project from Office 365, but using the newer version 15.0.4659.1001

The setup fails with error 259-4

I found this relevant information in verbose log file:

10/28/2014 12:23:58.767 OFFICECL (0xd9c) 0x1530  Click-To-Run ap3qf Verbose CCS::Publish: start. 
10/28/2014 12:23:58.767 OFFICECL (0xd9c) 0x1530  Click-To-Run amcxk Verbose OISVAPI::PublishPackage: packageIdString = 9AC08E99-230B-47e8-9721-4577B7F124EA, versionIdString = 1A8308C7-90D1-4200-B16E-646F163A08E8 
10/28/2014 12:24:05.428 OFFICECL (0xd9c) 0x1530  Click-To-Run ap3qg Verbose CCS::Publish: PublishPackage finished. 
10/28/2014 12:24:06.879 OFFICECL (0xd9c) 0x1530  Click-To-Run annvi Unexpected Worker::TaskExecutionThreadProc - Encounter OException for task CONFIGURE:{E25A6AFC-9880-4760-9008-4438EBF206B0}. {"MachineID":"981488a4904aad44b1f13142e3395fc6","SessionID":"03dcb06b-2eb1-4a93-b87a-619f39967b2c","GeoID":"223","Ver":"15.0.4649.1003","ErrorCode":"259","ErrorMessage":"ErrorCodeOnly (ORegistryKey.GetSubKeyNames failure: Cannot get all sub key names  for registry HKLM\Software\Microsoft\Office\15.0\ClickToRun\ProductReleaseIDs\Active , Error:0x103)","AppVErrorSource":"","ErrorType":"259"} 
10/28/2014 12:24:06.879 OFFICECL (0xd9c) 0x1530  Click-To-Run apm4s Medium Worker::TaskExecutionThreadProc - Encountered fatal exception "ErrorCodeOnly" while executing Task CONFIGURE:{E25A6AFC-9880-4760-9008-4438EBF206B0}. 
10/28/2014 12:24:07.144 OFFICECL (0xd9c) 0x1530  Click-To-Run Telemetry aoici Medium Task::DoHandleWorkerExceptionEvent - Task (E25A6AFC-9880-4760-9008-4438EBF206B0) starts handling Worker exception event for task (E25A6AFC-9880-4760-9008-4438EBF206B0). {"MachineID":"981488a4904aad44b1f13142e3395fc6","SessionID":"03dcb06b-2eb1-4a93-b87a-619f39967b2c","GeoID":"223","Ver":"15.0.4649.1003","ScenarioInstanceId":"D92AAB08-651E-4681-AD6F-59EC6BA860FB","InstallID":"CFFA125D-543D-4081-81A9-3698CD626574","TaskState":"TASKSTATE_EXECUTING","TaskId":"E25A6AFC-9880-4760-9008-4438EBF206B0","TaskType":"CONFIGURE:{E25A6AFC-9880-4760-9008-4438EBF206B0}","Scenario":"INSTALL"} 
10/28/2014 12:24:07.144 OFFICECL (0xd9c) 0x1530  Click-To-Run aqdyh Verbose ProcessPool::CreateOMutex - Creating Mutex Global\ClickToRun_TaskMutex_3B2063B8-1A55-431B-9934-D3C4A1AEBC61 
10/28/2014 12:24:23.540 OFFICECL (0xd9c) 0x1614  Click-To-Run ama1t Verbose ServiceStartupBehavior::ServiceMain - Notifying timer listener 

Once this happens, Office 365 ProPlus just refuses to start, "Office Click-to-run Client has stopped working"

Problem signature:

  Problem Event Name: APPCRASH

  Application Name: officec2rclient.exe

  Application Version: 15.0.4659.1001

  Application Timestamp: 5423be93

  Fault Module Name: MSVCR100.dll

  Fault Module Version: 10.0.40219.1

  Fault Module Timestamp: 4d5f034a

  Exception Code: 40000015

  Exception Offset: 00000000000761c9

  OS Version: 6.1.7601.2.1.0.256.4

  Locale ID: 4108

  Additional Information 1: 1b1c

  Additional Information 2: 1b1c5e8386cfb867e421d159fddeb197

  Additional Information 3: cf16

  Additional Information 4: cf16543464bf843b28ebfef9af01a286

When following the activity using Procmon I don't see any error for the HKLM key said in the log.

Usually when installing again Project, it works and corrects all ProPlus..

But this is very annoying as I would like to deploy ProPlus and Project independently using a deployment tool like SCCM.

In this case, I was testing a machine where ProPlus was installed in an older version, never updated for any reason, and then my tool trying to install Project but in the newer version....

Thanks


Viewing all articles
Browse latest Browse all 3748

Trending Articles