Another error for server manager.Event ID: 1601

Log Name:      Microsoft-Windows-ServerManager/Operational
Source:        Microsoft-Windows-ServerManager
Date:          06/07/2009 2:29:30 PM
Event ID:      1601
Task Category: None
Level:         Error
Keywords:     
User:          ARTONA\Administrator
Computer:      sanhost02
Description:
Could not discover the state of the system. An unexpected exception was found:
System.Runtime.InteropServices.COMException (0x800B0100): No signature was present in the subject. (Exception from HRESULT: 0x800B0100)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)
   at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()
   at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
   at Microsoft.Windows.ServerManager.Common.Provider.Initialize(DocumentCollection documents)
   at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

Hello duke,
To troubleshoot the issue, please first run the following command to scan integrity of all files on that problematic server
SFC /SCANNOW
Please run CHKDSK on the problematic server.
Then please try running the System Update Readiness Tool
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows Server 2008 R2 Release Candidate, and for Windows 7 Release Candidate
http://support.microsoft.com/default.aspx?scid=kb;EN-US;947821
Server Manager is servicing operations similar to what Windows Updates is using so the System Update Readiness Tool can help with this error sometimes.
Please collect the following log files from the System Update Readiness Tool:
%SYSTEMROOT%\Logs\CBS\CheckSUR.log
%SYSTEMROOT%\Logs\CBS\CheckSUR.persist.log
Please also collect a listing of the %windir%\Servicing\Packages by running the following command.
Dir %windir%\Servicing\Packages > CBSlist.txt
Meanwhile, please collect all the above logs (CheckSUR.log, CheckSUR.persist.log and CBSlist.txt) and the CBS.log, and send to [email protected] for further research.
Please note: CBS.log is in the location of %systemroot%\Logs\CBS\CBS.log
I appreciated your time and effort.
This posting is provided "AS IS" with no warranties, and confers no rights.

Similar Messages

  • Won't install on clean OS X: Error enabling server management.

    Hi All,
    I'm getting seriously fed up of Server.app.
    I previously had it installed on my Mac Mini, but due to various reasons did a clean install of OS X. On boot, the only app I have installed so far is Parallels. My second app is Server.app, well it would be but it fails when trying to configure it:
    Error enabling server management.
    A problem was detected with Server. Please redownload Server from the App Store.
    Obviously I did do this, to no avail. I also copied over a known working version of Server.app from another machine and got the same message. I mean what gives? Why isn't it even letting me install it?!
    Thanks

    Not only do I have that folder already in existence, but I have a plist file located there that is for the server.app I'm sure.
    com.apple.serverd.plist
    I have tried deleting this and relaunching to no avail.
    Still stuck with the error.
    And terminal doesn't seem to agree with that command.
    Says "-al" isn't a valid command?
    Console is giving me a tiny bit of info that might help...
    3/21/13 12:40:19.800 PM Server[8383]: Could not find image named 'XSLock'.
    3/21/13 12:40:34.388 PM launchdadd[8388]: Could not open /Applications/Server.app/Contents/Library/LaunchServices/com.apple.serverd (open() error 2: No such file or directory)
    3/21/13 12:40:34.388 PM launchdadd[8388]: Could not close file descriptor for old temporary tool. Continuing on. We will be left with a dangling reference to the file, and this will prevent it from being cleaned up automatically by the system until launchdadd is either relaunched or the system is rebooted. (close() error 9: Bad file descriptor)
    3/21/13 12:40:34.389 PM launchdadd[8388]: FAILURE: Could not create a request for tool at path /Applications/Server.app/Contents/Library/LaunchServices/com.apple.serverd
    3/21/13 12:40:34.390 PM Server[8383]: ERROR: failed to enable serverd: Error Domain=kSMErrorDomainFramework Code=5 "The operation couldn’t be completed. (kSMErrorDomainFramework error 5 - The tool at the specified path is not valid.)" UserInfo=0x7fba6c0bc270 {NSDescription=The tool at the specified path is not valid.}
    Not sure where to go from here.

  • 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

  • Getting "Error 500--Internal Server Error" for Enterprise Manager

    Hi,
    I'm getting "Error 500--Internal Server Error" while invoking EM of wls server ie http://<host>:7001/em/ It used to work fine before. Restored config.xml from domain_bak, but still error persists. I can see following error in AdminServer logs while invoking above URL:
    Caused By: java.lang.ClassNotFoundException: oracle.binding.DataControl
            at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
            at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
            at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    Copied adfm.jar to domain lib and bounced all wls servers, but error still persists.
    Please let me know what else can be tried.
    Thanks,
    Vikas

    Some more lines from stack trace:
    ####<Oct 10, 2013 9:52:36 PM PDT> <Notice> <Diagnostics> <slc04qvi> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <f7fdeea2380fcf3a:-5d5bd989:141a5bc686c:-8000-000000000000005e> <1381467156262> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'AdminServer' has triggered at Oct 10, 2013 9:52:36 PM PDT. Notification details:
    WatchRuleType: Log
    WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-101020') OR (MSGID = 'WL-101017') OR (MSGID = 'WL-000802') OR (MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
    WatchData: DATE = Oct 10, 2013 9:52:36 PM PDT SERVER = AdminServer MESSAGE = [ServletContext@2095354505[app:em module:/em path:/em spec-version:2.5]] Root cause of ServletException.
    java.lang.NoClassDefFoundError: oracle/binding/DataControl
            at java.lang.ClassLoader.defineClass1(Native Method)
            at java.lang.ClassLoader.defineClass(ClassLoader.java:792)
            at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)

  • 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.

  • Using another CEN for Solution Manager

    Hi all,
    we have the situation, that our CEN was existing long before we raised our own solution manager.
    My question is quite simple: Is it possible to use that remote CEN for the system monitoring functions in solution manager or not - without migrating it to the solman. I would be very nice if anyone can make a proposal because I cannot imagine, that I am the only one in the world with this demand.
    thank a lot
    Andreas

    Hi Andreas,
    as far as I know, it is not possible to have "a CEN and a SOL in parallel" and connecting them e.g. via RFC to get the alert data from CEN to SOL. You can only use this constellation in special cases like SL-Reporting (where you can specifiy an RFC to CEN in customizing). But I do not know any way in area System Monitoring.
    We had the same situation as you have and decided to migrate the CEN into the SOL. For a couple of weeks, we let the two systems run in parallel (this was done by registering all the CCMS-Agents at both systems) and then simply overtaking all the agents from CEN to SOL. The only manual task you need to do is re-assigning the central autoreaction methods.
    If you want to know more about this, feel free to come back....
    Regards,
    Dirk

  • Compile error for DragManager.acceptDragDrop(event.target)

    This line
    DragManager.acceptDragDrop(event.target);
    seems to be giving me the following compile error:
    Implicit coercion of a value with static type Object to a
    possibly unrelated type mx.core:IUIComponent.
    (There is an arrow pointing to "target", I guess indicating
    that that is the Object causing the problem.)
    I'm not sure why this is giving me an error since the
    official Adobe document describing how to migrate applications from
    Flex 1.5 to Flex 2 says that
    DragManager.acceptDragDrop(event.target) is what's supposed to
    replace event.handled=true.

    Hi.
    The problem is that DragManager.acceptDragDrop expects a
    UIComponent but Event.target is typed as Object. You need to cast
    the target as a UIComponent. Try this:
    DragManager.acceptDragDrop(UIComponent(event.target));

  • Script error for desktop manager...

    everytime i go to install version 4.3 for my pearl it runs into a script error and the installation fails... does anyone know what this means??? thx for your help

    Hi caesar
    Could you post the error please, and your version of windows.  If it's a vbscript error try this.
    Cheers!

  • BI content error for contract management DSO

    Hi
    I am getting start rotine error from BI content while installing flow from 2lis_02_scl to
    2LIS_02_SCL -> ODSO 0SRCT_DS1
    E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
    SOURCE_PACKAGE" is incompatible with the formal parameter
    "DATA_PACKAGE"
    please let me know any possible solutions

    Hi,
    I am getting start rotine error from BI content while installing flow from 2lis_02_scl to 2LIS_02_SCL -> ODSO 0SRCT_DS1
    E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter
    SOURCE_PACKAGE" is incompatible with the formal parameter
    "DATA_PACKAGE"
    You must define equal fields/InfoObejcts in Source and Target, you need to open the start rotine in transformations and add manually, it will work.
    Thanks
    Reddy

  • Another Error For iTunes 9

    I have had a quick flick through a few of the topics on the forum and noticed lots of different issues regarding the new iTunes. I was going to wait a week and then update but, because I wanted to buy some stuff of iTunes, I had no choice but to upgrade!!
    After some messing around, I eventually got iTunes to work after the upgrade (I had to install Quicktime separately). I now have a different problem, when ever I try to purchase something I get the following message *"We could not complete your iTunes Store request. The network connection timed out. Make sure your network settings are correct and your network connection is active, then try again"*
    I have also tried to update my iPhone to the new firmware 3.1 and I get the same response can someone please advise me. Are there anyone else having the same problem?

    I have had the same problem and after a great deal of angst and screaming I went to the Quicktime Player and clicked on Run as Administrator. This has done the trick. Good luck!

  • Server Manager error 0x80070422 - Roles and features are not accesible

    Hi
    I cannot view Roles and Features in Server Manager on my Server 2008 R2 box. The error is:
    Unexpected error refreshing Server Manager: The service cannot be started, either because it is disbaled or because it has no enabled devices assicaited with it (Exception from HResult: 0x80070422)
    I have looked at my services - but don't know what service to look for, everything seems to be in order.
    After some investigation on the net, I understood that I need to setup the win readiness tool, I did and the output in CheckSur file is as follows
    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 12.0
    2011-05-31 19:02
    Checking Windows Servicing Packages
    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB2296199_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum  Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual
    file name
    (fix) CBS MUM Corrupt CBS File Replaced Package_for_KB2296199_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-servicing-x64-apr29.cab.
    (fix) CBS Paired File CBS File also Replaced Package_for_KB2296199_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-servicing-x64-apr29.cab.
    Checking Package Watchlist
    Checking Component Watchlist
    Checking Packages
    Checking Component Store
    Summary:
    Seconds executed: 4058
     Found 1 errors
     Fixed 1 errors
      CBS MUM Corrupt Total count: 1
      Fixed: CBS MUM Corrupt.  Total count: 1
      Fixed: CBS Paired File.  Total count: 1
    Here again, it seems that everything is fine.
    Thanks in advance for your help

    Hi,
    Please try to install Windows Server 2008 R2 Service Pack 1 directly and check the result. Service Pack 1 for Windows Server 2008 R2 includes all the
    previous released Windows Updates and hotfixes.
    If it does not work, you will need to copy these files from another working Windows Server 2008 R2 system to replace the corrupt ones.
    Otherwise, you will need to perform an In-Place upgrade to repair the system.
    Regards,
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • For server Eagle-PROD-Instance, the Node Manager associated with machine

    I have a wlst script that creates a domain and a managed server. I associate the server with a machine that's attached to a node manager. It creates the managed server fine but when I try and start it I get this error
    For server Eagle-PROD-Instance, the Node Manager associated with machine Eagle-Machine is not reachable.
    All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
    The machine is associated with the Node Manager and the NM is running. I can start the managed server from the command line, but not from the admin console
    This is the script, am I missing something?
    Thanks
    name: createManagedServer.py
    description: This script create the weblogic domain, and executes each weblogic queue module
    subfile. it reads a property file : weblogic_wlst.properties for server domain information
    author     : mike reynolds - edifecs 2011
    created     : April 8th 2011
    import sys
    from java.lang import System
    from java.util import Properties
    from java.io import FileInputStream
    from java.io import File
    from weblogic.management.security.authentication import UserEditorMBean
    from weblogic.management.security.authentication import GroupEditorMBean
    from weblogic.management.security.authentication import UserPasswordEditorMBean
    # Loads the contents a properties file into a java.util.Properties
    # configPropFile = "weblogic_wlst.properties"
    def loadPropertiesFromFile(configPropFile):
         configProps = Properties()
         propInputStream = FileInputStream(configPropFile)
         configProps.load(propInputStream)
         propInputStream.close()
         return configProps
    def getProperties():
         importConfigFile = sys.argv[1]
         print importConfigFile
         domainProps = loadPropertiesFromFile(importConfigFile)
         properties = Properties()
         input = FileInputStream(importConfigFile)
         properties.load(input)
         input.close()
         return properties
    def create_users(username, password, description):
    # create admin user
    cmo.getFileRealms()
    try:
    userObject=cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider("DefaultAuthenticator")
    userObject.createUser(username,password,description)
    print "Created user " + username + "successfully"
    except:
    print "check to see if user " + username + " exists "
    def add_user_to_group(username):
    print "Adding a user to group ..."
    cmo.getFileRealms()
    try:
    userObject2 = cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider("DefaultAuthenticator")
    userObject2.addMemberToGroup('Administrators',username)
    print "Done adding user " + username
    except:
    print "check to see if user " + username + " is already in group "
    def connect_server(user,pw,url):
              connect(user,pw,url)
    def create_machine():     
    try:
    print 'Creating machine' + machine
    # cd('/')
    # create(machine, 'Machine')
    mach = cmo.createUnixMachine(machine)
    mach.setPostBindUIDEnabled(true)
    mach.setPostBindUID('oracle')
    mach.setPostBindGIDEnabled(true)
    mach.setPostBindGID('oracle')
    mach.getNodeManager().setNMType('ssl')
    except:
         print "machine exists"
    def build_domain():
    ### Read Basic Template
    WL_HOME = "C:/Oracle/Middleware/wlserver_10.3"     
    readTemplate(WL_HOME+"/common/templates/domains/wls.jar")
    template=WL_HOME+"/common/templates/domains/wls.jar"
    cd('Servers/AdminServer')
    set('ListenAddress', adminServerAddress)
    set('ListenPort', int(adminServerPort))
    cd('/')
    cd('/Security/base_domain/User/weblogic')
    cmo.setPassword('w3bl0g1c')
    ### Write Domain
    setOption('OverwriteDomain', 'true')
    print "writing domain " + domainDir + domainName
    writeDomain(domainDir+'/'+domainName)
    closeTemplate()
    create_machine()
    arg = "Arguments=\" -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -da\""
    prps = makePropertiesObject (arg)
    domain = domainDir + domainName
    try:
         #startNodeManager()
    #nmConnect('weblogic', 'w3bl0g1c', host, 5556, 'AdminServer', domain, 'ssl')
    # nmStart('AdminServer')
    startServer('AdminServer', domainName, url, adminUser, adminPassword, domainDir, 'true')
    except:
    print "could not connect to Node Manager"
    def create_server():     
    # get server instance properties
    name = properties.getProperty("serverName")
    domain = properties.getProperty("domainName")
    port = properties.getProperty("listenPort")
    address = properties.getProperty("listenAddress")
    servermb=getMBean("Servers/" + name)
    machine = properties.getProperty("machineName")
    nodePort = properties.getProperty("nodeManagerPort")
    domainDir = properties.getProperty("domainDir")
    if servermb is None:
              startEdit()
              cd('/')
              cmo.createServer(name)
              cd('/Servers/'+ name)
              cmo.setListenAddress(address)
              cmo.setListenPort(int(port))
              cd('/')
              cmo.createMachine(machine)
              cd('/Machines/' + machine + '/NodeManager/' + machine )
              cmo.setNMType('Plain')
              cmo.setListenAddress(address)
              cmo.setListenPort(int(nodePort))
              cmo.setDebugEnabled(false)
              cd('/Servers/' + name)
              cmo.setListenPortEnabled(true)
              cmo.setJavaCompiler('javac')
              cmo.setClientCertProxyEnabled(false)
              cmo.setMachine(getMBean('/Machines/' + machine ))
              cmo.setCluster(None)
              cd('/Servers/' + name + '/SSL/' + name)
              cd('/Servers/' + name + '/ServerDiagnosticConfig/' + name)
              cmo.setWLDFDiagnosticVolume('Low')
              cd('/Servers/' + name)
              cmo.setCluster(None)
              cd('/Servers/' + name + '/SSL/' + name)
              cmo.setEnabled(false)
    ### Executable Script
    ### CreateDomain.py
    ### Define constants
    WL_HOME = "C:/Oracle/Middleware/wlserver_10.3"
    print "Starting the script ..."
    print "Getting properties ... "
    properties = getProperties()
    adminServerAddress = properties.getProperty("adminServerAddress")
    adminServerPort = properties.getProperty("adminServerPort")
    adminUser = properties.getProperty("adminUser")
    adminPassword = properties.getProperty("adminPassword")
    edifecsUser = properties.getProperty("edifecsUser")
    edifecsPassword = properties.getProperty("edifecsPassword")
    host = properties.getProperty("host")
    domainDir = properties.getProperty("domainDir")
    domainName = properties.getProperty("domainName")
    user = properties.getProperty("username")
    pw = properties.getProperty("passwd")
    url = properties.getProperty("adminURL")
    machine = properties.getProperty("machineName")
    print "Building the domain..."
    build_domain()
    print "Connecting to server"     
    connect_server(adminUser, adminPassword, url)
    edit()
    startEdit()
    # create managed server
    # create_machine()
    create_server()
    print "Creating users"
    # starting configuration tree
    serverConfig()
    create_users(adminUser, adminPassword, "Administrator")
    add_user_to_group(adminUser)
    create_users(edifecsUser, edifecsPassword,"Administrator")
    add_user_to_group(edifecsUser)
    # have to restart edit to save config
    edit()
    startEdit()
    # nmKill('AdminServer')
    print "saving configuration"
    try:
         save()
         activate(block="true")
         print "script returns SUCCESS"
         print "admin server is running"
         print "starting server " + name
         startServer(domainName, name ,url,adminUser, adminPassword, domainDir,'true')
    except:
         print "failed to save server"
         dumpStack()

    Actually the cert is coming from your Dev machine but it is sending the Prod cert.
    What cert is used by your admin server ? It should match the host name.
    So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
    The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
    In your nodemanager.properties, are you explicitly accessing keystores, such as with:
    KeyStores=CustomIdentityAndJavaStandardTrust
    CustomIdentityAlias=some_alias
    CustomIdentityKeyStoreFileName=some_path_to_keystore
    CustomIdentityKeyStorePassPhrase={3DES}...
    CustomIdentityKeyStoreType=jks
    CustomIdentityPrivateKeyPassPhrase={3DES}
    In my multi-machine clusters, I have multiple certificates such as:
    admin machine1:
    has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
    has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
    all other machines:
    has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
    has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

  • Run as for .msc and Server Manager

    I have installed RSAT for Win 8.1 Pro x64 and created custom .msc console with ADUC, DNS, DHCP and other snapins, put it on my desktop. Also I put shortcut for Server Manager on my desktop. Is there any way to start these as domain admin account which I
    have along with my "normal" user account - using run as in some way. I could use shift+right click and run as different user but I prefer the other way if possible. I want the same for Windows PowerShell and Windows PowerShell ISE.
    Thanks in advance!

    seems only the domain administrator who have right to open the MMC console saved by other user. Right click the console document and choose Run
    as administrator, then enter your user name and password. The console opened with the Administrator right...
    Best,
    Howtodo

  • Access denied in Windows 2012 Server Manager after a period of time working without problems

    Hello,
    I had 2 servers with windows 2012 installed in a domain (dc is in a 3rd server) and both added to server manager of each other. Both servers had Failover cluster installed and configured roles. After startup in both servers i can see the other and manage
    it without problems (in server manager and failover cluster manages) but after a period of 30-40 minutes in both servers I see "Online - Data Retrieval failures Ocurred" for the partner server and "Online - Access Denied" for local server.
    When I access de Failure Cluster Manager I had errors accessing resources and roles and can´t failover the cluster.
    I removed the failover cluster thinking that could be the original problem, remove servers from domain, change names and add again to the domain without install failover cluster.
    Now, the servers have not the failover cluster feature and the problem persists. 30-40 minutes after boot the server manager show messages of inaccesible partner with same messages. I tried to execute powershell commands to add a new ip to the NIC and I
    receive a Access Denied Message and show Access Denied message in other events in log.
    I´m using Domain Administrator Account and tried different solutions but not solved. I saw that this message can occur in a variety of different scenarios, but i don´t know why works during a period of time before failing. It´s frustrating
    Regards
    EDITED: in detail of Online - Data retrieval failures i see that: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The WS-Management service cannot process the request.
    The WMI provider returned an 'access denied' error.

    Hi PabloVDL,
    It seems is this two server has register the incorrect DNS, please try to add this server manage NIC IP to your manager hosts file or if possible trmpory disable the useless NIC DNS register. This issue also some times caused by when you installed
    the HP insignth management, if in your environment you have this tools please temporarily uninstall it.
    More information:
    Windows Server 2012 - Server Manager Troubleshooting Guide, Part III: Common
    Events and Errors in Server Manager
    http://social.technet.microsoft.com/wiki/contents/articles/13445.windows-server-2012-server-manager-troubleshooting-guide-part-iii-common-events-and-errors-in-server-manager.aspx
    I’m glad to be of help to you!
    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.

  • EBS 12.0.6 Upgrade to 12.1.1 Another Error

    Hi Hussein,
    I just hit a another error for worker 1.
    sqlplus -s APPS/***** @/mnt/data/u01/oracle/TEST32/apps/apps_st/appl/fnd/12.0.0/patch/115/sql/afgstusr.sql &un_fnd &pw_fnd
    PL/SQL procedure successfully completed.
    ERROR: The Profile "Guest User Password" is not properly defined or
    the data associated with this profile is out of configuration.
    CORRECTIVE ACTION: Please contact Oracle Applications Support for
    assistance in validating the configuration of this profile
    The "GUEST_USER_PWD" in vault has been validated as : "GUEST/ORACLE"
    DECLARE
    ERROR at line 1:
    ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-06512: at line 15
    Thanks again.
    Regards,
    cmadiam

    Please see these docs.
    GUEST_USER_PWD Profile Option Is Not Available In R12.1 Instance [ID 788979.1]
    How To Set A System Profile Value Without Logging In To The Applications [ID 364503.1]
    How to Change Profile Option Value Without Forms? [ID 943710.1]
    How To Successfully Change The Guest Password In E-Business Suite 11.5.10 and R12 [ID 443353.1]
    Thanks,
    Hussein

Maybe you are looking for