Servicepoint Server not Available After Upgrade
Article ID: 255971
Updated On:
Products
Issue/Introduction
After upgrading SDM and Catalog from 17.3.0.15 to 17.4, ServicePoint does not show the Service Catalog offerings.
The post installation steps for CA Service Catalog were run, adding the next values in web.xml
<param-name>cors.allowed.origins</param-name>
<param-value>http://usshostname:ussport,http://servicepointhostname:servicepointport</param-value>
After restarting the services, the error persists, stating "Server is unavailable. Contact the Administrator".
Checking Task Manager Details page we only found the one microservice running on port 9444
The above screencap shows just one microservice, the Incident MS, running on port 9444. All microservices (incident, collab, insight, push, search) should be present
Environment
All versions of Service Desk Manager
Cause
When looking at the installation folders for the microservices it was noticed that the "lib" folder was missing from the folders for collabmicroservice, insightmicroservice, pushmicroservice, and searchmicroservice.
Resolution
We went to another server where the same install was successfully installed and created zip files of the lib files for those microservices.
We then unzipped those folders on the server with the problem, restoring the missing lib folders for those microservices.
After this we restarted xFlow and everything appears to be working now.
Root cause as to why those lib folders were missing was never found. Speculating possible permissions issue with updating the directory structure during install run.
Additional Information
For each RU installation, there are post-installation instructions that must be followed. For example, for SDM 17.4 RU1, the instructions can be found here:
Feedback
