ShowTable of Contents
Troubleshooting IBM Lotus Notes issues
This document discusses basic troubleshooting tips for common IBM® Lotus® Notes® v8 issues.
If you have trouble connecting to your server, there are some basic troubleshooting tools to determine whether the issue is related to your network environment.
Ping is a network administration utility commonly used to test if a computer is reachable on an Internet Protocol network environment. It basically measures the round-trip time for messages sent from your computer to a destination computer you specify.
You can ping a computer by opening Command Prompt window and executing the ping.exe file pointing it to a computer of your choice, either by IP address or host name, as shown in figure 1.
Figure 1. Example ping command
In this example, you can see that the computer specified by host name leonardo2.austin.ibm.com can be reached successfully, and the time it takes for a message to go and come back is listed in milliseconds. This means that you have a successful network connection from your workstation to the computer you specified above.
If the ping result was negative, it would indicate a network issue between your workstation and the specified computer. You should first check locally to see if you can identify the problem such as a loose or unplugged cable, a disabled network adapter, etc.
You could perform the same test on a workstation next to you to compare the results; if neither can ping the server, it could indicate an issue with the server, but if the other workstation can ping the server while yours cannot, it indicates there is a problem with your machine.
If, even after performing the basic troubleshooting and checking for the more common issues, you are still not able to identify the cause of the problem and fix it, you should contact your network administrator for further help.
Telnet is a network utility that allows you to connect to a remote host computer over a TCP/IP network. You can use the telnet software client on your computer to attempt to establish a connection to a remote host and a remote port you specify.
Knowing that the standard port that Notes and IBM Lotus Domino® use is port 1352, you could use the Telnet utility to try to establish a connection to your Domino server on port 1352, which should be the port that Domino is listening for incoming connections, to make sure that your Domino server is online and responding.
Let's look at an example of checking basic connectivity to a Domino server that is listening to connections on port 1352:
1. Open a Command Prompt window and enter the command shown in figure 2, using the syntax “telnet server_name port_number”:
Figure 2. Telnet command entered
2. After you execute the above command, the window in figure 3 should display. As you can see, you are now using the Telnet utility to connect to the server leonardo2.austin.ibm.com on port 1352, as previously specified.
Figure 3. Telnet command executed
3. Next, press CTRL + ] to display a window like that in figure 4.
Figure 4. Welcome to Telnet window
4. At this point you could enter “?” for a list of available options; however, for our purposes we just enter “status” to show that the client is, in fact, connected to the server on port 1352 (see figure 5).
Figure 5. Status command
As shown above, we confirmed that the workstation could connect to port 1352 on the Domino server, indicating that the server is up and running. If the test had failed, it would indicate an issue connecting to the the server on the port specified.
You can use the combined results obtained from the Ping and Telnet tests to troubleshoot connectivity issues. For example, if you can ping the server, but you cannot connect to port 1352, it means that you have a working connection to the server but the service is not online. A probable assumption is that your Domino server is down and therefore you cannot connect with your Notes client either.
For more information about using Telnet to check connectivity to a Domino server using port 1352, refer to IBM Support Technote #1248258, ”How to check connectivity over port 1352 with Telne
If your Notes client is not working as expected, it might indicate a database corruption. Database corruption can be generally characterized as when a part or the entire database has suffered data loss, integrity issues, inconsistent data, limited functionality, or is just plain unreadable.
When you have this situation in any local databases, you can try to run maintenance with some Notes built-in tools such as fixup, compact, and updall. It is not guaranteed that any of the tools will be able to fix the issue as the corruption could be beyond repair, in which case it might be necessary to restore a backup.
Close your Notes client before attempting to run any of the following tools:
Fixup is usually run in an attempt to fix corrupted views and documents in a database. It should be used when a database is suspected to have a problem, but it is not recommended to have it run periodically on a database as a preventive measure.
To run fixup:
1. Open a Command Prompt window and navigate to the folder where the Notes client was installed (see figure 6).
Figure 6. Example navigation to folder
2. Type the command nfixup -F and the full path of database, including the file name and extension as shown in figure 7.
Figure 7. nfixup -F command
3. Press the Enter key to run the command; it then asks for your user ID password. Type the password and then press the Enter key again. A window like that in figure 8 should display.
Figure 8. Enter password
After the nfixup completes, you should see a window similar to that in figure 9.
Figure 9. nfixup results
Compact is usually run to reduce database size and in an attempt to solve database corruption issues for which the use of fixup did not help.
1. You run the procedure the same way you did above for the fixup, but using the command, ncompact -c -i, and the full path of database, including the file name and extension (see figure 9).
Figure 10. ncompact -c -i command
2. Press the Enter key to run the command; you are prompted for your user ID password. Type the password and then press the Enter key again. The window like that in figure 11 should display.
Figure 11. Enter password
After the ncompact completes, you should see a window similar to that in figure 12.
Figure 12. ncompact results