Closed
Bug 737130
Opened 12 years ago
Closed 12 years ago
Can't sync; Sync.Store.Forms WARN Failed to apply incoming record; Encountered exception; Got exception
Categories
(Firefox :: Sync, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 739697
People
(Reporter: steffen.wilberg, Unassigned)
Details
Attachments
(2 files)
I can't sync since two days, there's not even a log in about:sync-log, and that's with services.sync.log.appender.file.logOnSuccess (and .logOnError) set to true. The sync info bar at the bottom of the main window displays: "Sync encountered an error while syncing: Unknown error. Sync will automatically retry this action." If I click the "Sync Now" button, the info bar disappears and reappears within a few seconds. Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120319 Firefox/14.0a1 The error console shows: 1332181817842 Sync.Store.Forms WARN Failed to apply incoming record 4V8f+0MWSaqUYU3n 1332181817843 Sync.Store.Forms WARN Encountered exception: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [mozIStorageConnection.beginTransaction] Stack trace: resource:///components/nsFormHistory.js:253 < FormStore_remove()@resource:///modules/services-sync/engines/forms.js:264 < Store_applyIncoming()@resource://services-sync/engines.js:273 < applyIncoming()@resource:///modules/services-sync/engines/forms.js:218 < applyIncomingBatch()@resource://services-sync/engines.js:243 < resource:///modules/services-sync/engines/forms.js:213 < resource://services-sync/util.js:168 < applyIncomingBatch()@resource:///modules/services-sync/engines/forms.js:214 < doApplyBatch()@resource://services-sync/engines.js:795 < doApplyBatchAndPersistFailed()@resource://services-sync/engines.js:810 < SyncEngine__processIncoming()@resource://services-sync/engines.js:910 < SyncEngine__sync()@resource://services-sync/engines.js:1320 < WrappedNotify()@resource://services-sync/util.js:148 < Engine_sync()@resource://services-sync/engines.js:517 < WeaveSvc__syncEngine()@resource:///modules/services-sync/service.js:1496 < resource:///modules/services-sync/service.js:1389 < WrappedNotify()@resource://services-sync/util.js:148 < WrappedLock()@resource://services-sync/util.js:103 < _lockedSync()@resource:///modules/services-sync/service.js:1289 < resource:///modules/services-sync/service.js:1280 < WrappedCatch()@resource://services-sync/util.js:77 < sync()@resource:///modules/services-sync/service.js:1268 1332181817843 Sync.Engine.Forms WARN Got exception Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [mozIStorageConnection.commitTransaction] Stack trace: resource://services-sync/util.js:171 < applyIncomingBatch()@resource:///modules/services-sync/engines/forms.js:214 < doApplyBatch()@resource://services-sync/engines.js:795 < doApplyBatchAndPersistFailed()@resource://services-sync/engines.js:810 < SyncEngine__processIncoming()@resource://services-sync/engines.js:910 < SyncEngine__sync()@resource://services-sync/engines.js:1320 < WrappedNotify()@resource://services-sync/util.js:148 < Engine_sync()@resource://services-sync/engines.js:517 < WeaveSvc__syncEngine()@resource:///modules/services-sync/service.js:1496 < resource:///modules/services-sync/service.js:1389 < WrappedNotify()@resource://services-sync/util.js:148 < WrappedLock()@resource://services-sync/util.js:103 < _lockedSync()@resource:///modules/services-sync/service.js:1289 < resource:///modules/services-sync/service.js:1280 < WrappedCatch()@resource://services-sync/util.js:77 < sync()@resource:///modules/services-sync/service.js:1268, aborting processIncoming. The attached sync log, which is the last one and 2 days old, also contains those errors, but it said it was successful.
Reporter | ||
Comment 1•12 years ago
|
||
Apart from the three errors mentioned above, which I get on every attempt to sync, I got one instance of the following: 1332185251271 Sync.Engine.Forms WARN GUID query returned undefined; turn on Trace logging for details. 1332185251271 Sync.Tracker.Forms WARN Attempted to add undefined ID to tracker I've then set services.sync.log.logger.engine.forms to "Trace" and restarted Nightly. I got one instance of this: 1332185720646 Sync.Engine.Tabs WARN DATA LOSS: Both local and remote changes to record: iq0piUyjo-
Reporter | ||
Comment 2•12 years ago
|
||
A successful sync slipped through somehow.
Reporter | ||
Updated•12 years ago
|
Summary: Sync.Store.Forms WARN Failed to apply incoming record; Encountered exception; Got exception → Can't sync; Sync.Store.Forms WARN Failed to apply incoming record; Encountered exception; Got exception
Comment 3•12 years ago
|
||
I suspect that this is a corrupted form database. My resolution would be to delete the form database then force Sync to pull down all server data. Please wait for confirmation from someone else before performing these steps, as I'm not sure it is optimal or will work. 1) Delete formhistory.sqlite from your profile when Firefox is not running (go to about:support to find the location of your profile) 2) Start Firefox. Open about:config and set the values of services.sync.forms.lastSync and services.sync.forms.lastSyncLocal to 0. 3) Perform a sync
Comment 4•12 years ago
|
||
Dupe of Bug 739697?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Comment 5•12 years ago
|
||
(In reply to Gregory Szorc [:gps] from comment #3) > I suspect that this is a corrupted form database. > > My resolution would be to delete the form database then force Sync to pull > down all server data. Please wait for confirmation from someone else before > performing these steps, as I'm not sure it is optimal or will work. In bug 739697, Joe was able to use form history features just fine despite this error. Before deleting formhistory.sqlite, please keep a backup of it so we can diagnose the problem.
Reporter | ||
Comment 6•12 years ago
|
||
I could use the form history features just fine as well, so I renamed formhistory.sqlite instead of deleting it. Apart from that, comment 3 helped me fix this on my machine.
Assignee | ||
Updated•6 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•