Other 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, 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 specified in geoportal.xml is correct.
- If the MetadataServer has been deployed (SDE-enabled database model only), check that the MetadataServer service has been configured correctly and has been started.
- If the MetadataServer has not been deployed - i.e. your geoportal uses the standalone database model - then check settings in your gpt.xml file according to the section on Troubleshooting for Connecting Geoportal LDAP to an Active Directory. Is the user specified in the catalogAdminDN attribute in 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 Connecting the Geoportal LDAP to 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.
