Error Messages in the Geoportal Web Application

Error Messages in the Geoportal Web Application

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 extension or user registration page, see Problems Connecting the Geoportal LDAP to Active Directory. Note: After changing any of the Geoportal configuration files during troubleshooting, your servlet engine (e.g., Tomcat) must be restarted for changes to take effect.

• Error message: The LuceneConfig indexLocation is empty. Action: Check that the <indexLocation> tag in the gpt.xml file has a folder path specified
• Error message: Could not translate gpt criteria as string query : Could not make xslt template from path null. Could not perform operation. Action: Check that the metadataAccessPolicy in the gpt.xml file has been specified properly.
• Error message: Error getting metadata: Error accessing full metadata xml for: {<Doc UUID>}. 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, GlassFish, and ServletExec, the JNDI connection is configured through these application servers' interfaces, as per their respective installation guides found in the Documentation folder when you run the Geoportal file installation media.
  • In your gpt.xml file, check that the user settings are correct, and that issues outlined in Problems for Connecting Geoportal LDAP to an Active Directory have been resolved. Especially check that the user specified in the catalogAdminDN attribute is a member of the Geoportal Administrators group in your LDAP structure.
• Error behavior: After logging in, the Administration and Repositories Tabs do not appear. Action: Check that the metadataAccessPolicy in the gpt.xml file has been specified properly. Also, follow troubleshooting suggestions in Problems for Connecting Geoportal LDAP to an Active Directory to verify that the <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: (Glassfish) 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 installation document for full instructions.