Cannot Access iPrint Web Page - Page Cannot be Displayed

  • 3936234
  • 14-Mar-2007
  • 26-Apr-2012


Novell Apache on NetWare 2.0.48
Novell iPrint for NetWare Novell NetWare 6.5 Support Pack 3
Novell iPrint for NetWare Novell NetWare 6.5 Support Pack 4
Novell iPrint for NetWare Novell NetWare 6.5 Support Pack 5
Novell iPrint for NetWare Novell NetWare 6.5 Support Pack 6


When attempting to hit the iPrint Web Page (either default or custom map) user receives 'Page Cannot Be Displayed' message.
After typing 'AP2WEBUP' at the server console, the'Apache2.nlm' and 'Aprlib.nlm' show a load status of 'OK' (both at the main server console and on the logger screen), but if the administrator looks at the list of available consoles (in RCONJ - click the down arrow and look through the list; - OR - if the administrator is physically at the server console, press CTRL+ESC) 'Apache 2.0.xx for Netware' is not displayed.


Most often the above situation is due to certificate corruption. This is typically resolved using the PKIDIAG utility or by exporting the trusted root certificate and replacing the SYS:\Public\RootCert.der file.
As a first step to resolving the issue, do the following:
  1. Type 'PKIDIAG' at the server console
  2. At this point you will be prompted to authenticate. You must log in with a user that has Administrator rights to the tree, and you must include the full context (including the leading dot) in the username.
  3. After you are logged in, enter the following options 4, 5, 6 and then enter 0 (zero) to run the utility (Before you hit the 0, the display should look something like this: 4) Actions: Fix mode 5) Default KMO replacement mode: Rekey existing KMO 6) Update default KMO mode: Always Re-key).
  4. After hitting '0' the utility will run, then provide a display of errors found, errors fixed, etc. and display a 'hit any key to continue' message. -- Hit Enter and that will bring you back to the system console.
  5. Enter the 'AP2WEBUP' command, then check the list of available consoles to see if 'Apache 2.0,xx for Netware' is displayed in the list.
If the PKIDIAG does not resolve the issue, do the following to capture Apache debug logs and to further troubleshoot the issue.
  1. Go to the Sys:\Apache2\logs directory on the iPrint server
  2. Delete the contents of the 'logs' directory
  3. Open the SYS:\Apache2\conf\httpd.conf file using Notepad from a workstation or through the Edit console on the server itself.
  4. Modify the 'Loglevel' setting in the httpd.conf file (this is usually about a third of the way down in the file) from 'warn' to'debug'
  5. Save the changes to the httpd.conf file
  6. At the server console, issue the 'AP2WEBUP' command
  7. View the contents of the 'SYS:\Apache2\logs\startup.err' file (or any other log files created during the startup process for Apache) either using Notepad or the Edit console at the server. **If there is only one file in the logs directory after a failed attempt to load Apache, then it will be the'startup.err'. If there are multiple files, your best bet is to begin troubleshooting with the error.log file.
  8. Based on the error message(s), conduct a knowledgebase search ( for the specific error.
If the startup.err shows the following message:'[error] (1)No such file or directory: LDAP: Could not open SSL trusted certificate authority file - SYS:/PUBLIC/rootcert.der' then export the trusted root certificate and replace the SYS:\Public\RootCert.der file with the newly exported certificate.
  1. Export the Self Signed Certificate from ConsoleOne.
  2. Open CA object in O=Security
  3. Select Certificates -> Self Signed Certificate
  4. Do not export the private key.
  5. Export the file in DER format; name it c:\RootCert.der

Additional Information

Due to the variety of possible messages contained in the logs we are unable to provide specifics for every possibility. As noted above, the most frequent cause of Apache load problems has to do with certificates; therefore, certificate troubleshooting steps are provided.