LO54984: "REGISTRY EVENT DISPATCHER" HAS ENCOUNTERED A PROBLEM.

APAR status

• Closed as program error.

Error description

• PROBLEM
  
  After the installation of FP3 or FP4 the following message comes
  up when
  starting Notes for the first time on Citrix or in their non  ND
  Roaming
  solution:
  
  >>>
  "Registry event dispatcher" has encountered a problem.
  
  Error notifying registry change listener.
  
  (Detail)
  
  Error notifying registry change listener.
  Error notifying registry change listener.
  Invalid thread access
  <<<
  
  ENVIRONMENT
  
  Domino Server Windows 2003 64bit R2 Enterprise + SAN
  Domino 8.5.1+FP4 App using NRPC + Web Access
  Domino 8.5.1+FP4 Mail DAOS enabled + SMTP routing topology.
  Standard (Eclipse) Notes 8.5.1+FP4 Win XP SP2
  Panagenda Roaming Client file re-direction (Citrix+AAM Full
  Client)
  DUCs 1.2.5 + Cisco Unity 7.0(2).
  SSO MS Active Directory, SPNEGO, Kerberos and LTPA Tokens
  
  
  STEPS
  
  Install FP3 or FP4 for Notes 8.5.1 Standard.
  Start Notes Client after FP install.
  
  Error message comes up for customer.
  
  TROUBLESHOOTING AND BACKGROUND INFO NEEDED IN ORDER TO
  UNDERSTAND THE ISSUE:
  
  Note: The issue can not be reproduced by IBM in Citrix
  Environment or
  N/D Roaming as tested by Citrix Team and Roaming PAE.
  
  Citrix PAE pointed out that the issue is not being caused by
  Citrix but
  may be caused by the Eclipse windows save state function.
  
  Customer tested the workaround to disable save state and indeed
  then no
  error occurs in their environment.
  
  Customer feedback:
  
  >>>
  The workaround (disabling "save state") is not a perm fixture as
  this
  will affect a policy setting we have set by default, if we ask
  users to
  apply this in all cases it effectively takes away some nice
  functionality.
  <<<
  
  Feedback from XPD PAE:
  
  >>>
  In My previous update I explained this might be caused because
  of the
  workspace folder in the Notes Data directory is recreated at
  each launch
  due to their whole data directory being copied from another
  location.
  
  When customer disables
  Eclipse has preferences stored for that OS and I think they will
  see
  this error when ever the workspace folder is moved from one
  machine to
  another. I am not aware of a fix as this is not a supported
  configuration.
  
  They should be using Domino Roaming instead and not roam the
  whole data
  directory.
  
  If the customer and AVL wants an official answer, please
  escalate to L3
  for review and their comments.
  <<<
  
  AVL went onsite and provided the following infos:
  
  Notes Standard (Eclipse) Client 8.5.1 + FP4 uses either Citrix
  or AAM's
  own Roaming User, both of which use Panagenda file re-direction
  to
  selectively save and restoring Notes Data + some Eclipse files
  to save
  server disk space.
  
  Domino uses both SMTP based Routing combined with Fully
  Distinguished
  Names routing.
  
  These are all deemed Critical Production systems all recently
  upgraded
  to 6.x => 8.5.1 and very recently upgraded to FP4 to fix DAOS
  issues.
  
  AAM uses Notes Standard (Eclipse) Client 8.5.1 + FP4 either over
  Citrix
  or using AAM's own Roaming User, both of which use
  Panagenda file re-direction to selectively save and restoring
  Notes
  Data + some Eclipse files to save server disk space.
  
  The Panagenda product instantly backs-up selected files (*.xml
  *.prefs
  *.dic ) on each exit from Notes and then instantly restores them
  as
  Notes is started.
  
  Unfortunately they appear to have forgotten to add in at least
  one key
  file (perspectivemap.properties) that appears to store the Notes
  state
  changes under Eclipse:
  
  Sample Contents:
  com.ibm.workplace.noteswc.views.NotesView:1284563439005=Notes://
  XXXXXXX
  XX01/802568BF004F82B6/Main?OpenFrameset
  
  homepref= com.ibm.workplace.noteswc.homepage.perspective
  D6A34CC1857E050686FE8070CE3B840F_6_3KE527R200VQ502MGJOIMC20H7=no
  tes:///8
  0256ED9003BDDA1/MailFS?OpenFrameset^true^cai:///D6A34CC1857E0506
  86FE8070
  CE3B840F_1F_3KE527R200VQ502MGJOIMC2096/D6A34CC1857E050686FE8070C
  E3B840F_
  6_3KE527R200VQ502MGJOIMC20H7?hint=nrpc%3A%2F%2XXXXXXl02%252FServ
  ers%
  252FAberdeen%2520Asset%2520Management%2F__80256ED9003BDDA1%2Fcom
  posite.x
  ml%3Fname%3DNotesMailApps.xml%26file%3Dmail%255XXXXXX03%255XXXXX
  X.ns
  f%26clnk%3Dt
  
  
  This particular file clearly stores the names and positions of
  the open
  tabs and current views, such that when the option to Restore All
  Settings on Startup is enabled, this file is updated (as above)
  but
  since it isn't backed up, they don't get the correct State
  restored
  (they never did, but didn't actually realise this has never
  worked!)
  and this Eclipse file omission from Panagenda backup also seems
  to
  causes Eclipse to issue a Windows Java error on startup if "Save
  State
  on Shutdown" is enabled:
  
  Message:
  
  >>>
  "Registry event dispatcher" has encountered a problem.
  
  Error notifying registry change listener.
  
  (Detail)
  
  Error notifying registry change listener.
     Error notifying registry change listener.
     Invalid thread access
  <<<
  
  Please find Screenhots, Notes error logs and nsd attached to the
  SPR.
  
  This error suggests that Eclipse is attempting to over-ride or
  ignore
  the fact that an expected file has invalid content or is
  missing, but
  is denied the ability to change something in the registry. I am
  speculating at what the error actually means.
  
  The file perspectivemap.properties is updated when Notes is shut
  down,
  but then not "used" during the startup!!
  
  We played with this file for a while, and if the file contents
  are
  manually changed, eg we editted a tab and view out of it, it
  didn't
  change the startup (ie it ignore our edit), suggesting that
  after
  writing the contents to perspectivemap.properties on Notes
  shutdown,
  Eclipse subsequently placed the contents of the file "somewhere
  else",
  (in the Registry, possibly?) and then read the contents from
  that
  location, not the text file we had just editted, when it
  restarted.
  
  We had disabled Panagenda during this testing, to stop it
  overwriting
  our editted file on restart, as it possibly might have.
  
  Although we don't backup or recover this file with Panagenda, it
  will
  be recovered from the generic "zip" of all the Eclipse files
  that
  Panagenda  loads initially , then Panagenda loads the users own
  unique
  saved files (*.xml *.prefs *.dic ) which are over-laid on top of
  the
  standard generic "zipped up" set, then finally Notes is allowed
  to
  start up.
  

Local fix

• Disable save state.
  

Problem summary

• A programming error was found and will be corrected in a future
   release.
  

Problem conclusion

• A programming error was found and will be corrected in a future
   release.
  

Temporary fix

Comments

• This APAR is associated with SPR# GMAA89LC65.
  

APAR Information

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

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

Fix information

• Fixed component name

  NOTES CLIENT

• Fixed component ID

  5724E6255

Applicable component levels

• R851 PSN

     UP