"Collection *** not yet loaded" error on startup

muaddib28

Hello!

I'm running the latest Beta build on Mac OS 11.7.10 and after a forced restart of my machine, Zotero now won't launch. Before the items load, I get the following message with a prompt to check for updates which also hangs. Any suggestions to get it unstuck?

Thanks!


Collection 344 not yet loaded

UnloadedDataException: Collection 344 not yet loaded
Zotero.Exception.UnloadedDataException@chrome://zotero/content/xpcom/error.js:159:16
Zotero.DataObjects.prototype.get@chrome://zotero/content/xpcom/data/dataObjects.js:123:15
Zotero.Item.prototype.getCollections/<@chrome://zotero/content/xpcom/data/item.js:4324:34
Zotero.Item.prototype.getCollections@chrome://zotero/content/xpcom/data/item.js:4323:28
Zotero.Item.prototype.toJSON@chrome://zotero/content/xpcom/data/item.js:5485:30
Zotero.Item.prototype.migrateExtraFields@chrome://zotero/content/xpcom/data/item.js:5645:26
Zotero.Schema</this.migrateExtraFields@chrome://zotero/content/xpcom/schema.js:694:26
From previous event:
this.init@chrome://zotero/content/xpcom/zotero.js:414:25

dstillman

Can you provide a Debug ID for Zotero startup, using the "Restart with Logging Enabled…" option?

muaddib28

Thanks for your help! Unfortunately, I can't seem to get one, since the error message pops up immediately and then prevents any further action (see image).

I managed to launch in debug mode from the command line, but the debug window won't let me select Submit report. The terminal did give me a few more errors though:

$ /Applications/Zotero.app/Contents/MacOS/zotero -ZoteroDebug
[unrelated messages removed — D.S.]

https://s3.amazonaws.com/zotero.org/images/forums/u302796/5ol9a0fgxxsson66u2at.png

dstillman

You may still be able to use Cmd-` (backtick, above Tab) to switch to the debug output window and submit it, but if not, see Logging to a Terminal Window, including the part about saving the log file to your desktop.

dstillman

But if this really started after your computer crashed, you might want to try the DB Repair Tool to see if that finds any errors in your database. If you tell us the Upload ID, we can also run some tests on your database to see what's going on.

Another option would be to restore to the last automatic backup, assuming the timestamp is from before this happened. Assuming you were syncing, you can then just sync to pull down any more recent data. (If you were syncing, you could also just start with a new, empty database and pull down everything, but you might as well start with a more recent backup of your database.)

In any case, it would be good to get the full debug output so we can see what's happening here.

muaddib28

I can switch to the debug output window but it won't let me click the submit button. I just emailed the text debug output to the support@ email address.

I tried to use the DB repair tool but it keeps timing out with a 504 Gateway Time-out. It's a pretty large db (171.1MB, 69.3MB zipped)

I can try to run the manual repair process later today, but will wait to hear back from you for now. Thanks again!

muaddib28

Update: just tried the manual recovery step and it still hangs with the same errors...

dstillman

This should be fixed now in beta 105.

muaddib28

Confirmed! Just downloaded the latest beta and was able to launch without issue. Thanks so much for the fix, and all you do to keep this vital application going strong!