Skip to content

Error Messages in the Geoportal Web Application

Jump to bottom
Marten Hogeweg edited this page Dec 14, 2012 · 1 revision

Listed below are some common errors that can occur when configuring your Geoportal, and how to begin for resolving them. For errors related to logging into the Geoportal or user registration page, see Connecting to a User Directory. Note: After changing any of the Geoportal configuration files during troubleshooting, the geoportal web application must be restarted for the changes to take effect.

Table of Contents

Error message: The LuceneConfig indexLocation is empty.

Action: Check that the <indexlocation></indexlocation> tag in the gpt.xml file has a local folder path specified.

Error message: Error getting metadata: Error accessing full metadata xml for: {}.

Action: Check the following things:

  • Check that the JNDI connection information is correct. For Tomcat, this is specified in the geoportal.xml context file. For WebLogic and GlassFish, the JNDI connection is configured through these application servers' interfaces, as per their respective installation guides (see Installation topic).
  • In your gpt.xml file, check that the user settings in the identity section are correct, and that issues outlined in Connecting to a User Directory have been resolved. If your geoportal is a version prior to 1.2, especially check that the user specified in the catalogAdminDN attribute is a member of the Geoportal Administrators group in your user directory structure (as of 1.2, the catalogAdminDN is no longer needed and thus is not in the gpt.xml file).

Error behavior: After logging in, the Administration tab does not appear.

Action: Follow troubleshooting suggestions in Connecting to a User Directory to verify that the <ldapadapter></ldapadapter> section in the gpt.xml file has been configured properly.

Error behavior: Download Tab does not appear.

Action: Check gpt.xml file and locate the taskUrl and mapserviceUrl tags. Verify that the geoprocessing and map service url are specified correctly.

Error behavior: Search results are not returning expected documents

Action: The search results returned are determined by what parts of the metadata are indexed. See Details of Lucene Indexing in the Geoportal to understand how to adjust the geoportal configuration such that the geoportal indexes your organization's fields of interest.

Error behavior: You made a configuration change, but the change doesn't appear when you re-launch the geoportal.

Action: If you are using Tomcat, you may need to delete the \\Tomcat\work\Catalina\localhost\geoportal folder. This folder acts as a cache for Tomcat so it doesn't have to rebuild your geoportal web application from scratch every time. Deleting the folder forces Tomcat to load the newly configured version of the web application. Caution: make sure you are deleting the one from the work folder and not the one from the webapps folder.

Error behavior, Glassfish-only: Navigation from Search page results in HTTP request error.

Action: Check the gpt.xml file that the searchResultsRender=jsf' has been added. This needs to be added in the Search setting section. Refer to the Glassfish Geoportal installation guide for full instructions.

Back to Common problems and solutions
Clone this wiki locally