USS throws 500 error on search  on 17.2 

book

Article ID: 141704

calendar_today

Updated On:

Products

CA Service Catalog

Issue/Introduction

USS 17.1.x integrated with SDM and Catalog.     Intermittently USS Search usage results in HTTP STATUS 500

Cause

This problem is caused due to  jcifs.jar file is missing under  <USS HOME>\OSOP\tomcat-7.0.40\webapps\front-office-hook\WEB-INF\lib\  folder  on USS server 

Environment

Release : 17.2

Component : CA SERVICE CATALOG

Resolution

1)  With 17.1 USS version ,  you can open a support case to obtain a point fix T6EE503.caz  to apply on USS server  or you can use the approach mentioned in 2) below.

2)  With 17.2 USS version , there is no any point fix for this version of USS anymore .  But you can do the following to fix it :

 jcifs.jar  file  should be in both   <USS HOME>\OSOP\tomcat-7.0.40\webapps\ROOT\WEB-INF\lib\ folder and also  <USS HOME>\OSOP\tomcat-7.0.40\webapps\front-office-hook\WEB-INF\lib\  folder .    But with OOTB USS installation of 17.1 or 17.2  ,  this file is missing under <USS HOME>\OSOP\tomcat-7.0.40\webapps\front-office-hook\WEB-INF\lib\ folder  .

You can do the following to address this problem manually :

On your USS server machine

1)  go to <USS HOME>\OSOP\tomcat-7.0.40\webapps\ROOT\WEB-INF\lib\  folder  ,  copy jcifs.jar file 

2)  then go to <USS HOME>\OSOP\tomcat-7.0.40\webapps\front-office-hook\WEB-INF\lib\  folder  , paste that jcifs.jar file there .

3)  recycle USS service