Showing results for 
Search instead for 
Do you mean 
Reply
New User
Posts: 2
Registered: ‎01-19-2016
0

Re: "This library is currently being used by someone else. Try opening it again later"

This did not solve my problem. None of the suggestions about copying the file and placing somewhere else solve the problem. Currently, I have no access to my main library. I tried a different library and it opened fine. But this makes no sense, as I was using my main library just yesterday on the same computer. Nothing has changed since then. How has the library suddenly become corrupted?

Mentor
Posts: 7,773
Registered: ‎04-10-2008
0

Re: "This library is currently being used by someone else. Try opening it again later"

Did you copy both the .enl file and the .DATA folder to the same new location?  

(long time Endnote user)
New User
Posts: 1
Registered: ‎05-25-2018
0

Re: "This library is currently being used by someone else. Try opening it again later"

[ Edited ]

Greetings All,

 

I too experienced this frightening issue with Endnote X8. I called Endnote support (1-800-336-4474; Option 4) and they wonderfully gave me the following instructions for MAC Book Pro (High Sierra):

 

  1. Create a new folder in APPLICATIONS called "Endnote Libraries".
  2. Copy and paste your corrupted Endnote library (.enl) and its corresponding .Data folder to the new folder you just created. 
  3. Open Endnote X8 program.
  4. Go to Tools "Recover Library".
  5. Choose the new copied version of your .enl file in the "Endnote Libraries" folder you just created.
  6. It will recover your library and make a new file with a new name by simply adding "-Saved" to it (ORIGINALNAME-Saved.enl) and it will also paste a new corresponding .Data folder with the "-Saved" added.
  7. Open the new "-Saved.enl" file and voila - your library is back.

All of my groups, attachments (PDFs,), etc. were there too. Crisis averted

Highlighted
New User
Posts: 1
Registered: ‎06-12-2018
0

Re: "This library is currently being used by someone else. Try opening it again later"

Thanks - this has solved my issue too.  So not cloud friendly, even though my library is synced in your cloud.  Too funny!