Freitag, 28. März 2014

Replica-Style compact resets quota limits

If you have a quota and warning limit in place for a database which you treat with the new replica-style-compact in Domino 9, then the quota and warning limit is reset to "no quota". I think that compact should really keep these settings.

Mittwoch, 26. März 2014

Beware of Domino 9.0.1 if you're using document locking!

There's an issue with document locking not working at all in 9.0.1.

I can confirm that we have the same issue here - this is quite a mess ...
Seems that you can work around that issue if you happen to have an older server (8.5.3) with a replica of your application which you set as the administration server for that database.

Freitag, 24. Januar 2014

Legacy data path

As we already learned, IBM dropped the term "Lotus" starting with IBM Notes 9.0. This will quite probably cause problems if you want to upgrade your clients from 8.x to 9.0.
With Notes 8.x the client automatically appended the path "Lotus\Notes\Data" to the path which was set by the MSI-parameter "MultiUserBaseDir" (which corresponds to the registry-key "DataPath"). Beginning with v.9 the default path appended is "IBM\Notes\Data".
If you prefer to use the legacy path, you need to set an undocumented registry-key:

UseLegacyDataPath=1 (DWORD)

Dienstag, 12. November 2013

IBM Notes crashes with errors related to PNGFILT.DLL --> check your DEP settings!

A lot of our users suffered from random crashes when they just wanted to open and read newly received emails in IBM Notes. Most of the time, the crash reports involved the file pngfilt.dll which is probably supposed to render PNG-Images. Since the crashes weren't reproducible, it didn't seem very easy to find a solution for this. Luckily, most (if not all) of those crashes occured when Notes was used in a Citrix environment, so that seemed to be a hint. Our "normal" users didn't seem to have that issue when they used their own workstations or notebooks with a local IBM Notes client installation. After ruling out missing M$-patches as a possible cause, i stumbled upon an article that dealt with errors caused by the DEP-feature.Disabling the data execution prevention using bcdedit immediately stopped our IBM Notes clients from crashing all the time.

Mittwoch, 30. Oktober 2013

Traveler - Upgrade from to 9.0.1 failed

Unfortunately, the Traveler upgrade from to 9.0.1 doesn't seem to work on one of our servers. Trying to start Traveler results in the following messages:

[14649:00002-1800746784] 30.10.2013 14:35:09   Notes Traveler: Starting JVM with Maximum Memory = 2048M based on maximum of 1/4 of physical memory (3072M) or the Maximum Memory Size specified in the server document (2048M)
[14649:00002-1800746784] 30.10.2013 14:35:11   Notes Traveler: Server starting...
[14649:00002-1800746784] 30.10.2013 14:35:11,40 CSRF Init: iNotes_WA_Security_ReturnUrlCheck> c_CSRFReturnUrlCheck: 1
[14649:00002-1800746784] iNotes Init: Credential Store Configuration not enabled, less secure mode.
[14649:00002-1800746784] 30.10.2013 14:35:14   Notes Traveler: Upgrading IBM Notes Traveler Database schema from version to version
[14649:00007-2926597888] 30.10.2013 14:35:14   Notes Traveler: SEVERE *system  Exception Thrown: com.lotus.sync.db.PersistenceException: There is already an object named 'bind' in the database. (SQLState: S[14649:00002-1800746784] 30.10.2013 14:35:14   Notes Traveler: Upgrading IBM Notes Traveler Database schema from version to version
[14649:00009-2926597888] 30.10.2013 14:35:14   Notes Traveler: SEVERE *system Unable to connect to database.  Verify the database is running and that the database configuration is correct.  Use travelerUtil to modify configuration parameters as necessary.otus.sync.db.PersistenceException: Cannot define PRIMARY KEY constraint on nullable column in table 'sec_r
[14649:00009-2926597888] 30.10.2013 14:35:15   Notes Traveler: SEVERE *system IBM Notes Traveler server could not be started.  The exception was java.lang.ExceptionInInitializerError. Exception Thrown: java.lang.ExceptionInInitializerError
[14649:00002-1800746784] 30.10.2013 14:35:15   Notes Traveler: Server stopping...
[14649:00002-1800746784] 30.10.2013 14:35:15   Notes Traveler: Server stopped.

Hoping to find a solution, soon...

Freitag, 1. März 2013

Using a proxy server with Lotus Notes: NTLM authentication and exclusion lists

If you ever wondered why it's sometimes such a hassle to copy & paste data from a webbrowser directly into your Lotus Notes Client, it might be due to a missing proxy configuration.
If your company's proxy server requires NTLM-Authentication, you'll notice that entering your domain-credentials in the proxy configuration dialog of your location document will not work as expected. The client will keep prompting for the proper credentials since it will always try basic authentication with the proxy server. That's because Lotus Notes doesn't support NTLM-authentication out of the box. In order to make this work, you need to set the (undocumented) parameter W3ContextNTLMMode=1 in notes.ini. Now you don't even need to enter any credentials in order to use the proxy, since the Lotus Notes Client (on a Windows OS) will use your operating system login to authenticate with the proxy server.
Now that you're able to use your companies proxy server with your Lotus Notes Client, you'll quite probably want to make some exclusions for hosts that aren't accessible through the proxy server (hosts on your internal network)
When you try to do this through a policy, you need to enter multiple values separated with semicolons. If you separate them with CRLFs, only the first entry of the list will be honored. Unfortunately, this isn't documented anywhere, so i had to figure this out using trial & error.