My Oracle Support Banner

File Manager Fail To Start and Filemanager Configuration Page Ends In HTTP Status 500 (Doc ID 2448323.1)

Last updated on MAY 21, 2021

Applies to:

Oracle Agile PLM Framework - Version 9.3.6.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
When trying to start the File Manager using the start script, it ends in below error from the log. 

ERROR

******************************************************************************************************************
*** File Manager Initialization failed ***
Reason :Error downloading information from Agile.

The failure could be attributed to:
1. The Application Server is currently Unavailable
2. File Manager is not configured correctly - [Admin -> Server Settings -> Locations -> <File Manager Entry>-> File Manager Internal Locator] must EXACTLY match the above-mentioned FileManager URL
3. File Manager Entry has been DISABLED or the setting is incorrectly specified
4. ifsuser username/password may not be correct.
*********************************************************************************************************************

FACT

File Manager Configuration page is displaying HTTP Status 500 error.

HTTP Status 500

type Exception report

message
description The server encountered an internal error that prevented it from fulfilling this request.

exception

java.lang.NullPointerException
com.agile.webfs.configuration.FMInformationStore.getAppServerURL(FMInformationStore.java:535)
com.agile.webfs.admin.FileManager.checkServerConfiguration(FileManager.java:132)
com.agile.webfs.admin.FileManager.CheckFMConfiguration(FileManager.java:110)
com.agile.webfs.admin.FileManager.handleRequest(FileManager.java:101)
com.agile.webfs.admin.FileManager.doGet(FileManager.java:91)
javax.servlet.http.HttpServlet.service(HttpServlet.java:622)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
note The full stack trace of the root cause is available in the Apache Tomcat/8.5.3 logs.


STEPS
The issue can be reproduced at will with the following steps:
1. Start File Manager using the start script : startup.sh

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.