Clarity

 View Only
  • 1.  CA PPM Upgrade From 15.3 to 15.8 Fails

    Posted Jun 03, 2020 09:00 PM
      |   view attached
    Hello all, 

    I am having an issue while upgrading from 15.3 to 15.8. I add first couple of line error message when the first time I get it. Also I attached the install.log file. 

    6/04/20 3:36 AM (ExecTask) The service name is invalid.
    6/04/20 3:36 AM (ExecTask) The service name is invalid.
    6/04/20 3:36 AM (ExecTask) 
    6/04/20 3:36 AM (ExecTask) More help is available by typing NET HELPMSG 2185.
    6/04/20 3:36 AM (ExecTask) 
    6/04/20 3:36 AM (UnknownElement) Task "exec" finished with error.C:\beat\upgStage\PPM_15_8\install.xml:1161: exec returned: 1 at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:643) at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:669) at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:495) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38) at org.apache.tools.ant.Project.executeTargets(Project.java:1248)


    Thank you

    ------------------------------
    Software Specialist
    Beat Software Solutions
    ------------------------------

    Attachment(s)

    log
    install.log   2.11 MB 1 version


  • 2.  RE: CA PPM Upgrade From 15.3 to 15.8 Fails

    Broadcom Employee
    Posted Jun 03, 2020 09:22 PM
    Hi Ferhat
     Please rollback the filesystem, and before you try again, remove the services:
    service stop remove all
    See if this works for you

    ------------------------------
    Nika Hadzhikidi
    Sr Principal Support Engineer
    Broadcom
    ------------------------------



  • 3.  RE: CA PPM Upgrade From 15.3 to 15.8 Fails

    Posted Jun 04, 2020 08:06 AM
    Edited by Ferhat Kuran Jun 04, 2020 08:06 AM
      |   view attached
    Hi Nika, thank you for you early reply. I managed to pass that step after rollback the filesystem. Now I'm getting sql error in step 15.7.1. I share both install.log and specific part from install.log that only contain the error.

    Thank you for your help. 
    ------------------------------
    Software Specialist
    Beat Software Solutions
    ------------------------------

    Attachment(s)

    log
    install2.log   2.12 MB 1 version


  • 4.  RE: CA PPM Upgrade From 15.3 to 15.8 Fails
    Best Answer

    Broadcom Employee
    Posted Jun 04, 2020 08:25 AM
    Hi Ferhat

    This is an issue with the Compatibility level in MSSQL, you have to rollback, ensure the compatibility is set to 130, and then retry the upgrade.
    Here is the KB with the information:
    https://ca-broadcomcsm.wolkenservicedesk.com/wolken/esd/knowledgebase_search?articleId=142274

    ------------------------------
    Nika Hadzhikidi
    Sr Principal Support Engineer
    Broadcom
    ------------------------------



  • 5.  RE: CA PPM Upgrade From 15.3 to 15.8 Fails

    Posted Jun 04, 2020 09:08 AM
    I just found it after I post here. Maybe docops must be updated. I remember that compatibility level must be 120 written in docops.

    Thank you Nika. I ll let you know when upgrade successfully finished. Have a good day

    ------------------------------
    Software Specialist
    Beat Software Solutions
    ------------------------------



  • 6.  RE: CA PPM Upgrade From 15.3 to 15.8 Fails

    Broadcom Employee
    Posted Jun 04, 2020 09:42 AM
    Thank you Ferhat, keep me updated! The Compatibility level we request is different for each MSSQL version, this is why we needed 120 before, and now it's different.

    ------------------------------
    Nika Hadzhikidi
    Sr Principal Support Engineer
    Broadcom
    ------------------------------