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

I’m having the same problem after updating my mac OS - never fails that everything gets messed up after a new update. I can’t use the data folder if it has the same name as the endnote library file.

I have followed your steps and you are right that desktop and documents folders are checked in chrome. However I get the following message (attached) when I uncheck them. I’m not sure whether I will lose things by unchecking the box, or if I need to do something to safeguard things. Also where is the go and home that you’re suggesting?

Thanks for your help

Angela

I have followed your steps and you are right that desktop and documents folders are checked in chrome. However I get the following scary message when I uncheck them.

if you continue items will be removed from the Desktop and the Documents folder on this Mac and will remain available in icloud …

I’m not sure whether I will lose things by unchecking the box, or if I need to do something to safeguard things. Also where is the go and home that you’re suggesting?

Thanks for your help

Ange1

It helped to move the .enw file into a new folder, and open it in EndNote from the new folder placement.

Didn’t need to rename, and the reference works fine.

Thank you for all tips in this thread!

It helped to move the .enw file into a new folder, and open it in EndNote from the new folder placement.

Didn’t need to rename, and the reference works fine.

Thank you for all tips in this thread!

HI Guys, I had the same problem with my endnote after updating the OS.  I managed to get my library to open, with attachments and grouped as previous by just moving the endnote .enl and .data files from the cloud account onto my computer hardrive. the transfer seemed to take a couple of hours (8gb). Hope its this easy for others with the same problem.

Thanks, it’s help me too

I want to pass on a good piece of advice  to solve this issue that I got from a Norwegian customer supporeter (thanks, Thorgrim) a few years back and that I just now checked (high Sierra + Endnote X8), is still working (with the same and other error messages indicating a corrupted library): 

Create a new folder

Move the .enw file into the folder, double-click it. 

If the enw.file is not currupted, it will open in Endnote, creating automatically a new data folder (with the subfolders PDF, rdb and tdb) - but of course without the PDF’s of your old library.

Then copy the pdf’s from your old library to the new PDF folder. 

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?

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

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

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

I came across the same issue today, but fortunately found a quick solution (which might have been particular to my circumstances).

I recently migrated from 2013 MacBook Air to 2018 MacBook Pro, both using fully up-to-date software. iCloud Desktop + Documents was enabled on both machines. I successfully opened my EndNote X8 library on MBP. Later, while Apple Support helped me with an unrelated matter, I disabled iCloud and re-enabled it. When I opened EndNote today, I got the dreaded error message other users have mentioned. Not wanting to go through the labourious steps mentioned above, I checked my EndNote folders and found that many of them were in the cloud, but not locally downloaded (they had the cloud with down arrow logo next to them). I clicked on the cloud icon to manually download EndNote folders, then rebooted (because why not). On reboot, I was able to open my old library without having to go through the recovery process.

Just thought I’d offer this in case it helps anyone else!

I came across the same issue today, but fortunately found a quick solution (which might have been particular to my circumstances).

I recently migrated from 2013 MacBook Air to 2018 MacBook Pro, both using fully up-to-date software. iCloud Desktop + Documents was enabled on both machines. I successfully opened my EndNote X8 library on MBP. Later, while Apple Support helped me with an unrelated matter, I disabled iCloud and re-enabled it. When I opened EndNote today, I got the dreaded error message other users have mentioned. Not wanting to go through the labourious steps mentioned above, I checked my EndNote folders and found that many of them were in the cloud, but not locally downloaded (they had the cloud with down arrow logo next to them). I clicked on the cloud icon to manually download EndNote folders, then rebooted (because why not). On reboot, I was able to open my old library without having to go through the recovery process.

Just thought I’d offer this in case it helps anyone else!

I ran into the same problem as the folks on this page recently. I did the following and it worked for me:

I took several files from the .data folder and deleted them from the rdb and tdb subfolders. Files: csort 2.MYI, csort.frm, csort. MYD, csort.MYD 8.49.52 PM, csort.MYI 

I have no idea why this worked. I was just systematically deleting newly updated files from the day it malfunctioned. 

THANK YOU  nhnorsker!!!  

I just spent a couple of figuring out how to get my Library to open, got in touch with the tech support, it did not work. All the other options were tried to no avail. This one solution works, many thanks to Thorgrim and you. And copying the pdf file content works, but I tried to also copy the rdb content (maybe my groups are there??) but it messed up things again, so I reverse that, and I just have to regroup my refs… again, I am just happy to be able to open it again and to have the pdf.

Another idea came to my mind as I was reading the thread. If you library was previously synced, you can create an empty library and sync it again (download it from the server). Worked for me. Thanks to all of you for the sharing of ideas!

This happened to me months ago, but unfortunately I forgot how I resolved it. I think I had switched to Box Drive from Dropbox in hopes of it being specific to the cloud storage provider.

Since most people said it was cloud-related and my library is in a Box Drive folder, I looked to see what files had changed around the time the error popped up. Three files in the “rdb” folder had been edited.

The “pdf_index (MYUSERNAME 2).myd” file was new, but it was the first version of it.

Next were the “misc.myd” and “misc.myi” files. I restored these to versions that predated this error about the library being used by someone else.

The library opened fine and a Word doc that used this library “Updated Citations and Bibliography” just fine! Success after spinning my wheels for too long!

Cloud storage has been so helpful when switching machines, so I hope this can be less of a problem in the future. 

Hi all, 

I just find a solution that works for me. You get this error because some of the files are saved in the cloud (not offline accessible).  Just make sure both the data folder and .enl file are locally available by clicking the iCloud icon on the right of the folder/file name. Now it works like a charm.

Leo

Hi all, 

I just find a solution that works. You get this error because some of the files are saved in the cloud (not offline accessible).  Just make sure both the data folder and .enl file are locally available by clicking the iCloud icon on the right of the folder/file name. Now it works like a charm.

best,
Leo