WinWord.EXE failing with error R6031

A little worrying that Office14/WinWord.exe is failing under Windows 10 Technical Preview for Enterprise Build 9879 with this error. Any possible solution? Regards, John

Hi John,
It seems that your issue is on Office 14/WinWord.exe under Windows 10 Technical Preview rather than Visual Studio. You know, this forum is to discuss Visual Studio IDE issues, so I am afraid that your issue is out of the support range.
I saw someone else also encountered this issue and submit this issue to Windows Community:
http://answers.microsoft.com/en-us/windows/forum/windows_tp-winapps/r6031-error-launching-word-office-14/36d39a23-128d-4668-8aba-d502d7480fb9?status=AllReplies&status=AllReplies%2CAllReplies%2CAllReplies%2CAllReplies
You can reference those suggestions there. If no help, I suggest opening a new thread for your issue on Windows Community which is a better forum for your issue.
Thank you for your understanding.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

Referencing MMPPF winmd file causing "MdilXapCompile.exe failed with error code 2001"

In my windows phone app I am including Microsoft Media Player Framework (MMPPF) to include MediaPlayer and WebVTT functionality. I am referencing the DLL's and winmd files that were built from the MMPPF universal project as appose to referencing the installed
MMPPF extension in Visual Studio. On x86 and ARM(non phone) devices this worked just fine but on ARM phone, no. According to the MDILXapCompileLog the offending file is Microsoft.Media.WebVTT.winmd. Attached is the MDILXapCompileLog. Bellow is the directory
tree of what is included. That bracketed by * are what is referenced in the app. The rest is what is dragged in with it.
+---Universal.WinRT.WebVTT
| | Microsoft.Media.WebVTT.pri
| | *Microsoft.Media.WebVTT.winmd*
| |
| \---Microsoft.Media.WebVTT
| | Microsoft.Media.WebVTT.xr.xml
| |
| \---themes
| Generic.xbf
|
+---Universal.Xaml.Core
| | *Microsoft.PlayerFramework.dll*
| | Microsoft.PlayerFramework.pri
| |
| \---Microsoft.PlayerFramework
| | Microsoft.PlayerFramework.xr.xml
| |
| \---Themes
| Classic.xbf
| Entertainment.xbf
| Generic.xbf
| Phone.xbf
|
\---Universal.Xaml.WebVTT
*Microsoft.PlayerFramework.WebVTT.dll*

Have you tried official sample? https://playerframework.codeplex.com/SourceControl/latest
How did you set the configuration of solution?
Best Regards,
Please remember to mark the replies as answers if they help

Error installing mastercollection cs6 Windows7 x64 - ERROR: Third party payload installer vcredist_x64.exe failed with exit code: 1603

Here's the error summary:
Exit Code: 6
See error summary below:
I installed the Visual C++ 2008 redis pkg from Microsoft site (both x86&x64) then tried reinstalling and after 2 hours the very error and nothing installed!!!
VERY FRUSTRATING...
Please advise
Please see specific errors below for troubleshooting. For example, ERROR:
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 4 error(s)
----------- Payload: Microsoft Visual C++ 2008 Redistributable Package (x86) 9.0.30729.4148 {9C4AA28F-AC6B-11E0-8997-00215AEA26C9} -----------
ERROR: Third party payload installer vcredist_x86.exe failed with exit code: 1603
ERROR: Failed to install Microsoft Visual C++ 2008 Redistributable Package (x86). Please try installing it by double clicking on the executable at "\\nbcc-srv-v-fs01\co-share\Finance and Administration\Information Technology\Software\Adobe\MasterCollection_CS6_LS16\WIN\Adobe CS6\payloads\Microsoft VC 2008 Redist (x86)\vcredist_x86.exe", or download and install the latest Microsoft Visual C++ 2008 Redistributable Package (x86) from Microsoft website - www.microsoft.com
----------- Payload: Microsoft Visual C++ 2008 Redistributable Package (x64) 9.0.30729.4148 {9B78FAB0-AC6B-11E0-8EF3-00215AEA26C9} -----------
ERROR: Third party payload installer vcredist_x64.exe failed with exit code: 1603
ERROR: Failed to install Microsoft Visual C++ 2008 Redistributable Package (x64). Please try installing it by double clicking on the executable at "\\nbcc-srv-v-fs01\co-share\Finance and Administration\Information Technology\Software\Adobe\MasterCollection_CS6_LS16\WIN\Adobe CS6\payloads\Microsoft VC 2008 Redist (x64)\vcredist_x64.exe", or download and install the latest Microsoft Visual C++ 2008 Redistributable Package (x64) from Microsoft website - www.microsoft.com

uninstall those old ms vc packages and install the latest, Latest Supported Visual C++ Downloads
then uninstall anything cs6 that did get installed, clean and reinstall per, Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6

ERROR: Third party payload installer vcredist_x86.exe failed with exit code: -2147024546

My install of Photoshop CC failed during download with the error message:
----------- Payload: Microsoft Visual C++ 2012 Redistributable Package (x86) 11.0.61030.0 {873BE68F-480F-49A6-9649-F98CAB056AFC} -----------
ERROR: Third party payload installer vcredist_x86.exe failed with exit code: -2147024546
ERROR: Failed to install Microsoft Visual C++ 2012 Redistributable Package (x86). Please try installing it by double clicking on the executable at "C:\Users\Charles\AppData\Local\Temp\{6451C8AE-D1A8-4B06-9A19-583A0AAC7146}\Photoshop_15_ LS20_win64\Adobe CC 2014\payloads\Microsoft VC 2012 Redist (x86)\vcredist_x86.exe", or download and install the latest Microsoft Visual C++ 2012 Redistributable Package (x86) from Microsoft website - www.microsoft.com
But I don't find anything in the path described.
The machine is an Asus desktop PC running Windows 8.1 (which I hate and despise) but was stuck with on this recently purchased PC.
Since I can't find the file or error code -2147024546 what is my next step to complete an install?
Thanks,
Charles

Charles the Microsoft Visual C++ 2012 Redistributable Package (x86) component of your operating system has become damaged. You can reinstall it from Latest Supported Visual C++ Downloads.

ERROR: Third party payload installer Install Lightroom 5 CCM.exe failed with exit code: 1603

Anyone out there that knows how to get past this? I´m using Adobe Application Manager and nothing else.
Installed Photoshop and Illustrator without problem, but as I try to install Lightroom 5 it is aborted.

I am having the same problem, I am using win vista 64, and everything but LR 5 works,
{{ Third party payload installer Install Lightroom 5 CCM.exe failed with exit code: 1603 }}
any solutions out there??

[Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messa

Error
[Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There
may be error message
I am using BIDS Microsoft Visual Studio 2008 and running the package to load the data from excel .
My machine has 32 bit excel hence have set property to RUN64BITRUNTIME AS FALSE.
But the error still occurs .
I checked on Google and many have used Delay validation property at Data flow task level to true but even using it at both excel connection manager and DFT level it doesnt work
Mudassar

Thats my connection string
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\SrcData\Feeds\Utilization.xlsx;Extended Properties="Excel 12.0;HDR=NO";
Excel 2010 installed and its 32 bit edition
Are you referring to install this component -AccessDatabaseEngine_x64.exe?
http://www.microsoft.com/en-us/download/details.aspx?id=13255
Mudassar
You can try an OLEDB provider in that case
see
http://dataintegrity.wordpress.com/2009/10/16/xlsx/
you might need to download and install ms access redistributable
http://www.microsoft.com/en-in/download/details.aspx?id=13255
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Windows 7 update fails with error 8000FFFF

I've got a Windows 7 x64 installation that I've had for around three months. Everything has been fine and working up until a few weeks ago. When I run Windows Update it finds updates and allows me to select them, but when I run the install it fails with error 8000FFFF. Update used to work, but then suddenly quit.
I've dug through tons of forum and web sites regarding this specific error, but they all of their solutions do nothing to fix my problem. In frustration I decided to put in a spare hard drive and install Windows 7 from scratch. I did that and the first thing I tried to do after logging in was updates and it failed for the same reason (8000FFF).
I have the same situation with a Windows Storage Server 2008 x64 that I have as well. It has been runing for about six months or more and updates were working fine. Then update started failing for the same or some other reason about the same time. On this machine I can start the update and see it report a percentage downloading the update. It gets to about 5 or 6 percent and then fails.
Is there some possible networking issue at play in my situation? I have earlier Windows versions (XP, XP64, Svr 2003 and Svr 2003 R2) and updates work fine on those. I know those are using a different mechanism, but I do not notice any other kind of networking issues from my house to the Internet. I have not changed anything or any settings in my firewall at all. Is there some specific protocol, port or something that has to work prefectly in order for the new Windows update to work?
All of my machines are pretty much Intel based. Win7 box is a Core2Duo on an EVGA 680i motherboard. The servers are Intel Xeons with Intel motherboards, chipsets and nics.
Thanks for any advice and help

Wow, suddenly I have the same bizarre error at 11% of downloading, then error #8000FFFF.
Fix IT, registry keys and SoftwareDistribution folder cleaning, uninstalling previous updates, manual downloading of appropriate updates and attempt do install it and creating/deleting user profiles - don't work at all.
Any new ideas?
Thanks,
Win7 x64 SP1
Package KB2633873 failed to be changed to the Installed state.
Status: 0x8e5e0408.Windows update "Security Update for Windows (KB2633873)" could not be installed because of error 2388526088 "" (Command line: ""C:\Windows\system32\wusa.exe" "C:\Users\Wiewior\Downloads\Windows6.1-KB2633873-x64.msu"
Package KB2645640 failed to be changed to the Installed state. Status: 0x8e5e0408.
Windows update "Security Update for Windows (KB2645640)" could not be installed because of error 2388526088 "" (Command line: ""C:\Windows\system32\wusa.exe" "C:\Users\Wiewior\Downloads\Windows6.1-KB2645640-x64.msu"

CcmSetup failed with error code 0x80004005 - windows 8.1

using sccm 2012 r2, trying to push to a windows 8.1 client i get:
<![LOG[==========[ ccmsetup started in process 7416 ]==========]LOG]!><time="16:05:28.041+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:9437">
<![LOG[Running on platform X64]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="util.cpp:1837">
<![LOG[Updated security on object C:\WINDOWS\ccmsetup\cache\.]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9272" file="ccmsetup.cpp:9281">
<![LOG[Launch from folder C:\WINDOWS\ccmsetup\]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:721">
<![LOG[CcmSetup version: 5.0.7958.1000]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:727">
<![LOG[In ServiceMain]LOG]!><time="16:05:28.044+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:3365">
<![LOG[Running on 'Microsoft Windows 8.1 Pro' (6.3.9600). Service Pack (0.0). SuiteMask = 272. Product Type = 18]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1"
thread="9468" file="util.cpp:1919">
<![LOG[Ccmsetup command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1"
thread="9468" file="ccmsetup.cpp:3590">
<![LOG[Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context=""
type="1" thread="9468" file="ccmsetup.cpp:3775">
<![LOG[Command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
file="ccmsetup.cpp:3776">
<![LOG[SslState value: 224]LOG]!><time="16:05:28.085+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:4425">
<![LOG[CCMHTTPPORT:    80]LOG]!><time="16:05:28.086+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8617">
<![LOG[CCMHTTPSPORT:    443]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8632">
<![LOG[CCMHTTPSSTATE:    224]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8650">
<![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8668">
<![LOG[FSP:    ]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8720">
<![LOG[CCMFIRSTCERT:    1]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8778">
<![LOG[Config file:      C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
file="ccmsetup.cpp:4539">
<![LOG[Retry time:       10 minute(s)]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4540">
<![LOG[MSI log file:     C:\WINDOWS\ccmsetup\Logs\client.msi.log]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
file="ccmsetup.cpp:4541">
<![LOG[MSI properties:    INSTALL="ALL" SMSSITECODE="consto" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"]LOG]!><time="16:05:28.088+00"
date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4542">
<![LOG[Source List:]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4550">
<![LOG[                  \\TA-SRV-SC.constoplc.local\SMSClient]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup"
context="" type="1" thread="9468" file="ccmsetup.cpp:4557">
<![LOG[                  \\TA-SRV-SC.constoPLC.LOCAL\SMSClient]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup"
context="" type="1" thread="9468" file="ccmsetup.cpp:4566">
<![LOG[MPs:]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4569">
<![LOG[                  TA-SRV-SC.constoplc.local]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context=""
type="1" thread="9468" file="ccmsetup.cpp:4584">
<![LOG[MapNLMCostDataToCCMCost() returning Cost 0x1]LOG]!><time="16:05:28.091+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmutillib.cpp:5479">
<![LOG[No version of the client is currently detected.]LOG]!><time="16:05:28.093+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:2748">
<![LOG[Folder 'Microsoft\Configuration Manager' not found. Task does not exist.]LOG]!><time="16:05:28.094+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="wintask.cpp:622">
<![LOG[Updated security on object C:\WINDOWS\ccmsetup\.]LOG]!><time="16:05:28.095+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:9281">
<![LOG[A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent.]LOG]!><time="16:05:28.095+00" date="01-15-2014" component="ccmsetup" context="" type="1"
thread="9468" file="ccmsetup.cpp:9763">
<![LOG[Running as user "SYSTEM"]LOG]!><time="16:05:28.118+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:1995">
<![LOG[A Fallback Status Point has not been specified. Message with STATEID='328' will not be sent.]LOG]!><time="16:05:28.118+00" date="01-15-2014" component="ccmsetup" context="" type="1"
thread="9468" file="ccmsetup.cpp:9763">
<![LOG[CcmSetup failed with error code 0x80004005]LOG]!><time="16:05:28.119+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:10879">
any ideas why its failing?

Hi,
I've seen the same error on a customer where we had Windows Intune Client (SCCM) installed previously. Did you try it on a newly deployed computer? If you had Intune or another CCM client on it previously make sure you clean it up. Here is a well formulated
instruction:
http://douwevanderuit.wordpress.com/2014/01/30/removing-windows-intune-client/
Usually when deploying to many clients we use a startup script, there is a great one that Jason Sandys made in the link below.
http://blog.configmgrftw.com/configmgr-client-startup-script/
There should be no problems deploying SCCM 2012 R2 clients on Windows 8.1 unless there is something wrong with either the setup or the client computer.
All the best, Jesper Hassing - MCTS SCCM 2012 - MCSA 2012 Server - MCP

Third party payload installer DistillrStarter.exe failed with exit code: 1603

I need to reinstall FrameMaker 11 after a system crash. At 99% of the installation process, I get the following message.
(For my understanding, downloading a new DistillrStarter.exe should solve the issue.
The file is for creating Japanese PDFs. I do not even need it. :-)
Exit Code: 7
Please see specific errors below for troubleshooting. For example, ERROR: DW030 ...
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 2 error(s)
----------- Payload: Adobe PDF Creation Add-On 10 10.0.0.0 {AC76D478-1033-0000-3478-000000000005} -----------
ERROR: Third party payload installer DistillrStarter.exe failed with exit code: 1603
----------- Payload: Adobe FrameMaker 11_AdobeFrameMaker11_en_US 11.0.0.0 {E26880FB-DEB4-4299-A1EB-FDEB85C09FD7} -----------
ERROR: DW030: Custom Action for payload Adobe FrameMaker 11_AdobeFrameMaker11_en_US 11.0.0.0 {E26880FB-DEB4-4299-A1EB-FDEB85C09FD7} returned error. Failing this payload.

Hi Mylenium,
from the notifications, IMHO, FrameMaker installation failed because of a corrupt DistillrStart.exe file in the installer.
What I did not know, in the installation options, I could disable PDF maker.
I do not need this module, that is already installed with Acrobat Pro on my system.
In the support chat, I was not pointed to this, either. Although I asked if I really had to uninstall
all Adobe software from my system before re-installing, even Acrobat...
Thank God, my company's administration remembered this issue from a previous installation.
Best regards,
Michael

Client installation fails with error: The client version 4.00.6487.2000 does not match the MP version 2.50.4253.3000. The client wil not be installed.

Hello World,
I have this remote server that used to be a sms 2003 secondary site server. We uninstalled the SMS role. And used the server as an SCCM remote distribution point. We also want to install an client agent on that server machine. But no mather how i try
to install the client i always see the same error in ccmsetup.log:
File download 100% complete (17847296 of 17847296 bytes). ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Download complete. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Successfully downloaded client files. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Searching for available transform ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Failed to find resource file 'client.mst' ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
No transform available for this locale. Installation will proceed with no transformation. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
An MP exists on this machine. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
The client version 4.00.6487.2000 does not match the MP version 2.50.4253.3000. The client will not be installed. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
A Fallback Status Point has not been specified. Message with STATEID='318' will not be sent. ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
Deleted file C:\WINDOWS\system32\ccmsetup\WindowsServer2003-KB923845-x86-ENU.exe.download ccmsetup 8/18/2010 9:17:18 AM 9916 (0x26BC)
I think the installer finds some remenance of the old SMS_MP. When looking i found some remains in IIS . I tried to remove the remains but still have the same error when installing the client. I uninstalled IIS completly. Can someone tell me where the client
installer looks for the MP version? Would it help if i installed an SCCM MP on that server and the uninstalled it (Upgrade the MP)?

Hello Kent, i ran the ccmclean.exe from the SMS2003 Toolkit. It informed me that my system was cleaned. I ran the sccm client setup manualy and found this in the ccmsetup.log
MSI PROPERTIES are SMSSITECODE=AUTO CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' is MS signed. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
Running installation package
Package: C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi
Log: C:\WINDOWS\system32\ccmsetup\client.msi.log
Properties: SMSSITECODE=AUTO CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: INSTALL. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: WindowsFolder.8AE6A59B_5597_4D75_9BFD_7F566BF56500. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder.98C5B086_7EB0_422A_B0A8_674010F525CD. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SystemFolder.4C5E03E8_F8E5_47CB_8FF4_E46FE34D35A6. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: System64Folder.597B26B2_B5D6_40FF_90DA_B8E672626B1D. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: System64Folder.541D9CA5_CE53_4DCE_903A_9B9E5A6EF2C6. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:21: SmsCheckConfig. ccmsetup 8/18/2010 10:48:21 AM 3140 (0x0C44)
MSI: Action 10:48:22: SMSValidateClientInstallStamp. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: LaunchConditions. Evaluating launch conditions ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: SmsDetectWindowsEmbeddedFBWF. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: SmsCheckNewRemoteTools. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: AppSearch. Searching for installed applications ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: CCPSearch. Searching for qualifying products ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: RMCCPSearch. Searching for qualifying products ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: ValidateProductID. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: CcmSetInstallDir. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: BCDSetX64Dir. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: CcmSetInstallDirFromCmdLine. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: CcmSetPrimaryFolder. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: FindRelatedProducts. Searching for related applications ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: Action 10:48:22: SmsDetectInvalidOrderColocUpgrade. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
MSI: An older version of the SMS Management Point is installed. Please upgrade the Management Point before attempting to upgrade the client. ccmsetup 8/18/2010 10:48:22 AM 3140 (0x0C44)
Installation failed with error code 1603 ccmsetup 8/18/2010 10:48:23 AM 3140 (0x0C44)
Next retry in 120 minute(s)... ccmsetup 8/18/2010 10:48:23 AM 3140 (0x0C44)
Their must be something remaining that ccmclean can't find or can' access so i ran ccmclean /mp. This did some stuff and told me the system was clean again. I reran the client setup.
Guess what
It worked !
Thanxs Kent

Windows Server 2008 SP2 randomly reboots due to lsass.exe failed with status code 255

Hello,
Any help on this issue would be greatly appreciated. I have an older Windows Server 2008 SP2 (I don't believe it is R2) (running SQL Server 2008 and SSRS 2008 on the machine) that is crashing randomly
during business hours. Looking into the event logs, I have found the following:
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066d9669a3e1c.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted.
The process wininit.exe has initiated the restart of computer RIDEDB02 on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.
I found a Hot Fix for a similar issue (https://support.microsoft.com/en-us/kb/2732595?wa=wsignin1.0), but it appeared to only be applicable to Windows Server 2008 R2 and Windows 7.
A few hours later, the crash happened again, with a slightly different error:
The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819. The system will now shut down and restart.
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066fa9d74c5d7.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted.
The security package Kerberos generated an exception. The exception information is the data
I have been unable to find a reason for these exceptions and the server rebooting. Any thoughts or ideas on how I can correct this error so it doesn't reboot our server again? .
Thank you,
Ben

Hello,
Any help on this issue would be greatly appreciated. I have an older Windows Server 2008 SP2 (I don't believe it is R2) (running SQL Server 2008 and SSRS 2008 on the machine) that is crashing randomly
during business hours. Looking into the event logs, I have found the following:
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066d9669a3e1c.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted.
The process wininit.exe has initiated the restart of computer RIDEDB02 on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.
I found a Hot Fix for a similar issue (https://support.microsoft.com/en-us/kb/2732595?wa=wsignin1.0), but it appeared to only be applicable to Windows Server 2008 R2 and Windows 7.
A few hours later, the crash happened again, with a slightly different error:
The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819. The system will now shut down and restart.
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066fa9d74c5d7.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted.
The security package Kerberos generated an exception. The exception information is the data
I have been unable to find a reason for these exceptions and the server rebooting. Any thoughts or ideas on how I can correct this error so it doesn't reboot our server again? .
Thank you,
Ben

Imaging failed with error 175

We recently updated all of our servers with the new ZDM7NWSP1IR4HP1. We distributed the zenworks update through our zenworks for servers so we downloaded the CPK files. Updates were successful except now we have lost our reimage on next boot functionality on all servers. We get the message "imaging failed with error 175". We downloaded and tried the Zenworks Imaging Driver Update for October 2009. We tried this on one server in our environment that we use for testing purposes. This did not fix the problem.
Can anyone help us? We don't see anything additional on the support site to patch.

Originally Posted by spond
Busytech710,
could you please
1) boot to ZENworks maintenance mode
2) export DEVELOPER_LOG=a
3) perform the imaging task and send me the imglog
spond at novell dot com
Shaun Pond
I will be glad to try this and send you the log. I too tried installing the service pack with winsetup.exe and found that also worked for me as far as making image on next boot work. We really want the CPK method to work as we have so many servers and we were able to update them all in one day versus weeks using winsetup.exe. I'll respond back with info you need as soon as possible.

[ForumFAQ]How to troubleshoot error "SSPI handshake failed with error code 0x80090324"

Understanding the problem:
When connect to SQL Server with Windows authentication, you may receive the following message in the SQL Server error log:
SSPI handshake failed with error code 0x80090324, state 14 while establishing a connection with integrated security; the connection has been closed.
Security Support Provider Interface (SSPI) is a set of Windows APIs that allows for delegation and mutual authentication over any generic data transport layer, such as TCP/IP sockets. SQL Server supports Kerberos indirectly through the Windows Security Support
Provider Interface (SSPI) when SQL Server is using Windows Authentication.
"SSPI Handshake Failed" error happens usually when connection failed between the server and domain controllers or failed Kerberos Authentication. There are many reason for SSPI Handshake error to appear in SQL Server error log.
Troubleshot the problem:
Download and install the Windows error code lookup tool Err.exe to view error descriptions for Windows Error Codes.
The error code 0x80090324 (SEC_E_TIME_SKEW) means "clock on client and server machines are skewed". In most case, this is a Kerberos issue. Kerberos is using a timestamp to protect against replay attacks. The maximum time skew that can be tolerated
between a ticket's timestamp and the current time at the KDC is 5 minutes by default.
Also check the Windows Event Log of client machine, domain controller and the SQL Server machine for existence of W32time error messages.
The solution:
Make sure the clock of client server, domain controller and the server running SQL Server are within five minutes of each other. Or Resynchronize the clock by run w32tm /resync on client machine and SQL Server machine.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

This error can happen due to Active Directory configuration issue or Network related issues. Assuming they are fine,
another reason could be related to fail Kerberos Authentication to connect to SQL Server.
In Windows 2003 and above, the default method of establishing a connection is Kerberos but if it fails, then connection may be established using NTLM. An error may be registered on SQL Server error log due to Kerberos failure.
To confirm if you have any database connection using Kerberos authentication, run this on your SQL Server
SELECT distinct auth_scheme FROM sys.dm_exec_connections
If you only see NTLM and SQL then, there is no Kerberos connection.
To use Kerberos, the client and SQL Server must be in the same domain or trusted domains and a Service Principal Name (SPN) must be registered with Active Directory for SQL Server service account.
You can check if the service account already has SPN, by running this on the SQL Server
setspn -l <domain\sqlserviceaccount>
If you don't see anything starting with MSSQLSvc\ then the account is not setup with SPN.
You can manually register SPN as a Domain Administrator using these commands.
To      create an SPN for the NetBIOS name of the SQL Server use the following      command:
setspn –A MSSQLSvc/<SQL Server computer name>:1433      <Domain\Account>
To      create an SPN for the FQDN of the SQL Server use the following command:
setspn      -A MSSQLSvc/<SQL Server FQDN>:1433 <Domain\Account>
If SQL Server service account is granted "Validated write to service principal name" privilege in Active Directory, SQL Server database engine will register itself when it starts and unregisters at shutdown. If you Domain Administrators do not permit this setting
then you should manually register the SPN and the SSPI error will go away.
Also the SQL Server service account must be granted "Account is trusted for delegation" privilege in Active Directory. If your SQL Server connects to other SQL Server using Linked Server then the server must also be granted "Trust this computer for delegation
to any service" privilege.
For a named instance, you can use the FQDN of the named instance instead of SQL Server FQDN and use the port number.
For a clustered server, you should use the FQDN of the SQL Server virtual name. In this case you will need two entries, one with port name and one without such as
setspn -A MSSQLSvc/<Virtual SQL Server FQDN> <Domain\Account>
setspn -A MSSQLSvc/<Virtual SQL Server FQDN>:1433 <Domain\Account>
Kerberos authentication works when SQL Server, Service Account and Windows account accessing the SQL Server are in same windows domain. If anyone these are in different domain, there must be bidirectional trust established between the domains, otherwise it
does not work.

_Media creation failed with error message: 'The system cannot find the path specified.'

SCCM 2012 R2 CU2 all latest patches.
I attempted to create a task sequence media and I get the error in the screenshot below. I have deleted and recreated the operating system,boot image, driver pack and task sequence. The usb media is 16GB and the task sequence size is 3004MB.
I only see the error in CreateTSMedia.log as below. How do you fix this?
<![LOG[Beginning media generation]LOG]!><time="12:37:44.522+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="mediagenerator.cpp:418">
<![LOG[Partition activated]LOG]!><time="12:37:47.720+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="diskvolume.cpp:849">
<![LOG[Finished formatting volume F:\]LOG]!><time="12:37:55.723+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="imagewriter.cpp:772">
<![LOG[Assigning staging directory to F:\]LOG]!><time="12:37:55.724+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="imagewriter.cpp:1122">
<![LOG[===========================================]LOG]!><time="12:37:56.257+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="mediagenerator.cpp:476">
<![LOG[ Beginning pass to compute volume layout]LOG]!><time="12:37:56.257+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="mediagenerator.cpp:479">
<![LOG[===========================================]LOG]!><time="12:37:56.257+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="mediagenerator.cpp:487">
<![LOG[Setting up new volume]LOG]!><time="12:37:56.257+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="mediagenerator.cpp:1297">
<![LOG[WriteVolumeId()]LOG]!><time="12:37:56.257+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="mediagenerator.cpp:1038">
<![LOG[Failed to create media (0x80070003)]LOG]!><time="12:38:04.925+240" date="06-17-2014" component="CreateTsMedia" context="" type="3" thread="4668" file="createtsmedia.cpp:345">
<![LOG[CreateTsMedia failed with error 0x80070003, details='']LOG]!><time="12:38:04.925+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="createtsmedia.cpp:355">
<![LOG[MediaGenerator::~MediaGenerator()]LOG]!><time="12:38:04.925+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4668" file="mediagenerator.cpp:396">
<![LOG[Media creation process that was started from Admin Console completed.
]LOG]!><time="12:38:05.182+240" date="06-17-2014" component="CreateTsMedia" context="" type="1" thread="4772" file="createmedia.cpp:1065">
<![LOG[CreateMedia.exe finished with error code 80070003]LOG]!><time="12:38:05.182+240" date="06-17-2014" component="CreateTsMedia" context="" type="2" thread="4772" file="createmedia.cpp:1123">

Hi,
Error code 0x80070003 = "The system cannot find the path specified."
Have you checked the log file smsAdminUI.log? Maybe it can give us some clues.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

CreateMedia.exe finished with error code 80070002

Hi,
In one of our locations, we are unable to create USB boot media. We keep getting the error "The system cannot find the file specified" CreateMedia.exe finished with error code 80070002. Does anyone know what would be the cause of this? TIA
CreateTSMedia.log
<![LOG[ADK installation root registry value not found.]LOG]!><time="13:51:24.598+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="wimfile.cpp:207">
<![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="13:51:24.598+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="wimfile.cpp:344">
<![LOG[Opening image file D:\sources\boot.wim]LOG]!><time="13:51:24.598+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="wimfile.cpp:422">
<![LOG[Applying image 1 to volume C:\Users\hidden\AppData\Local\Temp\_tsmedia_3836\BootImageTemp]LOG]!><time="13:51:24.602+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836"
file="wimfile.cpp:613">
<![LOG[Closing image file D:\sources\boot.wim]LOG]!><time="13:51:25.993+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="wimfile.cpp:458">
<![LOG[BootLoader::restore: C:\Users\hidden\AppData\Local\Temp\_tsmedia_3836\BootImageTemp, D:\]LOG]!><time="13:51:46.081+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836"
file="bootloader.cpp:382">
<![LOG[Copied D:\EFI\Microsoft\Boot\bootmgfw.efi to D:\EFI\Boot\bootx64.efi]LOG]!><time="13:51:59.693+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836"
file="bootsystem.cpp:1815">
<![LOG[Copied D:\EFI\Microsoft\Boot\bootmgfw.efi to D:\EFI\Boot\bootia32.efi]LOG]!><time="13:51:59.921+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836"
file="bootsystem.cpp:1815">
<![LOG[Successfully staged files to make media bootable]LOG]!><time="13:51:59.921+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="bootsystem.cpp:1822">
<![LOG[State has been executed.]LOG]!><time="13:52:00.077+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="mediagenerator.cpp:622">
<![LOG[Media Remaining Space= 6597 Mb]LOG]!><time="13:52:00.077+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="mediagenerator.cpp:627">
<![LOG[-------------------------------------------]LOG]!><time="13:52:00.077+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="mediagenerator.cpp:630">
<![LOG[Size available = 6597 Mb, size required = 0 Mb]LOG]!><time="13:52:00.077+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="mediagenerator.cpp:509">
<![LOG[-------------------------------------------]LOG]!><time="13:52:00.077+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="mediagenerator.cpp:610">
<![LOG[Staging base files]LOG]!><time="13:52:00.077+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="mediagenerator.cpp:611">
<![LOG[Media Remaining Space before executing state is 6597 Mb]LOG]!><time="13:52:00.078+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="mediagenerator.cpp:616">
<![LOG[StageBaseFiles::Execute()]LOG]!><time="13:52:00.078+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="stagebasefiles.cpp:562">
<![LOG[Failed to create media (0x80070002)]LOG]!><time="13:52:00.086+360" date="01-09-2015" component="CreateTsMedia" context="" type="3" thread="3836" file="createtsmedia.cpp:345">
<![LOG[CreateTsMedia failed with error 0x80070002, details='']LOG]!><time="13:52:00.086+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="createtsmedia.cpp:355">
<![LOG[MediaGenerator::~MediaGenerator()]LOG]!><time="13:52:00.086+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="3836" file="mediagenerator.cpp:396">
<![LOG[Media creation process that was started from Admin Console completed.
]LOG]!><time="13:52:10.244+360" date="01-09-2015" component="CreateTsMedia" context="" type="1" thread="7776" file="createmedia.cpp:1065">
<![LOG[CreateMedia.exe finished with error code 80070002]LOG]!><time="13:52:10.244+360" date="01-09-2015" component="CreateTsMedia" context="" type="2" thread="7776" file="createmedia.cpp:1123">

You shouldn't really need the path. Just make sure that the distribution point has the content for all packages referenced by the task sequence. You can check that in the Monitoring node of the console under Distribution Status | Content Status
or by going to the Distribution Pints node in Administration. Right click the DP in question and select properties. Then go to the COntent tab
Jeff

WinWord.EXE failing with error R6031

Similar Messages

Maybe you are looking for