Virtual Office or NetStorage display "Internal Server Error 500"

When trying to access Virtual Office or NetStorage, an "Internal Server Error 500" page is displayed. Both Apache and Tomcat are running and other applications that use Tomcat are functioning correctly.

Other websites on the server are displayed without Apache server errors.

Virtual Office uses the Xtier registry keys to authenticate into the NetStorage portal. If these keys are not configured as they should be, Apache will have a problem getting to the Virtual Office login page. An "Internal Server Error 500" when trying to access the Virtual Office or NetStorage page is indicative that some of the XTier registry keys have been removed or changed in some way.

Verify that the folder sys:/xtier exists and that it is populated with files. Apache will likely fail if this doesn't exist but it is always good to make sure it is there by a visual inspection.

Check the XTier registry keys and make sure they exist.

1. Open Remote Manager in a browser (http://ipaddress_of_server:8008).
2. From the menu on the left, expand "Manage Applications" and then select "NetWare Registry."
3. Then navigate to the "My Server\Software\Novell\XTier\Configuration\XSrv\Authentication Domains" key value. This should be the value of the primary authentication server.

If any part of this path doesn't exist (for example: XTier is not found under "My Server\Software\Novell\") then follow TID 3374174: How to Recreate Missing XTier Registry Keys to create the keys.

After creating the XTier registry keys, stop Tomcat using 'tc4stop' and then delete the Tomcat cache, which is the sys:/tomcat/4/work/STANDALONE directory. After removing this directory, start tomcat with the 'tomcat4' command. When tomcat has finished loading, open a browser and point it to the Virtual Office page.

Virtual Office-- A blank page may indicate that there is a server specific setting in the sys:/tomcat/4/webapps/vo/WEB-INF/PortalServlet.properties file that isn't configured properly. Open this file and verify that the IP address for the 'System.DirectoryAddress' and'Custom_Backend_Renderer_Portal_Location' are correct. These should be the IP addresses of the LDAP authentication server and the server where the Virtual Office files are located respectively.

In clustered environments, please recall that these addresses should resolve to either the cluster IP address, or a master server that will be operational - if it points to a node and that node is down, VirtualOffice will not authenticate any users.