Can you provide a Debug ID for reproducing this?

(Also, while you don't say why you're doing this, just to be clear, an export isn't a backup.)

I'm not seeing an export attempt there.

You can go to Help → Debug Output Logging → View Output to see when it stops logging anything, which would mean it stalled and we'd want to see the log at that point. If it's still logging, it's still doing stuff.

For some reason it will not export past this author:

https://s3.amazonaws.com/zotero.org/images/forums/u46077/ld93ytri7q8wxniiuczc.png

Eriksen et al. ... it stops here every time. Makes zero sense! I even updated my account and storage last night.

https://s3.amazonaws.com/zotero.org/images/forums/u46077/p3m8xz4hdoubw190tgmb.png


This is the command I ran... last night I tried going one author at a time, still it wouldn't work.

I specifically said we need a Debug ID that covers the export attempt. You haven't provided that. Nothing else is going to get this fixed.

The linked page explains how to produce a Debug ID for a given operation. That's what we need.

Let me know if you need anything else.

Thank you for helping me to walk through this. I have never used the support page before and am relieved that you are helping me!

That debug output still doesn't include what we need. It looks like you perhaps left it on while Zotero was idle, at which point it started doing background full-text indexing. Again, from the linked page:

2. Immediately perform the relevant action (syncing, saving, importing, etc.) and reproduce the problem you're experiencing.

3. Before doing anything else, return to Help → Debug Output Logging and click Submit Output

As soon as files stop appearing in the filesystem, you should submit the debug output.

In any case, while we do need to see a Debug ID that includes the error, this of course isn't going to be fixed in the next hour. You'll need to figure out the file that's failing — e.g., by exporting half at a time, and then splitting the failing half in half, and so on, until you find the item that's failing. That shouldn't take more than 10 or tries, no matter the number of items you're exporting. If you're able to provide a Debug ID that actually shows the export taking place, we could likely tell you the item in question, but you don't need us to do this.

In a future update, we'll make sure it continues after an error like this and shows a report listing the files that failed.

I am really hoping this one works!

@lambertl: Oh, well, also, if you're not actually using PDF annotations, you can just uncheck "Include Annotations" in the export options window. That should greatly speed up the export and also avoid this error, even with that item selected.

You don't need to erase it. You can just deselect until this is fixed — or as I say, just uncheck "Include Annotations".

And please do send us the file.

However, now it is stopping somewhere else, so I can rerun the debug ID and rerun the action to see what it is, or I can copy the reference below the one where it stopped. Since it is in alphabetical author order, this way works. However, I don't know how to find the unique number identifier to send to support, and I believe I do need this next reference...

Okay, can you tell me the number for the failing file in this new debug ID: D668472542