Office 2013 Installer - Fails with No Errors

Hello,
I ran into issues on two different Windows 8 (64-bit) machines today, both with Office 2013 Pro Plus (32-bit) installed. I could not get the installer to come up to add a module (or make any other changes).
On one of the PCs, I tried running the Fixit to remove Office, since the option of the "Online Repair" was not accessible, (installer would not start). Fixit removed Office, but after a reboot, it still would not run the office installer, even
with Office 2013 completely gone.
Things I tried:
- Disabled anti-virus (windows defender)
- Run with elevated privileges (I'm a domain admin and UAC is off, but just to be safe)
- Removed skydrive
- Cleaned out temp directory
- Scanned for registry errors (none)
- Re-downloaded the installer DVD
- Made sure no pending windows update
- Reboots (lots of times, definitely after the uninstall)
- Checked the install log in %temp%, this is what I get:
2013/08/12 13:51:14:263::[2848] PERF: TickCount=1295931 Name=OBootStrapper::Run Description=Begin function
2013/08/12 13:51:14:264::[2848] Operating System version: 6.2.9200 . Platform ID: 2
2013/08/12 13:51:14:264::[2848] Running 32-bit setup on a 64-bit operating system.
2013/08/12 13:51:14:264::[2848] Command line: "F:\SETUP.EXE"
2013/08/12 13:51:14:264::[2848] No command line arguments given
2013/08/12 13:51:14:513::[2848] Verify file signature in "F:\SETUP.EXE"
2013/08/12 13:51:14:562::[2848] F:\SETUP.EXE is trusted.
2013/08/12 13:51:14:562::[2848] Verify file signature in "F:\proplus.ww\OSETUP.DLL"
2013/08/12 13:51:14:598::[2848] F:\proplus.ww\OSETUP.DLL is trusted.
2013/08/12 13:51:14:612::[2848] Using setup controller dll at [F:\proplus.ww\OSETUP.DLL].
2013/08/12 13:51:14:612::[2848] PERF: TickCount=1296274 Name=OBootStrapper::Run Description=Calling RunSetup
This is almost identical to what I see on the other PC, except with different drive letters.
THERE ARE NO ERROR MESSAGES - no popup, no installer dialog - nothing, which makes it really hard to troubleshoot. And it's happening on both Windows 8 machines that have had Office 2013 installed. I am so frustrated right now after wasting half of today
troubleshooting this.
Any thoughts?

Hi
Let’s follow these steps: 
Make sure you have end the tasks of setup.exe and integratedoffice.exe.      
   1. Press the Ctrl + Alt+ Delete key -> Click on Task Manager to open.      
   2. Under Processes tab -> Select setup.exe -> Click on End Process.    
    3. Under Processes tab -> Select integratedoffice.exe -> Click on End Process.  
  Restart the computer in Clean Boot and install Office 2013. Follow the steps:
       http://support.microsoft.com/kb/929135
   Note: After you have finished troubleshooting in clean boot, ensure you restart the computer in normal mode.
In addition, you can also refer to the following link to try more methods:
http://support.microsoft.com/kb/2822317/en-us
Regards

Similar Messages

  • Installation fails with "internal error 2502"

    I have a client running Windows Vista Home Premium Edition (32 bit) and my app's CVI-built installer fails with "Internal Error 2502".
    This installation kit has been successfully deployed on hundreds of computers with various versions of Windows and I have never seen this one. No device drivers or advanced libraries - just the standard runtime. I use CVI 9.0.1.
    Searches reveal very little - some old issues with Office installation, date/time settings etc. but I have yet to find anything that indicates what this error represents.
    Any insights or ideas very welcome.
    Thanks,
    Ian
    Solved!
    Go to Solution.

    That appears to be a Windows Installer (MSI) error, and can have many different causes. Can you confirm that anyWindows installers (perhaps try newest Adobe Reader) work on that system? Is the system's date/time set correctly? Could there be a permissions restriction with C:\Windows\system32 or C:\Programs\National Instruments\Shared?
    I'd also try doing an internet search for "installer error 2502" and see what other tips you might find. If all else fails, try running the installer from the command line like this:
    setup.exe /log install_log.txt
    That will generate a log file that might contain a hint for us.
    Mert A.
    National Instruments

  • Office 2013 SP1 fails with code 17302 - SCCM 2007 R2

    Hi,
    I am trying to deploy Office 2013, along with SP1, in the following order:
    1. Prompt to close all office apps and continue (vbs)
    2. Installation of Office 2013, using modified msp.
    3. Restart
    4. Installation of SP1 with command line /passive /norestart.
    I am doing this all through a package I created in SCCM 2007 R2.
    The first few programs works well. However, when the installation of SP1 starts, SCCM launches the program, then SP1 fails with code 17302.
    Manual installation, through command prompt, with the same switches works fine.
    The error is only when remotely deploying.
    The system is Windows 7 X86 with latest SP.
    Please help!

    Hi,
    Have you checked the log file? Does it say anything there? Also, where is the SP1 installation file stored? Since this only happens while remotely deploying, check the network or the setting of your filewall.
    By the way, you can slipstream Service Pack 1 with your Office 2013 installation media, Office 2013 will be directly installed at Service Pack 1 level, saving you the trouble of applying it afterwards. For the details, please refer to this article:
    http://www.howto-outlook.com/otherprograms/slipstreamoffice2013sp.htm
    (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.)
    Regards,
    Ethan Hua
    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.

  • Oracle Database Express Edition 11g Release2 11.2.0 silent Installation failing with port8081 error

    Hi everyone,
    We are trying to create silent(unattended) install package to install Oracle database 11g express edition 11.2.0 silently on our machines. We modified the provided .iss file as per the requirement and tried to install with below command,
    setup.exe /verbose /s /f1"c:\DISK1\response\oracleXE-install.iss" /f2"c:\DISK1\oracle_log.txt" /v" /l*v "c:\DISK1\oracle_msi_log.txt""
    Installation is failing with below error from the log file,
    1: OracleXE-Server-Install-Message: Port 8081 is in use. Specify a different port number.
    Installshield 11:22:22: Installation aborts, ready to shut down.
    Port 8081 is being used by mcAfee in our organization. We tried passing a different port number for Http in the response file(.iss), but it is failing with same reason.  We have searched foruns and found that we need to stop the port8081 during the oracle XE installation and can start it later once the installation is completed. But As port 8081 is being used by McAfee in our organization, we could not stop it even during oracle XE installation as it creates security issues.
    I am attaching the MSI log(failure log) and modified .iss(modfied .iss file to .iss.txt to be able to attach) files. Please look into it and suggest how can we achieve silent installation in this case.

    Pl see previous discussions about this topic - seems to be a limitation of the silent install process
    OracleXE-Server-Install-Message: The 8081 port is in use.

  • Dreamweaver installation failing with DF012 error

    I am trying to install dreamweaver on windows 8 using cc. Installation is failing with following error message;
    Summary --------------------------------------  - 0 fatal error(s), 2 error(s)    ----------- Payload: Adobe Dreamweaver CC 2014.1 15.0.0.0 {7F823F8E-4348-11E4-8BF8-81763C49AA32} -----------  ERROR: DF012: Unable to find file(Seq 9334)  ERROR: DF024: Unable to preserve original file at "C:\Windows\Fonts\SourceCodePro-Bold.ttf" Error 32 The process cannot access the file because it is being used by another process.(Seq 9334)  -------------------------------------------------------------------------------------
    Please help

    Is there an Exit Code indicated with that message?

  • Project Professional 2013 Installations Fails with Office 2010 installed on Windows 7 x86

    When attempting to install Project Professional 2013 Pro (x86) on Windows Professional x86 PC that has Office 2010 ProSp2 installed client getting an error message at the end of the installation "Project 2013 has encountered an error during setup".
    I have gotten the installer to work on x64 PC with Office 2010 installed. (Something worth noting that even thought I set the reboot to prompt its automatically reboots without warning but, appears to be working.)  I also tried using the OTC, custom XML
    file and just running setup.exe and get the error no matter what. When looking in the logs I there are MSI installer error with an error: Product:
    Microsoft Project Professional 2013 - Update '{A6FFA77F-C1C1-43D3-A2C7-6A5B68138D9F}' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for
    instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
    Without having to uninstall Office 2010 what do I need to modify in the installer to get it to Project 2013 Pro to install on the x86 machine?
    Thanks

    Hi,
    Your environment will support 32 bit of Project professional 2013 (x86) as you have Windows and Office of (X86).
    You try to modify registry then you wont face issue.
     The issue when you hit a "1653" is that Windows
    Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653"
    error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer
    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
     these are the issues I've seen:
    Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
    CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old. 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
    Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
    Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).
    The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603
    If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
    "logging"= "voicewarmup"
    kirtesh

  • Project Server 2013: QueueUpdateProject2 fails with LookupTableItemInvalidLookupTable error

    Hi,
    We have a strange problem here using the newly introduced QueueUpdateProject2 PSI method in WebSvcProject. The server is running version 15.0.4481.1005 (Project Server 2013, March 2013 PU). Here's the minimum repro code:
    projectService.CheckOutProject(projectUid, sessionUid, sessionDescription);
    var projectDataSet = projectService.ReadProject(projectUid, DataStoreEnum.WorkingStore);
    projectDataSet.Project[0].SetModified(); // Simplest repro
    var jobUid = Guid.NewGuid();
    projectService.QueueUpdateProject2(jobUid, sessionUid, projectDataSet, false);
    Unfortunately the QueueUpdateProject2 queue job always fails with error LookupTableItemInvalidLookupTable for this project. Here's the full error information as shown in PWA:
    LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07:
    LookupTableItemInvalidLookupTable (11073). Details: id='11073' name='LookupTableItemInvalidLookupTable' uid='b1c62182-924c-e311-9404-00155d027b07'.
    Queue:
    GeneralQueueJobFailed (26000) - ProjectUpdate.ProjectUpdate2Message. Details: id='26000' name='GeneralQueueJobFailed' uid='b020bf82-924c-e311-9404-00155d027b07' JobUID='f294b911-f500-45bc-91ec-a493bdf3d07a' ComputerName='1beb2ff2-5dc9-4136-aa24-1c2be86c5768'
    GroupType='ProjectUpdate' MessageType='ProjectUpdate2Message' MessageId='2' Stage='' CorrelationUID='ce4e569c-0aa5-70d6-c576-8b3b764d14f1'. For more details, check the ULS logs on machine
    1beb2ff2-5dc9-4136-aa24-1c2be86c5768 for entries with JobUID
    f294b911-f500-45bc-91ec-a493bdf3d07a.
    Here are some corresponding entries from the ULS log:
    11/13/2013 19:36:30.82  Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                 Active Cache Save            
     myzo Medium   Error is: LookupTableItemInvalidLookupTable. Details: LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07 . Standard Information: , LogLevelManager Warning-ulsID:0x6D797A6F has no
    entities explicitly specified. ce4e569c-0aa5-70d6-c576-8b3b764d14f1
    11/13/2013 19:36:30.82  Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                 Active Cache Save            
     4zbp Monitorable PWA:, ServiceApp:Project Server Service Application, User:i:0#.w|my\account, PSI: [TrackingId:fa790381-924c-e311-9404-00155d027b07][ResourceId:3222f5b7-c13b-e311-9404-00155d027b07][SessionGuid:db83645c-50e1-4368-a59f-94df13ff7d5e][SessionDescr:][JobGuid:af20bf82-924c-e311-9404-00155d027b07][ProjectGuid:81a4a757-c446-e311-9404-00155d027b07][PS_AC][400]
    Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.WinProjException: LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07     at Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.P12Deserializer.PostReadRow(P12ContainerHeader
    cntrHeader, Row row)     at Microsoft.Office.Project.Server.BusinessLayer.WinProj.SaveProjectInternal(Guid projGuid, String projName, Int32 projType, Boolean ... ce4e569c-0aa5-70d6-c576-8b3b764d14f1
    11/13/2013 19:36:30.82* Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                 Active Cache Save            
     4zbp Monitorable ...isNewProj, Guid jobGuid, Guid sessionGuid, Guid checkOutByResUid, String sessionDescr, Boolean isFirstPacket, Boolean isLastPacket, String newVersionStamp, Int16 dataFormatVersion, Boolean isDataCompressed, Byte[] projectData,
    String winprojBuildNumber, ACProcessorType acProcType), LogLevelManager Warning-ulsID:0x347A6270 has no entities explicitly specified. ce4e569c-0aa5-70d6-c576-8b3b764d14f1
    We would be happy to provide more information if needed. Project Professional can open and save the project just fine, so it seems to be unrelated to other forum posts (1, 2).
    Has anybody seen this before? Any hints on where to search or what to look for?
    Thanks,
    Thomas
    TPG The Project Group
    [1] http://social.technet.microsoft.com/Forums/projectserver/en-US/da3c0d64-1ced-45dd-ace6-ce821fd1c362/what-are-the-lookup-fields-in-the-local-project-cant-publish-project-to-the-server
    [2] http://answers.microsoft.com/en-us/office/forum/office_2010-project/error-110730x2b41-importsave-to-project-server/03fd792f-4451-4512-ac0b-ddad946c3e3

    Just to clarify,  I get these errors in the ULS logs:
    06-11-2014 14:15:02.42        w3wp.exe (0x23AC)        0x23E0        Project
    Server        Active Cache Save        myzo        Medium        Error is: LookupTableItemInvalidLookupTable.
    Details: LookupTableItemInvalidLookupTable for lookup table value 440c1ce7-61f1-e311-944d-00155de84b1a . Standard Information: PSI Entry Point:  Project User: i:0#.w|africa\spsetupdev Correlation Id: f6a91701-62f1-e311-944d-00155de84b1a PWA Site URL:
    http://epmdev.af.didata.local/PWA SA Name: SharePoint_EPM_Dev_ProjectServerService PSError: LookupTableItemInvalidLookupTable (11073), LogLevelManager Warning-ulsID:0x6D797A6F has no entities explicitly specified.        72d0999c-429e-80e4-4f95-1037e3c788ff
    06-11-2014 14:15:02.42        w3wp.exe (0x23AC)        0x23E0        Project
    Server        Active Cache Save        4zbp        Monitorable        PWA:http://epmdev.af.didata.local/PWA,
    ServiceApp:SharePoint_EPM_Dev_ProjectServerService, User:i:0#.w|africa\spsetupdev, PSI: [TrackingId:f6a91701-62f1-e311-944d-00155de84b1a][ResourceId:f6760993-7a33-47ef-8cea-0c9cc5231ae7][SessionGuid:6c189001-cd9e-e311-9426-00155d879c00][SessionDescr:ZABRYSVEPMD01\Dev
    PWA][JobGuid:d3e31201-62f1-e311-944d-00155de84b1a][ProjectGuid:7537ccc0-7692-4456-93dd-fc7adcb5d1c8][PS_AC][807] Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.WinProjException: LookupTableItemInvalidLookupTable for lookup table value 440c1ce7-61f1-e311-944d-00155de84b1a    
    at Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.P12Deserializer.PostReadRow(P12ContainerHeader cntrHeader, Row row)     at Microsoft.Office.Project.Server.BusinessLayer.WinProj.SaveProjectInternal(Guid projGuid, String projName,
    Int32 projType, Boolean isNewProj, Guid jobGuid, Guid sessionGuid, Guid checkOutByResUid, String sessionDescr, Boolean isFirstPacket, Boolean isLastPacket, String newVersionStamp, Int16 dataFormatVersion, Boolean isDataCompressed, Byte[] projectData, String
    winprojBuildNumber, ACProcessorType acProcType), LogLevelManager Warning-ulsID:0x347A6270 has no entities explicitly specified.        72d0999c-429e-80e4-4f95-1037e3c788ff
    And in addition to that, we get the Error  9000 when saving in MSP.  
    Still downloading the files, but the more and more I look at it I'm hopeful this will solve our problem.
    http://blogs.umtsa.co.za/nicoo

  • Windows 2008 r2 SP1 installation failed with unspecified error 0x80004005 - E_FAIL

    Hi Team,
    We have SQL data base server with Win 2008 r2 OS.When trying install Sp1 it fails after reboot with unspecified error -0x80004005 - E_FAIL.
    Server having snap drive connected with 6 SQL data bases. Sp1 installation running 7 hrs and falling after couple of reboot.
    Any help appreciated.CBS log attached.
    ================================ 2015-01-24 18:48:22, Info CBS Starting TrustedInstaller initialization. 2015-01-24 18:48:22, Info CBS Loaded Servicing Stack v6.1.7601.17514 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\cbscore.dll
    2015-01-24 18:48:23, Info CSI 00000001@2015/1/24:18:48:23.137 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee8d4e94d @0x7fee9079839 @0x7fee90434d3 @0xff03e94c @0xff03d769 @0xff03daff) 2015-01-24 18:48:23, Info CBS Could not load SrClient DLL
    from path: SrClient.dll. Continuing without system restore points. 2015-01-24 18:48:23, Info CSI 00000002@2015/1/24:18:48:23.139 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee8d4e94d @0x7fee90c6806 @0x7fee9092a9c @0x7fee90435a9 @0xff03e94c @0xff03d769)
    2015-01-24 18:48:23, Info CSI 00000003@2015/1/24:18:48:23.139 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee8d4e94d @0x7fee9988728 @0x7fee9988856 @0xff03e444 @0xff03d7ae @0xff03daff) 2015-01-24 18:48:23, Info CBS Ending TrustedInstaller initialization.
    2015-01-24 18:48:23, Info CBS Starting the TrustedInstaller main loop. 2015-01-24 18:48:23, Info CBS TrustedInstaller service starts successfully. 2015-01-24 18:48:23, Info CBS SQM: Initializing online with Windows opt-in: False 2015-01-24 18:48:23, Info CBS
    SQM: Cleaning up report files older than 10 days. 2015-01-24 18:48:23, Info CBS SQM: Requesting upload of all unsent reports. 2015-01-24 18:48:23, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT
    = 0x80004005 - E_FAIL] 2015-01-24 18:48:23, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL] 2015-01-24 18:48:23, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6 2015-01-24
    18:48:23, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL] 2015-01-24 18:48:23, Info CBS No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending. 2015-01-24
    18:48:23, Info CBS NonStart: Checking to ensure startup processing was not required. 2015-01-24 18:48:23, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x136f6c0
    2015-01-24 18:48:23, Info CSI 00000005 Creating NT transaction (seq 1), objectname [6]"(null)" 2015-01-24 18:48:23, Info CSI 00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x23c 2015-01-24 18:48:23, Info CSI 00000007@2015/1/24:18:48:23.144
    CSI perf trace: CSIPERF:TXCOMMIT;1211 2015-01-24 18:48:23, Info CBS NonStart: Success, startup processing not required as expected. 2015-01-24 18:48:23, Info CBS Startup processing thread terminated normally 2015-01-24 18:48:23, Info CSI 00000008 CSI Store
    3877440 (0x00000000003b2a40) initialized 2015-01-24 18:48:23, Info CBS Session: 30423046_1416810351 initialized by client RMT. 2015-01-24 18:48:24, Info CSI 00000009@2015/1/24:18:48:24.057 CSI Transaction @0x1761b90 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195}
    with flags 00000002 and client id [26]"TI5.30423046_1416810351:1/" 2015-01-24 18:48:24, Info CSI 0000000a@2015/1/24:18:48:24.059 CSI Transaction @0x1761b90 destroyed 2015-01-24 18:48:24, Info CBS Appl: DetectUpdate, Package: Microsoft-Windows-SecureStartup-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385,
    Remote Parent: DirectoryServices-DomainController-Tools, Intended State: Staged 2015-01-24 18:48:24, Info CBS Appl: DetectUpdate, Package: Microsoft-Windows-SecureStartup-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Remote Parent: DirectoryServices-DomainController-Tools,
    Intended State: Staged 2015-01-24 18:48:24, Info CBS Appl: Evaluating applicability block(detectUpdate part), disposition is: Staged, applicability: NotApplicable, result applicability state: Staged 2015-01-24 18:48:24, Info CBS Appl: Package: Microsoft-Windows-SecureStartup-OC-Package~31bf3856ad364e35~amd64~~6.1.7600.16385,
    Update: BdeAducExtTool, Applicable: NeedsParent, Dis 2015-01-24 18:48:24, Info CBS Appl: DetectUpdate, Package: Microsoft-Windows-WMI-SNMP-Provider-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Remote Parent: SNMP, Intended State: Installed 2015-01-24 18:48:24,
    Info CBS Appl: Evaluating applicability block(detectUpdate part), disposition is: Staged, applicability: Applicable, result applicability state: Installed 2015-01-24 18:48:24, Info CBS Appl: Package: Microsoft-Windows-WMI-SNMP-Provider-Package~31bf3856ad364e35~amd64~~6.1.7600.16385,
    Update: WMISnmpProvider, Applicable: Applicable, Dis 2015-01-24 18:48:24, Info CBS Appl: DetectUpdate, Package: Microsoft-Windows-IIS-WebServer-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, Local Parent: IIS-WebServerRole, Intended State: Staged 2015-01-24
    18:48:24, Info CBS Appl: Evaluating applicability block(detectUpdate part), disposition is: Staged, applicability: NotApplicable, result applicability state: Staged 2015-01-24 18:48:24, Info CBS Appl: Package: Microsoft-Windows-IIS-W

    Appreciate your suggestion Dave,
    Any idea what could be cause of this failure.?Do you see anything from the CBS logs.
    This server attached with SNAP drive luns,is there something or SQL application preventing this installation ?
    After reboot it revert the installation...it shows "Failure config service pack..reverting changes,do not not turn off your computer".
    Surprisingly it happens both of our SQL data base server.
    Do you think Increasing MaxNumFilters to
    14 shall work ?
    =====================
    =================================CheckSUR.Log==========
    Checking System Update Readiness.
    Binary Version 6.1.7601.22471
    Package Version 26.0
    2015-02-01 09:37
    Checking Windows Servicing Packages
    Checking Package Manifests and Catalogs
    Checking Package Watchlist
    Checking Component Watchlist
    Checking Packages
    Checking Component Store
    Summary:
    Seconds executed: 555
     No errors detected

  • Update 9.5.5 installation failed with no error message other than it failed

    Now my Acrobat is crashing everytime I open a pdf with Microsoft Visual C++ Runtime Error.  The error message says: Program: C...
    That's all, just "Program: C..."
    That's all I have to go on. tried to repair, received same Installation Failed.
    Is there a way I can remove just the 9.5.5 update?
    Thanks,
    Jeffery

    Hi Jeffery_01,
    Can you please follow the steps mentioned: http://helpx.adobe.com/x-productkb/global/troubleshoot-c-runtime-errors-products.html
    If this doesn't work, you can try these steps
    Update Acrobat to its latest patch of 10.1.7 and Reader to 9.5.5 and then test the issue.
    Navigate to where Acrobat or Adobe Reader is installed, usually C:\Program Files\Adobe\Acrobat 10.0\Acrobat\plug_ins  or  C:\Program Files\Adobe\Reader 10.0\Reader\plug_ins rename the Updater.api plug-in to Updater.api.old relaunch Acrobat or Reader and then test the issue.
    Provide full permission to the  Application Data folder and then test the issue. You can navigate to C:\Users\[USERNAME]\ location to get the AppData folder.
    On Windows 7 and Vista platforms, verify the LocalLow directory exists at C:\Users\<user>\AppData with Read and Write permissions.
    ~Deepak

  • MBAM installation fails with 1603 error

    I have a Windows 7 Enterprise client computer that I am attempting to install the MBAM client. The installation fails reporting a 1603 error. There are three areas in the installation log where I receive a return value 3:
    Exit: MBAMClientCAs.dll : PostInstall
    MSI (s) (10:EC) [08:36:37:653]: Closing MSIHANDLE (139) of type 790536 for thread 6612
    CustomAction MbamWmiProvidersInstallCustomAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (10:D4) [08:36:37:685]: User policy value 'DisableRollback' is 0
    MSI (s) (10:D4) [08:36:37:685]: Machine policy value 'DisableRollback' is 0
    Action ended 8:36:37: InstallFinalize. Return value 3.
    MSI (s) (10:D4) [08:36:42:146]: MsiProvideAssembly is returning: 1607
    MSI (s) (10:D4) [08:36:42:333]: Note: 1: 2318 2: 
    MSI (s) (10:D4) [08:36:42:333]: No System Restore sequence number for this installation.
    MSI (s) (10:D4) [08:36:42:333]: Unlocking Server
    MSI (s) (10:D4) [08:36:42:349]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
    Action ended 8:36:42: INSTALL. Return value 3.
    MSI (s) (10:8C) [08:36:42:427]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (10:8C) [08:36:42:427]: Restoring environment variables
    MSI (s) (10:8C) [08:36:42:427]: Destroying RemoteAPI object.
    MSI (s) (10:DC) [08:36:42:427]: Custom Action Manager thread ending.
    MSI (c) (B4:BC) [08:36:42:427]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (B4:BC) [08:36:42:427]: MainEngineThread is returning 1603.
    The lines preceding the first return value 3:
    Entry: RunMofComp
    MSI (s) (10!F4) [08:36:37:045]: Closing MSIHANDLE (148) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:061]: Creating MSIHANDLE (149) of type 790531 for thread 6900
    RunMofComp: mofcomp command line: 'mofcomp.exe "C:\WINDOWS\TEMP\dzorig55.1u0.mof"'
    MSI (s) (10!F4) [08:36:37:061]: Closing MSIHANDLE (149) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:061]: Creating MSIHANDLE (150) of type 790531 for thread 6900
    PreUninstallDeRegister: Ignorable Win32Exception thrown: System.ComponentModel.Win32Exception: The system cannot find the file specified
       at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
       at System.Diagnostics.Process.Start()
       at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
       at Microsoft.BitLockerManagement.ClientInstaller.CustomActions.RunMofComp(Session session, String mofFilePath)
       at Microsoft.BitLockerManagement.ClientInstaller.CustomActions.PreUninstallDeRegister(Session session)
    MSI (s) (10!F4) [08:36:37:061]: Closing MSIHANDLE (150) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:357]: Creating MSIHANDLE (151) of type 790531 for thread 6900
    Exit: PreUninstallDeRegister
    MSI (s) (10!F4) [08:36:37:357]: Closing MSIHANDLE (151) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:357]: Creating MSIHANDLE (152) of type 790531 for thread 6900
    PostInstallRegister: Assembly to install: 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.BitLockerManagement.WmiProviders\2.5.244.0__31bf3856ad364e35\Microsoft.BitLockerManagement.WmiProviders.dll'
    MSI (s) (10!F4) [08:36:37:357]: Closing MSIHANDLE (152) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:357]: Creating MSIHANDLE (153) of type 790531 for thread 6900
    PostInstallRegister: CLR version: 'v2.0.50727'
    MSI (s) (10!F4) [08:36:37:357]: Closing MSIHANDLE (153) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:638]: Creating MSIHANDLE (154) of type 790531 for thread 6900
    PostInstallRegister: Generating MOF file: 'C:\Program Files\Microsoft\MDOP MBAM\Microsoft.BitLockerManagement.WmiProviders.mof'
    MSI (s) (10!F4) [08:36:37:638]: Closing MSIHANDLE (154) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:638]: Creating MSIHANDLE (155) of type 790531 for thread 6900
    PostInstallRegister: MOF generation finished
    MSI (s) (10!F4) [08:36:37:638]: Closing MSIHANDLE (155) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:638]: Creating MSIHANDLE (156) of type 790531 for thread 6900
    PostInstallRegister: Post processing MOF file
    MSI (s) (10!F4) [08:36:37:638]: Closing MSIHANDLE (156) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:638]: Creating MSIHANDLE (157) of type 790531 for thread 6900
    PostInstallRegister: Running mofcomp.exe
    MSI (s) (10!F4) [08:36:37:638]: Closing MSIHANDLE (157) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:638]: Creating MSIHANDLE (158) of type 790531 for thread 6900
    Entry: RunMofComp
    MSI (s) (10!F4) [08:36:37:638]: Closing MSIHANDLE (158) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:638]: Creating MSIHANDLE (159) of type 790531 for thread 6900
    RunMofComp: mofcomp command line: 'mofcomp.exe "C:\Program Files\Microsoft\MDOP MBAM\Microsoft.BitLockerManagement.WmiProviders.mof"'
    MSI (s) (10!F4) [08:36:37:638]: Closing MSIHANDLE (159) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:638]: Creating MSIHANDLE (160) of type 790531 for thread 6900
    PostInstallRegister exception System.ComponentModel.Win32Exception: The system cannot find the file specified
       at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
       at System.Diagnostics.Process.Start()
       at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
       at Microsoft.BitLockerManagement.ClientInstaller.CustomActions.RunMofComp(Session session, String mofFilePath)
       at Microsoft.BitLockerManagement.ClientInstaller.CustomActions.PostInstallRegister(Session session)
    MSI (s) (10!F4) [08:36:37:638]: Closing MSIHANDLE (160) of type 790531 for thread 6900
    MSI (s) (10!F4) [08:36:37:638]: Creating MSIHANDLE (161) of type 790531 for thread 6900
    Exit: PostInstallRegister
    MSI (s) (10!F4) [08:36:37:653]: Closing MSIHANDLE (161) of type 790531 for thread 6900
    Exit: MBAMClientCAs.dll : PostInstall
    MSI (s) (10:EC) [08:36:37:653]: Closing MSIHANDLE (139) of type 790536 for thread 6612
    CustomAction MbamWmiProvidersInstallCustomAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (10:D4) [08:36:37:685]: User policy value 'DisableRollback' is 0
    MSI (s) (10:D4) [08:36:37:685]: Machine policy value 'DisableRollback' is 0
    Action ended 8:36:37: InstallFinalize. Return value 3.
    This appears to be an isolated problem, but I haven't been able to resolve this failed installation. Any help would be greatly appreciated.
    Thanks!

    Hi,
    Have you look at this knowledge base article:
    You receive an "error 1603:  A fatal error occurred during installation" error message when you try to install a Windows Installer package
    http://support2.microsoft.com/kb/834484
    Meanwhile, please seek for professional help from this forum:
    https://social.technet.microsoft.com/Forums/windows/en-US/home?forum=mdopmbam
    Karen Hu
    TechNet Community Support

  • ILM First Time Installation Fails with compilation errors

    I am using database version 10.1.0.4.2, and Apex version 3.0.0.00.20,
    These both are on the same machine.
    I login with sqlplus as sysdba and run
    @ilma_install apex sysaux none
    Following happens after running it:
    - It runs for a while creating different objects
    - then gives warning : view created with compilation error
    - then gives warning : view created with compilation error
    - then gives warning : view created with compilation error
    - then runs for a while
    - then gives error Package body created with compilation errors
    Errors for package body ILM_SYS_TOOLKIT
    Line/col Error
    1646/3 PLSQL: SQL Statement Ignored
    1647/22 PLS-009050 : Object ILM_Toolkit.ILM_Schedular_Steps is invalid
    Then the installation terminates.
    Please help.
    regards

    I am sorry to hear that you are still having difficulties with the installation. I set up a system that is as close to your configuration as I could replicate, with a 10gR1 database and Apex 3.0, and did not have any issue installing the ILM Assistant.
    It is possible that your install kit may have been corrupted during the modifications. I could build a new kit with the proper changes for your setup and send this directly to you if you would like.
    Alternatively, the problem may be with your Application Express installation. Try to verify that this was installed properly, and that the underlying schema account (FLOWS_030000) is unlocked and that you are using its proper password when installing ILM.
    Thanks,
    Adam

  • CS6 design standard installation fail with no error

    I am trying to install my student/staff version of CS6 on my computer (windows 7 prof.) and it keeps failing. The download of the .exe and .rar go fine.  I activate the .exe and it creates the extracted file.  During the installation (shortly after the windows config) the installation progress window just dissapears but the programs are no where on my computer (searched start menu, windows search, control panel, etc.).  There was never any error message given for why the installation didn't work.

    Hi,
    To solve this problem you must reinstall a clean system Win 7 and then do not forget to update the system with Service Pack 1 for Windows 7.
    good luck,
    TendanceLinks

  • VS 2013 Build tools installation fails with error "Signature or catalog could not be verified"

    VS 2013 ultimate - Build tools installation fails with error "Signature or catalog could not be verified" for MSBuild assemblies. Any idea what could be the problem?
    Thanks
    NM

    Hello,
    Do you mean you are trying to use this tool:
    https://www.microsoft.com/en-us/download/details.aspx?id=40760
    Can you navigate to your %temp% folder and filter by date to see the log of the Build tool?
    I want to know which assemblies failed to be verified.
    By the way, since MSBuild is embed in Visual Studio why you want to install this again? Do you have any error about this Build Tool when you install Visual Studio 2013 Ultimate?
    “Signature or catalog could not be verified” is always related to corrupt source
    , please double check you have a healthy network and then try the web installer again.
    Best regards,
    Barry
    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.

  • Office 2013 updates fail on computers with Access 2013 installed

    I have about 10 workstations with the combination of Windows 7 enterprise 32 bit, Access 2013 and Office 2007 installed.
    SCCM offers up both Office 2007 and Office 2013 updates to these machines, but the Office 2013 updates, fail to install.
    The same thing happens when I go to Microsoft updates and manually install the required Office 2013 updates.
    I read that one of the updates required Office 2013 sp1.
    But when I downloaded it, it won't install:  KB2817430 "The expected version of this product was not found on the system."
    This is the second month I've had the failures. I removed KB2878316 and KB2889927 from my deployments and packages to stop repeated install attempts.
    But this month I've got a new on failing, KB2899493.
    Is there a way around this problem?

    Thanks, I couldn't really find anything but it looks as though this could be just the way it is.
    from http://support.microsoft.com/kb/2784668
    When you start a version of Access on a computer that has multiple versions of Access installed, the Windows Installer may start, and
    a message that states that the Windows Installer is preparing to install Access may be displayed before Access starts.
    Every time that you start Access 2003, Access 2007, or Access 2010 after you use Access 2013, the Windows Installer repair operation registers
    that version of Access. Similarly, the Windows Installer repair operation registers Access 2010 every time that you start it after you use an earlier version of Access. This does not occur when you start Access 2002, nor does it occur when you start the same
    version of Access again. 
    Is this likely to also apply even when running App-V?

  • I ve updated my i pod touch to version 6.0.1. Installation got failed with some error msg, and now my i pod is not getting detedted in my system.Help me to fix it up.

    i ve updated my i pod touch to version 6.0.1. Installation got failed with some error msg, and now my i pod is not getting detedted in my system.Help me to fix it up.

    What's the error mesage?

Maybe you are looking for