Manually Install Patch Agent??

We recently purchased Zenworks Patch Management. However, right before
purchasing ZCM Patch Mgmt, we upgraded to ZCM 11. The ZCM 11 Agent
components for patch management automatically installed to ZCM 11 clients,
but not to version 10 clients. My guess is that it might have something to
do with the fact that the MSIs for 10.3.1 are now renamed as "superceded"
MSIs.
I had a friend build me an "unconfigured" ZCM agent package from his 10.3.1
system (he has ZCM Patch Management), and that successfully installs on a
freshly imaged machine and Zenworks Patch Management seems to be working.
However, that doesn't help me with the rest of my 10.3.1 machines that I
don't wish to reimage right now.
If you're asking: Why don't I upgrade my clients to the ZCM 11 Agent? I'll
tell you my answer: IT'S WAY TOO SLOW!! Until they iron out a few issues,
we're going to hang with the 10.3.1 agent.
So, my question is: Is there anyway to take the MSIs that are renamed as
"superceded" and manually install them to a workstation to get ZCM Patch
Management working on my existing 10.3.1 clients? I tried to simply install
the MSIs, but it doesn't seem to show up as an installed option on the ZCM
Agent properties page.
Thanks in advance!

Ryan,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Similar Messages

  • How to manually install QTP Agent Chrome plug-in

    Hello All,
    How can I manually install QTP Agent Chrome plug-in? Unable to locate plug-in in my machine.
    I have installed QTP patch: QTPWEB_00088.EXE
    By mistake, I have removed it from chrome extensions.
    Thanks.
    Ankit Nigam

    Solution:
    Install Chrome Agent.crx located at C:\Program Files\HP\QuickTest Professional\bin\Chrome
    Can refer steps to install crx file:
    http://askubuntu.com/questions/254643/ho-to-install-an-already-downloaded-crx-file-extension-in-chro...

  • AIX Monitoring works for 6.1 and not if 6.1.0.0 even if I manually install

    I pushed scom 2012 agent to a list of AIX servers wherein it got successfully installed for sever it discovered version as 6.1 and failed with the message ( Signed certificate verification operation was not successful )for the servers it discovered
    as 6.1.0.0 . even if I manually install  . Following is the message I got on running Get-OS version.sh.
    <DiscoveredOS><Hostname>HOSTNAME</Hostname><OSName>AIX</OSName><OSAlias>AIX</OSAlias><Version>6.1.0.0</Version><Arch>powerpc</Arch><IsLinux>false</IsLinux></DiscoveredOS>

    Yes, SCOM can manage each server in the cluster but you will need to do the following:
    - Make sure each node in the cluster is registered in the DNS server SCOM uses. If you cannot update DNS you will need to update the hosts file on each SCOM server that manages the agent.
    - On each node, manually install the agent -->
    http://technet.microsoft.com/en-us/library/hh212686.aspx
    - After you install the agent you can manually generate the certificate by running the following command on the agent:
       /opt/microsoft/scx/bin/tools/scxsslconfig -h <hostname> -d <domain name> -f -v
    Where <hostname> and <domain name> are what you have in DNS for the server.
    - Run the discovery wizard and SCOM should sign the certificate and manage the agent.
    Regards,
    -Steve

  • Manually Installed Agent is not showing up in the Operations Manager Console Under Pending Management.

    Hi Community,
    I submitted this question because I'm a bit stuck with SCOM 2012 R2, I'll try to explain briefly what is happening right now in my environment,  we have a DEV SCOM Deployment in which all the roles are installed in a single server, this servers is a
    VMware machine running Windows Server 2008R2.
    The Initial installation of the SCOM Operations Manager and all the other components was not performed by me but by a co-worker, unfortunately he doesn't remember much about the initial configuration. So i had to pickup where he left things about a year
    ago, neither of us are SCOM experts, and we have almost no previous experience with previous versions of this application.
    Now the problem that I'm facing is the following, all the DEV Servers are Domain Controllers and one of the indication within the "Guide for System Center Management Pack for Active Directory for Operations Manager 2012" states the following
    Configuration
    Supported?
    Agent-less monitoring
    No
    After my first review I notice that our servers were being monitor by agent-less mode and given the above statement from the Operations Guide the only way that we could ever get those domain controllers monitor by SCOM would be by installing the agent on
    each server, so I read somewhere (Can't remember where) that in order to install the agents in all the servers I should first remove them from the Agent-less node, which I did. Then I tried to use the discovery wizard to get the agent install in all of them
    but it didn't matter how many times I try the servers never show up.
    I read in a Tech Net Article that you had to modify the security settings so SCOM would let me decide if I wanted to approve it or not.
    --> http://technet.microsoft.com/en-us/library/hh212853.aspx
    I performed the suggested steps from the article but still the servers were not showing up, not even if I run the Discovery wizard, so I decided to go and perform the installation manually in a couple of servers I was able to install the agent in one of
    the Domain Controllers, I configured the agent to use a service account that has Domain Admin rights. An hour after I installed the agent I went back to the Operations Console Manager and I check under Pending Action but the Server was not showing up. So i
    went back to the Internet to try to find out if someone else had experience the same problem, and in one website some mentioned that if the servers were not showing up it was probably because they were still register in the SCOM Database, now I have no idea
    of how i can check that or How can i remove them from there to have them available again, but what troubles me the most is that even after i installed the agent manually the server were not being recognize.
    I went to the Event Viewer and I found one particular event that caught my attention, see below :
    Log Name:      Operations Manager
    Source:        Health Service Modules
    Date:          6/12/2014 12:48:19 PM
    Event ID:      11551
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MyManagementServer
    Description:
    Computer verification failure for Machine Name: MyManagementServe is 0x800706BA. The RPC server is unavailable.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Health Service Modules" />
        <EventID Qualifiers="49152">11551</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-06-12T16:48:19.000000000Z" />
        <EventRecordID>1945680</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>MyManagementServer</Computer>
        <Security />
      </System>
      <EventData>
        <Data>MyManagementServe</Data>
        <Data>0x800706BA</Data>
        <Data>The RPC server is unavailable.</Data>
      </EventData>
    </Event>
    Not sure if this is related to the problem that I'm facing right now, but , I make sure that the RPC Services were running and also the related dependencies too. There's no Firewall enable in any of the servers and DNS seems to be working properly.
    Ports 135 / 5723 are open and listening so since I ran out of ideas, I would like to know if some of the experts in this field could perhaps give me some guidelines.
    There's one caveat that I haven't mention yet and that is related to SQL, I checked and my user just has read access to SQL i'm not sure if that could affect this but i think is worth mentioning.
    My main goal is to have all the servers showing up in the Operations Manager Console.
    So thanks all in advance !
    Oscar Loria

    So you can ping and nslookup from your ms to these agents and vice versa right?  I wouldn't do a manual install, I would push the agent from the management server.  You can uninstall the agent manually, or use cleanmom to get rid of them.  Then
    do an install from the console.  When you initiate the install from the console (management server), should it run into any issues it will dump out an error which will give you an idea of where the problem may be.
    From Holmans post on this:
    e MOM Server could not execute WMI Query "Select * from Win32_OperatingSystem" on 
    computer “servername.domain.com” 
    Operation: Agent Install 
    Install account: DOMAIN\account 
    Error Code: 800706BA 
    Error Description: The RPC server is unavailable.
    The MOM Server could not execute WMI Query "(null)” on 
    computer “servername.domain.com” 
    Operation: Agent Install 
    Install account: DOMAIN\account 
    Error Code: 800706BA 
    Error Description: The RPC server is unavailable.
    8004100A 
    800706BA
    1.  Ensure agent push account has local admin rights 
    2.  Firewall is blocking NetBIOS access.  If Windows 2008 firewall is enabled, ensure “Remote Administration (RPC)” rule is enabled/allowed.  We need port 135 (RPC) and the DCOM port range opened for console push through a firewall.  
    3.  Inspect WMI service, health, and rebuild repository if necessary 
    4.  Firewall is blocking ICMP  (Live OneCare) 
    5.  DNS incorrect 
    http://blogs.technet.com/b/kevinholman/archive/2009/01/27/console-based-agent-deployment-troubleshooting-table.aspx
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

  • Manual install of patch 118844-28

    I'm trying to do a patchadd on 118844-28, but it complains that patch 117435-02 must be installed first or that the computer needs to be rebooted after the patch 117435-02 has been applied.
    When using the Update Manager it seems that 117435-02 has been installed and I've rebooted numerous times after that, but still when I try patchadd on the kernel patch above it gives me that error message.
    Am I doing something wrong or what's going on?
    It was quite awhile since I used Solaris and I've now installed Solaris 10 x86 1/06 and used the Update Manager to install patches, but the kernel patch apparently must be installed manually so I've done a "shutdown -i S" to get into single user mode (I'm not sure if that's how one is supposed to do it) then
    cd /var/sadm/spool/
    patchadd 118844-28
    Any ideas?

    There may be a bug in the patch, in the prepatch script to be precise.
    In the prepatch script there the line
    bootdev=`prtconf -v /devices | sed -n '/boot-device/{n;p;}' | grep pci | cut -f 2 -d \'`
    change boot-device to bootpath and then the patch seems to install alright.
    See this thread for more information http://forum.sun.com/thread.jspa?threadID=28707&tstart=0

  • Scom 2012 R2 Convert Manually installed Agents to Remotely managed

    Hi
    Need to convert manually installed agents to remotely managed.
    Found this post :
    http://damatisystemcenter.com/2013/01/25/convert-manually-installed-agents-to-remotely-managed/
    The last Query converts one agent to remotely managed
    How do I do if I want ALL my agents to be converted to remotely ?

    Hi,
    Setting Agents as Remotely Manageable in SCOM 2012 R2
    http://daxsnippets.wordpress.com/2014/04/08/setting-agents-as-remotely-manageable-in-scom-2012-r2/
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Can I manuall install latest SCDPM agent?

    If I manually  install the 2012 Data Protection Agent from the
    C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\ProtectionAgents\RA\4.2.1205.0
    directory, I then have to run an update to get to version 4.2.1254.0. Is there any way to do a manual install of the latest agent without having to update later?

    Hi,
    Yes, you can install the latest UR agent from under the C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\agents\RA\4.2.1254.0\amd64\1033
    Execute the DPMAgentInstaller_KB2966014_AMD64.exe
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • Do manually installed Agents failover?

    Hi, a very quick question that I can't find an answer for.
    Does automatic failover work (once configured) for a SCOM agent that is manually installed?
    I think they can't but would like confirmation.
    Cheers

    For SCOM 2012, all agents will automatic failover whether it is installed manually or not. you may also use the following powershell cmdlet to verify the auto failover of the agent
    #Verify Failover for Agents reporting to MS1
     $Agents = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq 'MS1.DOMAIN.COM'}
     $Agents | sort | foreach {
     Write-Host "";
     "Agent :: " + $_.Name;
     "--Primary MS :: " + ($_.GetPrimaryManagementServer()).ComputerName;
     $failoverServers = $_.getFailoverManagementServers();
     foreach ($managementServer in $failoverServers) {
     "--Failover MS :: " + ($managementServer.ComputerName);
     Write-Host "";
    Roger

  • Error installing DPM Agent in Update Rollup 5 for System Center 2012 R2 Data Protection Manager

    I have updated my main DPM server to Update Rollup 5 for System Center 2012 R2 Data Protection Manager and all went well.
    All Protected servers updated and rebooted and continued protection - EXCEPT one;
    Physical Windows Server 2012 R2 Datacenter.
    Tried Manual install - no luck
    Removed Protection Agent / rebooted / re-installed - no luck
    Installed all updates / re-install - no luck
    this seems to be the only indicated problem in MSDPMAgentInstall.LOG.....
    Property(S): PATCHMediaSrcProp = C:\Windows\Microsoft Data Protection Manager\DPM\ProtectionAgents\RA\4.2.1292.0\DPMProtectionAgent_KB3021791.msp
    MSI (s) (04:34) [09:24:23:772]: Product: Microsoft System Center 2012 R2 DPM Protection Agent - Update 'Microsoft System Center 2012 R2 DPM Protection Agent Update - KB3021791' could not be installed. Error code 1603. Additional information is available in
    the log file C:\Windows\\Temp\MSDPMAgentInstall.LOG.
    MSI (s) (04:34) [09:24:23:772]: Windows Installer installed an update. Product Name: Microsoft System Center 2012 R2 DPM Protection Agent. Product Version: 4.2.1292.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: Microsoft System
    Center 2012 R2 DPM Protection Agent Update - KB3021791. Installation success or error status: 1603.
    MSI (s) (04:34) [09:24:23:772]: Note: 1: 1729
    MSI (s) (04:34) [09:24:23:772]: Note: 1: 2205 2:  3: Error
    MSI (s) (04:34) [09:24:23:772]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1729
    MSI (s) (04:34) [09:24:23:772]: Note: 1: 2205 2:  3: Error
    MSI (s) (04:34) [09:24:23:772]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
    MSI (s) (04:34) [09:24:23:772]: Product: Microsoft System Center 2012 R2 DPM Protection Agent -- Configuration failed.
    MSI (s) (04:34) [09:24:23:772]: Windows Installer reconfigured the product. Product Name: Microsoft System Center 2012 R2 DPM Protection Agent. Product Version: 4.2.1292.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success
    or error status: 1603.
    Any help would be greatly appreciated.

    Hotfix for known issue with Update Rollup 5 for System Center 2012 R2 Data Protection Manager
    http://www.microsoft.com/en-us/download/details.aspx?id=45914&WT.mc_id=rss_alldownloads_all
    Have a nice day !!!
    DPM 2012 R2: Remove Recovery Points

  • Updatemanager java.null.pointer exception in installing patches !

    Hey,
    I started Updatemanager and get 8 patches to be installed on my system. When I click: Install 8 items now I get an exception from updatemanager:
    Updating the local cache complete.
    inside AvailablePanel.applyUpdateCollection()
    updateCollection: Current Available Updates
    updateCollection.getUpdates().length: 8
    mouse clicked at column index: 0
    java.lang.NullPointerException
    at com.sun.swup.client.engine.solaris.SolarisInstaller.beginInstall(SolarisInstaller.java:61)
    at com.sun.swup.client.ui.InstallDialog$InstallWorker.construct(InstallDialog.java:321)
    at com.sun.swup.client.ui.foundation.swing.SwingWorker$2.run(SwingWorker.java:109)
    at java.lang.Thread.run(Thread.java:595)
    and the installation process is stall. Nothing happens for hours so I have to manually kill the client, updatemanager. Every time I try I get this error which makes for me impossible to install patches !
    anyone any ideas what's going on ? I'm running Solaris 10 GA.
    thank you,
    stefan

    This issue should now be resolved. If you are using the Update Manager you will first need to manually update your analysis (click "Check for Updates") which will clear out the bad patch meta data causing the problem. You then should be able to use UM to install updates as intended.
    thanks for your patience
    -Dave

  • Install Nagios agents on Solaris 10 to monitor from RHEL 5

    Hi,
    Could anyone let me know the steps to be followed to install Nagios agents on Solaris 10 for monitoring from RHEL5. It is very urgent please help me.
    Thanks
    Rao

    Hi Sugunakar,
    There are a few small things I can think of checking:
    I am trying to install SMC on solaris 10What version of Solaris 10 are you using? You need 11/06 (aka "Update 3") or later. Also, it looks like this is on a V210: how much memory and swap do you have ([requirements here|http://docs.sun.com/app/docs/doc/820-2215/deployment-72?l=en&a=view])? And have you [edited your /etc/project file|http://docs.sun.com/app/docs/doc/820-2216/chapter2-1000?l=en&a=view] to adjust the shared memory settings?
    Have you applied any of the [patch sets|http://forums.halcyoninc.com/showthread.php?t=104]?
    smcdatabase service is always in maintenance mode.It would be interesting to see what that service log says. Look in /var/svc/log/application-management-sunmcdatabase:default.log for clues.
    /var/opt/SUNWsymon/install/guibased-setup.1285765588453.sh: /var/opt/SUNWsymon/db/data/SunMC/pg_hba.conf: cannot createIs there any reason why SunMC may not be able to write to /var (or /var/opt/SUNWsymon)? Maybe portions of /var are read-only (shared from a global zone, or over NFS)?
    I've done a lot of SunMC pilot projects over the years: if you could use some help speeding up your eval just send me an email.
    Regards,
    [email protected]

  • Install patch 8333939, error occurs

    Dear All,
    My customer trying to apply patch 8333939, but error occurs.
    Referred
    Note 1224313.1: Getting Started with Oracle E-Business Suite Plug-in, Release 4.0 (Doc ID 1224313.1)
    when running in the Section 5: Preparing Oracle Enterprise Manager 11g Grid Control
    and installing patch 8333939, error occurs:
    "the staging area needs oracle universal installer version 11.1.0.7.0 or late"
    EBS version: 11.5.10.2
    Platform: Linux x86-64
    I have following questions:
    1. Is this patch need to install on DB or APP?
    2. Customer has two OUI home, does he need to upgrade OUI home to 11.1.0.7.0 or later? How? Is there a patch number or something?
    [applprod3@ITEEBSTE oui]$ cat oraparam.ini |grep OUI_VERSION
    OUI_VERSION=10.1.0.6.0
    [applprod3@ITEEBSTE oui]$ pwd
    /EBSTEST/PROD3/apps/tech_st/10.1.3/oui
    [applprod3@ITEEBSTE oui]$ cat oraparam.ini |grep OUI_VERSION
    OUI_VERSION=10.1.0.6.0
    [applprod3@ITEEBSTE oui]$ pwd
    /EBSTEST/PROD3/apps/tech_st/10.1.2/oui
    Thanks,
    Jackie

    Hussein,
    I have a question.
    Is this means customer need to execute following steps first
    3. Install Oracle Enterprise Manager 11g Grid Control (11.1.0.1.0)
    3.1. Install OEM on the OMS server
    3.2. Install OEM Agents on the Targets (where EBS is installed)
    3.2.1. Targets having the same OS version as the OMS server
    3.2.2. Targets having different OS versions as compared to the OMS server
    Then, patch 8333939 can be applied successfully?
    Because refer to
    http://docs.oracle.com/cd/E17559_01/em.111/e18708/T506934T511454.htm
    Section "Running Oracle Universal Installer"
    It says:
    Stop all the Management Services before installing the pack to a Management Service. Management Services will be restarted automatically after the pack has been installed.
    Stop the OMS.
    $PROMPT> $ORACLE_HOME/bin/emctl stop oms
    Note: If your EM Repository (EM Database) is on the same machine, it must be left running. Only OMS and Agent services need to be taken down.
    Set the environment variable ORACLE_HOME to ORACLE_HOME of Management Service 11.1.0.1 as shown here:
    export ORACLE_HOME=/d1/oracle/em11g/oms11g
    Then unzip this patch and install it. Am I right?
    My customer's purpose is to install EM on R12, does
    Note 1224313.1: Getting Started with Oracle E-Business Suite Plug-in, Release 4.0 (Doc ID 1224313.1)
    is the correct note?
    Thanks,
    Jackie
    Edited by: Jackie Han on Sep 3, 2012 8:28 PM

  • Install protection agent failed. Error 324

    Hi
    So this is my problem.
    I have 2 Windows 2012R2 servers, where DPM2012R2 are installed on server2.
    They are both on the same domain and network. I have talked to the network team and there should not be anything that stops the DPMserver from talking to the agent on server 1.
    The errors i get are:
    Install protection agent on BRG-WI-HV01C01.felles.firma.no failed:
    Error 324: The agent operation failed because the DPM Agent Coordinator service on BRG-WI-HV01C01.felles.firma.no did not respond.
    Error details: Internal error code: 0x8099090E
    Recommended action: Do the following to troubleshoot this issue:
    1) Verify that BRG-WI-HV01C01.felles.firma.no is remotely accessible from the DPM server.
    2) If a firewall is enabled on BRG-WI-HV01C01.felles.firma.no, make sure that it is not blocking requests from the DPM server and has an exception for Windows Management Instrumentation(WMI).
    3) Try installing the agent manually by selecting "Attach Agents" in the agent installation wizard
    AND
    Agent operation failed. (ID: 370)
    The agent operation failed because the DPM Agent Coordinator service on BRG-WI-HV01C01.felles.firma.no did not respond. (ID: 324)
    I have done every test, firewall is of, the server is accessible, i have tried installing the agent manually and attaching it. Same errors.
    I have even tried removeing SCDPM and installing it again.
    Anyone have any idea what this could be?
    I tried installing the dpm agent from another server I have, and that worked fine. This DPM server is not on the same location or network, but they are in the same domain.

    Hi,
    <snip>
    I also tried to start the DPMRA service on the protected server and I get this error:
    Windows could not start the DPMRA on local computer.
    >snip<
    This problem needs to be fixed - the dpmra needs to be able to run either by manually starting it or by normal "on demand" request when a DPM job is initiated.
    If you look in the C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\dpmracurr.errlog and see if there are any clues why it cannot start.
    Manually delete any files or folders under the MTATempStore$ share on the DPM server. This is typically the c:\Program Files\Microsoft DPM\DPM\temp\MTA folder.
    DO NOTE DELETE the MTA folder itself.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
    posting is provided "AS IS" with no warranties, and confers no rights.

  • Failing to load processes after installing patch 10.1.2.3

    I have installed patch 10.1.2.3 after Oracle advised that it may resolve some database adapter problems I was getting in 10.1.2.0.2. However after installing the patch, many of the BPEL processes are now failing to load when I bounce the OC4J component and I am getting ORABPEL-05215 errors.
    I turned on debug logging and an extract of the log file is as follows, has anybody got any ideas on how I might resolve these errors;
    <2008-07-09 15:32:33,311> <ERROR> <default.collaxa.cube.engine.deployment> <CubeProcessLoader::create>
    <2008-07-09 15:32:33,310> <ERROR> <default.collaxa.cube.engine.deployment> Process "DRSSecuritiesReader" (revision "1.0") load FAILED!!
    <2008-07-09 15:32:33,375> <DEBUG> <default.collaxa.cube.engine.dispatch> <BaseDispatchSet::receive> Receiving message log process event message afa47b51cbfc4dfa:4ee70b:11b0
    83c6e51:-7ffc for set system
    <2008-07-09 15:32:33,376> <DEBUG> <default.collaxa.cube.engine.dispatch> <Dispatcher::adjustThreadPool> Allocating 1 thread(s); pending threads: 1, active threads: 0, total
    : 0
    <2008-07-09 15:32:33,378> <DEBUG> <default.collaxa.cube.engine.dispatch> <QueueConnectionPool::getConnection> Fetched a queue connection from pool java:comp/env/jms/collaxa
    /BPELWorkerQueueFactory, available connections=24, total connections=25
    <2008-07-09 15:32:33,403> <DEBUG> <default.collaxa.cube.engine.dispatch> <DispatcherBean::send> Sent message to queue
    <2008-07-09 15:32:33,403> <DEBUG> <default.collaxa.cube.engine.dispatch> <QueueConnectionPool::releaseConnection> Released queue connection to pool java:comp/env/jms/collax
    a/BPELWorkerQueueFactory, available connections=25, total connections=25
    <2008-07-09 15:32:33,404> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::bind> Exception while loading process
    java.lang.AbstractMethodError
    at com.collaxa.cube.engine.core.BaseCubeProcess.loadActivationAgents(BaseCubeProcess.java:946)
    at com.collaxa.cube.engine.core.BaseCubeProcess.load(BaseCubeProcess.java:310)
    at com.collaxa.cube.engine.deployment.CubeProcessFactory.create(CubeProcessFactory.java:66)
    at com.collaxa.cube.engine.deployment.CubeProcessLoader.create(CubeProcessLoader.java:391)
    at com.collaxa.cube.engine.deployment.CubeProcessLoader.load(CubeProcessLoader.java:302)
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(CubeProcessHolder.java:882)
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.getProcess(CubeProcessHolder.java:790)
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAll(CubeProcessHolder.java:362)
    at com.collaxa.cube.engine.CubeEngine.loadAllProcesses(CubeEngine.java:910)
    at com.collaxa.cube.admin.ServerManager.loadProcesses(ServerManager.java:284)
    at com.collaxa.cube.admin.ServerManager.loadProcesses(ServerManager.java:250)
    at com.collaxa.cube.ejb.impl.ServerBean.loadProcesses(ServerBean.java:219)
    at IServerBean_StatelessSessionBeanWrapper14.loadProcesses(IServerBean_StatelessSessionBeanWrapper14.java:2466)
    at com.collaxa.cube.admin.agents.ProcessLoaderAgent$ProcessJob.execute(ProcessLoaderAgent.java:401)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:141)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:281)
    <2008-07-09 15:32:33,419> <ERROR> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAll> Error while loading process 'DRSSecuritiesReader', rev '1.0': Error
    while loading process.
    The process domain encountered the following errors while loading the process "DRSSecuritiesReader" (revision "1.0"): null.
    If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
    ORABPEL-05215
    Error while loading process.
    The process domain encountered the following errors while loading the process "DRSSecuritiesReader" (revision "1.0"): null.
    If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:1270)
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(CubeProcessHolder.java:883)
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.getProcess(CubeProcessHolder.java:790)
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAll(CubeProcessHolder.java:362)
    at com.collaxa.cube.engine.CubeEngine.loadAllProcesses(CubeEngine.java:910)
    at com.collaxa.cube.admin.ServerManager.loadProcesses(ServerManager.java:284)
    at com.collaxa.cube.admin.ServerManager.loadProcesses(ServerManager.java:250)
    at com.collaxa.cube.ejb.impl.ServerBean.loadProcesses(ServerBean.java:219)
    at IServerBean_StatelessSessionBeanWrapper14.loadProcesses(IServerBean_StatelessSessionBeanWrapper14.java:2466)
    at com.collaxa.cube.admin.agents.ProcessLoaderAgent$ProcessJob.execute(ProcessLoaderAgent.java:401)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:141)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:281)

    I forgot to mention that I did flush the JAR cache to make sure the new JAR's would be downloaded.
    Gerrit

  • Smpatch update ALERT: Failed to install patch

    I do not even know where to start. Since installing Solaris 10 0606 it
    seems every time I try to patch the system I get failures of one type
    or another. One problem today has to do with zones:
    "To install the new instance of this package in all zones you must
    first remove the existing instance of this package from the global
    zone first (via pkgrm) and then install the new instance of this
    package in all zones."
    If sun already knows a pkgrm must be run why can't the smpatch command
    just do it?
    Another problem seems to be
    For patch 121018-03, required patch 120759-04 does not exist
    If sun knows a patch is required which is not on the system just Getit
    and install it.
    Also, what is up with having to reboot the box to install patches?
    Why? Has this always been a required step? Do these reboots pertain only to kernel patches .etc?
    I have seen other postings in this forum expressing unhappiness with
    the patch system, some mentioning testing lab/group or certification
    issues. I think smpatch should have an option to send smpatch results
    back to sun for review. That way the Certification Group could have
    real life situations to investigate. Or do they know the problems
    already and just dont want to fix them? Just once I would love it if
    smpatch came back with no failures and I was assured the system was
    patched, up to date and secure.
    Regards
    # smpatch update
    Update 120759-07 will not be downloaded since it already exists in the
    download directory.
    Update 121018-03 will not be downloaded since it already exists in the
    download directory.
    Update 121016-03 will not be downloaded since it already exists in the
    download directory.
    Update 121020-02 will not be downloaded since it already exists in the
    download directory.
    Update 121616-02 will not be downloaded since it already exists in the
    download directory.
    Update 120762-02 will not be downloaded since it already exists in the
    download directory.
    Installing patches from /var/sadm/spool...
    Failed to install patch 120759-07.
    patchadd utility failed. Reason code :0
    Validating patches...Loading patches installed on the
    system...Done!Loading patches requested to install.Done!Checking
    patches that you specified for installation.Done!Approved patches will
    be installed in this order:120759-07 Preparing checklist for
    non-global zone check...Checking non-global zones...The following
    requested patches rejected on non-global zone.Entire installation is
    possible but those patcheswill not be installed on non-global
    zone.myzone: Packages from patch 120759-07 are not installed on the
    system.myzone2: Packages from patch 120759-07 are not installed on the
    system.This patch passes the non-global zone check.None.Summary for
    zones:Zone myzoneRejected patches:120759-07 Patches that passed the
    dependency check:None.Zone myzone2Rejected patches:120759-07 Patches
    that passed the dependency check:None.Patching global zoneAdding
    patches...Checking installed patches...Verifying sufficient filesystem
    capacity (dry run method)...Patch 120759-07 failed to install due to a
    failure produced by pkgadd.See /var/sadm/patch/120759-07/log for
    detailsPatchadd is terminating. WARNING: patchadd returned <5> for
    global zone
    ALERT: Failed to install patch 120759-07.
    Failed to install patch 121018-03.
    patchadd utility failed. Reason code :0
    Validating patches...Loading patches installed on the
    system...Done!Loading patches requested to install.Done!Checking
    patches that you specified for installation.Done!The following
    requested patches will not be installed becauseno patches required by
    the patch are installed on this system. 0 For patch 121018-03,
    required patch 120759-04 does not exist.No patches to install.
    ALERT: Failed to install patch 121018-03.
    Failed to install patch 121016-03.
    patchadd utility failed. Reason code :0
    Validating patches...Loading patches installed on the
    system...Done!Loading patches requested to install.Done!Checking
    patches that you specified for installation.Done!The following
    requested patches will not be installed becauseno patches required by
    the patch are installed on this system. 0 For patch 121016-03,
    required patch 120759-06 does not exist.No patches to install.
    ALERT: Failed to install patch 121016-03.
    Failed to install patch 121020-02.
    patchadd utility failed. Reason code :0
    Validating patches...Loading patches installed on the
    system...Done!Loading patches requested to install.Done!Checking
    patches that you specified for installation.Done!The following
    requested patches will not be installed becauseno patches required by
    the patch are installed on this system. 0 For patch 121020-02,
    required patch 120759-01 does not exist.No patches to install.
    ALERT: Failed to install patch 121020-02.
    Failed to install patch 121616-02.
    patchadd utility failed. Reason code :0
    Validating patches...Loading patches installed on the
    system...Done!Loading patches requested to install.Done!Checking
    patches that you specified for installation.Done!Approved patches will
    be installed in this order:121616-02 Preparing checklist for
    non-global zone check...Checking non-global zones...The following
    requested patches rejected on non-global zone.Entire installation is
    possible but those patcheswill not be installed on non-global
    zone.myzone: Packages from patch 121616-02 are not installed on the
    system.myzone2: Packages from patch 121616-02 are not installed on the
    system.This patch passes the non-global zone check.None.Summary for
    zones:Zone myzoneRejected patches:121616-02 Patches that passed the
    dependency check:None.Zone myzone2Rejected patches:121616-02 Patches
    that passed the dependency check:None.Patching global zoneAdding
    patches...Checking installed patches...Verifying sufficient filesystem
    capacity (dry run method)...Patch 121616-02 failed to install due to a
    failure produced by pkgadd.See /var/sadm/patch/121616-02/log for
    detailsPatchadd is terminating. WARNING: patchadd returned <5> for
    global zone
    ALERT: Failed to install patch 121616-02.
    Failed to install patch 120762-02.
    patchadd utility failed. Reason code :0
    Validating patches...Loading patches installed on the
    system...Done!Loading patches requested to install.Done!Checking
    patches that you specified for installation.Done!Approved patches will
    be installed in this order:120762-02 Preparing checklist for
    non-global zone check...Checking non-global zones...The following
    requested patches rejected on non-global zone.Entire installation is
    possible but those patcheswill not be installed on non-global
    zone.myzone: Packages from patch 120762-02 are not installed on the
    system.myzone2: Packages from patch 120762-02 are not installed on the
    system.This patch passes the non-global zone check.None.Summary for
    zones:Zone myzoneRejected patches:120762-02 Patches that passed the
    dependency check:None.Zone myzone2Rejected patches:120762-02 Patches
    that passed the dependency check:None.Patching global zoneAdding
    patches...Checking installed patches...Verifying sufficient filesystem
    capacity (dry run method)...Patch 120762-02 failed to install due to a
    failure produced by pkgadd.See /var/sadm/patch/120762-02/log for
    detailsPatchadd is terminating. WARNING: patchadd returned <5> for
    global zone
    ALERT: Failed to install patch 120762-02.
    /var/sadm/spool/patchpro_dnld_2006.08.22@11:16:20:EDT.txt has been
    moved to
    /var/sadm/spool/patchproSequester/patchpro_dnld_2006.08.22@11:16:20:EDT.txt
    #

    Enterprise users have strict policies on change management so dependent patches are not automatically installed when using "smpatch add". Neither are packages blithly uninstalled for zones if currently only existing in the global zone.
    For your needs using "smpatch update" should analyse, download and install dependant patches in order for patches specified on the command line or for a global update. Note that that is with the exception of patches not matching the currently defined patch policy such as those needing a reboot. See the smpatch man page for information on policies.
    Patches requiring reboots or being installed in single user mode are primarily for kernel and driver patches.
    Your problems installing the Sun Studio 11 patches have been encountered previously in regards to globally installed packages (and are covered in this forum) and is due to a combination of bug ID's 6337009, 6214678 and 6374972 for the patching utilities of which the last is still open.
    You will currently have to manually install the patches using patchadd with the "-G" flag whilst in the global zone to install them in the global zone only.

Maybe you are looking for