RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr

HCL Domino Domino Forum
1

Hi,

After upgrading to Domino version 7.0.1 we receive this error message:

RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr. Autoprocessing is being disabled for this dB.

The database is a mail-in database and not a resource database. How can we exclude this database from being processed by the RnRMgr task?

Thanks

Anja

2

Subject: RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr

my best guess is that your mail-in database is defined in the domino directory as a resource. remove the fields resourcetype and resourcefalg from the mail-in db document.

3

Subject: RE: RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr

I am also having this problem. I have checked the mailin doc and the fields are not present.

Did you ever fix the problem? Any help would be appreciated.

Regards

4

Subject: RE: RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr

I am also having the same problem on 7.0.2 FP1. Has anyone disovered a solution to this?

5

Subject: RE: RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr

Hi,Same error

http://www-1.ibm.com/support/docview.wss?uid=swg21219243

JYR

6

Subject: RE: RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr

I’ve the same problem and found no solution till now.

Any help?

7

Subject: RE: RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr

Hi Peter,

From my previous post–

pointing to this technote

Resource Reservation databases based on 6.x or earlier design do not function properly on Domino 7.0 servers

Lotus Domino 7.0 is working as designed. To function correctly on a Domino 7 server, the Resource Reservation database must be based on the Domino 7 Resource Reservation template (RESRC7.NTF) For the best results, the design of this database must be upgraded at the same time you upgrade the server to 7.0.

Besides the issues described above, what type of notification is there if the RRDB design has not been upgraded? The Rooms and Resource Manager task will detect pre-Domino 7 templates on RRDBs and create the following log entry for each database:

“RnRMgr: The design of D6ConfRooms.nsf is not one supportable by RnRMgr. Autoprocessing is being disabled for this dB.”

8

Subject: RE: RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr

Hi Jean-Yves,

I don’t understand the solution because the db referenced in the message at mine is not a RRDB. It’s a mail-in-database.

Regards,

Peter

9

Subject: MORE RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr

I think there is no solution.

At 2AM, the server always do a “tell sched validate” and “tell RnRMgr validate”. The two tasks look for every database that have a profile named “CalendarProfile” (this include the mail databases, and the Resources databases). You then get the typical errors like :

Error processing calendar profile document (NoteID: NT000008FA) in database mail\xxxxx.nsf: Cannot find user in Domino Directory

Error processing calendar profile document (NoteID: NT000008FA) in database mail\xxxxx.nsf: User’s mail is being forwarded to another location

The design of xxxxxx.nsf is not one supportable by RnRMgr. Autoprocessing is being disabled for this dB

The meaning is that these database will not be used by Sched and RnRMgr, the behaviour is correct.

So, like it has been said for all the messages “Error processing calendar profile document”, the only way to prevent the Sched/RnRMgr tasks to process these files is to delete by script the CalendarProfile. It can be a good idea for never-used mailboxes, but not for a working mail-in box.

Then…

10

Subject: RE: RnRMgr: The design of xxx.nsf is not one supportable by RnRMgr

I’m having the same problem under 7.0.2 FP1. The database is defined as a “mailin database” not a “resource”. Neither resourcetype nor resourcefalg exist in the mail-in db document or in the database design. Any other ideas on what to check?