Server 2009 R2 Stuck Installing Updates and Unexpected Error Refreshing Server Manager

I have a 2008 R2 server that is running but has issues when restarting or trying to install IE 10. I ran the System Readiness Tool and it fixed a number of issues but there are 5 remaining errors in the Component store that will not repair automatically.
They are:
Checking Component Store
(f) CSI Missing Identity 0x00000000 appid win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_eb5d85075a07f78b
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_3ef665796f74e084
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_e2d7c9f5b7176f4e
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_13026217d8d91020
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_6f20fd9b91368156
I tried to run a SFC but if failed because there is a repair operation that needs a reboot. When rebooting, the server tries to install a number of updates but the update fail and the server backs them out and then comes up. It goes through this
loop every restart. There is a pending.xml file that has much in it and I will copy at the end of this post.
I moved the pending.xml out of the winsxs folder and tried to run the SFC again and now it fails with: "Windows Resource Protection could not perform the requested operation".
Checking windows updates shows that the IE 10 upgrade for Server 2008 R2 failed a number of times. I tried to manually install it and it fails. I was going to go to the server manager and see if I could disable IE and then re-enable it (this
has worked on W7 pcs in the past) but the Server manager aborts with "Unexpected Error refreshing Server Manager: Catastrophic failure (Exception from HResult: 0x8000FFFF (E_UNEXPECTED)).
The details of the pending.xml is 32MB but here is an initial snipet:
<?xml version='1.0' encoding='utf-8'?>
<PendingTransaction Version="3.1" WcpVersion="6.1.7601.17592 (win7sp1_gdr.110408-1631)" Identifier="9afdc4c419d7ce01476300001c0cb817">
    <Transactions>
        <Transaction TransactionId="TI4.30332431_1303162608:4/Package_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1">
            <Install Application="mdmnis2u.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-2_neutral_GDR" RefExtra="16"/>
            <Install Application="mdmnis1u.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-4_neutral_GDR" RefExtra="16"/>
            <Install Application="mdmgen.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-6_neutral_GDR" RefExtra="16"/>
            <Install Application="mdmcpq.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-8_neutral_GDR" RefExtra="2"/>
        </Transaction>
        <Transaction TransactionId="TI4.30332431_1357902608:4/Package_for_KB2853587~31bf3856ad364e35~amd64~~6.1.1.2">
            <Install Application="e30c96e70bb8831ddd580ec5531db3e7, Culture=neutral, Version=6.1.7601.18219, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2853587~31bf3856ad364e35~amd64~~6.1.1.2.2853587-4_neutral_GDR" RefExtra="2"/>
        </Transaction>
        <Transaction TransactionId="TI4.30332431_1359952608:4/Package_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0">
            <Install Application="838a6900433638745b282fd8a4ba817a, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-3_neutral_GDR" RefExtra="2"/>
            <Install Application="50fab9749cbc66134f38ae1dc56c98dd, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-6_neutral_GDR" RefExtra="2"/>
            <Install Application="ff3f54cca48812ca511cd304f4431436, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-8_neutral_GDR" RefExtra="2"/>
            <Install Application="6ea506ab96b6a14822c1c2ab6846fc8f, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=b77a5c561934e089, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-10_neutral_GDR" RefExtra="2"/>
            <Install Application="87e192610d63f582a53ceb1723d390ab, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=b77a5c561934e089, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-12_neutral_GDR" RefExtra="2"/>
            <Install Application="4a1985f0141fae9c7cae493197a6b878, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=b77a5c561934e089, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-14_neutral_GDR" RefExtra="2"/>
            <Install Application="016dd2fdac3816d0990ef71a86b49ca5, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-17_neutral_GDR" RefExtra="2"/>
            <Install Application="a37f333ec2c8fbbf96c5ecfffad21444, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-20_neutral_GDR" RefExtra="2"/>
        </Transaction>
        <Transaction TransactionId="TI4.30332431_1370242608:4/Package_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1">
            <Install Application="8e09fc8e70ef526fe271bb58df1b359b, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_38_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-149_neutral_GDR" RefExtra="17"/>
            <Install Application="5e964ab696366f5925e35f48bce2e817, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_39_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-152_neutral_GDR" RefExtra="16"/>
            <Install Application="e7ec7425bc5783cd10ed371bbb5001dd, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_39_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-155_neutral_GDR" RefExtra="16"/>
            <Install Application="c4861d635189a7cabac3e380ad0cc01f, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_59_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-272_neutral_GDR" RefExtra="17"/>
            <Install Application="36b758890f2cc03ad4c1f7b69ba4b785, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_75_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-364_neutral_GDR" RefExtra="3"/>
            <Install Application="2e15e374d2e2b02519eb2bc107d92452, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_75_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-367_neutral_GDR" RefExtra="3"/>
            <Install Application="79efe25214ed979d4739ffca9cef136f, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_76_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-370_neutral_GDR" RefExtra="16"/>
            <Install Application="b8cda4a0fbf72009baf7a4d31ebb7e3f, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_76_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-373_neutral_GDR" RefExtra="16"/>
        </Transaction>
        <Transaction TransactionId="TI4.30332431_1428402608:4/Package_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2">
            <Install Application="65d33ad308914579e80ef4e979752b4e, Culture=neutral, Version=6.1.7601.18177, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2.2847311-5_neutral_GDR" RefExtra="2"/>
            <Install Application="449dd8313096e8ea0b2798f052e79452, Culture=neutral, Version=6.1.7601.18177, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2.2847311-8_neutral_GDR" RefExtra="2"/>
        </Transaction>
        <Transaction TransactionId="TI4.30332431_1441832608:4/Package_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2">
            <Install Application="0f6c352b3b8ab87d68b593ef7f08823f, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-2_neutral_GDR" RefExtra="3"/>
            <Install Application="8a9b3736ee0dfd9a2d51fe6ecb8262b9, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-4_neutral_GDR" RefExtra="3"/>
            <Install Application="f03bb92dd4f91f6ca1fea9aa5f3d01f6, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-6_neutral_GDR" RefExtra="3"/>
            <Install Application="d985d750c9b4e2d9ac9a71db0b5caeca, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-8_neutral_GDR" RefExtra="3"/>
            <Install Application="4564761e21602085599bee5eebe25ff9, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-10_neutral_GDR" RefExtra="3"/>
            <Install Application="3b2d92a9b35c82a0178c4a63bc04bfd0, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-12_neutral_GDR" RefExtra="3"/>
            <Install Application="c41ad6a9882c5db61704dffad48784e4, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-14_neutral_GDR" RefExtra="3"/>
            <Install Application="b9b638b3db7627f18507dfafb2c78403, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-16_neutral_GDR" RefExtra="2"/>
            <Install Application="54ae1ba9684b6049e8d67dcdc4f58954, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-18_neutral_GDR" RefExtra="2"/>
            <Install Application="4f41d944af2db3f0120fc02c77158999, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-20_neutral_GDR" RefExtra="2"/>
        </Transaction>
        <Transaction TransactionId="TI4.30332431_1462782608:4/Package_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0">
            <Install Application="588b833b8de1c71547d6a889dbb75439, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-3_neutral_GDR" RefExtra="2"/>
            <Install Application="0c2bb2bb69a4efa72cf82d30ab59e369, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-6_neutral_GDR" RefExtra="2"/>
            <Install Application="206b27624daebef1bb13dfa8dd6da833, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-8_neutral_GDR" RefExtra="16"/>
            <Install Application="bf6e4fabe941322fa7c42cb2ce5ab035, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-11_neutral_GDR" RefExtra="2"/>
            <Install Application="772cf3ed88bc1b0fc9931ec07075f86d, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-13_neutral_GDR" RefExtra="16"/>
            <Install Application="119d2a1cf82292079aacac2e30f2c14c, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-16_neutral_GDR" RefExtra="2"/>
            <Install Application="8c3eb9ca2caa78fb873d66d3c41a68c5, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-19_neutral_GDR" RefExtra="2"/>
            <Install Application="303a1ce634b3a16c69749f5139be8471, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-22_neutral_GDR" RefExtra="2"/>
            <Install Application="2be7629126ed2b6468203097350f0dfe, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-26_neutral_GDR" RefExtra="16"/>
        </Transaction>
        <Transaction TransactionId="TI4.30332431_1488382608:4/Package_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1">
            <Install Application="6f20d92a7648d71eb43ee35ded059bb1, Culture=neutral, Version=6.1.7601.18254, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-9_neutral_GDR" RefExtra="2"/>
            <Install Application="f0ed83bda0697abd97fd471015aed5c2, Culture=neutral, Version=6.1.7601.17939, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-12_neutral_GDR" RefExtra="16"/>
            <Install Application="febe4281e112cc22eaba92dbd2b4d55c, Culture=neutral, Version=6.1.7601.18254, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-15_neutral_GDR" RefExtra="2"/>
            <Install Application="2f9f4d4b3253a56c28a30f0cb9598076, Culture=neutral, Version=6.1.7601.18264, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-17_neutral_GDR" RefExtra="2"/>
            <Install Application="6cccd8f687e69c579827fb5568f5bd2a, Culture=neutral, Version=6.1.7601.17939, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-20_neutral_GDR" RefExtra="3"/>
        </Transaction>
        <Transaction TransactionId="TI4.30332431_1507982608:4/Package_for_KB2861191~31bf3856ad364e35~amd64~~6.1.1.0">
            <Install Application="98968d78510963c63353649885f3ecf0, Culture=neutral, Version=6.1.7601.18219, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2861191~31bf3856ad364e35~amd64~~6.1.1.0.2861191-2_neutral_GDR" RefExtra="17"/>
        </Transaction>
        <Transaction TransactionId="TI4.30332431_1608052608:4/Package_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1">
            <Install Application="4eac8b2780d12dcb68dc93ac25ddea50, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-9_neutral_GDR" RefExtra="17"/>
            <Install Application="f3f2fab1a47c8f10dba321b4564b5da2, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-12_neutral_GDR" RefExtra="17"/>
            <Install Application="5683dbcbaaf84c80d448b8e4ff5c4102, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-15_neutral_GDR" RefExtra="2"/>
            <Install Application="6a6f4875757b66f16c6a4827a5d031c4, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-18_neutral_GDR" RefExtra="16"/>
            <Install Application="ed4721225b1075dc927cca1f55a4feb7, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_4_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-21_neutral_GDR" RefExtra="2"/>
            <Install Application="8be73aa5d92530e63a3fa2360881e888, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-24_neutral_GDR" RefExtra="17"/>
            <Install Application="5102c4e5b602cbe09557ed48ea490121, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-27_neutral_GDR" RefExtra="3"/>
            <Install Application="7db7cf609e29d6d392051d1175075ae5, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-30_neutral_GDR" RefExtra="2"/>
        </Transaction>
        <Transaction TransactionId="TI4.30332431_2531772608:4/Package_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0">
            <Install Application="8a96329682d824abc0f8f934fb341ede, Culture=neutral, Version=7.1.7601.18142, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0.2834140-6_neutral_GDR" RefExtra=""/>
        </Transaction>
andy

Here is the contents of the CheckSur.log file:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-02-08 22:46
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Missing Identity 0x00000000 appid win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_eb5d85075a07f78b
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_3ef665796f74e084
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_e2d7c9f5b7176f4e
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_13026217d8d91020
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_6f20fd9b91368156
Summary:
Seconds executed: 825
Found 5 errors
CSI Missing Identity Total count: 1
CSI Missing Winning Component Key Total count: 4
andy

Similar Messages

Unexpected Error refreshing Server Manager:No signature was present in the subject. (Exception from HRESULT:0x800B0100)

Ran the update readiness tool and the summary returned below. This is a DC so need to repair without rebuild if possible
Windows 2008 Server x64
Summary:
Seconds executed: 1731
Found 1705 errors
Fixed 1702 errors
CSI F Mark Missing Total count: 2
Fixed: CSI F Mark Missing. Total count: 2
CBS MUM Missing Total count: 3
CSI SP File Not Yet Pre-Installed Total count: 2
Fixed: CSI SP File Not Yet Pre-Installed. Total count: 2
CSI Store Directory Missing Total count: 1698
Fixed: CSI Store Directory Missing. Total count: 1698
Unavailable repair files:
servicing\packages\Package_for_KB980182_ie8_0~31bf3856ad364e35~amd64~~8.0.1.1.mum
servicing\packages\Package_for_KB980182_ie8~31bf3856ad364e35~amd64~~8.0.1.1.mum
servicing\packages\Package_for_KB980182~31bf3856ad364e35~amd64~~8.0.1.1.mum
servicing\packages\Package_for_KB980182_ie8_0~31bf3856ad364e35~amd64~~8.0.1.1.cat
servicing\packages\Package_for_KB980182_ie8~31bf3856ad364e35~amd64~~8.0.1.1.cat
servicing\packages\Package_for_KB980182~31bf3856ad364e35~amd64~~8.0.1.1.cat

Hi Mickg_energ.co.uk,
I have extracted those unavailable repair files from the update package KB980182 and uploaded them to the workspace.
You can download those files from the following link. (Please choose "Receive Files from Microsoft")
Workspace URL:
https://sftasia.one.microsoft.com/choosetransfer.aspx?key=01ac3ca9-991d-418d-a501-f8ce68952b42
Password:
i96fH{2@Ka5vOH
Please copy those files and replace them under
%Windir%\servicing\Packages.
For more information about how to fix such servicing corruption problems, please refer to the article below.
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779%28WS.10%29.aspx
Regards,
Karen Ji
This posting is provided "AS IS" with no warranties, and confers no rights.

Stuck between installing updates and off screen!?

MacBook ran out of battery, and turned off, I then went to charge it and now can't install updates and goes to black screen with this sign on it

The message is ...
The iPad "iPad" could not be updated. An unknown error occurred (3004)
There is a More Information button which takes you to an Apple help page but that doesn't help
Error 3194, Error 17, or "This device isn't eligible for the requested build" - Apple Support
Thanks

Keep getting error: None of the selected updates could be installed. An unexpected error occurred. Please help!

Hey I am kind of new to this forum situation, but I keep trying to install software updates on my macbook for the last two weeks and the aforementioned error (None of the selected updates could be installed. An unexpected error occurred.) keeps resulting. I would download them straight from online, but I don't know which ones to download. What should I do?

Bring up Software Update, and when it says it has updated software to download, click the button on the left bottom of the window, might say something like show details. That will open the box to show you exactly what would download. You can then visit the Apple download site at http://support.apple.com/downloads/

"None of the selected updates could be installed. An unexpected error occurred."

Whenever I tried to update my softwares, It said: "None of the selected updates could be installed. An unexpected error occurred." I don't know how to update all the softwares. I cannot connect to my printers. And I think it's becasue of the software updates. Anyone can help me, please? Plus, how do I know what operating system I have?

Then your friend really needs to clean it up, and give you only software which he is licensed to give. He should read my FAQ*:
http://www.macmaps.com/selling.html
Without doing so, he probably has left have some gremlins of his own that cause problems. Cleaning up a Mac for resale really means cleaning it up.

Installing Update Rollup 7 for Exchange Server 2010 SP3

Hi,
I have 4 Exchange servers. Two CAS and two DAG. I am currently on Rollup 2 for Exchange Server 3010 SP 3. Can I install Update Rollup 7 for Exchange Server 2010 SP3 or do I need to install a previous one first?
Thannks!
Wave~Chaser

Hi,
When I try to install Exchange 2010 SP3 roll up 7, am getting the below error:
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may
be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
and please find below event log:
Product: Microsoft Exchange Server - Update '{A93DA06F-A5B8-4DF8-8B3F-B285E014C659}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions
on turning on logging support.
Can you please help me with this error.
Thanks

After i installed updates for my mac mini server, the web services for the server app wont start, it gives an error massage: "Error Reading Settings"

After i installed updates for my mac mini server, the web services for the server app wont start, it gives an error massage: "Error Reading Settings"
The system logs reads:
Mar 29 22:06:25 server servermgrd[82]: servermgr_web: Error Domain=XSServerFoundationErrorDomain Code=4 "Failed to read settings: Exception:
          undefined method `downcase' for nil:NilClass
          ." UserInfo=0x7fc547901080 {NSLocalizedDescription=Failed to read settings: Exception:
          undefined method `downcase' for nil:NilClass

To check the local network for some of the common configuration problems, launch Terminal.app and issue the following diagnostic command:
sudo changeip -checkhostname
That'll report some local configuration information and then either no errors detected and no changes required, or it'll point to whatever configuration errors or issues it might detect. That doesn't catch everything, but it catches the common errors.
FWIW, 192.168.0.0/24 and 192.168.1.0/24 are poor choices for the local network, as VPNs are based on IP routing and IP routing gets tangled when the same subnet is used on both ends of the VPN. 192.168.0.0/24 and 192.168.1.0/24 are near ubiquitous in home networks and coffee shops.

Windows Update in Endless Loop of 'Installing updates" and "Undoing changes" on New Windows 8.1 Pro Install

I am setting new Windows 8.1 Pro computers, and am installing Windows 8.1 Pro to bare drives. Everything goes fine until Windows Update starts installing updates, and then the computer goes for hours installing updates, and then "We
could not complete the updates Undoing changes". It's an endless loop. It seems to be the same 38 updates. This is a recent phenomenon. I have not run into this until the last week or two on several new computer installs.
Again these are brand new installs, so something is clearly wrong with the Windows updates.
If anyone can please tell me how to avoid this, it would be much appreciated.
Michael

Hi Michael,
" This is a recent phenomenon"
Have you made any modifications to the machines ?
To resolve this issue ,running the built-in troubleshoot tool is a very good beginning .It will automatically diagnostic the windows update components and check the configurations for us .
Control Panel\All Control Panel Items\Troubleshooting\Fix problems with Windows Update
If there are antivirus software installed in these machines, please turn off them temporarily to have a check.
The command line included in the link as S.Sengupta posted is very useful and convenient to repair the windows corrupted files .We can have a try .
"sfc /scannow" ,"DISM.EXE /online /cleanup-image /restorehealth "
We also can check the windowsupdate.log for more information to troubleshoot this issue .
Run "windowsupdate.log"
If you have trouble in analyzing the log ,please upload them to the OneDrive and paste the link here .
Best regards

The document could not be saved. The server said: "The operation failed because an unexpected error occurred. (Result code 0×80020005)" Please ensure you have completed all required properties with the correct information and try again.

I am having problems saving documents back to SharePoint when any of the document properties (metadata columns) are set to be "managed metadata". The check-in/save fails with error:
The document could not be saved. The server said:
“The operation failed because an unexpected error occurred. (Result code 0×80020005)”
Please ensure you have completed all required properties with the correct information and try again.
I have seen similar threads that suggest this is a known issue with this version of Acrobat but I would like conformation from Adobe that this is a known issue and whether it is fixed in a newer version?
Adobe Acrobat version 10.1.13
SharePoint 2010

Hi quodd,,
We are sorry for the issue being faced by you. I need some information from you so that I take further steps:
1. Which Adobe product are you using Acrobat or Adobe reader- what is the complete version?
2. How are you opening and saving the PDF, the exact workflow?
Are you doing it from within Adobe Reader/Acrobat application or opening it from browser, doing changes and saving it using browser itself.
3. Can you try to save a PDF to library with Custom template and managed metadata columns using browser directly.
4. Please verify that columns name do not contain spaces or some other special characters.
Can you try to save PDF to library with Custom template and just a single managed metadata column with a simple name
Thanks,
Nikhil Gupta

Windows 8.1 Pro Workstations - Not Getting "Install Updates and Shut Down" notification for new updates

We've got a small handful of Windows 8.1 Pro workstations on our domain (SBS 2008).
The workstations show up in the WSUS Console list along with the details of how many updates need to be installed.
On the Windows 8.1 Pro workstations, at the logon screen they display "Important Updates Are Available. Go to PC Settings to install them". If we go to PC Settings or Windows Updates via Control Panel the updates show as awaiting installation.
However, we can't rely on users to go into PC Settings or Control Panel to install Windows Updates. We need them to be installed as per Windows 7 and Windows XP - whereby when the user shuts down their workstations it displays the message "Install Updates
and Shutdown".
Currently the Windows 8.1 Pro workstations do not show this - if you choose to shut down there are no update installation messages and the workstations simply shut down.
Has anyone else encountered this? What needs to be done?
Thanks in advance.
I don't work for Microsoft - I just use their products.

It does sound weird yes.
Id like to try and mirror your setup in my lab.
What settings do you have in your WSUS GPO?
Have you seen this, in the 'Configure Automatic Updates' setting?
On Windows 8 and later, you can set updates to install during automatic maintenance instead of a specific schedule. Automatic maintenance will install updates when the computer is not in use, and avoid doing so when the computer
is running on battery power. If automatic maintenance is unable to install updates for 2 days, Windows Update will install updates right away. Users will then be notified about an upcoming restart, and that restart will only take place if there is no potential
for accidental data loss.
Automatic maintenance can be further configured by using Group Policy settings here: Computer Configuration->Administrative Templates->Windows Components->Maintenance Scheduler
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Verify that SQL Server Reporting Services is installed properly and that it is running.

I am trying to install DPM 2010 on Windows 2008 R2. Running through installation and the server that I'm installing DPM to will also host the SQL instance and Reporting instance. Pretty much choosing all the defaults.
Installation gets to reporting portion and fails. It says that I need to verify that Reporting Services is running.   The exact error is:
Data Protection Manager installation has failed. To return the server to its original state, you must uninstall Data Protection Manager by using Add or Remove Programs in Control Panel. This will remove all files and components copied during installation.
For details, click the Error tab.
DPM Setup has not configured Reporting Services to use Secure Sockets Layer. For more information on how to configure the Report Server for Secure Sockets Layer (SSL) connections, see Configuring Report Server for Secure Sockets Layer (http://go.microsoft.com/fwlink/?LinkId=178289)
Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812
It is running and working, I can go to the URL and see Reports installed.   It grabbed a server certificate which is valid and binds that to 443. I have tried this as well with the certificate removed.
Here is the relative portion of the DPM 2010 log:
[6/25/2010 10:30:01 AM] * Exception : => System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException: Exception of
type 'Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException' was thrown.
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException.UnableToConfigureAccount(ErrorCode errorCode)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateUserAccount(String server, String password, Boolean create)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.SetReportingPassword(String password, String server, String instanceName, String dbConnectionString)
*** Mojito error was: PasswordTooShort; 0; None
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
[6/25/2010 10:30:01 AM] * Exception : => Report configuration failed.Verify that SQL Server Reporting Services is installed properly and that it is running.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception --->
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.ReportDeploymentException: exception ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException:
Exception of type 'Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException' was thrown.
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException.UnableToConfigureAccount(ErrorCode errorCode)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateUserAccount(String server, String password, Boolean create)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.SetReportingPassword(String password, String server, String instanceName, String dbConnectionString)
*** Mojito error was: PasswordTooShort; 0; None
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
   --- End of inner exception stack trace ---
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.ConfigureReporting(String reportserverConfigFilePath, Boolean existingDB, Boolean isOemSetup, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
*** Mojito error was: ReportDeploymentFailed; 0; None
   --- End of inner exception stack trace ---
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.ConfigureReporting(String reportserverConfigFilePath, Boolean existingDB, Boolean isOemSetup, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.ConfigureReporting(Boolean isRemoteDb)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Mojito error was: ReportDeploymentFailed; 0; None
[6/25/2010 10:30:07 AM] *** Error : Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812
[6/25/2010 10:30:07 AM] Information : Data Protection Manager installation has failed. To return the server to its original state, you must uninstall Data Protection Manager by using Add or Remove Programs in Control Panel. This will remove all files and components
copied during installation.
For details, click the Error tab.
DPM Setup has not configured Reporting Services to use Secure Sockets Layer. For more information on how to configure the Report Server for Secure Sockets Layer (SSL) connections, see Configuring Report Server for Secure Sockets Layer (http://go.microsoft.com/fwlink/?LinkId=178289)

Hello,
The real problem is the error UnableToConfigureAccount and *** Mojito error was: PasswordTooShort; 0; None
The reason is due to the new password complexity on Windows 2008 which states the following:
Password must meet complexity requirements
This security setting determines whether passwords must meet complexity requirements.
If this policy is enabled, passwords must meet the following minimum requirements:
Not contain the user's account name or parts of the user's full name that exceed two consecutive characters
Be at least six characters in length Contain characters from three of the following four categories:
English uppercase characters (A through Z)
English lowercase characters (a through z)
Base 10 digits (0 through 9)
Non-alphabetic characters (for example, !, $, #, %)
Complexity requirements are enforced when passwords are changed or created.
Default:
Enabled on domain controllers.
Disabled on stand-alone servers.
Note: By default, member computers follow the configuration of their domain controllers.
Please use a more secure password adhering to the above criteria and DPM should install fine.
Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

How to Install XI and EP on Single server

Hi,
How to install XI and EP on same server. I tried to install XI then EP . After EP installed then iam not able to access XI j2ee engine . I think some where port conflicts . I gave system number for XI : 00 and EP : 02
Can any one help for this. Where did i made mistake.
Thanks
Kristene

Hi Kristene,
I have installed XI and EP on the same server (for test purposes) without any problems, so it should be possible. I installed them in a different order (first EP then XI), but I don't think that matters much.
The only real difference is that I kept the system number the same.
What do you mean exactly with not being able to access the XI j2ee engine? How did you try to access it?
Regards,
Martin

Trying to update iPhone 5.1.1 and it says unable to install update. An error occurred installing iOS 5.1.1

Trying to update iPhone 5.1.1 and it says unable to install update. An error occurred installing iOS 5.1.1

If you did the update through iTunes, try going into the Settings App on your iPhone and doing the Software Update in there. The same thing happened to me, and the wireless update worked.

'Install Updates and Shutdown' option not appearing for Windows 8.1 users

Windows 8.1 users are reporting, and I have verified, that they are not being prompted to install Windows updates while shutting down, even though the updates are downloaded. Here are the relevant Windows Update gpo's from a sample Group Policy Result
for a typical user on one of our Windows 8.1 workstations:
(Note: The "Specify intranet Microsoft update service location" is the last policy in the updates section, and the value specified there is not relevant to this question.)
These same settings when applied to Windows XP workstations used to prompt users to install updates at shutdown. That is, the default shutdown option was "Install Updates and Shutdown". That was a great workflow because all client workstations
were shut down every night and the user didn't have to worry about updates installing while they were using the workstation. All client workstations are now running Windows 8.1 Pro and the only way updates are getting installed is by manually pulling
up the Windows Update dialog and initiating updates from there. That is even worse than automatic updates that install during business hours.
I do notice that
a notification that updates are available appears in the login screen, but one can not take action upon it from there, and most users don't know how to find the update screen once they sign in; and
once updating is begun, then the Install Updates and Shutdown option becomes a default - but by that point its rather cosmetic: that is the only option (to configure the partially installed updates during shutdown) and there is nothing
that could be done to NOT do that at that point.
Is anyone having similar issues? As far as I can tell right now, there is no ability to actually switch the user's default option to
Install Updates and Shutdown in the same way as in previous Windows editions even though the GPO is identical.

Hi,
>>Is anyone having similar issues? As far as I can tell right now, there is no ability to actually switch the user's default option to
Install Updates and Shutdown in the same way as in previous Windows editions even though the GPO is identical.
Regarding this point, the following blog may provide a good explanation.
Minimizing restarts after automatic updating in Windows Update
http://blogs.msdn.com/b/b8/archive/2011/11/14/minimizing-restarts-after-automatic-updating-in-windows-update.aspx
Best regards,
Frank Shen

Is it OK to install BW and BO in same server

Is it OK to install BW and BO in same server ?
BW 3.5
BO XI 3.1 SP2 FP2.9
Is there any known issue in this approach ?
What is the recommended system requirement for it ?

I would do it only if it is on Unix and the H/W is powerful enough.
Keep in mind that when you shutdown/reboot you are taking offline 2 systems at once.
In 64bit Windows there are conflicting versions of the required rfc libraries (32bit and 64bit) which are not easy to resolve and will affect the MDX parser.
Regards,
Stratos

Server 2009 R2 Stuck Installing Updates and Unexpected Error Refreshing Server Manager

Similar Messages

Maybe you are looking for