Veritas Netbackup Client Installed on Solaris 10 Zone Unable to Work

Hi
I am having problems with Veritas Netbackup client which had been installed on a Solaris 10 zone only. We are using Veritas Netbackup server which is installed on a Windows 2000 server and the NBU server is unable to add the new client for backup.
The way I installed the NBU client was using the manual method where I installed directly on the zone. The zone I've created is a full root zone and the installation seems to be successful.
Somehow the NBU server just can't see the new client. Do I need to install the client in the global zone to make it work? Is there any checks I can do to make sure I have installed the client correctly and that the services are running in the solaris 10 zone side? Any kind of help would be much appreciated.
Thanks
Xavier

Hi mcbrune1
I've check on the services in the client and all 4 services were up and running. Than I realized that this client was hardened a few weeks back. So I checked on the /etc/hosts.allow file and added an entry to allow the Master server to communicate using bpcd.
Now the Master server is able to see the client and everything seems to be working. Thanks for your help.
Cheers

Similar Messages

  • Veritas Netbackup Client 6 for Solaris 10

    Hi
    Can anyone tell me where I can download Veritas Netbackup client for Solaris 10. We had the netbackup client for solaris 9 running but then we did a clean install of Solaris 10.
    The netbackup server is running on an AIX server and I want to push the solaris client from there. We have separate license for all our clients running the netbackup agent but the netbackup server does not have the latest solaris 10 client. The AIX server do not have internet access, so I want to download the solaris 10 netback agent and put on the netbackup server.
    Need to know the URL where I can download the netbackup agent for Solaris 10.
    Many Thanks
    Pioneer

    Hi mcbrune1
    I've check on the services in the client and all 4 services were up and running. Than I realized that this client was hardened a few weeks back. So I checked on the /etc/hosts.allow file and added an entry to allow the Master server to communicate using bpcd.
    Now the Master server is able to see the client and everything seems to be working. Thanks for your help.
    Cheers

  • Solaris Branded Zones, Unable to reboot/Halt

    Hi People,
    Hoping someone can help. Im running Solaris 10 on a Sun Workstation Ultra 45. I have two disks. One disk has the default install of solaris 10 all updated to the latest patches.The second disk is mounted as /zones and holds each of the zones on ZFS. I have then downloaded and installed successfully Solaris 8 and Solaris 9 and Solaris 10 zones. So I have 3 zones.
    The problem I am facing is I can boot up all 3 zones fine and they work great, however when I halt or reboot either Solaris 8 or solaris 9, they never come back up. I try and zlogin to them and telnet and ssh and they are totally unresponsive and quite literally dont boot. I have tried to pkill -9 -z zonename ; umount /zonesfilesystem; zpool clear and even rebooted the Global zone. Still will not come up. The only way they will boot after being shutdown is if i shutdown the global zones and turn the server off and back on.
    Solaris 10 Zone boots up and down fine with no isses. I have tried this on both UFS and ZFS thinking it might be a file lock issue. Still unable to reboot or halt a zone and bring it back up.
    Any help please :)
    Thanks in advance.

    When they are unable to come back up, what does 'zoneadm list -cv' say? If the state of the zone is "down" or "shutting_down", you can probably benefit from the fix for:
    7038404 outstanding zone references should not cause zone_destroy(2) to hang
    This is available in 147440-05 (sparc) / 147441-05 (x86) or later.

  • Unable to install a Solaris OS in a Single disk slice

    Hi,
    We are unable to install the Solaris-OS on a single slice disk.
    We found that, only "Solaris 10 10/08 (U6)" release can support the single slice disk installation, prior release are not. Is it true ?
    We found it from "LDoms Community Cookbook " , from given link
    http://wikis.sun.com/display/SolarisLogicalDomains/Section+2+-VirtualDevices
    Paragraph is
    " Before Solaris 10 10/08 (U6), when a backend is exported to a domain as a single slice disk, it will appear in that domain as a disk with a single partition (s0). Such a disk is not visible with the format(1m) command and its partition table can not be changed. A single slice disk will not be visible from the Solaris installer and can not be select as a disk device on which Solaris can be installed. "
    Our Configuration are
    sc> showhost
    System Firmware 6.6.4 Sun Blade[TM] T6300 2008/07/01 02:03
    Host flash versions:
    OBP 4.28.9 2008/06/30 21:26
    Hypervisor 1.6.4 2008/06/06 04:57
    Sun Blade T6300 Server Module POST 4.28.6 2008/05/23 12:35
    -bash-3.00# cat /etc/release
    Solaris 10 8/07 s10s_u4wos_12b SPARC
    Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.
    Use is subject to license terms.
    Assembled 16 August 2007
    We Installed a 127127-11 patch also.
    -bash-3.00# ldm -V
    Logical Domain Manager (v 1.0.3)
    Hypervisor control protocol v 1.1
    Using Hypervisor MD v 1.1
    System PROM:
    Hypervisor v. 1.6.4 @(#)Hypervisor 1.6.4 2008/06/06 04:57\015
    OpenBoot v. 4.28.9 @(#)OBP 4.28.9 2008/06/30 21:26
    Use below command to add single slice disk
    *# ldm add-vdsdev options=slice /dev/dsk/c0t1d0s3 vol3@primary-vds0*
    Getting error in between installation,
    ERROR: No disks found
    - Check to make sure disks are cabled and powered up
    Please help us to, resolve this issue. Thanks a lot.
    Best Regards,
    Parvez Memon.

    Hi,
    Whenever i try to installed the patch 137137-09, it required a below patch
    0 For patch 137137-09, required patch 138866-01 does not exist.
    And try this then
    # patchadd 138866-01
    The following requested patches will not be installed because
    the packages they patch are not installed on this system.
    0 No Packages from patch 138866-01 are installed on the system.
    No patches to install.
    I am not able to install this patch 138866-01, even i try with 138866-02 but not success.
    Thanks for your reply, please help to resovle the same.
    Regards,
    Parvz Memon

  • Can EM12c Cloud Control agent be installed in a solaris zone?

    Can EM12c Cloud Control agent be installed in a solaris zone?
    If so, are Solaris 8 and Solaris 9 zones supported?
    thanks

    Yes we can...
    Solaris 9 is supported...I have installed agents on solaris 9 and 10

  • Client Install Fails - Unable to get Win32_OperatingSystem object

    I have a PC that won't install the SCCM client via Client Push.  In the CCM.Log file on the site server, it connects to the IPC$ and admin$ shares using my client installation account, but then it comes back with this error:
    ---> Unable to get Win32_OperatingSystem object from WMI on remote machine "PCNAME", error = 0x80080005.
    I know that error means that access was denied to WMI, and I verified that when I run wbemtest manually (using the same client installation account), I can connect to the root\cimv2 object on that PC but when I try to enumerate the instances of the Win32_OperatingSystem object, I get the same error.
    I also tried using Computer Management applet (remotely - I have no local access to this PC) to look at the WMI Control properties.  Again, I get the same access denied error so I can't check/change the security permissions that way.
    I have verified that my client installation account is in the local Administrators group of the PC.  I've already tried rebuilding the WMI repository - that worked but it didn't fix the access issue.  I know I can install the client manually but I'm guessing I'd still have a problem with inventories, etc. that are dependent on access to that WMI object.  Any suggestions about how to go about fixing the WMI access issue?
    Thanks so much, --Jo

    Finally getting back to this issue after vacaton... sigh.
    I got a little further.  I took client push out of the mix and ran ccmsetup.exe locally on the PC.  This time the client installation ran.  However, I'm still getting a similar error from the client itself and the client is not talking to the site.  After the client was installed, only about 10 of the log files showed up in system32\ccm\logs. 
    ccmexec.log shows this error: 
    Endpoint'PolicyAgent_PolicyEvaluator' return 0x80070057 from event notification
    PolicyAgentProvider.log has these lines repeating:
    Failed to create actual config class for 'CCM_RootCACertificates' 
    Failed to update namespace 'Machine' (80041002) 
    Successfully updated namespace 'DefaultMachine' 
    Successfully updated namespace 'DefaultUser' 
    Failed to create actual config class for 'CCM_MulticastConfig' 
    Failed to update namespace 'Machine' (80041002) 
    PolicyEvaluator.log has this error:
    Received notification that Local policy has changed. 
    Failed to trigger Machine settings update (80070057)
    SrcUpdateManager has these errors:
    Instance of CCM_SourceUpdateClientConfig doesn't exist in WMI
    Failed to get instance of CCM_SourceUpdateHistory, error 80041002
    ClientIDManagerStartup.log has these errors:
    GetSystemEnclosureInfo failed (0x80080005)
    ComputeHardwareID failed (0x80080005).
    RegTask: Failed to create registration request body. Error: 0x80080005
    The rest of the logs that exist (LocationServices, StatusAgent, ClientLocation, RemCtrl, and setuppolicyevaluator) appear to be OK. 
    These seem to all be WMI-related errors/issues, but I can't find any specific information on any SCCM/SMS websites/forums that address these particular errors in these particular log files.  I've tried rebuilding the repository (several times), I've done the regsvr stuff as discussed above, etc. 
    I ran WMIDIAG next.  It ran for a little less than two hours - not sure if that's normal or not, but the log file continued to update the entire time.  Now I have this log file and I'm not sure what to do with the issues I found.  I'm looking at the WMI REPORT: BEGIN section...  I see instructions that make sense for most of the errors.  However, the section of log file below shows the area that is most likely causing issues for SCCM because it is the same error I get on the client install.  I have no idea how to fix this stuff - any help would be appreciated:
    31997 14:20:05 (1) !! ERROR: WMI ENUMERATION operation errors reported: .......................................... 33 ERROR(S)!
    31998 14:20:05 (0) ** - ROOT/CIMV2, InstancesOfAsync, CIM_USBDevice, 0x80080005 - .
    31999 14:20:05 (0) ** - ROOT/CIMV2, InstancesOfAsync, CIM_USBHub, 0x80080005 - .
    32000 14:20:05 (0) ** - ROOT/CIMV2/SMS, InstancesOfAsync, SMS_Class_Template, 0x80041011 - (WBEM_E_PROVIDER_NOT_FOUND) Provider referenced in the schema does not have a corresponding registration.
    32001 14:20:05 (0) ** - Root/Default, InstancesOf, SystemRestore, 0x80080005 - Server execution failed.
    32002 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_Process, 0x80080005 - Server execution failed.
    32003 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_OperatingSystem, 0x80080005 - Server execution failed.
    32004 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_ComputerSystem, 0x80080005 - Server execution failed.
    32005 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_Service, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32006 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_Bios, 0x80080005 - Server execution failed.
    32007 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_Tcpip_IP, 0x80080005 - Server execution failed.
    32008 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_Tcpip_TCP, 0x80080005 - Server execution failed.
    32009 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_Tcpip_UDP, 0x80080005 - Server execution failed.
    32010 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_Tcpip_ICMP, 0x80080005 - Server execution failed.
    32011 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_Cache, 0x80080005 - Server execution failed.
    32012 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_Memory, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32013 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_Objects, 0x80080005 - Server execution failed.
    32014 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_PagingFile, 0x80080005 - Server execution failed.
    32015 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_Processor, 0x80080005 - Server execution failed.
    32016 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfOS_System, 0x80080005 - Server execution failed.
    32017 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfProc_Process, 0x80080005 - Server execution failed.
    32018 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfRawData_PerfProc_Thread, 0x80080005 - Server execution failed.
    32019 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_Tcpip_IP, 0x80080005 - Server execution failed.
    32020 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_Tcpip_TCP, 0x80080005 - Server execution failed.
    32021 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_Tcpip_UDP, 0x80080005 - Server execution failed.
    32022 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_Tcpip_ICMP, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32023 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_Cache, 0x80080005 - Server execution failed.
    32024 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_Memory, 0x80080005 - Server execution failed.
    32025 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_Objects, 0x80080005 - Server execution failed.
    32026 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_PagingFile, 0x80080005 - Server execution failed.
    32027 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_Processor, 0x80080005 - Server execution failed.
    32028 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfOS_System, 0x80080005 - Server execution failed.
    32029 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfProc_Process, 0x80080005 - Server execution failed.
    32030 14:20:05 (0) ** - Root/CIMv2, InstancesOf, Win32_PerfFormattedData_PerfProc_Thread, 0x80080005 - Server execution failed.
    32031 14:20:05 (0) **
    32032 14:20:05 (1) !! ERROR: WMI EXECQUERY operation errors reported: ............................................ 17 ERROR(S)!
    32033 14:20:05 (0) ** - Root/Default, SELECT * FROM SystemRestore, 0x80080005 - Server execution failed.
    32034 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_LogicalDisk WHERE FreeSpace > 10000000 AND DriveType = 3, 0x80080005 - Server execution failed.
    32035 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_PageFileUsage, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32036 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_BIOS WHERE Version IS NOT NULL, 0x80080005 - Server execution failed.
    32037 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_NetworkAdapter WHERE AdapterType IS NOT NULL AND AdapterType != "Wide Area Network (WAN)" AND Description != "Packet Scheduler Miniport", 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32038 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_Processor WHERE Name IS NOT NULL, 0x80080005 - Server execution failed.
    32039 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_DiskDrive, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32040 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_ComputerSystem, 0x80080005 - Server execution failed.
    32041 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_DiskPartition, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32042 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_LogicalDisk WHERE Description != "Network Connection", 0x80080005 - Server execution failed.
    32043 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_SoundDevice, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32044 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_VideoController, 0x80080005 - Server execution failed.
    32045 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_USBController, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32046 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_DesktopMonitor, 0x80080005 - Server execution failed.
    32047 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_PointingDevice WHERE Status = "OK", 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32048 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_Keyboard, 0x80080005 - Server execution failed.
    32049 14:20:05 (0) ** - Root/CIMv2, SELECT * FROM Win32_SystemDriver WHERE StartMode != "Disabled", 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    32050 14:20:05 (0) **
    32051 14:20:05 (0) ** WMI PUT operations: ........................................................................ OK.
    32052 14:20:05 (0) ** WMI DELETE operations: ..................................................................... OK.
    32053 14:20:05 (0) ** WMI GET VALUE operations: .................................................................. OK.
    32054 14:20:05 (0) ** WMI static instances retrieved: ............................................................ 1541.
    32055 14:20:05 (0) ** WMI dynamic instances retrieved: ........................................................... 0.
    32056 14:20:05 (0) ** WMI instances request cancellations (to limit performance impact): ......................... 0.
    32057 14:20:05 (0) **
    32058 14:20:05 (0) ** 38 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
    32059 14:20:05 (0) **
    32060 14:20:05 (0) ** 1 error(s) 0x80041011 - (WBEM_E_PROVIDER_NOT_FOUND) Provider referenced in the schema does not have a corresponding registration
    32061 14:20:05 (0) ** => This error is typically due to the following major reasons:
    32062 14:20:05 (0) **    - The application queried by the WMI provider is not installed, not available or not running
    32063 14:20:05 (0) **      at the time of the request was made. This error can also be generated because
    32064 14:20:05 (0) **      the application supporting the providers has been uninstalled.
    32065 14:20:05 (0) **    - The WMI provider binary files are not accessible (e.g. access denied ACL).
    32066 14:20:05 (0) **    - A WMI provider registration problem at the CIM level (MOFCOMP.EXE) or at the COM level (REGSVR32.EXE).
    32067 14:20:05 (0) **      You must re-register the WMI provider by recompiling its associated MOF file with MOFCOMP.EXE
    32068 14:20:05 (0) **    Note: - If the WMI provider DLL CIM and COM registrations are correct, this error can
    32069 14:20:05 (0) **            be returned because the provider has a dependency on another DLL that cannot be
    32070 14:20:05 (0) **            loaded (missing or bad DLL)
    32071 14:20:05 (0) **          - Dependencies can be found with the DEPENDS.EXE tool coming with the
    32072 14:20:05 (0) **            Windows XP and Windows 2003 Support Tools. The command line is as follows:
    32073 14:20:05 (0) **            e.g. DEPENDS.EXE <PATH><Provider.DLL>
    32074 14:20:05 (0) ** => If the software has been de-installed intentionally, then this information must be
    32075 14:20:05 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove the provider
    32076 14:20:05 (0) **    registration data and its set of associated classes.
    32077 14:20:05 (0) ** => To correct this situation, you can:
    32078 14:20:05 (0) **    - Install or start the application supporting these providers.
    32079 14:20:05 (0) **    - Register the providers in CIM (MOFCOMP) or DCOM (REGSVR32).
    32080 14:20:05 (0) **    Note: In this case the provider should also be listed in the 'missing WMI
    32081 14:20:05 (0) **          provider DCOM registrations' or in the 'missing WMI provider files' section.
    32082 14:20:05 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from 'C:\WINDOWS\SYSTEM32\WBEM\'
    32083 14:20:05 (0) **          may not solve the problem as the DLL supporting the WMI class(es)
    32084 14:20:05 (0) **          can be located in a different folder.
    32085 14:20:05 (0) **          You must refer to the class name to determine the software delivering the related DLL.
    32086 14:20:05 (0) **
    Thanks, --Jo

  • Unable to install open solaris

    Dear all,
    We have sun sparc T5220 server with solaris 10/U7.we are trying to install open solaris.But geting error can not open boot device,using same cd we are able to install normal sparc server.please help me.
    Regards
    kk

    Uninstall iTunes and all related components. You may need to do this more than once.
    (99935)

  • Sun c4 and veritas netbackup 6 mp4 installation

    Hello, please help me!
    We have SAN with 2 st6140 and 3 broacade 200e switch. One site is: two 200e and 3 linux hosts, other site is: v240 server (one FC port) with solaris preinstalled and installed Veritas NetBackup mp4, 1 200e switch, Sun C4 library whith FC ports.
    On second site I connected C4 FC host port to the 200e swith, FC port on v240 also connected to the 200e switch.
    Can you describe me a common porcedure to configure correctly a server with Veritas and C4?
    I cant add "device" in veritas Administration console now, because it cant see nothing.
    How i have to connect C4 and Veritas server to SAN correctly ?

    create a soft zone on your brocade , with your C4's FCs ports and your Netbackup Master server, for Netbackup use version 6.5 , not 6.0
    once you activate your zone, run cfgadm -al -o show_FCP_dev, you should be able to see your paths, one path or more paths from your server, two or more from your C4 libraries' fabrics, netbackuop 6.5 is very clean and installed , to be able to recognize your drivers ...once the software installed, go to your GUI, to configure device...
    Also, use the latest version of Solaris10 on this..it is much cleaner to work with netbackup 6.5

  • Zfs core dumps in Solaris Zones after patchcluster installation

    Hi
    I've installed the recommended patch cluster for Solaris 10 (SPARC) on my T2000 Server.
    Now after the reboot all the Solaris Zones (got about 10 of them) instantly do zfs core dumps when their booted.
    Some Output:
    Dec 15 15:34:43 XXXXX genunix: NOTICE: core_log: zfs[1711] core dumped: /var/core/core_XXXXXX_zfs_0_0_1292423682_1711
    bash-3.00# svcs
    STATE STIME FMRI
    online 13:58:50 svc:/system/svc/restarter:default
    online 13:58:51 svc:/system/filesystem/root:default
    online 13:58:51 svc:/network/loopback:default
    online 13:58:53 svc:/network/pfil:default
    online 13:58:54 svc:/system/installupdates:default
    online 13:58:55 svc:/system/boot-archive:default
    online 13:58:56 svc:/network/physical:default
    online 13:58:57 svc:/system/filesystem/usr:default
    online 13:58:57 svc:/system/identity:node
    online 13:58:58 svc:/system/device/local:default
    online 13:58:58 svc:/system/keymap:default
    online 13:58:58 svc:/milestone/devices:default
    online 13:58:58 svc:/system/filesystem/minimal:default
    online 13:58:58 svc:/system/rmtmpfiles:default
    online 13:58:58 svc:/system/cryptosvc:default
    online 13:58:59 svc:/system/identity:domain
    online 13:58:59 svc:/system/name-service-cache:default
    online 13:58:59 svc:/system/coreadm:default
    online 13:58:59 svc:/network/ipsec/ipsecalgs:default
    online 13:58:59 svc:/application/print/ppd-cache-update:default
    online 13:58:59 svc:/network/ipsec/policy:default
    online 13:59:00 svc:/milestone/network:default
    online 13:59:00 svc:/network/initial:default
    online 13:59:00 svc:/system/manifest-import:default
    online 13:59:00 svc:/network/service:default
    online 13:59:00 svc:/milestone/single-user:default
    online 13:59:00 svc:/network/dns/client:default
    online 13:59:00 svc:/network/routing-setup:default
    online 13:59:00 svc:/milestone/name-services:default
    online 13:59:03 svc:/milestone/sysconfig:default
    online 13:59:03 svc:/system/utmp:default
    online 13:59:03 svc:/system/console-login:default
    offline 13:58:51 svc:/system/sysidtool:net
    offline 13:58:51 svc:/network/rpc/bind:default
    offline 13:58:51 svc:/system/sysidtool:system
    offline 13:58:52 svc:/network/nfs/status:default
    offline 13:58:52 svc:/network/nfs/nlockmgr:default
    offline 13:58:52 svc:/network/nfs/cbd:default
    offline 13:58:52 svc:/network/nfs/mapid:default
    offline 13:58:52 svc:/network/inetd:default
    offline 13:58:52 svc:/network/nfs/client:default
    offline 13:58:52 svc:/system/filesystem/autofs:default
    offline 13:58:53 svc:/system/system-log:default
    offline 13:58:53 svc:/network/smtp:sendmail
    offline 13:58:53 svc:/system/cron:default
    offline 13:58:53 svc:/milestone/multi-user:default
    offline 13:58:54 svc:/application/management/snmpdx:default
    offline 13:58:54 svc:/application/management/dmi:default
    offline 13:58:54 svc:/application/management/seaport:default
    offline 13:58:54 svc:/network/ssh:default
    offline 13:58:54 svc:/milestone/multi-user-server:default
    offline 13:58:54 svc:/application/font/fc-cache:default
    offline 13:58:55 svc:/application/management/sma:default
    offline 13:58:58 svc:/system/sac:default
    offline 13:59:00 svc:/network/shares/group:default
    offline 13:59:00 svc:/system/boot-archive-update:default
    maintenance 15:34:43 svc:/system/filesystem/local:default
    uninitialized 13:58:52 svc:/network/rpc/gss:default
    uninitialized 13:58:54 svc:/application/font/stfsloader:default
    uninitialized 13:58:55 svc:/network/rpc/rstat:default
    uninitialized 13:58:55 svc:/application/print/rfc1179:default
    uninitialized 13:58:55 svc:/application/x11/xfs:default
    uninitialized 13:58:55 svc:/network/finger:default
    uninitialized 13:58:55 svc:/network/ftp:default
    uninitialized 13:58:56 svc:/network/login:rlogin
    uninitialized 13:58:56 svc:/network/nfs/rquota:default
    uninitialized 13:58:56 svc:/network/rpc/rusers:default
    uninitialized 13:58:56 svc:/network/rpc/smserver:default
    uninitialized 13:58:57 svc:/network/security/ktkt_warn:default
    uninitialized 13:58:57 svc:/network/shell:default
    uninitialized 13:58:57 svc:/network/telnet:default
    uninitialized 13:58:58 svc:/network/rpc-100235_1/rpc_ticotsord:default
    uninitialized 13:58:58 svc:/network/rpc/cde-calendar-manager:default
    uninitialized 13:58:59 svc:/network/rpc/cde-ttdbserver:tcp
    bash-3.00# svcs -x
    svc:/system/filesystem/local:default (local file system mounts)
    State: maintenance since Wed Dec 15 15:34:43 2010
    Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
    See: http://sun.com/msg/SMF-8000-KS
    See: /var/svc/log/system-filesystem-local:default.log
    Impact: 24 dependent services are not running. (Use -v for list.)
    svc:/network/rpc/gss:default (Generic Security Service)
    State: uninitialized since Wed Dec 15 13:58:52 2010
    Reason: Restarter svc:/network/inetd:default is not running.
    See: http://sun.com/msg/SMF-8000-5H
    See: gssd(1M)
    Impact: 11 dependent services are not running. (Use -v for list.)
    svc:/network/rpc/rstat:default (kernel statistics server)
    State: uninitialized since Wed Dec 15 13:58:55 2010
    Reason: Restarter svc:/network/inetd:default is not running.
    See: http://sun.com/msg/SMF-8000-5H
    See: rpc.rstatd(1M)
    See: rstatd(1M)
    Impact: 1 dependent service is not running. (Use -v for list.)
    bash-3.00# cat /var/svc/log/system-filesystem-local:default.log
    [ Jul 10 03:41:35 Enabled. ]
    [ Jul 10 03:43:45 Rereading configuration. ]
    [ Jul 10 03:44:17 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 03:44:18 Method "start" exited with status 0 ]
    [ Jul 10 12:44:36 Enabled. ]
    [ Jul 10 12:44:45 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 12:44:45 Method "start" exited with status 0 ]
    [ Jul 10 12:45:03 Enabled. ]
    [ Jul 10 12:45:09 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 12:45:09 Method "start" exited with status 0 ]
    [ Jul 10 13:54:39 Enabled. ]
    [ Jul 10 13:54:46 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 13:54:46 Method "start" exited with status 0 ]
    [ Jul 18 12:34:19 Enabled. ]
    [ Jul 18 12:34:27 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 18 12:34:27 Method "start" exited with status 0 ]
    [ Jul 18 17:29:08 Enabled. ]
    [ Jul 18 17:29:15 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 18 17:29:15 Method "start" exited with status 0 ]
    [ Jul 19 11:13:34 Enabled. ]
    [ Jul 19 11:13:42 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:13:42 Method "start" exited with status 0 ]
    [ Jul 19 11:32:23 Enabled. ]
    [ Jul 19 11:32:30 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:32:31 Method "start" exited with status 0 ]
    [ Jul 19 11:57:06 Enabled. ]
    [ Jul 19 11:57:13 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:57:13 Method "start" exited with status 0 ]
    [ Jul 19 12:40:05 Enabled. ]
    [ Jul 19 12:40:12 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 12:40:12 Method "start" exited with status 0 ]
    [ Jul 20 15:51:46 Enabled. ]
    [ Jul 20 15:51:54 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 20 15:51:54 Method "start" exited with status 0 ]
    [ Jul 24 11:42:17 Enabled. ]
    [ Jul 24 11:42:25 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 24 11:42:25 Method "start" exited with status 0 ]
    [ Jul 27 12:05:06 Stopping because service disabled. ]
    [ Jul 27 12:05:07 Executing stop method (null) ]
    [ Jul 27 12:13:10 Enabled. ]
    [ Jul 27 12:13:17 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 27 12:13:17 Method "start" exited with status 0 ]
    [ Jul 27 13:10:26 Stopping because service disabled. ]
    [ Jul 27 13:10:26 Executing stop method (null) ]
    [ Jul 27 13:18:19 Enabled. ]
    [ Jul 27 13:18:26 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 27 13:18:26 Method "start" exited with status 0 ]
    [ Jul 31 10:12:31 Enabled. ]
    [ Jul 31 10:12:38 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 31 10:12:39 Method "start" exited with status 0 ]
    [ Aug  7 10:08:52 Stopping because service disabled. ]
    [ Aug  7 10:08:52 Executing stop method (null) ]
    [ Aug  7 10:34:50 Enabled. ]
    [ Aug  7 10:34:57 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  7 10:34:58 Method "start" exited with status 0 ]
    [ Aug  9 09:14:50 Stopping because service disabled. ]
    [ Aug  9 09:14:50 Executing stop method (null) ]
    [ Aug  9 09:55:03 Enabled. ]
    [ Aug  9 09:55:10 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  9 09:55:11 Method "start" exited with status 0 ]
    [ Aug 16 10:46:43 Enabled. ]
    [ Aug 16 10:46:50 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 10:46:50 Method "start" exited with status 0 ]
    [ Aug 16 12:06:56 Enabled. ]
    [ Aug 16 12:07:02 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 12:07:02 Method "start" exited with status 0 ]
    [ Aug 16 13:45:10 Enabled. ]
    [ Aug 16 13:45:16 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 13:45:16 Method "start" exited with status 0 ]
    [ Aug 16 14:36:59 Enabled. ]
    [ Aug 16 14:37:07 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 14:37:07 Method "start" exited with status 0 ]
    [ Aug 16 15:00:40 Enabled. ]
    [ Aug 16 15:00:47 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 15:00:47 Method "start" exited with status 0 ]
    [ Aug 22 16:00:13 Enabled. ]
    [ Aug 22 16:00:21 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 22 16:00:21 Method "start" exited with status 0 ]
    [ Aug 23 09:49:04 Enabled. ]
    [ Aug 23 09:49:10 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 09:49:11 Method "start" exited with status 0 ]
    [ Aug 23 09:49:23 Stopping because service disabled. ]
    [ Aug 23 09:49:23 Executing stop method (null) ]
    [ Aug 23 10:04:13 Enabled. ]
    [ Aug 23 10:04:20 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 10:04:20 Method "start" exited with status 0 ]
    [ Aug 23 10:06:57 Enabled. ]
    [ Aug 23 10:07:04 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 10:07:05 Method "start" exited with status 0 ]
    [ Oct 23 08:43:05 Enabled. ]
    [ Oct 23 08:43:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Oct 23 08:43:14 Method "start" exited with status 0 ]
    [ Nov 21 14:51:50 Enabled. ]
    [ Nov 21 14:51:58 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Nov 21 14:51:59 Method "start" exited with status 0 ]
    [ Nov 29 15:33:19 Enabled. ]
    [ Nov 29 15:33:26 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Nov 29 15:33:27 Method "start" exited with status 0 ]
    [ Dec 18 13:37:35 Enabled. ]
    [ Dec 18 13:37:42 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 18 13:37:42 Method "start" exited with status 0 ]
    [ Dec 19 08:48:07 Enabled. ]
    [ Dec 19 08:48:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:48:14 Method "start" exited with status 0 ]
    [ Dec 19 08:56:07 Enabled. ]
    [ Dec 19 08:56:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:56:14 Method "start" exited with status 0 ]
    [ Dec 19 08:57:41 Enabled. ]
    [ Dec 19 08:57:48 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:57:48 Method "start" exited with status 0 ]
    [ Feb  1 10:39:48 Enabled. ]
    [ Feb  1 10:39:55 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb  1 10:39:56 Method "start" exited with status 0 ]
    [ Feb  8 11:12:50 Enabled. ]
    [ Feb  8 11:12:57 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb  8 11:12:57 Method "start" exited with status 0 ]
    [ Jun  6 10:08:34 Enabled. ]
    [ Jun  6 10:08:44 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jun  6 10:08:46 Method "start" exited with status 0 ]
    [ Aug  8 09:45:48 Enabled. ]
    [ Aug  8 09:46:35 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  8 09:46:36 Method "start" exited with status 0 ]
    [ Aug 14 17:53:59 Enabled. ]
    [ Aug 14 17:54:06 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 14 17:54:06 Method "start" exited with status 0 ]
    [ Aug 14 17:55:20 Enabled. ]
    [ Aug 14 17:55:27 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 14 17:55:27 Method "start" exited with status 0 ]
    [ Aug 18 15:19:17 Enabled. ]
    [ Aug 18 15:19:24 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 18 15:19:24 Method "start" exited with status 0 ]
    [ Aug 29 12:56:48 Enabled. ]
    [ Aug 29 12:56:55 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 29 12:56:55 Method "start" exited with status 0 ]
    [ Oct 13 11:59:43 Enabled. ]
    [ Oct 13 11:59:50 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Oct 13 11:59:51 Method "start" exited with status 0 ]
    [ Feb 26 16:47:00 Enabled. ]
    [ Feb 26 16:47:07 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb 26 16:47:07 Method "start" exited with status 0 ]
    [ Apr 14 15:54:17 Enabled. ]
    [ Apr 14 15:54:24 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Apr 14 15:54:25 Method "start" exited with status 0 ]
    [ Aug 28 08:49:58 Stopping because service disabled. ]
    [ Aug 28 08:49:58 Executing stop method (null) ]
    [ Aug 28 08:52:54 Enabled. ]
    [ Aug 28 08:53:01 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 28 08:53:01 Method "start" exited with status 0 ]
    [ Aug 28 09:08:20 Stopping because service disabled. ]
    [ Aug 28 09:08:20 Executing stop method (null) ]
    [ Sep  1 16:05:36 Enabled. ]
    [ Sep  1 16:06:05 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 16:06:05 Method "start" exited with status 0 ]
    [ Sep  1 19:29:19 Enabled. ]
    [ Sep  1 19:29:27 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 19:29:27 Method "start" exited with status 0 ]
    [ Sep  1 23:04:00 Enabled. ]
    [ Sep  1 23:04:08 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 23:04:08 Method "start" exited with status 0 ]
    [ Sep  2 00:23:41 Stopping because service disabled. ]
    [ Sep  2 00:23:42 Executing stop method (null) ]
    [ Sep  2 00:46:46 Enabled. ]
    [ Sep  2 00:46:53 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  2 00:46:54 Method "start" exited with status 0 ]
    [ Sep 26 12:04:34 Enabled. ]
    [ Sep 26 12:04:41 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep 26 12:04:42 Method "start" exited with status 0 ]
    [ Oct 20 13:05:09 Stopping because service disabled. ]
    [ Oct 20 13:05:10 Executing stop method (null) ]
    [ Oct 20 13:24:01 Enabled. ]
    [ Oct 20 13:24:08 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 20 13:24:09 Method "start" exited with status 0 ]
    [ Oct 21 16:30:59 Enabled. ]
    [ Oct 21 16:31:09 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 16:31:09 Method "start" exited with status 0 ]
    [ Oct 21 16:32:42 Stopping because service disabled. ]
    [ Oct 21 16:32:42 Executing stop method (null) ]
    [ Oct 21 16:42:05 Enabled. ]
    [ Oct 21 16:42:15 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 16:42:15 Method "start" exited with status 0 ]
    [ Oct 21 17:27:37 Enabled. ]
    [ Oct 21 17:27:47 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 17:27:47 Method "start" exited with status 0 ]
    [ Oct 22 11:08:34 Enabled. ]
    [ Oct 22 11:08:43 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 22 11:08:43 Method "start" exited with status 0 ]
    [ Dec  9 09:17:33 Stopping because service disabled. ]
    [ Dec  9 09:17:33 Executing stop method (null) ]
    [ Dec 10 11:47:14 Enabled. ]
    [ Dec 10 11:47:24 Executing start method ("/lib/svc/method/fs-local") ]
    [ Dec 10 11:47:25 Method "start" exited with status 0 ]
    [ Dec 15 10:52:25 Stopping because service disabled. ]
    [ Dec 15 10:52:25 Executing stop method (null) ]
    [ Dec 15 12:42:16 Enabled. ]
    [ Dec 15 12:42:26 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 12:42:28 Method "start" exited with status 95 ]
    [ Dec 15 13:13:19 Enabled. ]
    [ Dec 15 13:13:28 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 13:13:30 Method "start" exited with status 95 ]
    [ Dec 15 13:58:51 Enabled. ]
    [ Dec 15 13:59:00 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 13:59:03 Method "start" exited with status 95 ]
    [ Dec 15 15:34:41 Leaving maintenance because clear requested. ]
    [ Dec 15 15:34:41 Enabled. ]
    [ Dec 15 15:34:41 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 15:34:43 Method "start" exited with status 95 ]
    bash-3.00# /usr/sbin/zfs mount -a
    internal error: Unknown error
    Abort (core dumped)
    Before that I've installed the patch cluster with halted solaris zones which produced following output:
    Application of patches finished : 2010.12.15 12:08:43
    Following patches were applied :
    119254-77 119812-10 125719-31 140159-03 142911-01
    141588-04 119900-11 125731-05 142292-01 142933-02
    142251-02 119906-16 126206-05 141444-09 142909-17
    118666-28 120460-17 126363-08 141500-07 143140-04
    118667-28 121012-03 126365-16 141502-02 143502-01
    118777-16 121308-20 126868-04 141506-09 143506-01
    140860-02 122212-40 127724-02 141514-02 143615-02
    119059-56 122261-03 136998-09 141518-12 143731-01
    119213-23 122675-05 137000-07 141552-03 143733-01
    124628-10 123003-04 137080-05 141558-01 143977-01
    119252-29 123590-12 137147-06 141586-01 144053-04
    119280-23 123893-22 138195-04 141590-02 144106-01
    124188-03 124393-11 138822-07 141874-09 144254-01
    120199-15 124457-02 138826-07 141876-07 144488-04
    119534-19 124630-42 138880-02 142084-04 144492-01
    120272-28 125215-03 139099-04 142397-01 145124-01
    119757-18 125388-03 139620-01 142529-01 145796-01
    119783-15 125555-07
    Following patches were skipped :
    Patches already applied
    120900-04 119063-01 119810-05 123005-07 137093-01
    121133-02 119081-25 119986-03 124444-01 138866-03
    119317-01 119130-33 120061-02 124939-03 137137-09
    121296-01 123611-04 120201-05 124943-01 137871-02
    138215-01 140899-01 120292-02 124997-01 138181-01
    127884-01 122640-05 120329-02 125279-05 138361-01
    118712-23 126897-02 121975-01 125539-06 138373-02
    118918-24 127755-01 120719-02 125891-01 138647-01
    138217-01 125503-02 120830-06 126440-01 141016-01
    119578-30 125547-02 121095-02 126540-02 139555-08
    121453-02 140796-01 121606-04 127127-11 139967-01
    121453-02 120011-14 124171-07 136882-02 140455-01
    121118-16 139520-02 123630-03 137032-01 140563-01
    118833-36 119764-06
    Patches obsoleted by one or more patches already applied
    118731-01 124204-04 122660-10
    Patches not applicable to packages on the system
    121181-03 120410-33 121211-02 125533-15 143317-03
    119115-35 120412-11 122259-03 125541-06 143510-01
    119117-52 120414-27 122470-03 125952-20 143725-01
    119315-19 120543-21 122911-24 137004-08 143727-01
    119548-14 120739-06 122958-06 138387-01 143739-01
    119903-02 120811-09 123938-02 138824-07 144325-01
    120094-30 120849-04 125136-24 138876-01 145006-02
    120185-21 121104-11 125137-24 139986-01 145080-01
    119368-04 121136-02 125332-14 142244-02 145200-01
    120286-03
    Installation of patch set complete. PLEASE REBOOT THE SYSTEM.
    when i tried to reboot the system by init 6 the service iscsi hanged and produced syslog errors about a unkown iocall -> killed the process. System rebooted w/o errors.
    Does anyone have got an idea how to find out which patch or whatever do produce these errors?

    Hi,
    I'm having the same issue of diskmon core dumps after upgrading grid and database from 11.2.0.1 to 11.2.0.2 on Solaris 10 x86-64. Following this thread, I'm trying to deinstall the Oracle 11.2.0.1 grid home.
    I answered the following questions asked by the grid deinstall tool:
    1. ASM configuration was not detected in this Oracle home. Was ASM configured in this Oracle home (y|n): y
    2. Specify the ASM Diagnostic Destination: /db01/app/oracle/diag/asm/+ASM
    3. Specify the diskgroups that are managed by this ASM instance: DATA FRA
    4. De-configuring ASM will drop all the diskgroups at cleanup time. Do you want deconfig tool to drop the diskgroups:
    If I answer no to question 1, the tool exits with error.
    How do I answer question #4? (confused about this question of dropping diskgroups, it's already been upgraded)
    Deinstall of Oracle db Home 11.2.0.1 was successful.
    The +ASM instance has been upgraded and is running fine under 11.2.0.2 except for the excessive diskmon core dumps.
    Thanks,
    Lisa
    Edited by: user12018917 on Apr 19, 2011 10:21 AM

  • CONFIGURE NFS ON SOLARIS ZONES

    I want steps to configure NFS on solaris Zones

    Hi,
    I installed unfs3 in zone, but can't mount unfs3 share from solaris client(Solaris 10 10/08 s10s_u6wos_07b SPARC):
    root@prod-db $ mount -F nfs -o rw 192.168.219.13:/software /mnt
    nfs mount: 192.168.219.13: : RPC: Rpcbind failure - RPC: Authentication error
    nfs mount: retrying: /mnt
    nfs mount: 192.168.219.13: : RPC: Rpcbind failure - RPC: Authentication error....
    Any suggestions? I cant find in internet any forum or mailing list about unfs3 :(

  • Veritas netbackup sg driver failed to attach

    Hi,
    I am installing veritas netbackup on my V245 server (solaris 10).
    After the installation I am trying to do sg.build and sg.install, but I am getting an error message
    Warning: Driver (sg) successfully added to system but failed to attach
    No Scsi devices on your system
    the solaris sgen driver is already loaded, and when i do mt -f /dev/rmt/1, i can see the tape drive detected
    and on cfgadm -a lso shows the drive and the changer
    i have a C2 tape autoloader attached to my machine
    If i try to manullay load the driver by modload /kernel/drv/sparcv9/sg, It fails saying
    sg: WARNING: sg: _init failed on linkage 6
    No Scsi devices attached to the system
    Please help me in resolving this issue
    Thanking you
    Ushas Symon

    # ./sg.install
    Copied files to /kernel/drv to /kernel/drv/sparcv9.
    Doing add_drv of the sg driver
    devfsadm: driver failed to attach: sg
    Warning: Driver (sg) successfully added to system but failed to attach
    WARNING: /usr/sbin/add_drv failed.
    There may be no SCSI devices on this machine
    root@bkp-server # cfgadm -a
    c3 scsi-bus connected configured unknown
    c3::rmt/1 tape connected configured unknown
    c3::scsi/changer/c3t5d1 med-changer connected configured unknown

  • Client Install Issue - SCCM 2012 R2 - Manual Deploy Installed ok

    Hello, I have sccm 2012 configured with 2,000 machine approx. It is been used mainly as a Software Deployment tool for now. On checking a recent IE10 upgrade, I noticed that there is a number of machines that do not have the client installed (and thus did
    not upgrade IE). I picked 1 machine, searched in SCCM - had no client. I checked all relevant settings:
    Boundary for Client in question - ok
    Local Client Settings (ip,dns,no firewall, ping sccm ok and vice versa etc).
    Once i right clicked to deploy the client, it installed no problem. I checked the ccmsetup log file and the only info it had was from the time that the client was manually deployed (I will attach the log below anyway). I am really puzzled as to why the client
    did not install and if this is the issue why IE is not upgrading (it is hard to pinpoint as there are 250 sites approx). The automatic install task works no problem on other machines once the machine goes online.
    Any help, would be great. Here is the log (I am fairly new to SCCM btw):
    SCCM 2012 R2 - Windows 7 SP1 32 Bit
    ==========[ ccmsetup started in process 7196 ]==========    ccmsetup    05/02/2015 16:28:39    4100 (0x1004)
    Running on platform X86    ccmsetup    05/02/2015 16:28:39    4100 (0x1004)
    Launch from folder C:\Windows\ccmsetup\    ccmsetup    05/02/2015 16:28:39    4100 (0x1004)
    CcmSetup version: 5.0.7958.1401    ccmsetup    05/02/2015 16:28:39    4100 (0x1004)
    In ServiceMain    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /config:MobileClient.tcf    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /config:MobileClient.tcf    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    SslState value: 224    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    CCMHTTPPORT:    80    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    CCMHTTPSPORT:    443    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    CCMHTTPSSTATE:    224    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    CCMHTTPSCERTNAME:        ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    FSP:    COLSCCM01.LC-UK.ORG    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    CCMFIRSTCERT:    1    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Config file:      C:\Windows\ccmsetup\MobileClientUnicode.tcf    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Retry time:       10 minute(s)    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    MSI log file:     C:\Windows\ccmsetup\Logs\client.msi.log    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    MSI properties:    INSTALL="ALL" SMSSITECODE="COL" FSP="COLSCCM01.LC-UK.ORG" SMSCACHESIZE="10240" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"  
     ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Source List:    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
                      \\COLSCCM01.lc-uk.org\SMSClient    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
                      \\COLSCCM01.LC-UK.ORG\SMSClient    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    MPs:    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
                      COLSCCM01.lc-uk.org    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    No version of the client is currently detected.    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Folder 'Microsoft\Configuration Manager' not found. Task does not exist.    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Updated security on object C:\Windows\ccmsetup\.    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Sending Fallback Status Point message to 'COLSCCM01.LC-UK.ORG', STATEID='100'.    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Failed to get client version for sending messages to FSP. Error 0x8004100e    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    Params to send FSP message '5.0.7958.1401 Deployment '    ccmsetup    05/02/2015 16:28:39    500 (0x01F4)
    State message with TopicType 800 and TopicId {19607F6A-0C46-488C-B28D-36640FB0DF94} has been sent to the FSP    FSPStateMessage    05/02/2015 16:28:40    500 (0x01F4)
    Running as user "SYSTEM"    ccmsetup    05/02/2015 16:28:40    500 (0x01F4)
    Detected 434753 MB free disk space on system drive.    ccmsetup    05/02/2015 16:28:40    500 (0x01F4)
    Checking Write Filter Status.    ccmsetup    05/02/2015 16:28:40    500 (0x01F4)
    This is not a supported write filter device. We are not in a write filter maintenance mode.    ccmsetup    05/02/2015 16:28:40    500 (0x01F4)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=COL))'    ccmsetup    05/02/2015 16:28:40    500 (0x01F4)
    OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F0308201D8A00302010202104A263F5C34E3AAAA4C178EF33CA94377300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3134303630383134343831315A180F32313134303531363134343831315A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100A4FF6866BC9622545F811F8008ABDC534E96C9699A3354E990CADB04B1399B29EB80FB844425DEEDD9FE680C57AA0FE05D42CF1D431BB69080D4E7ED91A8255739089A83E4836F28B09331C100B0BAD81AD795EFD01C9ECF8DCE2BE03B52EE3AC35E7003B728E0FA56F145279301189388F3FC90A6C3DA5342C61230550C2B79DECB64AC0958C6DE2D5BF83C3EA29126E231FBEAADBD632F65AF41AC3267DB3986929C46A08AF0BF925A40E15A346B38219CC62C6C0BAC8990C05EA04037458F1853E251D8C16946F845D46CB47884D9EB00543AC8B02A7C099B53F7DE1EBD11AA1272476E5AAF55B2CC38122B62C751D988C81A07D06F87A9F7980D2B3560A90203010001A3383036301E0603551D11041730158213434F4C5343434D30312E6C632D756B2E6F726730140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100A0DE29D627EB45EF2D0074AD578B62CE9007918B4316351DB2DBEFF2D0DF52C0FF58B6DE3405C88572ECCFAF2A7B335B234FE7D1E5B0FDA20548FEFE4B9E6AFB45E77627EDB70E2378A3135FB1FC34C2308F0FBD1ADD890DD08D8D6081B73FFF86DE87DBF678A7CAD73AE32BF6EB3B9D1E4E0380D7FBE3E9F9EF49339031636F2B3CC60989B8443B91F9F69F5837025B6CAE64E2D1837FAF712186A02567EA87F9E82FD170C4DEA61DC61C16226450FCBE062948F2219FB5801DF3AF73443349421A7228F5E1372B5CA165D8ABAB9D1B3FEAF22705A473AAAB034C2A289AA7A507550050D6516C2D7BECDE5686F17CC66FBB7D2C439F15644EBF9EF7E8402109</SiteSigningCert></SecurityConfiguration><RootSiteCode>COL</RootSiteCode><CCM>
    <CommandLine>SMSSITECODE=COL FSP=colsccm01.lc-uk.org SMSCACHESIZE=10240</CommandLine> </CCM><FSP> <FSPServer>COLSCCM01.lc-uk.org</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState"
    Value="0" /></Capabilities><Domain Value="lc-uk.org" /><Forest Value="lc-uk.org" /></ClientOperationalSettings>'    ccmsetup    05/02/2015 16:28:41    500
    (0x01F4)
    Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    The MP name retrieved is 'COLSCCM01.lc-uk.org' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>'    ccmsetup  
     05/02/2015 16:28:41    500 (0x01F4)
    MP 'COLSCCM01.lc-uk.org' is compatible    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Retrieved 1 MP records from AD for site 'COL'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Retrived site version '5.00.7958.1000' from AD for site 'COL'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    SiteCode:         COL    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    SiteVersion:      5.00.7958.1000    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Only one MP COLSCCM01.lc-uk.org is specified. Use it.    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Searching for DP locations from MP(s)...    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Current AD site of machine is Millbank    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Local Machine is joined to an AD domain    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Current AD forest name is lc-uk.org, domain name is lc-uk.org    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    DhcpGetOriginalSubnetMask entry point is supported.    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Begin checking Alternate Network Configuration    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Finished checking Alternate Network Configuration    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Adapter {743579BD-D66A-4BF9-B487-2AAC075B9473} is DHCP enabled. Checking quarantine status.    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Adapter {8F25ACE0-AE8A-45DD-BF3D-F1315E2B9974} is DHCP enabled. Checking quarantine status.    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Adapter {8AE4D673-90E8-4FCF-AE50-79474ADC6190} is DHCP enabled. Checking quarantine status.    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Adapter {9AA2CA9C-0C0A-48E3-B67E-F9E574AE9DB2} is DHCP enabled. Checking quarantine status.    LocationServices    05/02/2015 16:28:41    500 (0x01F4)
    Sending message body '<ContentLocationRequest SchemaVersion="1.00">
      <AssignedSite SiteCode="COL"/>
      <ClientPackage/>
      <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0"
    UseInternetDP="0">
        <ADSite Name="Millbank"/>
        <Forest Name="lc-uk.org"/>
        <Domain Name="lc-uk.org"/>
        <IPAddresses>
    <IPAddress SubnetAddress="10.103.38.0" Address="10.103.38.10"/>
        </IPAddresses>
      </ClientLocationInfo>
    </ContentLocationRequest>
    '    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Sending message header '<Msg SchemaVersion="1.1"><ID>{57972056-54D4-461F-B818-D3420A0B5C51}</ID><SourceHost>LCD14572</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:LCD14572:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>COLSCCM01.lc-uk.org</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-02-05T16:28:41Z</SentTime><Body
    Type="ByteRange" Offset="0" Length="1084"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>'    ccmsetup    05/02/2015
    16:28:41    500 (0x01F4)
    CCM_POST 'HTTP://COLSCCM01.lc-uk.org/ccm_system/request'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Content boundary is '--aAbBcCdDv1234567890VxXyYzZ'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Received header '<Msg SchemaVersion="1.1">
        <ID>{48D22538-0FEA-44E6-AAD2-1829DDED2223}</ID>
        <SourceID>GUID:A5143C3E-EA22-4B93-BFF5-B8B859F869F5</SourceID>
        <SourceHost>COLSCCM01</SourceHost>
        <TargetAddress>direct:LCD14572:LS_ReplyLocations</TargetAddress>
        <ReplyTo>MP_LocationManager</ReplyTo>
        <CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID>
        <Priority>3</Priority>
        <Timeout>600</Timeout>
        <TargetHost>LCD14572</TargetHost><TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-02-05T16:28:39Z</SentTime><Body
    Type="ByteRange" Offset="0" Length="2378"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082019106092A864886F70D010702A08201823082017E020101310B300906052B0E03021A0500300B06092A864886F70D0107013182015D30820159020101303630223112301006035504031309434F4C5343434D3031310C300A06035504031303534D5302106A638C8D6A89DE904525D14326BE4DB0300906052B0E03021A0500300D06092A864886F70D01010105000482010027BAE95F5B0DD9F75743E1E40A189091900F78F19367C2A8328F823C63F24229608E7CF02FF2FE76FC61C6A61EF0FE8F19AC75755B88124B13964AE58F971DAB67E47B4DDCAA943B4C27F7AF9B5A0AD1DE956A3AACA26965F5FDAC8659E6263DBB55E025FB305C665AC1AA49972CC937A757EC14F1097DA27AB9998D7CAE332EC135A937A80285C87448AD7B4F4ED059063BCB5032920C65CE16FD32475CD395B279021F62E5C3B534697EDCD68A98D2A654379CCA17056F7B4FAB0346242CE56681F405DB9700FD766FDBD584BB69A4AC088BF3B971BE8B05B723701A22B9D76BB5C063F1BD32B56DB7B3BDC6D827E3D90106F3C1145E04B0629528EA24BD37</Property><Property
    Name="AuthSenderMachine">COLSCCM01;COLSCCM01.lc-uk.org;</Property><Property Name="MPSiteCode">COL</Property></Hook></Hooks><Payload Type="inline"/></Msg>'    ccmsetup  
     05/02/2015 16:28:41    500 (0x01F4)
    Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="16777216"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="COL" MasterSiteCode="COL"
    SiteLocality="LOCAL" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002" Signature="http://COLSCCM01.lc-uk.org/SMS_DP_SMSSIG$/COL00002"/><ADSite
    Name="Millbank"/><IPSubnets><IPSubnet Address="10.20.0.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property
    Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>COLSCCM01.lc-uk.org</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="1"/><Locality>LOCAL</Locality></LocationRecord></LocationRecords></Site></Sites><ClientPackage
    FullPackageID="COL00002" FullPackageVersion="2" FullPackageHash="DB3D5D115FC93F6275817FB9791864D98D4AF6897339B9D4AB1C0DE456C240A8" MinimumClientVersion="5.00.7958.1000" RandomizeMaxDays="7" ProgramEnabled="false"
    LastModifiedTime="30376953;932870912" SiteVersionMatch="true" SiteVersion="5.00.7958.1000" EnablePeerCache="true"/><RelatedContentIDs/></ContentLocationReply>'    ccmsetup    05/02/2015
    16:28:41    500 (0x01F4)
    Found local location 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Discovered 1 local DP locations.    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    PROPFIND 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Got 401 challenge Retrying with Windows Auth...    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    PROPFIND 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002'    ccmsetup    05/02/2015 16:28:41    500 (0x01F4)
    Using DP location http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    GET 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002/ccmsetup.cab'    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Got 401 challenge Retrying with Windows Auth...    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    GET 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002/ccmsetup.cab'    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Retrieved client version '5.00.7958.1000' and minimum assignable site version '5.00.7845.1000' from manifest    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Checking compatibility of site version '5.00.7958.1000', expect newer than '5.00.7845.1000'    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Site version '5.00.7958.1000' is compatible. Client deployment will continue.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Location 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002' passed site version check.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Successfully loaded ccmsetup manifest file.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Checking if manifest version '5.00.7958.1000' is newer than the ccmsetup version '5.0.7958.1401'    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Running from temp downloaded folder or manifest is not newer than ccmsetup.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/vcredist_x86.exe' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/vcredist_x64.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/vc50727_x86.exe' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/vc50727_x64.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/WindowsUpdateAgent30-x86.exe' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/WindowsUpdateAgent30-x64.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/msxml6.msi' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/msxml6_x64.msi' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/msrdcoob_x86.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/msrdcoob_amd64.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'pkgmgr.exe' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'dism.exe' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'wimgapi.msi' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/MicrosoftPolicyPlatformSetup.msi' is applicable. Add to the list.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'x64/MicrosoftPolicyPlatformSetup.msi' is not applicable.    ccmsetup    05/02/2015 16:28:42    500 (0x01F4)
    Item 'i386/WindowsFirewallConfigurationProvider.msi' is applicable. Add to the list.    ccmsetup    05/02/2015 1

    Hi, Yes i had a look at the log yesterday. there are errors initially, but then the install completes. I can copy the whole log here, the machine in question is LCD14572. If you could take a look would be great. Still doesnt explain why i had to manually
    push the client though:
    Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154539    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:05:58    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushMachineName] 2097154539    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:05:58    3648 (0x0E40)
    Received request: "2097154539" for machine name: "LCD15000" on queue: "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:05:58    3648 (0x0E40)
    Stored request "2097154539", machine name "LCD15000", in queue "Processing".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:05:58    3648 (0x0E40)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154539, 1    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:05:58    3648 (0x0E40)
    ----- Started a new CCR processing thread. Thread ID is 0x12d8. There are now 1 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Submitted request successfully    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Getting a new request from queue "Retry" after 100 millisecond delay.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Found CCR "2097154540.ccr" in queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    ======>Begin Processing request: "2097154539", machine name: "LCD15000"    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    4824 (0x12D8)
    Execute query exec [sp_IsMPAvailable] N'COL'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    4824 (0x12D8)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    4824 (0x12D8)
    ---> Attempting to connect to administrative share '\\LCD15000\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    4824 (0x12D8)
    Execute query exec [sp_CP_GetPushRequestMachine] 2097154540    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Successfully retrieved information for machine LCD14589 from DB    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushRequestMachineIP] 2097154540    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154540    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushMachineName] 2097154540    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Received request: "2097154540" for machine name: "LCD14589" on queue: "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Stored request "2097154540", machine name "LCD14589", in queue "Processing".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154540, 1    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:00    3648 (0x0E40)
    ----- Started a new CCR processing thread. Thread ID is 0x1d10. There are now 2 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Submitted request successfully    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Getting a new request from queue "Retry" after 100 millisecond delay.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Found CCR "2097154542.ccr" in queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    ======>Begin Processing request: "2097154540", machine name: "LCD14589"    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    7440 (0x1D10)
    Execute query exec [sp_IsMPAvailable] N'COL'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    7440 (0x1D10)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    7440 (0x1D10)
    ---> Attempting to connect to administrative share '\\LCD14589\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    7440 (0x1D10)
    Execute query exec [sp_CP_GetPushRequestMachine] 2097154542    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Successfully retrieved information for machine LCD14571 from DB    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushRequestMachineIP] 2097154542    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154542    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Execute query exec [sp_CP_GetPushMachineName] 2097154542    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Received request: "2097154542" for machine name: "LCD14571" on queue: "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Stored request "2097154542", machine name "LCD14571", in queue "Processing".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154542, 1    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:02    3648 (0x0E40)
    ----- Started a new CCR processing thread. Thread ID is 0x1768. There are now 3 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:04    3648 (0x0E40)
    Submitted request successfully    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:04    3648 (0x0E40)
    Getting a new request from queue "Retry" after 100 millisecond delay.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:04    3648 (0x0E40)
    Sleeping for 60 minutes for queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:04    3648 (0x0E40)
    ======>Begin Processing request: "2097154542", machine name: "LCD14571"    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:04    5992 (0x1768)
    Execute query exec [sp_IsMPAvailable] N'COL'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:05    5992 (0x1768)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:05    5992 (0x1768)
    ---> Attempting to connect to administrative share '\\LCD14571\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:05    5992 (0x1768)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:21    4824 (0x12D8)
    ---> The device LCD15000 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:21    4824 (0x12D8)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:21    4824 (0x12D8)
    ---> Attempting to connect to administrative share '\\LCD15000.lc-uk.org\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:21    4824 (0x12D8)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:23    7440 (0x1D10)
    ---> The device LCD14589 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:23    7440 (0x1D10)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:23    7440 (0x1D10)
    ---> Attempting to connect to administrative share '\\LCD14589.lc-uk.org\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:23    7440 (0x1D10)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:26    5992 (0x1768)
    ---> The device LCD14571 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:26    5992 (0x1768)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:26    5992 (0x1768)
    ---> Attempting to connect to administrative share '\\LCD14571.lc-uk.org\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:26    5992 (0x1768)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> The device LCD15000.lc-uk.org does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> Attempting to connect to administrative share '\\LCD15000\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> The device LCD15000 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> ERROR: Unable to access target machine for request: "2097154539", machine name: "LCD15000",  access denied or invalid network path.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47  
     4824 (0x12D8)
    Execute query exec [sp_CP_SetLastErrorCode] 2097154539, 53    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    Stored request "2097154539", machine name "LCD15000", in queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154539, 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    Execute query exec [sp_CP_SetLatest] 2097154539, N'02/05/2015 16:06:47', 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    <======End request: "2097154539", machine name: "LCD15000".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:47    4824 (0x12D8)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> The device LCD14589.lc-uk.org does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> Attempting to connect to administrative share '\\LCD14589\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> The device LCD14589 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> ERROR: Unable to access target machine for request: "2097154540", machine name: "LCD14589",  access denied or invalid network path.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51  
     7440 (0x1D10)
    Execute query exec [sp_CP_SetLastErrorCode] 2097154540, 53    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    Stored request "2097154540", machine name "LCD14589", in queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154540, 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    Execute query exec [sp_CP_SetLatest] 2097154540, N'02/05/2015 16:06:51', 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    <======End request: "2097154540", machine name: "LCD14589".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:51    7440 (0x1D10)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> The device LCD14571.lc-uk.org does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> Attempting to connect to administrative share '\\LCD14571\admin$' using account 'LC-UK\VAdmin'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> The device LCD14571 does not exist on the network. Giving up    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    ---> ERROR: Unable to access target machine for request: "2097154542", machine name: "LCD14571",  access denied or invalid network path.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55  
     5992 (0x1768)
    Execute query exec [sp_CP_SetLastErrorCode] 2097154542, 53    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    Stored request "2097154542", machine name "LCD14571", in queue "Retry".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154542, 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    Execute query exec [sp_CP_SetLatest] 2097154542, N'02/05/2015 16:06:55', 2    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    <======End request: "2097154542", machine name: "LCD14571".    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:06:55    5992 (0x1768)
    CCR count in queue "Retry" is 3.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:07:42    6564 (0x19A4)
    Sleeping for 634 seconds...    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:07:43    6564 (0x19A4)
    Thread has been inactive too long. Closing thread    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:47    4824 (0x12D8)
    --- This thread is terminating due to inactivity    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:47    4824 (0x12D8)
    ----- Terminated CCR processing thread. There are now 2 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:47    4824 (0x12D8)
    Thread has been inactive too long. Closing thread    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:51    7440 (0x1D10)
    --- This thread is terminating due to inactivity    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:51    7440 (0x1D10)
    ----- Terminated CCR processing thread. There are now 1 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:51    7440 (0x1D10)
    Thread has been inactive too long. Closing thread    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:55    5992 (0x1768)
    --- This thread is terminating due to inactivity    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:55    5992 (0x1768)
    ----- Terminated CCR processing thread. There are now 0 processing threads    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:16:55    5992 (0x1768)
    Sleeping for 1 seconds...    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:16    6564 (0x19A4)
    The Site Control File has not changed since the last parameter update.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:17    6564 (0x19A4)
    Updating Site Parameters    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    MP Ports: 80    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    IISPreferedPort: 80    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    MP SSL Ports: 443    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    IISSSLPreferedPort: 443    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Default MP: COLSCCM01.lc-uk.org    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Default MP Type: 1    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Default MP: [None]    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Certificate Selection Criteria:    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Certificate Store:    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    SSL State: 224    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Select First Certificate: 1    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Certificate Issuers:    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Checking configuration information for server: COLSCCM01.LC-UK.ORG.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Checking configuration information for server: COLSCCM01.LC-UK.ORG.    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Fallback Status Point: COLSCCM01.lc-uk.org    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Install on DC: False    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Option for installing using IP address: 0    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Sleeping for 1200 seconds...    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:18:18    6564 (0x19A4)
    Waiting for change in directory "D:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout).    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:23:39  
     2876 (0x0B3C)
    Execute query exec [sp_CP_GetNewPushMachines] N'COL'    SMS_CLIENT_CONFIG_MANAGER    05/02/2015 16:28:09    2876 (0x0B3C)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154468, 1    SMS_CLIENT_CONF

  • Backup MaxDB 7.7.06.09 to Veritas Netbackup 6.5 fails

    We want to backup MaxDB to Veritas Netbackup server.
    According documentation found about this topic the backup is configured
    by creating 3 files: bsi.env, initWDO.par (for backint for MaxDB) and
    initWDO.utl (for backint for Oracle). The contents of these files are shown below.
    When running the backup, it seems that backint for MaxDB ends with return code 2,
    the error message received is:
      -24920,ERR_BACKUPOP: backup operation was unsuccessful
      The backup tool failed with 2 as sum of exit codes.
    Unfortunately no further errors/warnings are shown that points in any direction
    what's going wrong here.
    We start the backup via the following dbmcli-command:
    dbmcli -u control,****** -d WDO -uUTL control,****** backup_start BACKData_WDO
    (for the time being without xuser entries, first make sure the backup is ok)
    The files dbm.ebl, dbm.prt and several others do not show any additional details/hints.
    It seems as if the "save data quick" to the named pipe is ok, the sql-code returns "0".
    After this the backint for MaxDB should read the named pipe and write it to stage-files,
    but backint (for MaxDB) ends with return code 2.
    Any idea what might go wrong here?
    With kind regards,
    R. Hoogeveen
    The Netherlands
    File bsi.env:
    =========
    BACKINT                /sapdb/WDO/db/bin/backint
    INPUT                  /tmp/backint4maxdb_WDO.in
    OUTPUT                 /tmp/backint4maxdb_WDO.out
    ERROROUTPUT            /tmp/backint4maxdb_WDO.err
    PARAMETERFILE          /sapdb/data/wrk/WDO/initWDO.par
    TIMEOUT_SUCCESS        600
    TIMEOUT_FAILURE        300
    ORIGINAL_RUNDIRECTORY  /sapdb/data/wrk/WDO
    File initWDO.par:
    =============
    STAGING AREA:                  /tmp/stageWDO 1 GB
    FILES PER BACKINT CALL:        1
    BACKINT:                       /usr/openv/netbackup/bin/backint
    PARAMETERFILE OF BACKINT:      /sapdb/data/wrk/WDO/initWDO.utl
    HISTORY FILE:                  /sapdb/data/wrk/WDO/backint_history_WDO.log
    INPUTFILE FOR BACKINT:         /tmp/backint4ora_WDO.in
    OUTPUTFILE FOR BACKINT:        /tmp/backint4ora_WDO.out
    ERRORFILE FOR BACKINT:         /tmp/backint4ora_WDO.err
    MAXIMAL DELAY OF BACKINT CALL: 30
    File initWDO.utl:
    =============
    switch_list /tmp/.switch_WDO.lis
    switch_sem /tmp/.switch_WDO.sem
    switch_log /tmp/.switch_WDO.log
    drives 1
    client wdocsz01
    server backfire
    policy sap_WDO

    Lars,
    The /tmp/backint4maxdb.err file tells me:
    Backint for Oracle was unsuccessful.
    (Unfortunately that was all information in this file.)
    The backint4ora.in file tells me:
    /tmp/stageWDO.0
    (looks ok to me, also at the time backint4ora was started the stage file was created with non-zero size)
    The backint4ora.out file tells me:
    ERROR: incorrect format or option in .utl file (-p)
    (this seems as if the -p option is not recognized by the backint4ora executable)
    When I run this executable manually as user sdb it shows me the commandline that I should use, including the -p option.
    One strange thing I notice is that the order of the options is different from the commandline that is executed.
    (in the usage it shows -p as almost last parameter, the command executed has -p in the middle; I will see if I can execute the backint4ora command manually, since I have the stage file available, I have copied it during the process)
    The backint4ora.err file is empty.
    The commandline of the dbmcli command I execute shows me another interesting error message,
    this might also be the source of all problems here.
    -24920,ERR_BACKUPOP: backup operation was unsuccessful
    Could not get external backup ID's from the backup tool.
    I tried to retrieve the external backup id's manually for medium BACKDataWDO, it show me OK without any external backup id's.
    I am not sure, but I think this is correct since no successfull backup was created yet with external backup tool.
    Can it also be that the parameter "history file" from the initWDO.par file is set wrong?
    Currently it is set to "/sapdb/data/wrk/WDO/backint_history_WDO.log" (see above also), but I can imagine
    that this should be set to the dbm.knl or dbm.ebf file ??
    With kind regards,
    Roger Hoogeveen

  • For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

    While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
    Background:
    I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
    After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
    1.  Uninstall the OCS 2007 R2 client
    2.  Install all prerequisites for the Lync client
    3.  Install Lync on all user workstations silently.
    While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx".  Well, my response is, I
    tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
    start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them.  I was unable to find any switch or option to prevent the automatic launch.  I suppose the simple solution to that would
    be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
    The next simplest answer I saw was, "extract the MSI and use that with the right switches".  Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
    the MSI to be used or a hacked MSI that bypasses the registry key check.  I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly.  The other problem I ran into
    was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations.  It was this problem that ultimately led me to the solution that I'm about to detail and that has
    worked marvellously for us.
    Solution:
    As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install.  My first attempt was
    just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped.  So, my next attempt was to extract all the prerequisite
    files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
    In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique.  That's where you have, for example, 3 or more programs that run in a package
    in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order.  So, I created programs to 1) kill Communicator.exe 2) uninstall
    Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client.  That final step was always the point of failure because
    I couldn't get the hacked MSI for the Lync Client install to work.  I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error.  That's one of the downsides
    of program-chaining, if one step fails, SCCM completely bails on the deployment.  This is what also led me to the key to my solution:  TASK SEQUENCES.
    I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments. 
    One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running.  Another advantage is that task sequences have some very good built-in conditionals that
    you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine.  Both of those advantages factor highly into my solution.
    OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
    First, you need to extract all the files from the LyncSetup.exe for your needed architectures.  We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account.  To extract the files, just start up
    the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location.  The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
    both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
    or rename them to reflect the architecture).
    For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
    Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server.  Go to the SCCM console into Computer Management -> Software Distribution
    -> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
    Now you need to create 3 to 5 programs inside the package:
    1.  Name: Silverlight
       Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer. 
    The fact is the Silverlight installer is the same in both, so you only need one of them.)
       On the Environment tab:  Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
       On the Advanced tab:  Suppress program notifications
       All other options leave default.
    2.  Name:  Visual C++ x86
        Command Line:  x86\vcredist_x86.exe /q
       On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
       Environment and Advanced tabs:  same as Silverlight
       (If you have only x64 clients in your environment, change all x86 references to x64.  If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
    3.  Name:  Lync x86
        Command Line:  msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync"  (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
        Requirements, Environment, and Advanced tabs:  Same as with Visual C++ and Silverlight
        (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
    Now you need to make the Task Sequence.  Go to Computer Management -> Operating System Deployment -> Task Sequences.  Under the Actions pane, click New -> Task Sequence.  In the Create a New Task Sequence dialog, choose "create a
    new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
    The task sequence will have up to 12 steps in it.  I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
    Prereqs Phase:
    These are the easiest of the steps to do.  Highlight the task sequence and then in the Actions pane, click Edit.
    1.  Click Add -> General -> Install Software.  Name: "Install Microsoft Silverlight".  Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
    2.  Add -> General -> Install Software.  Name: "Install Microsoft Visual C++ 2008 x86".  Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
    As before, if you're an all-x64 environment, replace the x86 references with x64.  If you have a mixed environment, repeat step 2, replacing x86 with x64.
    3.  Add -> General -> Run Command Line.  Name: "Enable Lync Installation".  This step gets around the UseMSIForLyncInstallation registry requirement.  The Lync client MSI simply looks for the presence of this key when it runs, so
    we'll inject it into the registry now and it doesn't require a reboot or anything.  It just has to be there before the client MSI starts.
    Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
    Uninstall OCS Phase:
    This part consists of up to 6 Run Command Line steps.  (Add -> General -> Run Command Line)
    4.  Name: "Terminate Communicator".  Command Line: "taskkill /f /im communicator.exe".  On the Options page, check the box next to "Continue on error".  This will terminate the Communicator process if it's running, and if it's not, it'll
    ignore the error.
    5.  Name: "Terminate Outlook".  Command Line: "taskkill /f /im OUTLOOK.exe".  Check the "Continue on error" on the Options page here too.  Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
    because components are in use.
    (NOTE:  If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps.  I didn't run into
    this in my environment, though.  Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
    6.  Name: "Uninstall Microsoft Office Communicator 2007".  Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page:  Add Condition ->  Installed Software -> Browse to the
    Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
    7.  Name:  "Uninstall Microsoft Office Communicator 2007 R2".  Command Line:  "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart".  On the Options page:  Add Condition -> Installed Software ->
    Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
    SIDEBAR
    OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence.  I found out after I'd been deploying for a while that a tech in one of our remote
    offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there.  So, at first I just had our Help
    Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence.  Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
    and 7.  All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions.  This is part of how Windows knows that
    Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
    The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code.  This means that if I didn't have step
    6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong.  Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
    of the R2 client.  So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine.  If it was present, it uninstalled it and then skipped over the R2 step.  If non-R2 was not present,
    it skipped that step and instead uninstalled any version of the R2 client.  It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there.  What if neither is on the
    machine?  Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem.  It was assumed that the machines had some version of Communicator on them.
    8.  Name:  "Uninstall Conferencing Add-In for Outlook".  Command Line:  "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart".  Check the "Continue on error" on the Options Page and then Add Condition ->
    Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product.  If you don't use this in your environment, you can omit this step.
    9.  Name:  "Uninstall Live Meeting 2007".  Command Line:  "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart".  Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
    -> Browse to the MSI for this optional component and set it to match any version of the product.  If you don't use this in your environment, you can omit this step.
    Install Lync phase:
    Now, finally the main event, and it's pretty simple:
    10.  Click Add -> General -> Install Software.  Name: "Install Microsoft Lync 2010 x86".  Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program.  As before, if you
    only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
    And the task sequence is done!  The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement.  Go get a beer!
    Some final notes to keep in mind:
    1.  You can't make a task sequence totally silent...easily.  Users will get balloon notifications that an application is available to install.  The notifications cannot be suppressed through the GUI.  I've found scripts that supposedly
    hack the advertisement to make it be silent, but neither of them worked for me.  It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade.  The task sequence will appear
    in the "Add/Remove Programs" or "Programs and Features" Control Panel.  You can still do mandatory assignments to force the install to happen, you just can't make it totally silent.  On the plus side, the user shouldn't have to reboot at any point
    during or after the install!
    2.  In the advertisement setup, you can optionally show the task sequence progress.  I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress.  This means instead of seeing
    5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
    3.  One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete.  The user either had to start the client manually or just let it start on its own at the next logon.  However,
    while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
    tab, set it to "Run with user's rights" "only when a user is logged on".
    4.  My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
    and it would fail.  Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first.  It ran much more reliably this way.
    5.  For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
    then fail.  I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
    doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
    I hope this helps some of you SCCM and Lync admins out there!

    On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook.  Here's a list of the ones I found in the machines on my network:
    {987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
    {2BB9B2F5-79E7-4220-B903-22E849100547}
    {13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
    {C5586971-E3A9-432A-93B7-D1D0EF076764}
    I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

  • We have a set of oracle clients running on T5220 zones that need some help

    Greetings all -
    We have a set of oracle clients running on T5220 zones that need some help.
    If, for example, I execute the query "select (all) from dba_objects", trace output reports 90% of the elapsed time spent under "SQLNet message from client".
    Here are OS details for the clients: Solaris 10 5/08 s10s_u5wos_10 SPARC
    Running "uname -a" from the client gives:
    (SunOS bmc-ste-app 5.10 Generic_127127-11 sun4v sparc SUNW,SPARC-Enterprise-T5220)
    Here are OS details for the dataserver: Enterprise Linux Enterprise Linux Server release 5.2
    Running "uname -a" from the dataserver gives:
    (2.6.18-92.1.6.0.2.el5 #1 SMP Thu Jun 26 17:44:55 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux)
    The RDBMS is 10.2.0.4
    Again, please note, there is no application in the picture here. We are just running a simple catalog query (select * from dba_objects) from sqlplus. Why the wait on something like this? The wait also occurs when a different query is used (select (all) from SYS.COL$ where rownum < 50000). And it doesn't matter if I used the full client or the instant client. I still get the same high-wait.
    We had thought - maybe this is a network thing - so we put a test client on the same subnet as the dataserver. This helped - but not enough. The wait is still way too high even with firewalls taken out of the equation.
    We've also looked at arraysize, SDU, kernel settings. And we've spent time going over tkprof, truss and sqlnet-tracing.
    Has anyone ever had to solve this HIGH WAIT ON CLIENT issue? Is there a work around or some tweak I'm missing.
    Is anyone configured like we are (linux dataserver, solaris clients)? If so - did you see anything like this?
    tia -
    Jim
    Edited by: jim1768 on Mar 31, 2010 1:47 PM
    Edited by: jim1768 on Mar 31, 2010 2:12 PM
    Edited by: jim1768 on Mar 31, 2010 2:13 PM

    Hello,
    We have the exact same issue. Did you ever solve this issue? We have a t5220 and have just upgraded our 11.5.10.2 11i system on it from 9.2.0.8 32-bit sparc to 11.2.0.1 64-bit sparc. Things should be faster but arent, and our consultant has tracked it down to high wait times when the apps tier using forms connects to the database tier on the same box. So even though the t5220 is both server and client, there is something about the client sql connection.through TNS that his having trouble. Thanks for any information. We've also created an S/R with Oracle.
    Note: I am well aware of the other issues with the CMT server series but this particular issue seems independent of the regular / known issues and remains a mystery to us. Other known issues with the CMT servers for SPARC:
    Metalink Note 781763.1 (Migration from fast single threaded CPU machine to CMT UltraSPARC T1 & T2)
    http://blogs.sun.com/glennf/resource/Optimizing_Oracle_CMT_v1.pdf
    http://blogs.sun.com/glennf/tags/throughput
    http://blogs.sun.com/glennf/entry/getting_past_go_with_sparc
    http://www.oracle.com/apps_benchmark/doc/E-Bus-11i-PAY_ORA_SUN-T5220.pdf (this paper has some oracle init settings at the end. The kernel settings have been included in the OS upgrade)
    http://blogs.sun.com/mandalika/entry/siebel_on_sun_cmt_hardware

Maybe you are looking for

  • Text messages going to wrong person

    This issue has been reported for quite a while and is still occurring yet I do not see that Verizon is acknowledging it. I have also seen where it might actually be an Android O/S issue but it still needs to be addressed by Verizon.  My personal expe

  • Itunes crashes when I open it

    I have tried with multiple versions of iTunes and the outcome is the same each time. It opens, then crashes immediately without fail every single time. This is the error report I get each and every time: Problem Stopped working Problem signature Prob

  • Soldering standard 2nd gen iPod nano headphones...

    Has anyone out there had any experience soldering either the wire to wire or wire to jack? I know there is a lacquer on the wires, so it's kind of difficult to get the solder to stick. Thanks, Brandon

  • How to display "age of employee"?

    Hi, Can you pls tell me the procedure to display "age of employee" in IT 0002? I appreciate your helping nature. Thanks Yogi

  • DPI of a linked image, illustrator - extendscript

    Hi, I am creating a script that needs to be able to find the DPI of a linked image. I presume there must be some way of getting to this data as it is in the links window in illustrator. I do also need to get other information in that window (colour s