CA Service Management

  • 1.  14.1 CUM 3 Patch installation in AA

    Posted Oct 26, 2016 07:09 AM

    Hi,

     

    Am trying to apply 14.1 CUM 3 Patch on top of CUM 2 and when i click on setup.exe file, am not getting any response and below errors logged in stdlog and jstd log. please help to fix

     

    std Log:

     

    ntservice.c            311 Command return non-zero exit code. Command: redirect -m "C:\Users\CASDAD~1\AppData\Local\Temp\2\tmp36" "C:\Users\CASDAD~1\AppData\Local\Temp\2\tmp37" "E:/PROGRA~2/CA/SERVIC~1/bin/sql_check_db"   -S -s SINMQY34 >"C:\Users\CASDAD~1\AppData\Local\Temp\2\tmp36" 2> "C:\Users\CASDAD~1\AppData\Local\Temp\2\tmp37" . Exit Code: 1

     

    jstd log:

     

    10/26 07:07:24.637[Thread-4] ERROR SLUMP 526 Can't logon to slump - check server daemons: java.io.IOException: java.net.ConnectException: Connection refused: connect

     

    please help.



  • 2.  Re: 14.1 CUM 3 Patch installation in AA

    Posted Oct 26, 2016 08:35 AM

    Hi Sheik,

    Few questions:

    1. did you uncaz the patch, then unzip the zip file that the .caz file delivers?

    2. did you right click on "setup.exe" and select "run as administrator"?

    3. there should also be an install log for the patch in the users temp directory which may give some additional info - does that file exist at this point when it gets stuck?

    4. was this system running properly prior to installing the patch? 

    5. also was there anything in the windows event logs?

    Let us know,

    Jon I.



  • 3.  Re: 14.1 CUM 3 Patch installation in AA

    Broadcom Employee
    Posted Oct 26, 2016 08:46 AM

    Client raised it in chat and it got resolved after uncommenting and  updating @NX_WEB_CGI_URL value in NX.env file.



  • 4.  Re: 14.1 CUM 3 Patch installation in AA

    Broadcom Employee
    Posted Oct 26, 2016 02:54 PM

    Thank you Sirisha.

     

    As an additional notes to others reviewing this thread, if you ever hit a point where you attempt to run the setup.exe and nothing happens the first thing you should check is the c:\stderr.txt and c:\stdout.txt files. When you review the file go to the bottom and see the last line processed before it stops, the last line typically will provide an indication of where the problem is occurring. I've seen similar issues related to the CABI url in the NX.env file.



  • 5.  Re: 14.1 CUM 3 Patch installation in AA

    Broadcom Employee
    Posted Oct 26, 2016 03:10 PM

    FYI - this scenario is described in TEC1868987