Discussion Locked

Lotus Notes R5 - Memory Error

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Good day !

Recently there has a been a growing concern with some of the PCs I support. Lotus Notes R5, Domino Mail, has been randomly experiencing a Referenced Memory Error on my NT 4.0 builds. R5 is the upgrade from Lotus Notes 4.6. After uninstalling and re-installing the product several times to no avail, I started to re-build the machines with new and different images and profiles, using service pack 6. This also did not help. There is no particular time when the error appears, showing up basically at any moment, even when the users are in the middle of typing. This occurs between 2 and 3 times per week for each user.

The result of the referenced memory error is the complete shutdown of Lotus Notes. When trying to execute Notes R5 again, a message appears saying that the app has terminated abnormally . A reboot is necessary at that point. This takes up much time for the users and they can't really afford it.

There is no affect like this on the same PCs when they do not run R5.

It sounds like a bug to me. What do you guys think? Has anyone else experienced this problem and if so, what is the fix for it?

Thanks a lot in advance for your continued support,

Kelly

5 replies

by co2cyber

You might want to check on the Lotus patches that are available. There are indeed MANY DoS attacks that could cause a memory error and the restart of the server. This could be someone from within the company itself or someone outside seeing as an account is usually not needed to preform these types of DoS attacks against Lotus servers. This link http://www-10.lotus.com/ldd/down.nsf?OpenDatabase may be of some use to you in finding a patch/update for your product.

Andrew

by jayr

Kelly;

Lotus Notes R5.xx requires higher memory...You can try adding memory into your server.

One thing more is that depends into your version you are using. Because there is R5.06 has a bug...You can try R5.04.

This discussion is closed to new replies.