** System Error #3036: ooHandle(ooFDObj)::open(): Lock Server cannot
                       auto-recover FD.  Please verify that the account running
                       the Lock Server has permission to access all the database
                       files and the journal directory.  You may need to recover
                       this FD manually.  Please check the Lock Server log file.
** System Error #2502: ooHandle(ooFDObj)::open(): Object Manager is unable to
                       start a new transaction
** Error #190102: d_session::transStart() could not open:
                  </objy5data/databases/eisner/7.2.1/BaBar.BOOT> is
                  OO_FD_BOOT set correctly ?

Situations like this can occur if the lockserver crashes and is restart whilst the federation was being accessed. It can also happen when the federation has been deleted and is being re-created. In the
latter case, waiting a few minutes until the cache is cleared should be sufficient to get around this
error. In the former case, we have noticed that running "oocleanup" on the lockserver host
eliminates the error.