LNT – Mails disappear from inbox

Recently I posted that an update for Lotus Notes Traveler is available. Today I saw that this fixpack  causes problems.

When you receive a new mail, this mail is synced to the device. When you open the mail on the device, there is no problem, except that the unread mark is not exchanged with your client and the mail remains unread in the client inbox.

But … when you open an uread mail in the Lotus Notes client, the mail disappears from the inbox on the device.

I reverted back to 8.5.0.1-LNT-LO37251 and the mails stay on the device when read in the Notes client.

Anyone else who can reproduce this behaviour?


Lotus Notes Traveler 8.5.0.1 Interim Fix LO39586

The Lotus Notes Traveler software offer quick email access, address book, to-do list and journal to supported mobile devices or gadgets. This program can be quite handy for individuals who manage a lot of information. For instance you’re in the middle of gathering data from Advantage One Insurance and you need to save and organize them electronically so you can move on to another task. The Lotus Notes Traveler software will be a good fix for this situation.

8.5.0.1 Interim Fix LO39586 is now available on Fix Central.

The fix includes the following APARs:

  • L039586 – Anniversary calendar entry can not start before 1975
  • LO37036 – Troubles downloading bootstrap.nts file from  WM ppc device.
  • LO37329 – Unknown timezone error message displayed on Domino console.
  • LO36583 – Can not access LotusTraveler.ntf on new install if server is not part of LocalDomainAdmins group.
  • LO37264 – Inbox email is resent to recipients from Traveler device.
  • LO39627 – SERVER CRASH AFTER UPGRADE FROM 8.0.1 TO 8.5
  • LO39628 – Mail Filter range not working correctly.
  • LO39629 – CONTACT NAME MODIFIED ON DEVICE, NOT CHANGED ON SERVER.
  • LO39630 – CONTACT PHOTO CORRUPTED IF CONTACT MODIFIED ON SERVER AND DEVICE

VMWare Server on Lenovo S10e

I recently installed VMWare Server 2.0.1 on my brand new Lenovo S10e. I do not use the VMs every day, so I thought it would be a good idea to save some ressources on the computer and do not start the VMWare services automatically when the system starts.

First of all, change all VMWare … services from automatic to manual start.

To make the process of manually starting / stopping of the necessary services comfortable, I created two .cmd files with the following contents.

VM.Start.cmd:

net start “VMWare Server Web Access”
net start “VMWare NAT Service”
net start “VMWare DHCP Service”
net start “VMWare Host Agent”

VM.Stop.cmd:

net stop”VMWare Server Web Access”
net stop”VMWare NAT Service”
net stop”VMWare DHCP Service”
net stop”VMWare Host Agent”
net stop”VMware Authorization Service””

There are 5 services to stop , but you only need to start 4 services. The VMWare Authorization Service is started automatically when the WMWare Host Agent comes up.


New Toy

s10eYesterday, my new toy, a Lenovo S10e arrived.

It has an Intel Atom 270 processor, 2GB Ram, 160GB HDD and a 10.2” display. The display has a resolution af 1024 by 576. This takes a lot of getting used to.

The OS is Windows XP Sp3. I installed Lotus Notes 8.5 Standard including Admin and Designer client.

I was surprised, how well Lotus Notes runs on this little calculator. Even the Designer opens my mailfile in less than 40 seconds.

The S10e battery runs for almost 5 h with WiFi enabled and a lot of HDD activity during installation and configuration.



DAOS – Where do these files come from?

Here is another issue I encountered on my travel to the DAOS universe.

My mailfile is based on mail85.ntf. There are no documents in the database. The DAOS Dir does not contain any NLO files.

daostemplate2

No surprise is that. Then I changed the template on the database to ONTF_dwa702. After the design has changed, I found 2 NLO files in the DAOS repository!!

daostemplate1

Again I changed the template and used a DWA 7.0.3 template. Now I saw this in the DAOS repository.

daostemplate3

Does somebody has any explaination ??


DAOS – Encrypted mail

Yesterday I wrote about how to waste space using the wrong compression settings. I a comment, Mohamed asked about encrypted mail.

I tested this in my demo environment. The result is a bit scary …

I have two users, ALPHA and BETA. ALPHA sends a mail to BETA with an attachment. The mail is encrypted when sent. BETA uses the same bitlike attachment and sends an encrypted mail to ALPHA.

Here is the result

daos6

One NLO for the mail stored in the sent view and one NLO for the file in the receiver’s inbox

Can this be correct or did I something wrong??

UPDATE: Encryption and the number of NLO’s ( Gary Rheaume )


DAOS – How to waste space

DAOS is a great space saver. We all know this. But if you do not read the DAOS documentation carefully, you can waste space. I am preparing a session for AdminCamp 2009 where I will talk about DAOS.When setting up the demo server for the presentation, I came across one important thing to watch when you setup DAOS on your server.

This is described in the administration help, but as we all know, nobody reads the help and this question will be asked in forums sooner or later.

Assume you have two databases on your server that are DAOS enabled. The DAOS directory does not contain any NLO files at this moment.

Now create one document in DB1 and another one in DB2. Attach the same file to both documents. What would you expect? Right. There should be only one NLO file in the DAOS directory.

But, look at this

daos1

How can this happen? Well the answer is easy. DB1 has LZ1 compression enabled in the database properties, DB2 does not.

And now, look at this

daos2

Huhh … This is what you get when you create another document in both databases but uncheck the “Compress” option on the “Select File” dialog.

daos3

So, when you setup DAOS in your environment, make sure that all databases involved support the same compression algorithm.

After recompressing both databases with “load compact -c -ZU …” we now have the expected result; 4 documents containing 4 bitlike attachments resulting in one single NLO file.

daos4


DAOS – Catalog needs re-sync on Domino startup

Whenever I start my Domino after a clean shutdown, the DAOS catalog needs to be re-synced.

I see the following message on the server console :

postponed

The behaviour is reproducable. I have done a fresh installation of Domino 8.5 on Windows 2003 server and configured the server for the first start. After the server has started successfully, I opened the server document in names.nsf and configured DAOS and transactional logging. I saved my settings and restarted the server by typing “restart server” on the console. The server came up and created the transaction logs. Then I restarted the server once again and from now on the message appears at every server start.

This seems to be the same as described here. Just wonder, if there is already a fix available.


Error reading FolderModified time from header

Earlier this morning, I found the following entry in the servers log file:

23.03.2009 06:33:09   Error reading FolderModified time from header in database E:\mail\xxxxx.nsf. Run Fixup on the database.: Invalid Time or Date Encountered
23.03.2009 06:33:09   Error reading FolderModified time from header in database E:\mail\xxxxx.nsf. Run Fixup on the database.: Invalid Time or Date Encountered

I tried to run fixup -F -j on the database, but the error re-appeared at the next replication.  I assumed a problem with either document or design where @Created has a value that is “too far in the future” or so. But how to find this one (?) element in a database that is almost 10 GB of size ond holds 50.000 documents?

I opened the database with ScanEZ and did a search on all design and data documents ( @Created>[12/12/2009] ) and got one match.

goedecke2

As you can see in the screenshot,  “Created Initially” has a suspect value. I deleted the document from the database and the error does not occur any longer.

UPDATE: Seems that this is a known issue in 7.0.3 and has been fixed with 7.0.3FP1 ( http://www.badkey.com/db/blogsphere.nsf/d6plinks/JWIE-7LJUXW ) but I am running Domino 8.5. So I will open a PMR with IBM support …


DXL Roundtrip – IBM needs your input

Andre Guirard is currently working with a team to improve DXL and to make it round-trippable as has been occasionally requested by developers.

He is asking for some input from the community:

Please chime in with your prioritized list of the top five or so specific DXL issues. An explanation of how those fixes would affect you/what you would be able to do that you can’t now, would be welcome also.

Read more here


DAOS catalog cannot be updated

I have upgraded 4 of our production servers to Domino 8.5 during the last 2 weeks and yesterday I enabled DAOS on one machine. Occasionally I see the following entry on the console

daoserr

Unfortunately, this is the only hint that something seems to be wrong. But I cannot locate the problem. It would be great if an error message could be more verbose and says where the exact problem is. I’m running 3 parallel compact tasks at the moment.

Despite of this error message the compact task works fine and more and more data is written to the DAOS repository.


SnTT: Track delayed adminp requests

Found this IBM Lotus Knowledgebase  Technote # 1298009

The Attachment section in the technote contains a database that contains a “Delayed Processing by Server” view that can be added to your existing admin4.nsf database design. This view provides information about all delayed processing including the following:

  • Requests currently processing
  • What the user acted on
  • What the server request is running on
  • Time request started
  • Total time to perform the request

DAOS: Transaction Protocol Trap

I’m recently working with DAOS on our production servers and had an issue with transactional protocol. Well not really a problem but a thing to check before you enable DAOS on a database.

As you might know, you must enable trasaction protocol on your server to be able to use DAOS.

But, there is a second place where transaction protocol is controlled; on the advanced tab of the database.

For some reason, transaction protocol was disabled on a handful of databases.

When you trigger a “load compact -c -daos on path\database.nsf” on the server console, the database is compacted and DAOS is enabled on the database. But none of the attachments from the database are moved to the DAOS repository.

When you type “load daosmgr status dbsummary” on the console after the compact task has finished, you will see the following output

daostrans

At this point, you should look at the advanced tab of the database, uncheck “Disable Transaction Protocol” and run compact again.


Move database issue in ND85

Moving databases from one server to another or from one location to new location on the same server is an easy job when you use the Administration Client. Just select the database(s), click on “Move”, type in the target or change the database name and let adminp do the job of creating the database in the new location and deleting the database in its old location at the end of the process.

ND8.x has the advantage that unread marks are automatically exchanged during this process. A few days ago, I had to move some databases on one cluster member from one directory to another directory on the same server. The databases are cluster replicas of the users mailfiles and the server is not their home server.

I selected the databases and typed in the target directory. I expected to see something like this in admin4.nsf after a successful move.

movereplica703

But the entries in admin4.nsf looked different. The process stopped after creating the new replica and triggering the “Maintain Trends Database record”

movereplica85

I did some tests; here is what I’ve found so far:

  • This behaviour is reproducable with all databases on the cluster member that are not the users home mail files.
  • It is not reproducable if the same databases are moved on a server that is not a member of a cluster ( standalone Domino ).
  • If you use an Administration Client prior to 8.5 ( in this case 7.0.3 ) the requests in admin4.nsf are generated as shown in the first screenshot.
  • If you move a users home mail file in a clusterd environment, the process works as expected.

So I suppose that this is a bug in the 8.5 Admin Client. I’ve already created a PMR with IBM. No feedback so far …