Roaming not possible on 6.0.1CF1

HCL Domino Domino Forum
1

We wanted to change a single user to allow for roaming. After entering the roaming details in the dialog, an error message came up indicating that the server is not R6. But both the server and the administration client are 6.0.1CF1. No document was created in admin4.nsf.

What else could cause this error message? What exactly is checked before creating the admin4 request?

Thank you for your support.

Andy Brunner

CLP/CLI ND6

2

Subject: Roaming not possible on 6.0.1CF1

3

Subject: I think it is - Roaming not possible on 6.0.1CF1

http://www-10.lotus.com/ldd/today.nsf/62f62847467a8f78052568a80055b380/aa8e5890daeef5e285256cd40062831a?OpenDocument&Highlight=0,upgrade

4

Subject: Roaming not possible on 6.0.1CF1

5

Subject: Roaming not possible on 6.0.1CF1

IBM support helped me with this one.

There are two fields in the server document that control whether or not the server is “release 6” or not. Those fields are MAJver and MINver. We too had this problem and found that the two fields were missing from the server document that we wanted to use for roaming.

Here’s what we did to correct:

  1. Write an agent in your NAB, call it “fixroam” or something like that. It should operate on selected documents and contain one line of formula language that reads

FIELD ServerBuildNumber := “”

  1. Open the NAB and go to the server document of the server you want to use for roaming. Select that document and run “Actions, fixroam (or whatever you called your agent)”.

  2. If the server you are fixing is NOT the Admin server for your domain, replicate the NAB you are working with back to that server.

  3. Bounce the server. Doing this in conjunction with removing the ServerBuildNumber field will generate an AdminP request to “place server build number in address book”.

  4. If this isn’t the Admin server for your domain, replicate the ADMIN4.NSF database back to that server.

  5. From the Admin server for the domain, issue a “tell adminp process all” from the server console.

  6. Replicate the NAB from the admin server for the domain back to the roaming server you want to use.

Everything should work as published. The two missing fields should now be in the server document.

6

Subject: RE: Roaming not possible on 6.0.1CF1

Leonard,

Great answer. This may make sense. I certainly will try it.

Thank you very much for your help.

Andy Brunner

CLP/CLI ND6

7

Subject: RE: Roaming not possible on 6.0.1CF1

That information rocks! Thanks for posting…