"There was an error starting Zotero" with yellow exclamation mark
Hi,
I have the above issue and Zotero will not open at all. I have run through the "Reporting Startup Errors" steps here (http://www.zotero.org/support/reporting_bugs) and the error console yields the following:
Timestamp: 18/10/2012 10:07:07
Error: [Exception... "Component returned failure code: 0x80630002 (NS_ERROR_STORAGE_IOERR) [mozIStorageService.openDatabase]" nsresult: "0x80630002 (NS_ERROR_STORAGE_IOERR)" location: "JS frame :: chrome://zotero/content/xpcom/db.js :: <TOP_LEVEL> :: line 1104" data: no]
Source File: chrome://zotero/content/xpcom/zotero.js
Line: 749
I am running Firefox v. 16.0.1, Zotero v. 3.0.8, Windows 7 Professional.
Zotero was working fine yesterday but not this morning. Recent changes: a few days ago I installed Zotero Word for Windows Integration 3.1.8; around a month ago my zotero folder was moved to a new backed up home drive on my university network.
Many thanks
Anthony
I have the above issue and Zotero will not open at all. I have run through the "Reporting Startup Errors" steps here (http://www.zotero.org/support/reporting_bugs) and the error console yields the following:
Timestamp: 18/10/2012 10:07:07
Error: [Exception... "Component returned failure code: 0x80630002 (NS_ERROR_STORAGE_IOERR) [mozIStorageService.openDatabase]" nsresult: "0x80630002 (NS_ERROR_STORAGE_IOERR)" location: "JS frame :: chrome://zotero/content/xpcom/db.js :: <TOP_LEVEL> :: line 1104" data: no]
Source File: chrome://zotero/content/xpcom/zotero.js
Line: 749
I am running Firefox v. 16.0.1, Zotero v. 3.0.8, Windows 7 Professional.
Zotero was working fine yesterday but not this morning. Recent changes: a few days ago I installed Zotero Word for Windows Integration 3.1.8; around a month ago my zotero folder was moved to a new backed up home drive on my university network.
Many thanks
Anthony
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
Any idea what might have caused the error?
Thanks again