Office 2013 local Click to Run deployment error

I have downloaded the x32 version of Office2013 to a local deployment share, making use of the Office Deployment tools. The download succeeded. Share is read access for everyone.
When launching the installer from the share, on a x64 Win7 client, the splash screen is displayed, followed by an error after a few seconds which reads "Windows cannot find C:\Program Files\Microsoft Office 15\ClientX64\integratedoffice.exe"
(I need x32 office due to compatibility with our CRM system)
I reviewed the log file, and can confirm that the files do extract to the path listed in the error.
If I open explorer and browse to the path just after launching the installer, I can see that 'C:\Pogram Files\Microsoft Office 15\ClientX64\integratedoffice.exe' exists momentarily, then the entire "Microsoft Office 15" folder is deleted and the
error appears.
I did try delete the reg keys as per the windows fix recommendation, this made no difference.
There are no errors in the OfficeSetup log All move file commands succeed. The last line in the log file reads|:
[4512] ShellExec: C:\Program Files\Microsoft Office 15\ClientX64\integratedoffice.exe CUSTOMIZE RERUNMODE config "configuration.xml" app root\office15\firstrun.exe admin=1
Please help

Try to run the following hotfix and then check if we can install 32 bit version Office on 64 bit hardware without problem.
http://support.microsoft.com/kb/2809219/en-us
Tony Chen
TechNet Community Support

Similar Messages

SCCM 2012: Office 2013 click to run deploy?

Hi,
We would like to run Office 2013 next to Office 2010. Therefore the click-to-run option (app-v is only possible for Office 2013 ProPlus) looks the way to go.
I found a nice guide a Office 2013 Plus “Click to run” Deploy in SCCM:
http://www.peters.com/Blogs/Lists/Posts/Post.aspx?ID=90 However (posted it also on the site), can I use the /admin to generate the configuration.xml instead and use it within SCCM 2012 deploy?
J
Jan Hoedt

No. Click-to-run does not use the traditional Office setup methodology and thus does not have the same configuration options. More info at
http://technet.microsoft.com/en-us/library/jj219420(v=office.15).aspx
Jason | http://blog.configmgrftw.com | @jasonsandys

Successfully installed Lync 2013 via Click-to-Run, but getting "Choose your product" prompt

After installing Lync 2013 client using method
Click-to-Run "Deploy Office 365 ProPlus from an on-premises location",downloaded Office source is on local hard drive with the
"config.xml" shown below.
I'm getting "Choose your Product" prompt after signing-in. We have Office 365 Enterprise E3 plan and we just wanted to upgrade Lync 2010 to Lync 2013 (not the Basic).
<Configuration>
<Add SourcePath="E:\Temp" OfficeClientEdition="32" >
    <Product ID="LyncRetail">
      <Language ID="en-us" />
    </Product>

</Add>
<Display Level="NONE" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="E:\Temp" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
Though Lync will continue to work when you close the window. I need to deploy the full 2013 client to several
machines locally.
Thanks.

Hello,
Looks like you‘ve tried a hybrid deployment with Lync 2010 and 2013, right? This might be the reason why Lync 2013 keep prompting to choose your product. Lync 2013 will automatically identify the products that it found for your account which you used to
login Lync 2013.
So, please try to remove any earlier version (Better to remove all Office 2010 suite) on your computer and try a fresh installation again. Let’s see the "Choose your product" prompt would appear again.

Office 2013 Click to Run - VAMT error: product SKU is not found

We failed to install the retail key for Office 2013 Home and Business Retail through VAMT. Error is: The Software Licensing Service reported that the product SKU is not found.
VAMT key install and activation worked fine with other retail products. I believe it's somehow related to the click-to-run technology.
Any help would be appreciated.

Hi,
I'm not quite sure how exactly you did in VAMT, but usually, the error message will show up only if you are using a wrong product key.
Do you have any other product keys installed in VAMT? Make sure you are using the correct key. Also, which activation option are you using in VAMT?
http://technet.microsoft.com/en-us/library/hh825164.aspx
Regards,
Ethan Hua
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Office 2013 applications will not run as a domain users

I have a windows 7 64-bit pc with 2013 office home and and business installed. When trying to access Office as a domain user the programs will not run. Is there a fix for this other than making the users local admins?

Hi,
Which version of Office 2013 did you deployed, Windows Installer-based version or the Click-to-Run version?
Did you install the Office product with local administrator account? I notice that the users must be local administrators on their computers to install Office:
http://technet.microsoft.com/en-us/library/ee624360.aspx
If we add the local admin right to the user, can the Office programs be launched? If so, repair the Office programs and then remove the local admin right. See if it can work.
Best regards,
Rex Zhang
TechNet Community Support

Office 2013 Professional Plus - 32 bit Deployment takes an unacceptable time to deploy in SCCM 2012 - SP1 CU3

We recently migrated over to SCCM 2012 SP1 - CU3 the first of the year from SCCM 2007 SP2. We have used SCCM in the past to deploy Office 2010 and had deployed Office 2013 to our IT Dept. before moving over to SCCM 2012. The deployment went as
expected. Now that we are ready to start deploying Office 2013 to our corporate workstations, the deployment time is running 4.5 hours to 5.5 hours from the local site server DP. I am afraid to find out what time we are looking at for remote DP's.
The three factors that are different is that our SCCM site server is virtual, it is running 2012 for the OS, and obviously SCCM 2012-SP1 - CU3. We are using the same package source files. Previous to a successful deployment we were
seeing hash mismatch errors which MS support pointed us to the nic driver on the VM was using E1000E and to change it to a VMX something driver.
So I guess my question is anyone else out there deploying Office 2013 ProPlus - 32 bit from this type of environment? Our previous deployment time for office was a little over an hour (not five hours). Any suggestions where to look to improve
the deployment time?
I am expected to deploy this in one week and have been working on these issues for weeks.

I see now that you are using a combination of scripts and ConfigMgr package/program.
The AppEnforce.log file is for use with the new ConfigMgr Application model.
Is there any reason that you don't use the new model for deploying Office 2013? It's a single step process and perfect for it. If you use the Office Customisation Tool you can customise what you like. The process will then uninstall Office 2010 and install
Office 2013.
This is how you do it
http://www.gerryhampsoncm.blogspot.ie/2013/03/sccm-2012-sp1-step-by-step-guide-part_9368.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Activating MS Office 2013 ProPlus via KMS running on the same server

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Windows Script Host
Software licensing service version: 6.1.7601.17946
Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2015 10:00:12 AM
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0
OK
Output of cscript ospp.vbs /dstatus
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004f00c
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c
Last 5 characters of installed product key: GVGXT
DNS auto-discovery: KMS name not available
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---Exiting-----------------------------

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Windows Script Host
Software licensing service version: 6.1.7601.17946
Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2015 10:00:12 AM
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0
OK
Output of cscript ospp.vbs /dstatus
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004f00c
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c
Last 5 characters of installed product key: GVGXT
DNS auto-discovery: KMS name not available
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---Exiting-----------------------------

Office365(Click to Run) Deployment with MDT Offline Media

Hi,
I have a scenario where i have to deploy Office365 using click to run with MDT offline media. Now the problem is with configuration.xml file in which we specify the source path of office files.
Here in this scenario as i have to deploy client machines with offline media, so in this case what will be the path in the config.xml file?
For testing purpose, after downloading the office source files, placed the setup.exe,config.xml file and office source folder in a same folder. Here is the config.xml file that i am using
<Configuration>
<Add SourcePath=" " OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
In source path, i leave it blank,so that it will use the office source files which was saved in the same folder.
Then in MDT server, created a new application for Office365.In command line used the command :- setup.exe /config configuration.xml
Created a new task sequence for OS deployment and added the step install application for installation of Office365.
After creating a selection profile for the deployment, created a offline media for deployment of client machine.
Now while i am running the offline media on the bare-metal machine, after OS installation the deployment got stuck at step install Office 365. Got error message pop up, according to which internet connection needed during installation process so that the
click to run set-up will download the office source files, It means this will not use the previously downloaded file which was saved in the same folder.
So this is what my problem is.. How can i customize the configuration.xml file so that i can install office 365 with offline media.
Regards
Pallavi

<Add SourcePath=" "
....In source path, i leave it blank,so that it will use the office source files which was saved in the same folder.
As per
https://technet.microsoft.com/en-us/library/jj219426.aspx#BKMK_AddElement
SourcePath indicates the installation source path from which to install Office when you run the Office Deployment Tool in
configure mode. If you don’t specify SourcePath in
configure mode, Setup will look in the current folder for the Office source files. If the Office source files aren’t found in the current folder, Setup will look on Office 365 for them
So, for the /configure mode, you should remove the Sourcepath element completely - do not specify as <space>
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Office 365 x64 Click-to-Run Not Automatically Updating from Network Share

We are piloting Office 365 x64 and pointing the clients to a network share (see config file below) for updates. When we subsequently download the updates to the share the clients will not automatically install them. If we manually do so from
within an app (File > Account > Update Options > Update Now) it works fine. The ACL and Sharing permissions allow Everyone and Domain Computers read-only access (in addition to some other ancillary accounts). I've tried manually running
the Office Automatic Updates from Task Scheduler and left the box running overnight. I've rebooted, logged back on, closed and opened the app several times. Nothing happens, just always sits at the current version.
Anyone have any ideas?
      Thanks,
         Bryan
Here's the UpdateURL registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Configuration\UpdateUrl = \\<SERVERNAME>\Office_365\Pilot
ProPlusx64.xml:
<Configuration>
<Add OfficeClientEdition="64" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Updates Enabled="TRUE" UpdatePath="\\<SERVERNAME>\Office_365\Pilot\" />
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />
<Property Name="AUTOACTIVATE" Value="1" />
<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
</Configuration>
Here's what I think is the log file:
Timestamp Process TID Area Category EventID Level Message Correlation
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x554 Click-To-Run Telemetry aqkhc Medium {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","ExeVer":"15.0.4615.1002","SecuritySessionId":"0","ModulePath":"C:\Program Files\Microsoft Office 15\ClientX64\OfficeClickToRun.exe","CommandLine":"/service","Bitness":"64","IntegrityLevel":"0x4000"}
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x554 Click-To-Run Telemetry aqkhe Medium {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","OSVersion":"6.1","SP":"1","ProductType":"1","ProcessorArch":"9","Locale":"1033"}
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run annt7 Medium ProcessPool::Initialize - Initializing Main Process Pool
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run annuf Medium SystemProcessPool::DoInitialize - Initializing System Process Pool
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run anntv Medium ConfigurationManager::Initialize - Initializing ConfigurationManager
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run annt4 Medium Pipeline::Initialize - Initializing pipeline with PipelineServerName: "ClickToRun_Pipeline" and InstallationPath: "C:\Program Files\Microsoft Office 15"
05/01/2015 11:21:11.154 OFFICECL (0x550) 0x568 Click-To-Run annt1 Medium Orchestration::Initialize - Initializing Orchestration
05/01/2015 11:21:11.201 OFFICECL (0x550) 0x568 Click-To-Run annto Medium ApiServer::Initialize - Initializing ApiServer for endpoint: C2RClientAPI_Server_System
05/01/2015 11:24:50.661 OFFICECL (0x550) 0x828 Click-To-Run annty Medium ExecutionContext::QueueScenario - Set executing scenario to UPDATE
05/01/2015 11:24:50.661 OFFICECL (0x550) 0x828 Click-To-Run annuz Medium TaskFactory::TryLoadScenario - Start loading UPDATE scenario
05/01/2015 11:24:50.661 OFFICECL (0x550) 0x828 Click-To-Run annu0 Medium TaskFactory::TryLoadScenario - Loading UPDATE scenario is successful
05/01/2015 11:24:50.676 OFFICECL (0x550) 0x828 Click-To-Run amavh Medium ScenarioController::Initialize - requested display level: False
05/01/2015 11:24:50.676 OFFICECL (0x550) 0x828 Click-To-Run annua Medium ProcessPool::QueueTaskItem - Task SCENARIO:{AC2F0D89-6518-48E9-A0D9-EF039C456034} is being scheduled to run in this process
05/01/2015 11:24:50.676 OFFICECL (0x550) 0x828 Click-To-Run aoicd Medium ExecutionContext::QueueScenario - Successfully queue scenario UPDATE.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run annua Medium ProcessPool::QueueTaskItem - Task UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0} is being scheduled to run in this process
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run annvj Medium Worker::TaskExecutionThreadProc - Task SCENARIO:{AC2F0D89-6518-48E9-A0D9-EF039C456034} completed with TaskState TASKSTATE_EXECUTING.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run annu6 Medium TaskGroup::DoHandleWorkerCompleteEvent - Task {AC2F0D89-6518-48E9-A0D9-EF039C456034} complete event is handled by task {AC2F0D89-6518-48E9-A0D9-EF039C456034}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run apm4n Medium TaskGroup::Finalize - Task AC2F0D89-6518-48E9-A0D9-EF039C456034 is not finished.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run Telemetry amb0n Medium TaskUpdateDetection::ApplySettings: Beginning Update Scenario. {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","TargetVersion":"UNDEFINED","InstallID":"C5912794-7300-4A10-840B-575B03DB98F8","TaskId":"77176F9C-873B-4A7D-8051-EBEB52DDE8B0","TaskState":"TASKSTATE_EXECUTING","UpdatePathType":"CUSTOM","TaskType":"UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0}","Scenario":"UPDATE","TriggeringUI":"UNDEFINED","TaskCaller":"SCHEDULEDTASK"}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run Telemetry aoh6s Medium TaskUpdateDetection::Execute: Ending Update scenario, task trigger source disabled. {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","InstallID":"C5912794-7300-4A10-840B-575B03DB98F8","TaskState":"TASKSTATE_EXECUTING","TaskId":"77176F9C-873B-4A7D-8051-EBEB52DDE8B0","TaskType":"UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0}","Scenario":"UPDATE"}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run annvj Medium Worker::TaskExecutionThreadProc - Task UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0} completed with TaskState TASKSTATE_FAILED.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4b Medium Task::DoHandleWorkerCompleteEvent - Setting Task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0) Task State to (TASKSTATE_FAILED)
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run aqkg7 Medium Task::DoHandleWorkerCompleteEvent - No event is specified for task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0)
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run Telemetry apm4e Medium Task::HandleTaskStateFailed - Handling TaskState (TASKSTATE_FAILED) for task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0). {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","InstallID":"C5912794-7300-4A10-840B-575B03DB98F8","TaskState":"TASKSTATE_FAILED","TaskId":"77176F9C-873B-4A7D-8051-EBEB52DDE8B0","TaskType":"UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0}","Scenario":"UPDATE"}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apkpk Monitorable ScenarioController::CheckProcessPool - Failed to get/create ui process pool, and we are not the ui handler. Cannot process event
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run annu6 Medium TaskGroup::DoHandleWorkerCompleteEvent - Task {77176F9C-873B-4A7D-8051-EBEB52DDE8B0} complete event is handled by task {AC2F0D89-6518-48E9-A0D9-EF039C456034}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {AC2F0D89-6518-48E9-A0D9-EF039C456034}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4a Monitorable Task::DoCancel - Can't cancel task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0) because it is in TASKSTATE_FAILED state
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (57173191-24E0-42E1-96F4-914AF8CFD1D5) in TASKSTATE_NOTSTARTED, set to Cancelled.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (AA63EED2-70B9-4E21-952C-9CFB09EC37C0) in TASKSTATE_NOTSTARTED, set to Cancelled.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {D1506E3F-4B2A-41D3-913B-FA3E889CE20D}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {539BA5C1-BC18-4D11-AF61-CF6EDC58DC33}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (D1E1E548-917D-4D75-8AE5-FC76856C66DC) in TASKSTATE_NOTSTARTED, set to Cancelled.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {9A54EEBA-7B8D-4BD5-8EFE-D21E58FFFEE3}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {9C141B7D-2B22-4C33-9C5C-F6F3394AD19E}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {501487AD-0A47-419D-AF30-B9E616A4579B}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {0270BAF9-3CE0-46EE-A3FE-099ABC06BC14}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (F0E5AF5D-5D82-4370-A2A6-C064CBC39247) in TASKSTATE_NOTSTARTED, set to Cancelled.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 0270BAF9-3CE0-46EE-A3FE-099ABC06BC14.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 501487AD-0A47-419D-AF30-B9E616A4579B.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (A5E75ADF-8BF1-44C4-8900-1BE6070EB609) in TASKSTATE_NOTSTARTED, set to Cancelled.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 9C141B7D-2B22-4C33-9C5C-F6F3394AD19E.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 9A54EEBA-7B8D-4BD5-8EFE-D21E58FFFEE3.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 539BA5C1-BC18-4D11-AF61-CF6EDC58DC33.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task D1506E3F-4B2A-41D3-913B-FA3E889CE20D.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task AC2F0D89-6518-48E9-A0D9-EF039C456034.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task AC2F0D89-6518-48E9-A0D9-EF039C456034.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run annt0 Medium ExecutionContext::ResetExecutingScenario - Reset executing scenario

Hi,
I replied in the other thread:
http://social.technet.microsoft.com/Forums/office/en-US/e9e6be40-fb92-4734-9f94-9dee5599b1d8/office-365-pro-plus-2013-update-wont-apply-automatically?forum=officeitpro#c156ed8c-f65c-450c-9e0f-85f0de513c20
It seems when the install finished it added an extra Office\Data to the path. My path should be \\hsbswpush02\GPsoftware\o365\Office\Data\15.0.4551.1005
but it shows
\\hsbswpush02\GPsoftware\o365\Office\Data\Office\Data15.0.4551.1005
If I edit the path and delete the extra Office\Data Office 365 ProPlus updates from my network location. I cannot figure out why it is adding the extra Office\Data to the path.
My config file looks like this:
  <Updates Enabled="TRUE" UpdatePath="\\hsbswpush02\GPsoftware\o365\Office\Data" />
have you tried omitting the \Office\Data element, from the Updates element ?
http://technet.microsoft.com/en-us/library/jj219426.aspx#BKMK_UpdatesElement
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Office 2013 with Service Pack 1 installation error about "search path"

I have an automated installation technique that has worked fine with Office 2010 Pro Plus (32-bit), incorporating the latest Service Pack into the network administrative installation point (under \updates), adding 10 foreign languages to the network administrative
installation point, creating a custom .msp with the OCT (that goes into \updates too), editing the config.xml files, and then running setup.exe from that network administrative installation point. This works on 32-bit Windows XP clients and on 32- and 64-bit
Windows 7 clients.
For Office 2013 Pro Plus, I have built the network administrative installation point exactly the same way (original DVD files + languages + SP1 updates + config.xml updates), but the installation is failing with every type of client, all with
the same error message. The network administrative installation point is readable by the normal installing account, but I even get the same error when I login as me and initiate setup.exe manually, and I have all rights to this point.
Here's the critical point from a log file:
2014/03/11 11:53:49:691::[2372] DistributionPoint parsed. The distribution point is now set to: \\archive.ads.college.edu\archive\KBOXalt\Office2013
2014/03/11 11:53:49:691::[2372] COMPANYNAME specified in config.xml.
2014/03/11 11:53:49:691::[2372] USERNAME specified in config.xml.
2014/03/11 11:53:49:800::[2372] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode]
2014/03/11 11:53:49:910::[2372] Searching for default versions of resource files under the folder [\\archive.ads.college.edu\archive\KBOXalt\Office2013].
2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
Type: 34::InvalidDirectory.
2014/03/11 11:53:50:019::[2372] WER element [SuppressModal] is set to value [true]
2014/03/11 11:53:50:019::[2372] WER element [P4] is set to value [InvalidDirectory]
2014/03/11 11:53:50:019::[2372] Catalyst execution finished: 03/11/2014 11:53:50. Return code: 30034. Exception caught: InvalidDirectory.
2014/03/11 11:53:50:019::[2372] PERF: TickCount=894821 Name=RunSetup Description=End function
I cannot find any references to this exact error anywhere on the Internet. Can anyone tell me what this means, and how I fix it?

As automated, the utility that runs setup.exe maps a drive letter to
\\archive.ads.college.edu\archive\KBOXalt using a kboxmap AD account, which has read access to the whole \KBOXalt tree. I used that same kboxmap AD account manually to simulate what the utility does, and hit the same problem. But here's what's
odd: right next to that
\\archive.ads.college.edu\archive\KBOXalt\Office2013 directory is an
\\archive.ads.college.edu\archive\KBOXalt\Office2010 directory, both created the same way, and the Office 2010 installation has always worked perfectly using the kboxmap AD account. I don't understand why Office 2013 is only working for an account with
read/write access, where Office 2010 worked fine for an account with only read access. Especially when the Office 2013 resource kit documentation clearly states that the account running the installation should only have read access, nothing more. (All this
KBOX stuff comes from the fact that our deployment environment is a Dell KACE KBOX 1000. However, that plays no part in the problem: ignoring the KBOX 1000, I can manually recreate the problem every time.)

Office 2013 (local) vs. Office 365 (cloud)

For the moment we are primarily interested in using the main Office 2103 apps from the user Desktops. (We do not want users to even store documents on the cloud)
1. Is there a URL indicating the feature differences between local and cloud Office 2013?
2. If we install the suite locally and Microsoft updates the cloud based version, I presume our local verisons will
not be updated automatically. Is that correct?
TIA,
edm2

FWIW, Office 365 desktop applications are Office 2013 and are installed locally, on your desktop, just like every other previous version. Storing documents in the cloud is optional with all versions of office, either subscription or the perpetual license
version.
1. Which office suite are you looking at? The subscription is office pro plus. See http://products.office.com/en-us/buy/compare-microsoft-office-products for the non-subscription offers. Also, the perpetual license doesn't get a license for ipad/android
tablets.
2. You'll be able to install updates as you do now using windows updates, but the updates may not be available for days or weeks after the click to run versions. (So far this isn't happening, but it could in the future.)
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter

Is ms office 2013 supported for report generation? Error 41106

Hi
I have a copy of LV full development suite with the Excel and Word report generation toolkit added.
I have recently changed to using Office 365 that includes offline versions of Excel and Word from Office '13.
When using the report generation toolkit, I get an error 41106.
I have reinstalled the toolkit - no effect.
I sort of assume therefore that office 2013 is not supported?
Any hints, tips, patches or workarounds please.
Bill

Bill_Shepherd wrote:
Hi
I have a copy of LV full development suite with the Excel and Word report generation toolkit added.
I have recently changed to using Office 365 that includes offline versions of Excel and Word from Office '13.
When using the report generation toolkit, I get an error 41106.
I have reinstalled the toolkit - no effect.
I sort of assume therefore that office 2013 is not supported?
Any hints, tips, patches or workarounds please.
Bill
I've seen some issues when I upgraded to Office 2010. Note that it is possible that the route cause of your problem is totally different but in my case there was some ActiveX properties or Methods call that have been changed. I solved this issue by navigating to the property/method that caused the error, clicked on it and reselected the same property/method. You could probably find some older post that discuss that. Hope this help.
Ben64

Office 2013 (Mainly Outlook) Ribbon Menu Display Error

So i have created a MDT System Image for deploying Windows across our Business we are currently using Windows 8.1 32/64Bit Office 2013 SP1 now i have recently updated the image simply to install the latest load of Windows Updates so we are not installing
a load of updates when imaging a machine. a lot of our users are reporting issues in Office mainly Outlook but Word has the issue also, the Ribbon bar has Pixelated Display issues and one would have to close he application and re-open to resolve.
Now i have uploaded two screenshots to my box account and shared the images below as you can see from the screenshots it looks to be a display issue but it is only the Office Applications that fall victim, once you change to something else it dissapears
but this is happening a few times a day now. i have blanked out with black boxes the secure information from our relevant party's they are separate to the issue.
https://app.box.com/s/fd1e8vw5gr7hbtxo42pb
https://app.box.com/s/cyfsuad7uuml5uaq75az

Hi,
I would suggest you start Outlook in Safe Mode to determine if it's 3rd-party add-ins related:
Press Win + R, type "outlook.exe /safe" in the blank box, press Enter.
If there is no such problem in safe mode, disable suspicious add-ins to verify which add-ins caused this problem.
Since you have mentioned that you also meet this problem in Word, I doubt if it's related to a setting in Office:
In any Office application, such as Outlook, go to File -> Options -> Advanced -> Display -> Find "Disable hardware graphics acceleration", have you checked this box? If no, check it and click "OK" to save the setting.
This option is added since Office 2013, and it's global, once it's set in an Office application, it applies to others as well.
More information about hardware acceleration can be found in this article below:
http://social.technet.microsoft.com/Forums/en-US/cc26ac52-5c94-468e-ac34-35c9dcc5b422/hardware-graphics-acceleration?forum=outlook
We can also consider this:
On the Desktop, right click on This PC(or Computer) icon, select
Properties, then Advanced system settings on the left side, under
Advanced tab, click on the Settings button for
Performance.
Now we see this:
Uncheck the box for Animate controls and elements inside windows, click
OK button.
I hope the information can be helpful.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Error installing Office 2013 on Server 2012 R2 RDS - Error 25004: the product key you entered cannot be used on this machine

Hi there,
I really hope someone can help me as I am tearing my hair out trying to get this resolved!
I am working on a Server 2012 R2 server with RDS running. Before it was turned into a RDS server it had a copy of Office 2010 running as a trial to see would it work for the accounting package that is running for users via Remote Desktop. Trial worked ok
so it was converted into a RDS server. Now, as its a RDS it needs to run Office under a volume licence, which I have. However when trying to install I get the message: "Error 25004: the product key you entered cannot be used on this machine. this is most
likely due to previous Office 2013 trials being installed on the system."
In summary I have tried everything I can think of and find to remove all traces of the old Office from the machine but still this message persists. I have run the Fix It For Me uninstall from MS and it cannot find any Office installed. i have manually searched
through all of the Windows directories including Program Files and AppData and removed all traces of Office from there, I have searched the registry and removed all I can find from there.
Where or what file does the installer look at to see that a previous version was installed?
I cannot scrub this machine which I would have done long ago because there is another SQL Server based application running on it.
Really really appreciate anyone that can help me on this,
Thanks

Hi,
I have definitely heard your frustration, and I’ll try my best to help you.
Since Office 2010 installed on it before, you need to remove Office 2010 completely.
KB about this error:
http://support2.microsoft.com/kb/2792178
A similar issue is addressed here. Although this method is based on Office 2010, but we can have a try:
http://www.experts-exchange.com/Software/Office_Productivity/Office_Suites/MS_Office/Q_28475448.html
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best regards,
Greta Ge
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Office 2013 Home and Business terminal service error

i have a hp server with windows 2008 R2 and office home and business 2013 installed also i have installed ncomputing thin clients on the network and my windows is working fine
can any one please help why my ms office 2013 is not working on thin clients and giving me error of terminal services.
regards
shabbir nulwala

Hi,
By Office 2013 is not working, what is the symptom then?
Also, what is the error message?
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Office 2013 local Click to Run deployment error

Similar Messages

Maybe you are looking for