LO79244: THE UPGRADE OF USERS WITH DOMINO FILE SERVER ROAMING IS NOT COMP LETING ON SOME SERVERS

APAR status

• Closed as fixed if next.

Error description

• Scenario:
  
  - Apply File Server Roaming Policy to a Person Document
  - Notes Client authenticates and retrieves the
  policy
  - Roaming is setup on the Replicator page, and the following
  databases are
  replicated to the File Server location: (roamingdata.nsf,
  names.nsf,
  bookmark.nsf, localfeedcontent.nsf)
  
  - AdminP fails to create the request: "Update Roaming User State
  in Person
  Record" The users are never completely upgraded to roaming.
  
  
  
  Testing:
  
  
  
  A number of tests have been performed to eliminate possible
  causes of the
  problem.
  
  
  
  The same Multi-user 8.5.3 Standard client and ID combination has
  been tested on
  several servers. Some servers fail to create the AdminP request
  whilst others
  complete the task as expected. Where it fails, it always fails,
  and for all
  users. Where it succeeds, it is always               successful,
  and for all
  users. That is, where a server is failing to complete, it fails
  for all users
  on that server. Servers that are behaving correctly complete the
  task for all
  users connected to that server.
  
  
  
  
  Examples: Result  Server Names
  
  SUCCESS:Users with these home servers always upgrade
  successfully:
  AUYVIZLN - Release 8.5.3FP1HF182 - Windows/2003 5.2 Intel
  Pentium
  AUYNPX22 - Release 8.5.3FP1HF181 - Windows/2003/64 5.2
  
  FAIL:Users with these home servers never upgrade successfully:
  
  AUYZZZ02 - Release 8.5.3FP1HF182 - Windows/2003 5.2 Intel
  Pentium
  AUYHOA06 - Release 8.5.3FP1 - Windows/Longhorn/64 6.1
  
  AUYNPX21 - Release 8.5.3FP1 - Windows/Longhorn/64 6.1
  
  Importantly, these servers used to upgrade successfully in the
  past. We are
  unable to determine when the failures
  began.
  
  
  
  
  
  
  We tested following the instructions detailed in Technote
  1093356 to replace
  Adminp on a server where File Server Roaming was failing. This
  did not fix the
  problem.
  
  
  
  For each test, all user details were removed from the client, no
  Roaming Policy
  applied, and Roaming is set to 'No' in the Person Document in
  Domino
  Directory.
  Roaming Policy is then applied to the User's Person Document in
  Domino
  Directory, and the client logs on.
  
  The SAME process was followed on a cross section of servers with
  results as
  follows:
  
  
  
  Produced failures and success as follows:
  
  Users with Home Mail servers running either of MS Windows 32 bit
  or 64bit
  servers can experience the problem - OS dependancy eliminated
  
  Servers running Release 8.5.3FP1 HF182 can experience the
  problem  - other
  servers also running Release 8.5.3FP1 HF182 have no problem -
  Domino version
  dependancy eliminated
  
  The same Multi-user 8.5.3 client and ID combination has been
  tested on several
  servers. Some servers fail to create the AdminP request whilst
  others complete
  the task as expected. - Client version dependancy
  eliminated
  
  See above point - User account eliminated
  
  Users with non-clustered and clustered servers can experience
  the problem -
  cluster dependancy eliminated
  
  Users with virtual and non-virtual servers can experience the
  problem -
  virtual server dependancy eliminated
  

Local fix

Problem summary

• This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# JFBA9GNMVJ.
  This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R853 PSN

     UP