The server.id can be setup to have a password. This can cause problems on Windows where on Windows 2003 the Domino server starts, however it expects a password. This caused me the issue of getting stuck when logging in. Although passwords are recommended I tend to rely on the security of the server (Ensuring only valid users can actually logon and access important files).
To remove a password from your servers id file you can do the following (Recommended to be done when the server is not being accessed):
1.To remove the password log on to the IBM Lotus Domino Servers desktop via Remote Administrator
2.In the IBM Domino Server console type “l notes”
3.This will start Lotus Notes and log in with the server.id file
4.Once in to Lotus Notes goto File – > Security -> User Security…
5.Click Change Password
6.Click No Password
This is now complete, exit IBM Notes. If you want to test this then input the following command into the IBM Domino Console “server restart” and it will restart the domino server and go straight into firing up its services.
If you get stuck logging on to a Windows Server running password secured Domino 8 via Terminal Service (Where Terminal Services states “Applying Settings”)
If you can’t access Terminal Services but have access to a server which has an administrator account that matches the Domino Server, run the following command “taskkill /s /f /im nserver.exe /t” (Replace the server name with the servers name)
Although PSTools in theory should work I could not get this to work.
I had an issue where corruption on local Lotus Notes Database views resulted in views such as the Inbox showing [Replication or Save Conflict] instead of actual emails. For me this occurred during migrating nsf files to the latest version (Version 6.x to Version 8.x) on Lotus Domino (Domino was already version 8.0.1 however we wanted to take advantage of new Domino features such as improved compression). It appears some users local databases obviously were using old versions of the nsf file.
The first thing to do is refresh the affected views, open IBM Notes and get a view showing “[Replication or Save Conflict]”, press Shift + F9
Close the IBM Notes client and delete the Cache file in the Notes data directory (cache.ndk).
Reload IBM Notes and see if this has resolved the issue, if not on the Domino Server run “load updall -R mail\username.nsf”
As a last resort on the client rename cache.ndk desktop6/8.ndk’s in the users data directory (Obviously renaming the desktops may affect older IBM Notes apps!)
If a user finds they are unable to turn off their Out of Office Alert after setting it on Domino Web Access in version 8.0 the below fix from IBM Notes Forum can correct the affected Agents behaviour.
1. Run “tell amgr sched” on all the servers in the Domain in order to verify in what database (mail\.nsf) is running the Out Of Office agent.
2. Open the database with the problem (mail\.nsf) from the Domino Administrator.
3. Go to –> View –> Design. At this point the Lotus Domino Designer will be opened with the database selected.
4. Expand the Code section from the left side menu and double click in Agents.
5. Select the OutOfOffice agent from the list.
6. Click in Disable button and close.
7. Verify again the Out Of Office agent from the server console executing: “tell amgr sched”.
At this point, the Out Of Office for this specific client will be disabled.
To setup the Domino 8.0.x SNMP Agent (If not included as a feature when installing Lotus Domino) first ensure Windows snmp service is installed and stopped. Dominos SNMP utilises event4.nsf and therefore can be customised as required.
We can instruct the Domino Server to install a service on Windows by running the following in a Domino console window
As long as Domino is running with admin right a new service should appear and Domino should configure it to run automatically. Instead of restarting the server you can start both services from a Windows Command Prompt window running with administrative privileges.
net start snmp
net start lnsnmp
SNMP Tools (Requires loading Dominos MIB file which should be in the Domino’s executable folder) should now be able to query the status of the Lotus Domino Server.