none
dism add winemb-prnting.cab failure. RRS feed

  • Question

  • Hi, I use wes 7 x64. the system is new installed , include the dependency Core File System, Graphics Platform, Microsoft Standard Printer (NTPrint) Driver and Security Base.  when I attempt to run "dism /online /add-package /packagepath:<path to winemb-printing.cab>", the dism is success but it updates failure and rolls back when the computer restart. It seems the same problem as http://social.msdn.microsoft.com/forums/windowsazure/it-it/4969489a-70ed-4d67-9c5a-738f4a715c8c/wes7-dism-online-addpackage but no use to me. 

    I have checked the dism log and cbs log. the problem happened in cbs log:

    2013-10-19 19:40:41, Info                  CSI    0000003a Begin executing advanced installer phase 38 (0x00000026) index 80 (0x0000000000000050) (sequence 119)
        Old component: [l:0]""
        New component: [ml:332{166},l:330{165}]"Microsoft-Windows-Printing-LPRPortMonitor, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
        Install mode: install
        Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
        Installer name: [15]"Generic Command"
    2013-10-19 19:40:41, Info                  CSI    0000003b Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:20c0c709c0ccce01200000006803f403} pathid: {l:16 b:20c0c709c0ccce01210000006803f403} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-p..ting-lprportmonitor_31bf3856ad364e35_6.1.7601.17514_none_1229a6f0546e2346" pid: 368 starttime: 130266563273344000 (0x01ceccbfc604c400)
    2013-10-19 19:40:41, Info                  CSI    0000003c Calling generic command executable (sequence 1): [32]"C:\Windows\System32\rundll32.exe"
        CmdLine: [87]""C:\Windows\System32\rundll32.exe" C:\Windows\System32\SetupLpr.dll,SetupLprMon Install"
    2013-10-19 19:40:41, Info                  CSI    0000003d Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:8021ca09c0ccce01220000006803f403} pathid: {l:16 b:8021ca09c0ccce01230000006803f403} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_6.1.7600.16385_none_3868158f24725705" pid: 368 starttime: 130266563273344000 (0x01ceccbfc604c400)
    2013-10-19 19:40:41, Info                  CSI    0000003e Creating NT transaction (seq 1), objectname [6]"(null)"
    2013-10-19 19:40:41, Info                  CSI    0000003f Created NT transaction (seq 1) result 0x00000000, handle @0x324
    2013-10-19 19:40:41, Info                  CSI    00000040@2013/10/19:11:40:41.082 CSI perf trace:
    CSIPERF:TXCOMMIT;35663
    2013-10-19 19:40:41, Error                 CSI    00000041 (F) Done with generic command 1; CreateProcess returned 0, CPAW returned S_OK
        Process exit code 8 resulted in success? FALSE
        Process output: [l:0 ][gle=0x80004005]
    2013-10-19 19:40:41, Info                  CSI    00000042@2013/10/19:11:40:41.082 CSI Advanced installer perf trace:
    CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-Printing-LPRPortMonitor, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;64594
    2013-10-19 19:40:41, Error      [0x018007] CSI    00000043 (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
    2013-10-19 19:40:41, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 53.
    2013-10-19 19:40:41, Info                  CSI    00000044 End executing advanced installer (sequence 119)
        Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED) 
    
    2013-10-19 19:40:41, Info                  CSI    00000045 Begin executing advanced installer phase 38 (0x00000026) index 81 (0x0000000000000051) (sequence 120)
        Old component: [l:0]""
        New component: [ml:332{166},l:330{165}]"Microsoft-Windows-Printing-LPRPortMonitor, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
        Install mode: install
        Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}
        Installer name: [6]"Events"
    2013-10-19 19:40:41, Info                  CSI    00000046@2013/10/19:11:40:41.472 CSI Advanced installer perf trace:
    CSIPERF:AIDONE;{3bb9fd2b-351e-4b9c-b1fc-ed0758805998};Microsoft-Windows-Printing-LPRPortMonitor, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;31030
    2013-10-19 19:40:41, Info                  CSI    00000047 End executing advanced installer (sequence 120)
        Completion status: S_OK 
    
    2013-10-19 19:40:41, Info                  CSI    00000048 Begin executing advanced installer phase 38 (0x00000026) index 82 (0x0000000000000052) (sequence 121)
        Old component: [l:0]""
        New component: [ml:334{167},l:332{166}]"Microsoft-Windows-Printing-LPDPrintService, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
        Install mode: install
        Installer ID: {285fda60-31f4-417c-9407-2f7655a965fc}
        Installer name: [10]"Service SD"
    2013-10-19 19:40:41, Info                  CSI    00000049 Performing 1 operations; 1 are not lock/unlock and follow:
      LockComponentPath (10): flags: 0 comp: {l:16 b:00c80c0ac0ccce01250000006803f403} pathid: {l:16 b:00c80c0ac0ccce01260000006803f403} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-p..ing-lpdprintservice_31bf3856ad364e35_6.1.7600.16385_none_e792d2b08af68cc9" pid: 368 starttime: 130266563273344000 (0x01ceccbfc604c400)
    2013-10-19 19:40:41, Info                  CSI    0000004a@2013/10/19:11:40:41.472 CSI Advanced installer perf trace:
    CSIPERF:AIDONE;{285fda60-31f4-417c-9407-2f7655a965fc};Microsoft-Windows-Printing-LPDPrintService, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;7245
    2013-10-19 19:40:41, Info                  CSI    0000004b End executing advanced installer (sequence 121)
        Completion status: S_OK 
    
    2013-10-19 19:40:41, Info                  CSI    0000004c Begin executing advanced installer phase 38 (0x00000026) index 84 (0x0000000000000054) (sequence 123)
        Old component: [l:0]""
        New component: [ml:334{167},l:332{166}]"Microsoft-Windows-Printing-LPDPrintService, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
        Install mode: install
        Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}
        Installer name: [6]"Events"
    2013-10-19 19:40:41, Info                  CSI    0000004d@2013/10/19:11:40:41.503 CSI Advanced installer perf trace:
    CSIPERF:AIDONE;{3bb9fd2b-351e-4b9c-b1fc-ed0758805998};Microsoft-Windows-Printing-LPDPrintService, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;32207
    2013-10-19 19:40:41, Info                  CSI    0000004e End executing advanced installer (sequence 123)
        Completion status: S_OK 

    The SetupLpr.dll is apart of winemb-printing, when I move it into system32\ and run "C:\Windows\System32\rundll32.exe C:\Windows\System32\SetupLpr.dll,SetupLprMon Install" in the command line as administrator. it was nothing , include error return to me.

    Is anyone can help? 


    • Edited by ozzzp Saturday, October 19, 2013 3:36 PM
    Saturday, October 19, 2013 11:57 AM

Answers

  • All packages are language neutral, thus the language pack has to be re-installed for the newer package to work. My book has an example of this using Windows Accessories. It is better to create a configuration set to apply multiple packages at the same time - covered in my book and in online help.


    www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

    • Marked as answer by ozzzp Friday, October 25, 2013 11:21 AM
    Sunday, October 20, 2013 4:19 PM
    Moderator

All replies

  • Do you also re-install the language component? Did you include any dependency for the package?

    Why not rebuild with the package included?


    www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

    Saturday, October 19, 2013 4:24 PM
    Moderator
  • Ye, I have checked the dependency which include Core File System, Graphics Platform, Microsoft Standard Printer (NTPrint) Driver and Security Base, and all of them have been installed.

     There is only one language pack(en-us) in my system, and I didn't reinstall it while running dism. Is it possible that it's the reason why failure?  but what's the matter with language pack and winemb-printing?

    I thought it's not worth to solve this problem by reinstalling the system. if it can't be solved finally, I prefer to put up with the problem. The system is perfect, just this problem.  

    • Edited by ozzzp Sunday, October 20, 2013 8:49 AM
    Sunday, October 20, 2013 8:45 AM
  • All packages are language neutral, thus the language pack has to be re-installed for the newer package to work. My book has an example of this using Windows Accessories. It is better to create a configuration set to apply multiple packages at the same time - covered in my book and in online help.


    www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

    • Marked as answer by ozzzp Friday, October 25, 2013 11:21 AM
    Sunday, October 20, 2013 4:19 PM
    Moderator
  • Thanks a lot, I've done by reinstalling the system. It seems that the problem can't be solved by just using dism /online. 
    • Edited by ozzzp Friday, October 25, 2013 11:21 AM
    Friday, October 25, 2013 11:21 AM