Recent content by geier

If you mean the Lotus Notes client then go to: Datei (File) ----> Vorgaben (Preferences) ---> Benutzervorgaben (User Preferences) ---> International ----> Allgemein (General) and change the value in the field 'Sprache der Benutzerschnittstelle' (Content Language) to English. Every lotus client...

The logging of the compact task is done in the log.nsf under Miscellaneous Events. It looks something like this (at least in our log.nsf :-) ): 13.07.2008 13.05.59 Compacting Dach081/d081doc.nsf (DACH081 Dokumente) 13.07.2008 13.06.02 Compacted Dach081/d081doc.nsf, 12288K bytes recovered...

What you could check: - Are the affected groups multi-purpose or perhaps 'Access Only'? They should be 'Multi-Purpose'. - Is the access of the groups limited (e.g. are only certain people or servers allowed to use them?) - Are there people listed in the group that are also listed in the...

This is a known bug about which you can find a lot discussions in other Notes forums. We also have users that experience this phenomenon from time to time. The counter simply is wrong - there are no unread mails available. The only solution that gets rid of the problem is as far as I know: I...

It seems as if this guy either uses the wrong template on the personal address book or something got wrong when you upgraded him to R5. Especially when you say that he sees a 'Business Cards' page. I would first check the following: 1. Is the database you open with this shortcut really his...

Hi Tonty, you cannot view this file in the Windows explorer. You must get it via FTP from the corresponding directory on your iSeries to your local hard drive on the PC. Then you can open it with Notepad. The other thing you can do is view the file directly on the iSeries. On the command prompt...

Hi Tonty, the missing log information is normally included in the corresponding nsd file that is produced during a crash. You can find it in the directory IBM_TECHNICAL_SUPPORT which is under the server directory. That's how it is on our iSeries which is the same version as your ´machine. Bye...

If you experience the same problem when opening the database on the server then I would suggest that you replace the design of the mail template for the affected user (you can select the same template the user already uses but don't just make a design refresh but a replace). This often helps...

I assume that your user used to different addresses: the email-addresses for the external address and the Lotus address for the manager. If this has been the case then we are talking two different routing scenarios here: 1. Mail to the manager: NRPC routing within Notes 2. Mail to external: SMTP...

We just upgraded from 6.5.4 to 7.0.1 2 weeks ago on both iSeries and a Windows platform. We have a hub and spoke concept with one masterserver. We ran the installation process first. Then we restarted the servers - when we restarted the master server the software asked whether we would like to...

Have you checked whether the agent remains activated after the user has enabled it? We are using database quota and we experienced that when the user has exceeded the quota the OOO-Agent didn't work properly. Another idea: Is perhaps a Design task running that deactivates the agent again...

Sametime server doesn't require any additional license. If you are strictly using the Sametime capabilities built into Notes, you don't require additional client licenses. If, however, you need to use the full Sametime client, those need to be licensed separately.

Please find below what IBM support has written regarding this problem - hope it helps... :-) This issue has been reported to Lotus software Quality Engineering. There is currently no workaround; the issue has been reproduced. Supporting Information: In Domino 6.0x, AdminP began maintaining...

Do you perhaps have a group with this address where all members of 'Sales' are listed?

We had the problem a year ago (still under Notes 5) that some users suddenly received their mails into the 'All documents' view instead of the Inbox. In our case it was a design update that went wrong (it didn't run through properly for some unknown reason) -----> refreshing the database design...