Closed
Bug 649728
Opened 15 years ago
Closed 15 years ago
unable to sync due to 'specified GUID already exists'
Categories
(Firefox :: Sync, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 621846
People
(Reporter: bugzilla, Unassigned)
Details
after updating my nightly build Im suddenly unable to sync. I've done nothing else that Help->About->update
Mozilla/5.0 (Windows NT 5.1; rv:2.2a1pre) Gecko/20110412 Firefox/4.2a1pre ID:20110412030535
Error: [Exception... "Couldn't decrypt string" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gre/components/crypto-SDR.js :: <TOP_LEVEL> :: line 205" data: no]
Source File: resource://gre/components/crypto-SDR.js
Line: 205
Error: [Exception... "'specified GUID already exists' when calling method: [nsILoginManagerStorage::modifyLogin]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "JS frame :: resource://gre/components/nsLoginManager.js :: <TOP_LEVEL> :: line 442" data: no]
Source File: resource://gre/components/nsLoginManager.js
Line: 442
1302719957578 Engine.Passwords WARN Failed to reconcile incoming record {0f37ee6c-662a-4594-a331-2b6bd74e88bf}
1302719957579 Engine.Passwords WARN Encountered exception: 'specified GUID already exists' when calling method: [nsILoginManagerStorage::modifyLogin] Stack trace: resource://gre/components/nsLoginManager.js:442 < PasswordStore__changeItemID()@resource://services-sync/engines/passwords.js:212 < _handleDupe()@resource://services-sync/engines.js:858 < SyncEngine__reconcile()@resource://services-sync/engines.js:897 < resource://services-sync/engines.js:703 < resource://services-sync/record.js:813 < Channel_onDataAvail()@resource://services-sync/resource.js:587
Comment 1•15 years ago
|
||
Smells like a dupe of bug 621846.
Status: NEW → RESOLVED
Closed: 15 years ago
Component: Firefox Sync: Crypto → Firefox Sync: Backend
QA Contact: sync-crypto → sync-backend
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•7 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
•