VM Server 2.2.1 Install errors

I am new to OVM and am trying to get it installed so I can use the RAC templates and do some database feature testing.
I downloaded the Oracle VM Server 2.2.1 x86 64bit from the e-delivery site and followed the steps as indicated:
1. Download the compressed binary CD image
2. Uncompress the CD image
3. Write the CD image to CD
4. Insert the cd, and boot
When booting, I get the following errors:
unknown keyword in config
unknown keyword in config
unknown keyword in config
file could not find kernel image
boot:
Searching the internet led me to trying this:
boot: /isolinux/vmlinuz initrd=/isolinux/initrd.img
This got things moving until reaching error similar to this:
kernel panic-not syncing VFS:unable to mount root fs on unknown-block(0,0) (the unknown-block actually had numbers in my case)
This is going beyond my understanding of Linux and was hoping I could just install and get moving with the the templates.
The box being installed on is a Dell optiplex 760 with 4gb of memory and cpu is intel core duo E8400.
Any help would be appreciated.
Thanks.

I realize it's hard to find, but the appropriate forum should be http://forums.oracle.com/forums/forum.jspa?forumID=482
Also, you might want to use your Metalink account to discuss this with Oracle support.

Similar Messages

  • Win 2003 server SATA2 RAID 0 install errors

    I keep getting the following error when trying to install Win 2003 server, as it is loading drivers:
    "The file iaStor.sys is corrupted.
    Press any key to continue."
    Note: I get this error on every copy of win2003 server that I have AND I get it when trying to F6 install Intel's SATA RAID drivers from floppy, so it isn't really a corrupt file.
    So I continue on and finally when trying to load windows it says something about windows not detecting any harddrives.  Well, bios sees them fine.  The ROM Intel Matrix Storage Manager sees them fine.  I have all 3 drives set on one volume in Intel Matrix Storage Manager for a total of 698.7GB's.  If I change to SATA Mode IDE the BIOS sees them fine.
    I have the following relevant BIOS settings:
    SATA Mode RAID (I've tried all 3 settings with no luck)
    SATA Post speed setting DISABLED (I've tried Force Gen2 to no avail, and yes the HD jumpers are off so it runs at a full 3gbs)
    JMB361 Disabled (I don't have anything on SATA port 5)
    I've messed around with practically every possible combination of settings and am at a complete loss here as to what I should do to get this thing working.  I've even tried skipping RAID completely.  I've read through the (confusing) mobo instructions multiple times and just don't see what I am missing here.  =/  Any help would be greatly appreciated!  TY!  See profile for hardware specs.

    Well, you can only find out by re-installing the system with SBE 2003 again and if it doesn't works, you've got to install SBS 2003 back...
    It depends on how you want to play the game. A shot that may help you or burden you .

  • SQL Server 2008 R2 SP3 install error - caspol.exe Fatal error

    When I attempt to install sql server 2008 r2 sp3 I get caspol.exe - Fatal error.  Unable to load Jit Compiler:(mscorjit.dll): file may be missing or corrupt.  Please check or rerun setup.  Then after I click ok I get the Microsoft Windows
    popup that says Microsoft .NET Framework CAS Policy Manager has stopped working.  This is on a Windows 2008 Enterprise Server, service pack 2.  I am wondering if my .NET Framework had become corrupt on the server.  Any ideas?  This has
    been on a stable production sql server that has been running fine for many years.
    Thanks for reading my post.
    Joe Sitver

     Unable to load Jit Compiler:(mscorjit.dll): file may be missing or corrupt.  Please check or rerun setup. 
    Hi Joe,
    Mscorjit.dll (Microsoft .NET Runtime Just-In-Time Compiler) is a component of Web developing applications and the most prominent program that makes use of this file is the Microsoft.NET Framework.
    The most common reason of the above error is that there is an improper installation/update of your .NET framework. Please
    use this
    tool to repair .NET framework. If the issue persists, you might need to uninstall and reinstall your
    .NET framework.
    Thanks,
    Lydia Zhang
    If you have any feedback on our support, please click
    here.
    Lydia Zhang
    TechNet Community Support

  • Installation of Client Access role fails on Windows Server 2008 R2 (Execution of: "$error.Clear(); Install-ExchangeCertificate -services "IIS, POP, IMAP")

    Hello
    I am trying to install Exchange Server 2010 beta 1 onto a Windows Server 2008 R2 (build 7000) machine which has also been set up as a domain controller.
    However when attempting to install the Client Access role, setup fails with the error below.
    Does anyone know of a way to get around this please?
    I have already searched for this error and not found any similar threads.
    Also every time I press the code button on this forum it crashes the browser and I keep losing the message! (IE8 from within Server R2). Also the message box is very small, will not expand and keeps jumping to the top.
    Thanks
    Robin
    [code]
    Summary: 4 item(s). 1 succeeded, 1 failed.
    Elapsed time: 00:00:01
    Preparing Setup
    Completed
    Elapsed Time: 00:00:00
    Client Access Role
    Failed
    Error:
    The execution of: "$error.Clear(); Install-ExchangeCertificate -services "IIS, POP, IMAP" -DomainController $RoleDomainController", generated the following error: "Could not grant Network Service access to the certificate with thumbprint 2F320F5D5B5C6873E54C8AB57F604D8AFA31D18C because a cryptographic exception was thrown.".
    Could not grant Network Service access to the certificate with thumbprint 2F320F5D5B5C6873E54C8AB57F604D8AFA31D18C because a cryptographic exception was thrown.
    Access is denied.
    Elapsed Time: 00:00:01
    Mailbox Role
    Cancelled
    Finalizing Setup
    Cancelled
    [/code]
    Robin Wilson

    Hello
    Thanks for all the replies.
    I have since wiped the system and installed everything again and it all worked this time so not sure what was wrong last time. I did try to uninstall all Exchange components and then uninstall IIS and Application server, reboot and re-install but I received the same error still when it came to installing the client access role.
    Walter: I just attempted the standard installation which should have used the default self-signed certificate. Everything was a fresh install done at the same time on a freshly formatted PC.
    For info last time when it failed to work:
    - Installed Windows Server 2008 R2
    - Installed Domain Controller role using dcpromo. I set the forest and domain as Windows Server 2008 R2
    - Added a forest trust between main domain and test Exchange domain (set up as ex2010.local)
    - Installed IIS and Application Server role
    - Installed Hyper-v role
    - Installed Desktop Experience feature
    - Installed Exchange and recieved the error
    When it worked I set up the forest and domain in Windows Server 2008 mode (i.e. not R2), installed Exchange first and then set up the forest trust and then Hyper-v. It did say it failed to configure dns which was probably because it started trying to do automatic updates half way through the dcpromo! DNS seems to work ok though.
    I did notice this time that Hyper-v gave a warning about the virtual network adapter not being set up correctly and the local network did not work correctly although I could access the internet. Not sure if this could have been related to the cause of the problem previously. For now I have disabled the virtual network until I get time to try and get it working and so the mail will work in the meantime.
    I also noticed that Hyper-v added an extra 443 ssl binding to the default website so as it had 2 bindings on port 443 it refused to start. After deleting one it worked.
    I decided to install Exchange onto a domain controller as it is only a test and I wouldn't do it in a live environment. I am also short of test machines! It didn't give me any warnings about this actually, I think previous versions warn you that it is not recommended.
    Andreas and Chinthaka: I did not know about the requirement to run the domain at 2003 mode. The main domain is running in 2008 mode with Exchange 2007 so I assume this is just a temporary beta related requirement. It does seem to be working (second attempt) so far in a 2008 mode domain although I haven't had a chance to fully test it yet.
    Thanks
    Robin
    P.S. Sorry it's taken me a while to reply!
    Robin Wilson

  • Team Foundation Server 2013 update 4 New Install - Error 503 Service Unavailable for Sharepoint Central Admin

    Hello,
    I ran a new install of Team Foundation Server and let it install the built in SharePoint pieces on a single server setup. After the install i'm able to access the
    http://teamfoundation:8080/tfs/ address without issue but am unable to create a project. When I attempt to create a project I get the following error:
    TF30172: You do not have permission to create a new team project (when checking security i'm a member of the project collection administrators and Team Foundation Administrators)
    This led me to look at the sharepoint central administration site where I receive the following error:
    Error 503 Service Unavailable
    I've gone through and validated the identity is set correctly in IIS for the following services:
    SharePoint Central Admin v4
    SharePoint15AppPool
    The SharePoint Web Services Root is set as LocalService instead of the domain user.
    The identity domain user is setup as local administrator on the Team Foundation Server. They are all set to use .net v4.0.30319 with integrated Pipeline mode.
    Any help would be great!
    Thanks!
    Eric

    Hi Eric,      
    Thanks for your post.
    Please share your detailed team project creation log here.
    In your TFS Admin Console>>Extensions for SharePoint Products tab, ensure SharePoint Web Application shows correctly in the right panel. And go to TFS Admin Console>>Application Tier>>SharePoint Web Applications tab, ensure your SharePoint
    web application displays in the right panel, then select your SharePoint web application and click Repair Connection, ensure can repair successfully.
    In your IIS Manager, select your SharePoint Central Administration V4 site and click Browser:17012(http) in the right panel, check if your SharePoint Central site can be opened successfully or not. If your SharePoint Central site cannot be accessed, I think
    this issue relate to your SharePoint site, you should contact SharePoint experts to resolve this issue first. After you resolved this issue and your SharePoint Central Admin site can be accessed correctly, then try to create your team project(within SharePoint
    site) again, if there still has issue when creating team project, please share the detailed error message here, we will try to resolve it.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • SCSM Management Server install error

    Hi All
    I have a curious error with regards to an SCSM 2012 R2 Management Server install to a Windows Server 2012 with local SQL Server 2012 Standard); the SCSM 2012 R2 Data warehouse Server installed fine on a separate server.  I've checked that the install
    account has full SQL, Local and Domain Admins (for install), I've also fired the install from an elevated command prompt but with same error, I've also checked that PowerShell is set to Unrestricted.  There is also mention of a Timeout in the below error,
    which has lead me to think it could possibly be SQL SPN issue, however please see below and let me know if anyone has seen this before \ any suggestions welcome!
    The error I'm seeing in the MSI log is as follows:
    Calling custom action CAManaged!Microsoft.MOMv3.Setup.PreExtensionRegistration.PreRegisterExtensions
    PreRegisterExtensions: Begin
    PreRegisterExtensions: Starting in deferred mode
    PreRegisterExtensions: 20 extension records decoded
    PreRegisterExtensions: Connecting via InProc SDK
    PreRegisterExtensions: Loading management pack C:\Program Files\Microsoft System Center 2012 R2\Service Manager\System.Library.mp
    PreRegisterExtensions: Importing management pack C:\Program Files\Microsoft System Center 2012 R2\Service Manager\System.Library.mp
    PreRegisterExtensions: System.ArgumentException: The requested management pack is not valid. See inner exception for details.
    PreRegisterExtensions: Parameter name: managementPack ---> : Database error. MPInfra_p_ManagementPackInstall failed with exception:
    PreRegisterExtensions: Database error. MPInfra_p_ManagementPackInstall failed with exception:
    PreRegisterExtensions: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    PreRegisterExtensions: The statement has been terminated.
    PreRegisterExtensions:
    PreRegisterExtensions:    --- End of inner exception stack trace ---
    PreRegisterExtensions:    at Microsoft.EnterpriseManagement.ManagementPackManagement.TryImportManagementPack(ManagementPack managementPack, IDictionary`2 resources)
    PreRegisterExtensions:    at Microsoft.EnterpriseManagement.ManagementPackManagement.ImportManagementPack(ManagementPack managementPack, IDictionary`2 resources)
    PreRegisterExtensions:    at Microsoft.MOMv3.Setup.PreExtensionRegistration.PreRegisterExtensions(Session session)
    PreRegisterExtensions: End (fail)
    MSI (s) (D8:E4) [13:20:43:793]: NOTE: custom action _PreRegisterExtensionsDeferred unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
    CustomAction _PreRegisterExtensionsDeferred returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    04/02/2014 13:20:43.824 [3032]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
    04/02/2014 13:20:43.878 [3032]: Detailed info about C:\Windows\assembly\tmp\CPSNRJPD\Microsoft.EnterpriseManagement.OperationsManager.Apm.StatisticCounters.ScriptingLibrary.dll
    04/02/2014 13:20:43.878 [3032]:  File attributes: 00000080
    04/02/2014 13:20:44.124 [3032]:  Restart Manager Info: 1 entries
    04/02/2014 13:20:44.125 [3032]:   App[0]: (3032) Windows Installer (msiserver), type = 3
    Kind Regards
    Andrew

    Thanks Thomas
    Yep had checked permissions, see below.  Any others that I may have over looked that you can think of?
    1. Login \ install account as local Admin on the Server
    2. Login \ install account has full SQL SysAdmin rights, was also used for installing the SQL Instance locally
    3. Checked account in AD so that it is ok for Kerberos Delegation
    One thing is that I have specified this account for all account options during install (since its a test environment), in production would usually create distinct accounts, is this likely to be an issue though?
    Will attempt install again but use Local System etc instead of specifying my domain account just to check \ see if error changes.
    Kind Regards
    Andrew

  • 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 "certificate server is installed" error when attempting demote of server 2012

    Currently, we are testing server 2012 in our environment and using a 180 day trial version. Wanting to remove the complex password account restriction, I noticed that all removal options are grayed out, as the trial server is listed as a domain controller
    (although no accounts have been setup and no one is logging onto it).
    Using the "remove roles and features" option, I attempted to uninstall the active directory certificate services (after unchecking the box), but received a warning that the server must be demoted. Ok.
    So, now I follow through the process, check the "last domain controller" checkbox (I had previously checked the "force demotion" but that failed) and click the "demote" button.
    Fine.
    One would expect that the server would be demoted, it would reboot and all would be just as requested.
    No such luck.
    Received a "certificate server is installed" error and the demotion will not proceed. Tried it several more times with the same results. Any suggestions?
    Thanks.
    Dan David

    First if you plan on using this in a production environment ever you can't convert a evaluation license to a full license if the Domain controller role is installed.
    domain controllers have their own default policy, for just the opposite of what you are trying to do, it leaves the domain controllers hardened if someone changes the default domain policy, if you still have a stable server you should be able to go
    to the group policy management and adjust the security policy on the "default domain controller" policy.
    It sounds like you may have a server that is in a unstable state not a dc but it thinks it is may be? if that is the case starting over may be a fastest way to correct. 

  • Adobe CS3 - Server 2008 Install Error

    I am in the process of transitioning our organization to a cloud server running Windows Server 2008 x64. I would like to be able to install Creative Suite 3 Design Premium on the new server. I have attempted the install but get the following error at the beginning before the installation will ever really get started "Critical errors were found in setup. Please see the setup log for details". Therefore, I am not able to even start the install.
    I have tried for several hours to research on the web but have not found any definite answer. It does appear that CS3 is not supported by Adobe on Server 2008. Has any one had any luck getting it to install properly on Server 2008? If not CS3, will any of the newer version work on Server 2008 should I choose to upgrade to a newer Adobe product?
    Thank you in advance for any assistance that might be provided. I greatly appreciate it.
    Todd

    Thank you very much for your assistance. I really appreciate it.
    Todd
    Mylenium <[email protected]> wrote:
    Mylenium http://forums.adobe.com/people/Mylenium created the discussion
    "Re: Adobe CS3 - Server 2008 Install Error"
    To view the discussion, visit: http://forums.adobe.com/message/4115952#4115952

  • Ias 60 sp2 -  install - error message during start up  of web server

    I am installing ias60 sp2 on solaris 2.6.
    I have following issues:
    (1)
    While installing the ias 60 at the end of the installation while starting
    the web server I got the following
    error message.
    libthread panic: systhread_create():alloc_thread returns 0 (no mem) (PID:
    1566
    4 LWP 1)
    stacktrace:
    ef3c31e8
    1329c
    1236c
    0
    (2) I want to make the ias60 to communicate with the external web server.
    But the 'setup' utility does not allow me to do the selective install. It
    foreces the web server to be on the same machine as the appserver. I have
    installed the iws41 web server and proceed with the installation. In the
    installation doc it looks like by installing 'web connector' we can make the
    ias communicate with the external web server. Since the setup utility does
    not permit selective install how do i install the 'web connector' on the
    external web server. I am using the ias60 test drive for the installation.
    Is it a limitation on the 'test drive'.
    I apprciate your suggestions on the above.
    Thanks
    Palani
    Thanks
    Palani

    I'm not sure what the problem is with alloc_thread.
    But, yes, the installer limitation is because you are using the TestDrive bits.
    TestDrive is designed for ease of installation, and many of the installer
    options are not available in TestDrive.
    David
    (2) I want to make the ias60 to communicate with the external web server.
    But the 'setup' utility does not allow me to do the selective install. It
    foreces the web server to be on the same machine as the appserver. I have
    installed the iws41 web server and proceed with the installation. In the
    installation doc it looks like by installing 'web connector' we can make the
    ias communicate with the external web server. Since the setup utility does
    not permit selective install how do i install the 'web connector' on the
    external web server. I am using the ias60 test drive for the installation.
    Is it a limitation on the 'test drive'.

  • Siebel 8.1.1 Install error using MS SQL Server 08

    Hi,
    I am trying to set up a Siebel Proto environment on WinXP system. The database that I am using is MS SQL Server 2008 with SP1 installed.
    After installing Siebel at the Database Install step, I encountered a failure on step 'Import Repository Data' The error log generated is as follows:
    2010-04-03 18:47:45     C:\sba81\siebsrvr\bin\repimexp.exe /a I /G ENU /u SADMIN /p ***** /c SBA_81_DSN /d dbo /r "Siebel Repository" /f C:\sba81\dbsrvr\common\mstrep.dat /l C:\sba81\siebsrvr\log\install\output/imprep_prim.log
    2010-04-03 18:47:45     
    2010-04-03 18:47:45     Connecting to the database...
    2010-04-03 18:47:46     Connected.
    2010-04-03 18:47:46     Starting common api.
    2010-04-03 18:47:46     SQLstyle is 'Microsoft SQL Server'
    2010-04-03 18:47:46     SARM is OFF -change param SARMLevel to enable
    2010-04-03 18:47:46     SARM Client is OFF -change param SARMClientLevel to enable
    2010-04-03 18:47:46     SARM is OFF -change param SARMLevel to enable
    2010-04-03 18:47:46     SARM Client is OFF -change param SARMClientLevel to enable
    2010-04-03 18:47:46     SARM is OFF -change param SARMLevel to enable
    2010-04-03 18:47:46     SARM Client is OFF -change param SARMClientLevel to enable
    2010-04-03 18:47:47     Unable to verify login name SADMIN.
    2010-04-03 18:47:47     Unable to start common api.
    2010-04-03 18:47:47     Unable to start common api.
    2010-04-03 18:47:47     Error in initiate function..
    2010-04-03 18:47:47     Elapsed time: 2 sec.
    2010-04-03 18:47:47     (logapi.cpp (184) err=1 sys=0) SBL-GEN-00001: (logapi.cpp: 184) error code = 1, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)
    I am using SADMIN user for Database account and SIEBEL user for Table owner. I have also tried using SIEBEL user in both places.
    Basically what is SARM? And how can I enable it?
    I have tried connecting to the DB from the Server system and am successful in that.
    Thanks for the help in advance.
    With Regards,
    Tanmay Jain

    Hi EvtLoglvl,
    I am able to connect to the SQL Server using the ODBC connections and also SADMIN id has requisite SSE_ROLE granted to it and the default DB for it is SIEBEL_DB on which I am attempting installation. I was able to successfully run the grantuser.sql file that Siebel provides by default to create the roles and logins for SIEBEL, SADMIN and LDAPUSR.
    The problem I am encountering is when I try to perform the Database Server configuration. The system creates the required tables and indexes successfully on the DB. The problem is coming when it tries to Import the base repository that Siebel Server Installation comes with. The error log was for the same.
    I feel that the Siebel Installer is missing some APIs to connect to SQL Server 08.
    The SQL Server is hosted on a system with x64 architecture and the Siebel Server is on a x86 architecture system. I also have Service Pack 1 installed on both the DB Server and Siebel Server. Using third party tools I am able to manipulate the database without any hitches from the Siebel Server system.
    Latest, I have tried reinstalling the virtual environment completely, i.e. started from scratch and had the same issue when I tried the Siebel Database Server installation step. I sure hope I dont have to install SQL 05 and install Siebel Database on it and then do an upgrade of the database.
    Thanks for the info about SARM. It still shows up in the Log file and after it the install fails though.
    Thanks and Regards,
    Tanmay Jain

  • Oracle VM Server 3.0.2 driver errors on install

    I am trying to install OVM Server 3.0.2 on a brand new DELL R415 64 Bit AMD server with 64GB RAM and RAID 1
    and the screen after choosing the keyboard language asks for the location for the packages
    CDROM, Hard Drive, FTP, HTTP
    If I choose CDROM the software states that there is no driver asks me to pick from a long list
    I have selected each one and no success
    If I choose Hard Drive I must select /dev/sda1 /dev/sda2 or /dev/sdb1 (if USB used)
    I also have tried to specify the directory location of the ISO images and set to
    images
    isolinux
    Server
    all with no luck
    The R415 unit has SATA CDROM drive and has worked on a OLE6 install
    I have attempted tin install from DVD, CD, and USB thumb Drive with the same results
    I tried this same CD and installed the OVM Server on a DELL 1950 with no issues
    What can I do?

    I solved my problem with an external DVD USB drive and using the F11 Manual Boot to select the device
    OVM Server 3.0.2 installed
    I hope this helps someone else

  • Flash media server instalation error

    Unable to play video using fresh installation flash media server , showing 10000 , and 2032 error , please see the screen shot.

    FMS3 is officially support on Windows 2003 server &
    RHEL-4 only.

  • SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

    Hello,
    We have a Small Business Server 2003 server that we are trying to migrate to SBS 2011 using the out of the box migration process. After the install, the SBS console showed a couple installation issues - the big one turned out to be "Exchange Server
    2010 cannot be installed".
    Here is the end of 'ExchangeSetup.log' showing various error messages:
    [11/29/2014 23:00:07.0489] [2] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
    [11/29/2014 23:00:07.0490] [2] Beginning processing get-exchangeserver -Identity:'MB-MAINSERVER04' -DomainController:'MB-MAINSERVER04.Contoso.local' -ErrorAction:'SilentlyContinue'
    [11/29/2014 23:00:07.0506] [2] Searching objects "MB-MAINSERVER04" of type "Server" under the root "$null".
    [11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
    [11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
    [11/29/2014 23:00:07.0518] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
    [11/29/2014 23:00:07.0522] [2] Unexpected Error
    [11/29/2014 23:00:07.0522] [2] The operation couldn't be performed because object 'MB-MAINSERVER04' couldn't be found on 'MB-MAINSERVER04.Contoso.local'.
    [11/29/2014 23:00:07.0523] [2] Ending processing get-exchangeserver
    [11/29/2014 23:00:07.0523] [1] Executing:
    if ($server -eq $null)
    new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
    [11/29/2014 23:00:07.0545] [2] Active Directory session settings for 'New-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
    [11/29/2014 23:00:07.0545] [2] Beginning processing new-exchangeserver -DomainController:'MB-MAINSERVER04.Contoso.local' -Name:'MB-MAINSERVER04'
    [11/29/2014 23:00:07.0599] [2] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
    [11/29/2014 23:00:07.0600] [2] Ending processing new-exchangeserver
    [11/29/2014 23:00:07.0607] [1] The following 1 error(s) occurred during task execution:
    [11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
    [11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroup()
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroupId()
    at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
    at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
    at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
    [11/29/2014 23:00:07.0609] [1] [ERROR] The following error was generated when "$error.Clear();
    if ($server -eq $null)
    new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
    " was run: "Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.".
    [11/29/2014 23:00:07.0609] [1] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
    [11/29/2014 23:00:07.0609] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [11/29/2014 23:00:07.0610] [1] Setup is stopping now because of one or more critical errors.
    [11/29/2014 23:00:07.0610] [1] Finished executing component tasks.
    [11/29/2014 23:00:07.0618] [1] Ending processing Install-BridgeheadRole
    [11/29/2014 23:00:07.0626] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    [11/29/2014 23:00:07.0633] [0] End of Setup
    [11/29/2014 23:00:07.0633] [0] **********************************************
    [11/29/2014 23:39:03.0429] [0] **********************************************
    [11/29/2014 23:39:03.0435] [0] Starting Microsoft Exchange Server 2010 Setup
    [11/29/2014 23:39:03.0435] [0] **********************************************
    [11/29/2014 23:39:03.0456] [0] Local Time Zone: (UTC-08:00) Pacific Time (US & Canada).
    [11/29/2014 23:39:03.0457] [0] Operating System version: Microsoft Windows NT 6.1.7600.0.
    [11/29/2014 23:39:03.0469] [0] Setup version: 14.1.438.0.
    [11/29/2014 23:39:03.0473] [0] Logged on user: Contoso2K3\Administrator.
    [11/29/2014 23:39:06.0763] [0] Command Line Parameter Name='mode', Value='Install'.
    [11/29/2014 23:39:06.0776] [0] ExSetupUI was started with the following command: '-mode:install'.
    [11/29/2014 23:39:07.0413] [0] Setup is choosing the domain controller to use
    [11/29/2014 23:39:07.0730] [0] Setup is choosing a local domain controller...
    [11/29/2014 23:39:08.0459] [0] Setup has chosen the local domain controller MB-MAINSERVER04.Contoso.local for initial queries
    [11/29/2014 23:39:08.0747] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use MB-MAINSERVER04.Contoso.local
    [11/29/2014 23:39:08.0748] [0] Setup is choosing a global catalog...
    [11/29/2014 23:39:08.0758] [0] Setup has chosen the global catalog server MB-MAINSERVER04.Contoso.local.
    [11/29/2014 23:39:08.0819] [0] Setup will use the domain controller 'MB-MAINSERVER04.Contoso.local'.
    [11/29/2014 23:39:08.0820] [0] Setup will use the global catalog 'MB-MAINSERVER04.Contoso.local'.
    [11/29/2014 23:39:08.0823] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
    [11/29/2014 23:39:08.0830] [0] Exchange organization container for the organization is 'CN=Contoso2K3,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
    [11/29/2014 23:39:08.0867] [0] Setup will search for an Exchange Server object for the local machine with name 'MB-MAINSERVER04'.
    [11/29/2014 23:39:08.0914] [0] No Exchange Server with identity 'MB-MAINSERVER04' was found.
    [11/29/2014 23:39:09.0061] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
    [11/29/2014 23:39:09.0062] [0] The following datacenter roles are unpacked:
    [11/29/2014 23:39:09.0064] [0] The following roles are installed: AdminToolsRole
    [11/29/2014 23:39:09.0066] [0] The local server has some Exchange files installed.
    [11/29/2014 23:39:09.0320] [0] Setup will use the path 'C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1' for installing Exchange.
    [11/29/2014 23:39:09.0332] [0] The installation mode is set to: 'Install'.
    [11/29/2014 23:39:13.0558] [0] An Exchange organization with name 'Contoso2K3' was found in this forest.
    [11/29/2014 23:39:13.0560] [0] Active Directory Initialization status : 'True'.
    [11/29/2014 23:39:13.0561] [0] Schema Update Required Status : 'False'.
    [11/29/2014 23:39:13.0562] [0] Organization Configuration Update Required Status : 'False'.
    [11/29/2014 23:39:13.0563] [0] Domain Configuration Update Required Status : 'False'.
    [11/29/2014 23:39:13.0564] [0] The locally installed version is 14.1.218.15.
    [11/29/2014 23:39:13.0565] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
    [11/29/2014 23:39:13.0920] [0] Applying default role selection state
    [11/29/2014 23:39:13.0961] [0] Setup is determining what organization-level operations to perform.
    [11/29/2014 23:39:13.0962] [0] Because the value was specified, setup is setting the argument OrganizationName to the value Contoso2K3.
    [11/29/2014 23:39:13.0963] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V14\'.
    [11/29/2014 23:39:13.0972] [0] InstallModeDataHandler has 0 DataHandlers
    [11/29/2014 23:39:13.0972] [0] RootDataHandler has 1 DataHandlers
    [11/29/2014 23:39:15.0491] [0] Setup encountered an exception when trying to access the setup state file: Could not find file 'C:\ExchangeSetupLogs\exchangeInstallState.xml'.
    [11/29/2014 23:39:26.0117] [0] End of Setup
    [11/29/2014 23:39:26.0117] [0] **********************************************
    I should add that the source server's AD configuration might not be perfect due to this being the second attempt at a SBS 2011 migration install.
    I'd be grateful for any help I can get on this as SBS migration has been plauged with multiple setbacks already. I really need to get this done! ;)
    Thanks,
    Voon

    Thank you Larry and Al for your replies.
    I used the 'official' migration
    guide plus this page (http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/)
    as my migration references. The SBS migration prep tool gave no errors on the source server when I ran it.
    I have a full system drive image plus a a system state backup from before migration. Though I am very loathed to rollback the migration and attempt a new one - again. I will do some searching to see if I can resolve the Exchange server problem and continue
    the migration/installation. If not, then its a system state restore for me. One of Al's links had a resource for doing a thorough check of AD - which something I'd run if I have to another migration attempt.
    I am also really tempted to open up a paid MS support ticket for them to help me fix this problem. :)

  • (EPG Install) Error while loading image

    Hi,
    I am facing "ORA-22288: file or LOB operation FILEOPEN failed" error while running apex_epg_config step. But all the steps before that (i.e. APEX Install [@apexins users users temp /i/] and change admin password) went all fine.
    I am trying to install APEX 4.1 on "Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production".
    I went through [url https://forums.oracle.com/forums/thread.jspa?messageID=9673913]this thread. But I am not passing /apex directory (apex directory is under "C:/Ash/Technical/Database/Oracle/apex4.1") , here is the outcome:
    C:\Ash\Technical\Database\Oracle\apex4.1\apex>
    11:33:41 sys@dev10db> @apex_epg_config.sql C:/Ash/Technical/Database/Oracle/apex4.1
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.21
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.03
    Directory created.
    Elapsed: 00:00:00.03
    declare
    ERROR at line 1:
    ORA-22288: file or LOB operation FILEOPEN failed
    No such file or directory
    ORA-06512: at "SYS.XMLTYPE", line 296
    ORA-06512: at line 18
    Elapsed: 00:00:00.04
    Commit complete.
    Elapsed: 00:00:00.00
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:01.14
    declare
    ERROR at line 1:
    ORA-31001: Invalid resource handle or path name "/images"
    ORA-06512: at "XDB.DBMS_XDB", line 473
    ORA-06512: at line 37
    Elapsed: 00:00:00.17
    timing for: Load Images
    Elapsed: 00:00:01.42
    Session altered.
    Elapsed: 00:00:00.00
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.48
    Commit complete.
    Elapsed: 00:00:00.01
    Session altered.
    Elapsed: 00:00:00.01
    Directory dropped.
    Elapsed: 00:00:00.07I am installing from my windows XP, but the db server is on Linux.
    Error above (line 18) is actually on this line of "apex_epg_config_core.sql" (my db charset is UTF8)
    filelist_xml xmltype := xmltype(bfilename(upload_directory_name,file_list),nls_charset_id('AL32UTF8'));
    The error clearly suggest that the there is an issue with access my directory or file in that directory.
    And I believe the 2nd error "ORA-31001: Invalid resource handle or path name "/images"", will go itself once the first one is resolved.
    I went through the documentation and other forum threads, but I am stuck with this EPG install, it may be very silly thing that I may be missing, but any help in this matter would be highly appreciated.
    Thanks,
    Ash
    Edited by: ash0602 on Sep 5, 2011 5:19 PM

    Thanks Andy and Kiran for taking time to respond.
    Andy, "@apex_epg_config.sql C:/Ash/Technical/Database/Oracle/" will not solve the problem, neither changing directory's name from apex4.1 to apex_4.1_en, as my directory structure till images is: "C:\Ash\Technical\Database\Oracle\apex4.1\apex\images".
    Kiran, sorry but I do not understand the difference between what I have written what you mentioned above.
    Though I understood the issue, when you see the apex underlying code (apex_epg_config_core.sql) it is actually creating a directory object ('APEX_IMAGES') in the database. While I was trying to refer the directory on my local windows PC ('C:\Ash\Technical\Database\Oracle\apex4.1\apex\images'). I then logged into the LINUX server and ran the command and it all went fine, see the response below:
    SQL> @apex_epg_config /opt/oracle/product/11.2.0/db1
    PL/SQL procedure successfully completed.
    PL/SQL procedure successfully completed.
    old   1: create directory APEX_IMAGES as '&1/apex/images'
    new   1: create directory APEX_IMAGES as '/opt/oracle/product/11.2.0/db1/apex/images'
    Directory created.
    old  47:     if '&IMGUPG' != '' then
    new  47:     if '' != '' then
    old  48:         l_mv_folder := '&IMGUPG';
    new  48:         l_mv_folder := '';
    PL/SQL procedure successfully completed.
    Commit complete.
    PL/SQL procedure successfully completed.
    PL/SQL procedure successfully completed.
    timing for: Load Images
    Elapsed: 00:00:31.78
    Session altered.
    PL/SQL procedure successfully completed.
    Commit complete.
    Session altered.
    Directory dropped.Though I moved 1 step forward, but my apex login page (http://<server>:8080/apex/apex_admin => redirected to http://<server>:8080/apex/f?p=4550:10:<session>) refuse to come up as it is now showing "[url https://forums.oracle.com/forums/thread.jspa?threadID=1112378]apex is undefined" error.
    I did the installation as [@apexins users users temp /i/] mentioned in the docs, and this is first install not the upgrade.
    Any help on this ['apex' is undefined] (javascript error) would be really helpful.
    Thanks,
    Ash

Maybe you are looking for