Clarity

Expand all | Collapse all

Upgrade 12.1 to 13.1 fails after 13.0

  • 1.  Upgrade 12.1 to 13.1 fails after 13.0

    Posted Jun 20, 2013 05:24 PM
    Upgrade 12.1 to 13.1 fails after 13.0
    What do I do differently to get upgrade fro m13.0 to 13.1 also done?

    I've been trying to upgrade 12.1 to 13.1 for some timeand have not got there yet.
    I posted in another thread how upgrade first from 12.1 to 13.0 was successful and then failed in 13.0 to 13.1, see
    101225418
    Nika pointed out that it was due to a bug and showed the workaround.

    Now I am back to the problem in running the 13.1 upgrade directly on 12.1

    The starting point is

    Folders


    Clarity - 12.1 installation
    Clarity_13 - to be given as the target folder for upgrade
    jdk - jdk 6
    jdk7 - jdk 7
    Old Tomcat - Tomcat 6.026 for 12.1
    Tomcat - Tomcat 7.026


    When I gave the Clarity folder as the target for the upgrade the install failed in a few minutes.
    Therefore I had to Create Clarity_13 for the upgrade.


    The install folder only contains the clients and the install.jar because in the upgrade the database already exists,
    jdk 7 and Tomcat 7 are alredy installed.

    Environmental variables

    CLARITY_HOME=D:\Clarity_13
    JAVA_HOME=D:\jdk7
    NIKU_HOME=D:\Clarity_13

    PATH
    Path=D:\jdk7\bin;D:\Clarity_13\bin;C:\Windows\system32;...

    caches.xml in %NIKU_HOME%\.setup\templates\config

    v12.1.1 was dated 6/28/2012
    v13.0 was dated 3/22/2011 (from the 13.0 - 13.1 upgrade)

    So I copied the older file to ..\Clarity\config

    Start the upgrade
    jar -xvf install.jar and after unjarring delete install.jar to save space.
    Answer all questions
    Eg current install Clarity
    Target upgrade Clarity_13

    The installation in the command window finishes with




    [color=#2c95ff][size=4]-----------------------------------------------------
    2013-06-19 00:41:04: Finished updating database
    -----------------------------------------------------

    Trying to override old definition of task java

    init:

    postupgrade:
    Installation Successful - 19-June-2013 00:41:08

    BUILD SUCCESSFUL
    Total time: 27 minutes 27 seconds
    Trying to override old definition of task java

    init:

    _stop-services:
    Trying to override old definition of task java

    _stop-service:
    service id = beacon
    servicecmd = service.bat
    No registered service(s) found.
    Trying to override old definition of task java

    _stop-service:
    service id = app
    servicecmd = service.bat
    [-] Niku Server [app] is already stopped
    Trying to override old definition of task java

    _stop-service:
    service id = nsa
    servicecmd = service.bat
    [-] Niku System Admin Server [nsa] is already stopped
    Trying to override old definition of task java

    _stop-service:
    service id = bg
    servicecmd = service.bat
    [-] Niku Background Server [bg] is already stopped
    release.exec.result = Result: 1

    BUILD FAILED
    D:\131_u\gateway.xml:35: The following error occurred while executing this line:

    D:\131_u\install.xml:209: The following error occurred while executing this line
    :
    D:\131_u\install.xml:370: The following error occurred while executing this line
    :
    D:\131_u\install.xml:396: The following error occurred while executing this line
    :
    D:\131_u\install.xml:418: The following error occurred while executing this line
    :
    D:\131_u\install.xml:732: The upgrade step for 13.0.0 failed. Please consult the

    D:\131_u\install-packages\13.0.0\upgrade-repack.13.0.0.7032a/in
    stall.log for that release package."

    Total time: 28 minutes 47 seconds
    [size]
    [color]

    The lines referenced are
    [color=#2c95ff][size=4]
    gateway.xml:35

    <ant antfile="${target.ant.file}" target="${install_target}"/>

    install.xml:209

    <antcall target="_upgrade"/>


    install.xml:370

    <if property="proceedWithCaution" value="y" target="_proceed-upgrade"/>


    install.xml:396

    <foreach list="${release.list}" param="release.package" target="_process-release" inheritAll="true"/>


    install.xml:418

    <antcall target="_install-release">


    install.xml:732

    <fail>The upgrade step for ${release.package} failed. Please consult the
    ${release.package.path}/install.log for that release package."
    </fail>
    [size]
    [color]
    which don't really help at all

    The end of
    D:\131_u\install-packages\13.0.0\upgrade-repack.13.0.0.7032a/install.log
    is
    [color=#2c95ff][size=4]
    6/19/13 12:40 AM (ExecTask) ==========================================
    6/19/13 12:40 AM (ExecTask) DBTools Log - Wed Jun 19 00:40:21 EEST 2013
    6/19/13 12:40 AM (ExecTask) ==========================================
    6/19/13 12:40 AM (ExecTask)
    6/19/13 12:40 AM (ExecTask) Command: extract row count
    6/19/13 12:40 AM (ExecTask) To URL: jdbc:clarity:sqlserver://W2008:1433;DatabaseName=clarity;InsensitiveResultSetBufferSize=0;ProgramName=Clarity
    6/19/13 12:40 AM (ExecTask) As user: niku
    6/19/13 12:40 AM (ExecTask) For vendor: mssql
    6/19/13 12:41 AM (ExecTask)
    6/19/13 12:41 AM (ExecTask) Total time: 0H:0M:42S
    6/19/13 12:41 AM (ExecTask)
    6/19/13 12:41 AM (ExecTask) -----------------------------------------------------
    6/19/13 12:41 AM (ExecTask) 2013-06-19 00:41:04: Finished updating database
    6/19/13 12:41 AM (ExecTask) -----------------------------------------------------
    6/19/13 12:41 AM (ExecTask)
    6/19/13 12:41 AM (Target) Target "installsteps" finished.
    6/19/13 12:41 AM (Project) Trying to override old definition of task java
    6/19/13 12:41 AM (Target) Target "init" started.
    6/19/13 12:41 AM (Target) Target "init" finished.
    6/19/13 12:41 AM (Target) Target "postupgrade" started.
    6/19/13 12:41 AM (Target) Target "postupgrade" finished.
    6/19/13 12:41 AM (Echo) Installation Successful - 19-June-2013 00:41:08
    6/19/13 12:41 AM (Target) Target "_install" finished.
    6/19/13 12:41 AM (Target) Target "_upgrade" finished.
    6/19/13 12:41 AM (Target) Target "install" finished.
    [size]
    [color]
    which is not in line with what was displayed in the command window.


    If I look at cmn_install_history in the database



    that looks like the db was updated to v.13.0

    When I look at the service the niku services are there, no CA Clarity PPM services.

    Why did the install stop after an apparently successfull upgrade to 13.0 ?

    Manually I would continue by removing the niku services, create new services from the current Clarity folder
    and then go to to the newly created ..\131\install-packages\13.1.0
    and run the install from there.




    Martti K.


  • 2.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Jun 22, 2013 03:42 PM
    Martti,

    Try to do it removing services before to run install.bat script

    Regards
    Nico


  • 3.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Jun 24, 2013 02:20 AM
    We are using Windows and SQL server database backend.

    CA advised that the critical upgrade path must be from Clarity 12.0.4 to 12.0.6. Then 12.0.6 to 12.1.1. Then 12.1.1 to 13.1.

    We followed this recommendation and successfully upgraded from 12.0.4 to 13.1.

    Hope this helps.


  • 4.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Jun 24, 2013 03:24 AM
    Thanks
    Did you run the v.13.1 install when you had 12.1.? That is what I tried to do.
    As I write the 13.0 part install apparently finished OK except for setting up so that it could continue to 13.1. Did yours continue without any other action?

    Which jdk's did you have installed?
    What were the JAVA_HOME, CLARITY_HOME, NIKU_HOME and PATH when you started.
    Did you specify the same of different folder for the new version of Clarity when starting the install from 12.1

    Once 13.0 install completed were you asked for more questions?

    Martti K.


  • 5.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Jun 24, 2013 05:58 AM
    Hi Martti,

    Your log shows "No registered service(s) found." when stopping thea beacon.

    Our service had a similar problem once, and the reason was that some services have been removed before the upgrade was started.
    The installation tries to stop the app, bg, beacon, nsa services, it can't and failes.

    Try to ADD the beacon service and rerun the install.

    Kind regards,

    Sergiu Gavrila

    ------------------
    itd Assignment Editor - Effective Multiproject Resource Planning and Capacity Analysis www.itdesign.de/itd-addons/
    itd WebDAV - Easy Access to Documents in CA Clarity PPM www.itdesign.de/itd-addons/


  • 6.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Jun 24, 2013 11:10 AM
    I've experienced this issue before.

    The problem in my experience stems from the Beacon.

    Because your system still shows the Windows services being called "Niku Beacon" instead of "Clarity PPM Beacon" the build has generally failed because of that.

    However, if you go into the Services and check to see if the Clarity (Niku) services exe path is updated to the new install location, you should be able to start the services fine and proceed.


  • 7.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Jun 24, 2013 02:29 PM
    Sergiu and Rob-FCB thanks.

    The stop service fail, because new CA Clarity services are not there.
    If I wanted to continue manually I should remove the Niku services and create the Clarity services with the service add command. However, that gives no glue while the install did not finish on its own.

    One though is thought: being a single server I did not have Beacon. If I started from fresh again I could create beacon, too.

    Martti K.


  • 8.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Jun 24, 2013 11:10 AM
    I've experienced this issue before.

    The problem in my experience stems from the Beacon.

    Because your system still shows the Windows services being called "Niku Beacon" instead of "Clarity PPM Beacon" the build has generally failed because of that.

    However, if you go into the Services and check to see if the Clarity (Niku) services exe path is updated to the new install location, you should be able to start the services fine and proceed.


  • 9.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Broadcom Employee
    Posted Jul 26, 2013 11:37 AM
    Hi Martti,

    From what I can see, the installer could not deploy the services after successful upgrade of Clarity and database to 13.0. You should be able to safely run the upgrade to 13.1 now, with no issues. Please could you upload the complete install.log? I would like to check if there is no error code in the beginning of the install, as sometimes it happens at previous points.

    Regards
    Nika


  • 10.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Jul 26, 2013 03:59 PM
    Thanks, will do so, but it will be a couple of weeks before I can really sit down at the home office.

    Martti K.


  • 11.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Feb 03, 2014 02:24 PM

    Removed the Niku services before upgrading to v13.1

    New services were created - the Niku services and the upgrade fails as before.

     

    Martti K.



  • 12.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Broadcom Employee
    Posted Feb 04, 2014 04:33 PM

    Hi Martti,

    Would you mind uploading your latest install.log please? I would like to take a closer look.

    Many thanks in advance,

    Kind Regards,
    Nika



  • 13.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Feb 04, 2014 11:52 PM

    Here you go.

     

    Martti K:

    Attachment(s)

    txt
    admin.txt   13 KB 1 version
    txt
    install.txt   98 KB 1 version


  • 14.  RE: Upgrade 12.1 to 13.1 fails after 13.0
    Best Answer

    Broadcom Employee
    Posted Feb 05, 2014 12:24 PM

    Hi Martti,

     

    The error that failed your upgrade is the following:

     

    2/01/14 12:09 AM (ExecTask) Updating xogseeddata for component = database
    2/01/14 12:09 AM (ExecTask) Created dir: D:\Clarity\logs\xog-seeddata\out\database
    2/01/14 12:09 AM (ExecTask)      Applying lookup_autosuggest_corrections.xml
    2/01/14 12:09 AM (ExecTask)      Applying OBJECT_ACTION_MENU_ITEM_LOOKUPS.xml
    2/01/14 12:09 AM (ExecTask)      Applying platform_lookups.xml
    2/01/14 12:10 AM (ExecTask)      Applying XOG_ACCESS_RIGHTS.xml
    2/01/14 12:10 AM (ExecTask) Error Applying XOG: null
    2/01/14 12:10 AM (ExecTask) java.lang.NullPointerException
    2/01/14 12:10 AM (ExecTask)      at com.niku.security.service.AuthenticationService.removeSessionCaches(AuthenticationService.java:960)
    2/01/14 12:10 AM (ExecTask)      at com.niku.security.service.AuthenticationService.delete(AuthenticationService.java:231)
    2/01/14 12:10 AM (ExecTask)      at com.niku.xog.client.XOGAdminClient.processFileDescriptors(XOGAdminClient.java:793)
    2/01/14 12:10 AM (ExecTask)      at com.niku.xog.client.XOGAdminClient.execute(XOGAdminClient.java:437)
    2/01/14 12:10 AM (ExecTask)      at com.niku.xog.client.XOGAdminClient.main(XOGAdminClient.java:221)
    2/01/14 12:10 AM (ExecTask) D:\Clarity\.setup\scripts\db.xml:1800: The following error occurred while executing this line:
    2/01/14 12:10 AM (ExecTask) D:\Clarity\.setup\scripts\db.xml:1970: The following error occurred while executing this line:
    2/01/14 12:10 AM (ExecTask) D:\Clarity\.setup\scripts\db.macros.xml:92: Java returned: 3
    2/01/14 12:10 AM (ExecTask)      at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:551)

    This is a known Clarity issue you could fix by replacing the caches.xml file. Basically you have some old entries in your caches.xml file. So please do the following:

    1. Restore your environment to 12.1.1
    2. Remove the services as before
    3. Copy the caches.xml file from $CLARITY_HOME\.setup\template\config to $CLARITY_HOME\config, replacing the existing file
    4. Restart the upgrade

    For more information please check TEC578077.

    I will be looking forward to hearing from you, please let me know how it goes.

    Kind Regards
    Nika



  • 15.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Feb 05, 2014 04:05 PM
      |   view attached

    If you look at
    https://communities.ca.com/web/ca-clarity-global-user-community/message-board/-/message_boards/view_message/101223961?&#_19_message_101242820

    I have already done it and it did not work.

    This is the thread where I have first successfully upgraded to 13.0 which works OK and then try to upgrade to v13.1

    Replacing the caches.xml did not work. The install failed even faster.

     

    Somehow the instruction to roll back to back to v12.1 when the system is already upgraded into v13.0 and in use doesn not sound good.

    A better approach would be a revision of the install package which does not require that replacement, but contains everyhting that is needed for an install.

    My understanding was that v13.1 and later have improved install with preinstallcheck. That should detect problems like this.

    Further TEC578077 says This issue is fixed in 13.1.0.1 and 13.2. Does that mean

    1. If you upgrade to v13.2 this problem does not occur - to me it did- or

    2. When you upgrade from v13.2 you don't have the problem? If that is the case how do you get to v13.2?

     

    Martti K.

     

    Attachment(s)

    txt
    install.txt   1.06 MB 1 version


  • 16.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Broadcom Employee
    Posted Feb 05, 2014 05:31 PM

    Hi Martti,

     

    Thanks for your update and the link to the other thread, I had forgotten about this one :)
    While I reviewed your current log, it looks good : you fixed the caches.xml error and your upgrade failed because of another issue.
    The current error is:

    2/05/14 10:35 PM (UnknownElement) Task "move" finished with error.
    C:\131\install-packages\13.1.0\install.xml:230: Unable to delete directory D:\Clarity\.setup
                    at org.apache.tools.ant.taskdefs.Move.deleteDir(Move.java:305)
                    at org.apache.tools.ant.taskdefs.Move.deleteDir(Move.java:277)
                    at org.apache.tools.ant.taskdefs.Move.deleteDir(Move.java:295)
                    at org.apache.tools.ant.taskdefs.Move.deleteDir(Move.java:277)
                    at org.apache.tools.ant.taskdefs.Move.doFileOperations(Move.java:175)

    I would guess you still had the folder open in cmd or Windows Explorer, or didn't have permissions to actually delete it for other reasons.

    I completely understand your concern about having to rollback every time, but I am afraid that currently Clarity install on version 13 cannot be "resumed" in a supported way. Our Sustaining Engineering department is aware about this being an issue and is working out on improving the functionality.  I would not recommend you to force it to continue as you may get other issue related to missing/half-moved folders.

    Concerning the fix for the defect: I just checked the way it's done and the fix will actually automatically roll-back any of the changed setting in the file caches.xml to match the one provided under the templates directory. This change will happen on 13.1.0.1 and 13.2 which means that the issue during upgrade will still occur while upgrading to 13.2 (as the stages are (13.0>13.1>13.2), but not after this anymore.

    However as we know that your environment has old entries in the file we will just prevent this from happening by replacing it in advance prior to upgrade. Do you think we can rollback to 12.1.1, replace the caches file, remove the services and start the upgrade?

    Please let me know your feedback,

    Kind Regards
    Nika



  • 17.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Feb 06, 2014 04:14 PM

    Thank you Nika. That certainly did the trick.

    So the resolution for this thread is as you posted

    This is a known Clarity issue you could fix by replacing the caches.xml file. Basically you have some old entries in your caches.xml file. So please do the following:

    1. Restore your environment to 12.1.1
    2. Remove the services as before
    3. Copy the caches.xml file from $CLARITY_HOME\.setup\template\config to $CLARITY_HOME\config, replacing the existing file
    4. Restart the upgrade

    For more information please check TEC578077

    For dummies like me an additional note: Close all Explorer and other windows to the Install folder so that the install script can make the necessary changes.

     

    Martti K.



  • 18.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Feb 06, 2014 04:21 PM

    Consider yourself telehugged again.

     

    Martti K.



  • 19.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Feb 09, 2014 01:39 PM

    Also upgrading from v13.0 to v13.3 on another instance went smooth in 94 minutes after fixing the caches.xml

     

    Martti K.



  • 20.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Broadcom Employee
    Posted Feb 10, 2014 10:13 AM

    Great news Martti! Glad this worked smiley



  • 21.  RE: Upgrade 12.1 to 13.1 fails after 13.0

    Posted Feb 10, 2014 12:29 PM

    Yes, ain't it. Thanks to your persistent help. ;-)

     

    Martti K.