CA Service Management

 View Only
  • 1.  Xflow 17.2 Post Installation error

    Posted Oct 12, 2020 09:17 AM
    HI Team

    We are running with SDM 17.2 AA mode and ow installing installing Xflow 17.2 in one of our application server and we are getting below error in post installation. How can we resolve this.?
    below is the install.log snapshot.
    Can anyone advise how to overcome.









  • 2.  RE: Xflow 17.2 Post Installation error

    Broadcom Employee
    Posted Oct 12, 2020 09:55 AM
    Hi Asim,

    It looks like the install fails trying to integrate Jasper (Insights) with xFlow. Is there a JasperReports in the mix?


    ------------------------------
    Kind Regards,
    Brian
    ------------------------------



  • 3.  RE: Xflow 17.2 Post Installation error

    Posted Oct 12, 2020 12:27 PM
    Hi Brian

    No, we do not have Jasper installed in our environment. 






  • 4.  RE: Xflow 17.2 Post Installation error

    Posted Oct 12, 2020 12:32 PM
    Hi brian

    I checked Initial load on search server installation. Is this could be reason of this issue? 






  • 5.  RE: Xflow 17.2 Post Installation error

    Broadcom Employee
    Posted Oct 15, 2020 01:28 PM
    It seems to be a problem with the connection to the database. Please check the following document with the same SU2017 error message:
    https://knowledge.broadcom.com/external/article?articleId=14817
    Regards, 
    Pablo

    ------------------------------
    Senior Support Engineer
    ------------------------------



  • 6.  RE: Xflow 17.2 Post Installation error

    Posted Oct 18, 2020 11:39 AM
    anyone can pls. advise on this issue? 






  • 7.  RE: Xflow 17.2 Post Installation error

    Posted Oct 25, 2020 01:12 PM
    The issue has been resolved.

    the path for casm_insight. properties file is long and the data type for column PATH is nvarchar(100) in al_cdb_filrs table , thus the the entry was not creating during the post installation due to characters limit. 

    The actualy size of this column is (200) but during the upgrade from 14.1 to 17.2, this was not updated and remain 100 which caused the issue.

    We ran alter query to update this and after that the installation successful