CA Service Management

Expand all | Collapse all

Xflow 17.2 Post Installation error

  • 1.  Xflow 17.2 Post Installation error

    Posted 17 days ago
    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 17 days ago
    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 17 days ago
    Hi Brian

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






  • 4.  RE: Xflow 17.2 Post Installation error

    Posted 17 days ago
    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 14 days ago
    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 11 days ago
    anyone can pls. advise on this issue? 






  • 7.  RE: Xflow 17.2 Post Installation error

    Posted 4 days ago
    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