Office 2013 Service Pack 1 installation causes shim error in Windows 8.1 Enterprise

On a clean install of Windows 8.1 Enterprise and Office 2013 I installed RSAT and everything works fine initially. When I install the Office 2013 Server Pack 1 update (categorized as an "Important" update) I then get the following
errors when attempting to open Server Manager:
(I attempted to include an image of the error and a link to the KB article but it wouldn't allow that saying my account must be verified although there appears to be no way to actually verify my account. The "Verify Your Account 13" thread
doesn't help by the way.)
ServerManager.exe - This application could not be started. Do you want to view information about the issue?
Which if I click Yes it takes me to the page for this KB article:
KB2715633
The KB page refers to three different SHIM errors. The second two don’t apply to this scenario but the first seems to. Unfortunately the info on this one is:
“The app is not configured in a way that makes it possible to determine the appropriate version of the .NET Framework runtime.
You can't fix the configuration problem yourself. Contact the app vendor to resolve the issue.”
I've re-installed Windows twice and have been able to replicate the problem each time (Clean Win 8.1 install, Office 2013 install, RSAT, everything works, install Office 2013 SP1).
It says in the KB to "Contact the app vendor". In this case that would be Microsoft.

1. What is you install W 8.1 ENT + all important updates -> Office 2013 > Office 2013 SP1 > RSAT ?
2. Make sure that .NET 3.51 and 4.51 are installed.
3. Make sure that there is no coincidence with issues
http://support.microsoft.com/kb/2817430
4. Try to sesolve problem with Process Explorer and Process Monitor
HTH
Milos

Similar Messages

Cannot download Office 2013 Service Pack 1 (KB2850036)

I'm using SCCM 2012 Config Manager. I've created a software update date for Office 2013 - Service Pack 1. It contains only 1 update, and that's the Office 2013 SP1 (KB2850036).
The standalone installer for this KB is around 640MB, according to the following link.
http://support.microsoft.com/kb/2817430/en-us
When I choose to Download this update with SCCM, it starts the normal "Provisioning Update" process but sits at 0%. The deployment package directory grows to 334 folders, 329 files taking 3,707,522,416 bytes on the hard drive, and then eventually
throws the following error in SCCM.
Error: Service pack 1 for Microsoft Office 2013 (KB2850036) 32-Bit Edition. Failed to download content id 16844655. Invalid certificate signature.
I've tried the download a couple of times, and I get the same thing.
Any suggestions?

WSUS does not use the stand-alone installer for any updates. For this update in specific, because I had a battle with it, there are something like 700 different files that are part of the update and something like 800GB of data - those are ballpark numbers
based on my spotty memory; IOW, lots. Your best bet is just to right-click on the update itself and select download again.
If that still doesn't work at all, you can click on the update and go to the content tab, you'll see all of the files listed. You can individually copy the URLs (using Ctrl+C) and download them manually if there are one or two that won't download.
Jason | http://blog.configmgrftw.com

Office 2010 Service Pack 2 (SP2) installation failing with error code 0x80070643 and B56

I've been trying to install Office 2010 service pack 2 (32 bit) multiple ways without success. I've tried getting it directly from Microsoft Update, downloading the full file from Microsoft and installing it, using WSUS to deploy to clients, and I've tried
using LANDesk to deploy it. All methods are failing.
I need a solution that doesn't involve touching each PC manually, as I have a feeling this error is going to occur on several hundred PC's in my organization. So far on a group of 15-20 test PC's, every one has failed. We have not had problems with any other
Microsoft Updates before this one.
When I try Microsoft Update, I receive the following error:
Code B56 Windows Update encountered an unknown error.
Below is the WindowsUpdate.log excerpt:
2013-08-06 12:45:33:313 3952 dc4 Handler :::::::::::::
2013-08-06 12:45:33:328 3952 dc4 Handler :: START :: Handler: MSI Install
2013-08-06 12:45:33:328 3952 dc4 Handler :::::::::
2013-08-06 12:45:33:328 3952 dc4 Handler   : Updates to install = 7
2013-08-06 12:45:33:328 3952 dc4 Handler Extracting MSP file stored in CAB officesuiteww-x-none.cab
2013-08-06 12:45:43:671 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:43:671 3952 dc4 Handler Extracting MSP file stored in CAB proofing-en-us.cab
2013-08-06 12:45:43:702 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:43:702 3952 dc4 Handler Extracting MSP file stored in CAB proof-fr-fr.cab
2013-08-06 12:45:43:983 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:43:983 3952 dc4 Handler Extracting MSP file stored in CAB clientshared64ww-x-none.cab
2013-08-06 12:45:44:217 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:44:217 3952 dc4 Handler Extracting MSP file stored in CAB officesuitemui-en-us.cab
2013-08-06 12:45:44:482 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:44:482 3952 dc4 Handler Extracting MSP file stored in CAB clientshared64mui-en-us.cab
2013-08-06 12:45:44:529 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:44:529 3952 dc4 Handler Extracting MSP file stored in CAB proof-en-us.cab
2013-08-06 12:45:44:716 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:44:716 3952 dc4 Handler   : Batch installing 7 updates
2013-08-06 12:45:46:417 3952 dc4 Handler List of MSPs in transaction:
2013-08-06 12:45:46:417 3952 dc4 Handler   C:\Windows\SoftwareDistribution\Download\29f5035d168bf9e9d0369f84037ff787\img\officesuiteww-x-none.MSP
2013-08-06 12:45:46:417 3952 dc4 Handler MSP final command line: DISABLESRCPROMPT=1 LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS MSIRESTARTMANAGERCONTROL=Disable
2013-08-06 12:46:42:265 112 600 Report Uploading 2 events using cached cookie, reporting URL =
http://wsus:8530/ReportingWebService/ReportingWebService.asmx
2013-08-06 12:46:42:358 112 600 Report Reporter successfully uploaded 2 events.
2013-08-06 12:47:52:012 3952 dc4 Handler MSP Error List:
2013-08-06 12:47:52:012 3952 dc4 Handler 1: 2902 2: ixfAssemblyCopy
2013-08-06 12:47:52:012 3952 dc4 Handler   : MSI transaction completed. MSI: 0x80070643, Handler: 0x8024200b, Source: No, Reboot: 0
2013-08-06 12:47:52:012 3952 dc4 Handler   : WARNING: First failure for update {365F23BF-5D31-4811-A197-29C2C0751961}, transaction error = 0x8024200b, MSI result = 0x80070643, MSI action = InstallFiles
2013-08-06 12:47:52:012 112 938 AU >>## RESUMED ## AU: Installing update [UpdateId = {9C5E43A3-3AE9-434D-B105-A9D7902D5F9F}]
2013-08-06 12:47:52:012 112 938 AU   # WARNING: Install failed, error = 0x80070643 / 0x00000B56
2013-08-06 12:47:52:012 3952 dc4 Handler   : WARNING: Operation failed at update 0, Exit code = 0x8024200B
2013-08-06 12:47:52:012 3952 dc4 Handler :::::::::
2013-08-06 12:47:52:012 3952 dc4 Handler :: END :: Handler: MSI Install
2013-08-06 12:47:52:012 3952 dc4 Handler :::::::::::::
2013-08-06 12:47:52:168 112 5c4 Agent *********
2013-08-06 12:47:52:168 112 5c4 Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates]
2013-08-06 12:47:52:168 112 5c4 Agent *************
2013-08-06 12:47:52:168 112 938 AU Install call completed.
2013-08-06 12:47:52:168 112 938 AU   # WARNING: Install call completed, reboot required = No, error = 0x00000000
2013-08-06 12:47:52:168 112 938 AU #########
2013-08-06 12:47:52:168 112 938 AU ## END ## AU: Installing updates [CallId = {87C0C0A5-18CE-45A0-9376-989DCA9CACCA}]
2013-08-06 12:47:52:168 112 938 AU #############

I too have been unable to install the Office 2010 SP2 update on either a Win7 or a Win 8 system. Researching the errors I got led me to discover the following:
1. Many people are encountering errors during the SP2 installation. Some were able to get around it by downloading the self-installing package and bypassing Windows Update. Some were able to get it installed by first doing a Repair on Office 210 itself
first, and then installing SP2. But many others have not been able to install it at all.
2. Apparently a common and insurmountable issue that prevents SP2 from installing is the lack of the MSOCACHE directory. This directory normally gets installed on a machine during the original install of Office, and contains all the install files used
during the installation. Apparently the idea behind creating MSOCACHE was to allow subsequent updates without requiring the user to have the original source CD available.
The problem is that if MSOCACHE is deleted, which is an option many people choose, you can then no longer do any updates to Office.
I am one of those people.
I found a posting that described a way to recreate MSOCACHE from the source CD. I did that, and the SP2 update actually got farther - it started to install stuff but then stopped and asked for a particular file. I found the file on the CD and
pointed the installer to it, but it said the file was not found and quit. So my install still failed.
The last response I got at the Microsoft Answers site was to wait until SP2 is debugged. It's not clear to me this will ever happen, but we'll see.
Birk Binnard http://www.birkbinnard.com

Error in Configuration Wizard after installing SharePoint 2013 Service Pack 1

Windows Server 2012 with latest updates and SharePoint 2013 with latest updates:
I installed SharePoint 2013 Service Pack 1 and when I run the configuration Wizard i get this error:
Error in Configuration Wizard
Resource id to be retrieved is PostSetupConfigurationFailedEventLog for language English (United States)
Resource retrieved id PostSetupConfigurationFailedEventLog is Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information
located at {0}, fix the problem, and run this configuration wizard again.
Leaving function StringResourceManager.GetResourceString
Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\15\LOGS\PSCDiagnostics_3_8_2014_23_55_49_686_1872915373.log, fix the problem, and run this configuration wizard again.
In event view I see this two errors:
1) First error
System
Provider
[ Name]
SharePoint 2010 Products Configuration Wizard
EventID
104
[ Qualifiers]
0
Level
2
Task
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2014-03-08T21:41:59.000000000Z
EventRecordID
135580
Channel
Application
Computer
ABC-SRV-WEB01.abc.local
Security
EventData
Failed to initiate the upgrade sequence. An exception of type System.MissingMethodException was thrown. Additional exception information: Method not found: 'Void Microsoft.SharePoint.WorkflowServices.IWorkflowService.Upgrade(System.Object,
System.String, Microsoft.SharePoint.Upgrade.SPLog)'. System.MissingMethodException: Method not found: 'Void Microsoft.SharePoint.WorkflowServices.IWorkflowService.Upgrade(System.Object, System.String, Microsoft.SharePoint.Upgrade.SPLog)'. at System.RuntimeTypeHandle.GetTypeByName(String
name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type) at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError,
Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName) at System.Type.GetType(String typeName) at Microsoft.SharePoint.Utilities.SPTypeSerializer.DeserializeType(String typeName,
Guid classId, Boolean bResolveMissingTypes) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.ResolveObjectAndClassVersions(SPLog log) at Microsoft.SharePoint.Upgrade.SPManager.BootStrap(Guid sessionId, SPUpgradeOperationFlags flags) at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
2) Second error
System
Provider
[ Name]
SharePoint 2010 Products Configuration Wizard
EventID
100
[ Qualifiers]
0
Level
2
Task
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2014-03-08T21:41:59.000000000Z
EventRecordID
135581
Channel
Application
Computer
ABC-SRV-WEB01.abc.local
Security
EventData
Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\15\LOGS\PSCDiagnostics_3_8_2014_23_41_9_710_572545016.log, fix the problem, and run this configuration wizard again.
Please advise on next steps.
How can I successfully install SP1?
Thanks,
Alex

could you please share the upgrade log file, so that we understand the error?
did you reboot your server after the installation of SP1?
also try to clear the Config cache on the servers and then try again?
you can run this command on the server its failing
Get-SPProduct -local
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Office 2013 license pack does not allow me to activate key within configuration wizard

Hello,
I have a KMS host running Office 2010 activations for our client computers which is running fine. I installed the Office 2013 license pack on the same host. However, in the configuration wizard it doesn't allow me to activate the product key. Is there
a way around this?
My client laptop isn't activating against the KMS host, and I have Office 2013 installed on my laptop. This is what I get when I run
cscript ospp.vbs /act on my client laptop
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd c:\
c:\>cd program files
c:\Program Files>cd microsoft office
c:\Program Files\Microsoft Office>cd office 15
The system cannot find the path specified.
c:\Program Files\Microsoft Office>cd office15
c:\Program Files\Microsoft Office\Office15>ospp.vbs /act
c:\Program Files\Microsoft Office\Office15>cscript ospp.vbs /act
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
Installed product key detected - attempting to activate the following product:
SKU ID: b13afb38-cd79-4ae5-9f7f-eed058d750ca
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
Last 5 characters of installed product key: 92CD4
ERROR CODE: 0xC004F038
ERROR DESCRIPTION: The Software Licensing Service reported that the product coul
d not be activated. The count reported by your Key Management Service (KMS) is i
nsufficient. Please contact your system administrator.
---Exiting-----------------------------
c:\Program Files\Microsoft Office\Office15>

Hi,
Please check if your KMS host key for Office 2013 is valid and you can try to activate the KMS host by telephone.
To get the key for the Microsoft Office 2013 KMS, sign in to Microsoft Volume Licensing Service Center.
On this page, don’t choose the Key Management Service Host Key. Choose the Office version you are licensed for instead, and look for the KMS key for that version.
http://technet.microsoft.com/en-us/library/dn385356.aspx
To activate an Office KMS host by telephone
http://technet.microsoft.com/en-us/library/dn385356.aspx#BMK_ToactivateanOfficeKMSbytelephone
KMS activation of Office 2013
http://technet.microsoft.com/en-us/library/ee624357.aspx
If issue persists, it is recommended to post the question in Office forums for further troubleshooting.
http://social.technet.microsoft.com/Forums/office/en-US/home?category=officeitpro&filter=alltypes&sort=lastpostdesc
Hope this helps.
Jeremy Wu
TechNet Community Support

SharePoint 2013 Service Pack 1 broke Explorer View (WebDAV)?

We recently installed SharePoint 2013 Service Pack 1 and have since been troubled by Explorer View. Very often Explorer View doesn't work. This error often appears:
"We're having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again."
The weird thing is that sometimes the Explorer View works just fine, but more often it doesn't. There's are a lot of blogs / topics about this on the internet, but they all didn't help resolve this issue. We use persistent cookies for our STS (AllowSessionCookies
== false), we've added the site to Trusted Sites, made sure WebClient service is running on the clients, cleared cookie caches, etc., etc.
Explorer View works fine when we connect to Office 365 instances. But our local farm has these problems. We use ADFS auth.
Our problems actually resemble the problems this guy had:
http://blog.skadefro.dk/2011/09/sharepoint-2010-and-webdav.html
But his fix doesn't seem to apply to us.
This all started after installing Service Pack 1, so could this be a Service Pack 1 issue?

Hi LZandman,
There is a KB article, it provides that:
Issue 2
Assume that you access the date in a SharePoint Document Library. Then, you click Open with Explorer View when you view a SharePoint Document Library in Internet Explorer 10. In this situation, the operation fails, and you receive one of the following error
messages.
Error message 2
We're having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again.
Notes
These issues occur only when the SharePoint server is configured for cookie-based authentication, such as SharePoint Online.
You may encounter a similar issue when you use other Web Distributed Authoring and Versioning (WebDAV) servers that are configured for cookie-based authentication.
Please take a look at :
http://support.microsoft.com/kb/2846960/en-us , and download and install the hotfix, compare the result.
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

TypeLoadException after install SharePoint 2013 Service Pack 1

After install SharePoint 2013 Service Pack 1 Russian I got the following error (approximate translation from Russian):
TypeLoadException: Method 'Upgrade' does not implemented in 'WorkflowServiceApplicationProxy'
Any ideas how to workaround it?

Hi,
Please post your ULS logs here.
Please remember to click 'Mark as Answer' on the answer if it helps you

Every time I try to install windows service pack 2 I get error message WindowsUpdate_80004005

When I try to install windows service pack 2 I get error message WindowsUpdate_80004005, has anyone else had this problem and how do you fix it

If you have an external drive (USB thumbdrive or hard disk) connected, disconnect it and try the service pack installation again.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Detection Office 2010 Service Pack 2 - Slipstreamed Install and WSUS rebuild

Hi,
at a customer of us the WSUS infrastructure had some problems and after some investigation the WSUS infrastructure was built up from scratch. We do have one WSUS Server which syncs with Microsoft and two downstream servers. After rebuild the WSUS infrastructure
we do see one issue:
Many clients were deployed with Office 2010 SP2 slipstreamed. Now the WSUS tells us for the Office 2010 Service Pack 2 Update (KB2687455) that it is missing on the clients.
Is this a normal behaviour or is there an issue with the WSUS detection of the Service Pack? How can I see which updates a client reports to WSUS as installed while connecting with the new WSUS Server? I've tried to figure that out within the WindowsUpdateLog.log
file but without success.
Any ideas are very appreciated.
Peter Forster | MVP Virtual Machine 2002-2011 | Austria |

but wouldn't that cause SP2 to install again (or even downloaded to the client?)
Maybe.
Probably.
If the "SP2 slipstream" was incomplete, or additional Office modules were added post-image, then the service pack needs to be reapplied. The key here is understanding how Office 2010 SP2 is different from other Office service packs in history.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Exchange Server 2013 Service Pack Upgrade - Outlook connectivity issue

Hi,
After upgrading to Exchange Server 2013 service pack 1, we are unable to connect via Outlook 2010 or Outlook 2013. Outlook Web Access is working fine though. We have followed all the instructions, and have applied Outlook upgrades, but the issue remain the
same. Outlook was working fine before the upgrade.
Have we missed out something. I would highly appreciate if someone can help out? I'm not sure if this is the known issue as I can't seem to find anything on the internet.
Already applied the transport fix.
Thanks in advance!

Hi,
According to your description, your Outlook 2010 and Outlook 2013 come across the connectivity issue.
To narrow down the issue, I’d like to recommend the following troubleshooting:
1. Check if the issue happens on all Outlook users
2. Check the Outlook Anywhere connectivity by using ExRCA:
https://testconnectivity.microsoft.com/
Additionally, MAPI over HTTP is only supported when you use Outlook 2013 sp1 and Exchange 2013 sp1 at the same time. Since the issue also happens on Outlook 2010 client, we can firstly try the above troubleshooting.
If you have any question , please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Symbian Anna Service Pack installation cancelled i...

How can I check if I have the service pack installed correctly?
In Applications - SW Update - Options - View Update History I see:
Symbian Anna service pack - Installation cancelled
In Settings - Phone - Phone management - Device Updates I have:
Release: Symbian Anna
Software version: 022.014
In App Manager - Installed applications - Logs the last entries are:
Metadata System Upgrade - Installed
Java Runtime Update (2.0) - Installed
Conversation Server 1.58 - Installed
messaging 1.59(0) - Installed
Am I missing any components? Do you all have service pack cancelled? Is there any way to reinstall service pack? Cannot see it in updates or in Nokia Suite.
Thanks.

when you click on the "software update" icon, after the check don't you see the option to reinstall?
Greece Nokia X6 RM-559 v40.0.002
Attachments:
Capture.PNG ‏33 KB

Pushing Office 2007 service packs through WSUS

Does WSUS download MS Office 2007 service packs for administrators to approve and push to workstations?
If so, how can you redownload it or see if it was approved as I cannot find it as being downloaded, approved, declined or unapproved when searching through the wsus server reporting.

Hi,
How did you define products and classifications? You need check product office 2007 and classification service pack.
Another way is to import it via Microsoft update catalog.
http://catalog.update.microsoft.com
Hope this helps.

Which service packs are the eqivalent as the Windows 7 version for W2003?

Thank you for your response to "Crystal Reports XI Release 2 .Net 2005 Server Compatability":
Crystal Reports XI Release 2 .Net 2005 Server Compatability
I did try the Service Pack update for Windows 7 and it worked and resolved the error -- Thank you!
Several Service Pack links and instructions were provided for Windows Server 2008 R2 64-Bit.
I have not as yet tried them, but I did leave out a question:
The best practice to to use the same version of any software on all platforms: development, test and production.
Since it will be requried to use the Service Pack version for Windows 7 and we are currently on Windows Server 2003 32-Bit for development and production, which service packs are the eqivalent as the Windows 7 version for Windows Server 2003 32 Bit?
We currently use NO service pack version of Crystal Reports XI Release 2 .Net 2005 Server on these Windows 2003 Server 32-Bit web servers -- what is the equivalent version which matches the Windows 7 version? -- so that all platforms are using the same version of Crystal Reports XI Release 2 .Net 2005 Server?
Appreciate all of your help.....Dave

If I understand the question then the best way to approach this is to ensure that any and all versions of what ever OS you deploy to have the latest runtime:
https://smpdl.sap-ag.de/~sapidp/012002523100000634042010E/crxir2sp6_net_mm.zip
https://smpdl.sap-ag.de/~sapidp/012002523100000633302010E/crxir2sp6_net_si.zip
These will work on WIN2003, Win2008, Win7, XP, etc., etc.
- Ludek

Office 2013, click icon nothing happens, no errors, no eventlog, MANY clients with this issue

We're an IT solutions provider for companies of all sizes as well, as residential users, and we've been plagued by a new Microsoft-caused issue that's seriously affecting our client's perception of us since it seems like 'you didn't fix it the first
time' or 'you sold us the computer', so it's our responsibility to fix for free.
We've experienced this with 17 people so far, ranging from residential clients with systems that have come from big box stores and from systems we've sold with Microsoft Office 2013 and basically the entire suite stops working.
If you click an icon, you may see an hour glass for a few seconds and nothing happens (but usually nothing happens at all, as though you didn't click it).
Diagnostic steps:
No errors in eventlog, neither under system or application.
No third party add-ins, sometimes it's a stock install on a new / fresh system.
Starting Microsoft Office applications in safe mode, like winword /safe, has no effect.
A quick repair or an online repair will not resolve the issue, it will say it's done but issue still exists.
Microsoft Office 2013 cannot be uninstalled, we always receive the same error code: 0-4
Some systems do not have third party antivirus, some are simply using Microsoft Security Essentials.
This affects all Microsoft Office applications, including Outlook.
Makes no difference if you use another user account or run-as admin.
All Microsoft Office 2013 updates have been installed.
The installation source is undetermined but recent issues stemmed from a physical media (.ISO) install from Microsoft's latest source.
You cannot start the software by clicking on documents created with Office applications.
The only way to remove Microsoft Office 2013 is with the removal tool "O15CTRRemove.diagcab".
The problem returns after a random period of days and no client can relay the actual cause of the issue, it seems random in nature. After the issue is experienced, we go through the same steps including the necessity to utilize the removal tool.
This seems to be a new issue that's come out of the blue within the past few weeks, at least on our end. When 17 random people call out of the blue with the same problem, it suggests it's Windows Update related.
I'm really hoping someone has some insight into this Microsoft glitch and knows of a secret hotfix or special trick to prevent it. I attempted to call Microsoft and it would be more enjoyable to punch a concrete wall since you're dealing with useless people
in a foreign country who can't really comprehend the seriousness or technicality of the issue, and don't really care, and aren't skilled enough to provide
insight.
Does anyone know about this problem?

Thank you for the reply.
I understand the flash you are receiving while launching Excel or Word is very fast. However just wanted to check if it is possible to get a screenshot of it.
Also, are you able to work fine on Excel or Word even after receiving the flash.
It seems the Office installation might have not been done properly.
There is a possibility, everytime you Uninstall any application, there are still some patches left behind which could cause an issue while Installing the same application again or even after Installation is successful, it sometimes gives
issue while launching the application.
If you want to give a try, you may try to Uninstall the product using Offscrub by clicking on the below link & then can have a fresh installation again.
http://support.microsoft.com/kb/2739501
Please let me know the status update once done
Abhijeet, the box flash happens too fast for me to capture a screenshot of it but I believe it's similar to the smaller box activation process (enter your email).
Word and Excel work fine whenever this is observed.
I'm skeptical that this is a "not done properly" kind of scenario, especially when it applies to so many people and many have brand new computers. How can you take a Microsoft Office disc and install it improperly on a new PC? Or how can a person
go through Microsoft's https://officesetup.getmicrosoftkey.com/ setup, use the software for months and suddenly it stops working? If this is a 'not done properly' scenario, then this is a failing of Microsoft's
installation source. I can't reiterate this enough, the software works fine for people since installation date and then randomly stops working at a much later date (but many of them failed last month and this is a newer issue).
I'm starting to get frustrated again as I'd already stated we've used your linked removal tool in my first post and the problem has returned for another user by which I'd used it and reinstalled the product. The client who's PC we have now, one we'd sold
them, needs to be returned to them and while Microsoft Office is currently working, I was told that if this happens again, they're "going to throw the f#(*@ computer in the river". No joke.
If we're at the point where we've moved past evaluating logs, registry keys, or file versions or anything along the lines of a developer determining how this Microsoft bug occurs, then I'll return the system back to the client and hope for the best.
Three strikes and I'm out with this one but perhaps the delayed startup is the final solution... I just wish I knew for sure as we've had a bad year taking a beating for Microsoft's products and their support is the worst in the industry.
It's further frustrating that since I'd touched base with Microsoft via phone calls, the only person who's been able to provide any insight into the issue is me.

Deploying Office 2013 x64 - feature installation state msp not applying

So I created my MSP with setup.exe /admin and configured a number of options in it. I saved the msp as "1Office64bit.msp" and saved it into the Updates folder. I also have a service pack for Office 2013 in the Updates folder.
I created an SCCM application to deploy office. My deployment installation program looks like this - setup.exe /config proplus.ww\config.xml
During my SCCM Build and Capture task sequence Office 2013 installs, the updates apply, and all of the settings in the MSP apply except for one. I specificed in the msp feature installation states to NOT install the Outlook feature, but it's not working?
Also - as a test after the task sequence completes, I run "msiexec /p \\pathtomsp\1Office64bit.msp - and it removes Office like it should. But I don't know why this doesn't happen during the initial installation?

You should use either a config xml file or an MSP during the installation of Office (2013). In your current command line it looks like you're trying to use both. As you saved the MSP file in the updates folder, simply specifying setup.exe should be enough
to start the installation and let it use the MSP.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
So I tried just running setup.exe and it doesn't seem to be working either. I verified in the ccm appenforce.log that the install command was just setup.exe (so the change made it to the client) but Outlook was still installed.
I'm going to try changing it to setup.exe /adminfile to see if that works.

Office 2013 Service Pack 1 installation causes shim error in Windows 8.1 Enterprise

Similar Messages

Maybe you are looking for