XmarksException [source: internal, id: -50]

I am now getting the following when Xmarks tries to synchronize: "Unexpected error during synchronization: XmarksException [source: internal, id: -50]: putchanges failed during sync attempt". This started happening after I upgraded IE to 8.0.

I’m frustrated

Inappropriate?

Reply to this question

4 people have this question

I have this question, too! Tell me when someone answers.
The more people who ask this question, the more it gets noticed.

EMPLOYEE

Remove Inappropriate?
Delete or Edit

Colin, Official Rep, replied on May 20, 2009 20:08

Hi Rick,

Sorry about that! If you look in your log file (which can be accessed from the Advanced Xmarks settings) you should be able to find that error in there as well (it should be near the end of the file). Can you copy and paste the last couple of lines before that error?

this answers the question

Add a comment This answers the question Mark as a company answer
Remove Inappropriate?
Delete or Edit

Rick Turek replied on May 20, 2009 21:06

Wed May 20 16:07:22 2009: Starting sync
Wed May 20 16:07:22 2009: Sending local changes to server
Wed May 20 16:07:22 2009: New SyncRequest Initialized [POST]: http://sync.xmarks.com/sync/bookmarks... (cleaned body: {"baserev":"140","commands":[{"action":"delete","nid":"bhvn23"},{"action":"delete","nid":"mQVGv1"}],"log":{"mid":"khpo0w"}}
)
Wed May 20 16:07:25 2009: Cleaned SyncRequest response from server: {
"message" : "'unknown node bhvn23'",
"status" : 400
}

Wed May 20 16:07:25 2009: Unexpected error during synchronization: XmarksException [source: internal, id: -50]: putchanges failed during sync attempt

2 people say this answers the question

1 Comment Add a comment This answers the question
Remove
Colin, (Official Rep), commented on May 20, 2009 21:13

Okay, it sounds like Xmarks may have gotten a little confused. If you do a download (from the Advanced settings) it should get everything working again (the download will replace your current IE Favorites with what you have saved on the server).
Remove Inappropriate?
Delete or Edit

Rick Turek replied on May 20, 2009 21:18

That seems to have fixed the issue. Thanks!

1 person says this answers the question

1 Comment Add a comment This answers the question
Remove
milesrf commented on November 15, 2009 06:55

Rich,

Could you mention what antivirus program you were using then, in case that's part of the cause of the problem? For my last version of this problem, doing a download DIDN'T fix it.
Remove Inappropriate?
Delete or Edit

milesrf replied on November 02, 2009 07:05

I keep getting a similar synchronization error on one of my machines, but without the references to putchanges:

An error occured during synchronization. If the error message below doesn't
explain how to fix the problem, please note the error's source and click Help for
additional support.

Unexpected error during synchronization: XmarksException [source: internal, id:
-50]: Conflict: duplicate nids detected on insert Ehalw2: ,name:carbohydrates
Good Carbs Guide the Way - What Should You Eat - The Nut [...], pnid:QyqXc3,
name:carbohydrates Good Carbs Guide the Way - What Should You Eat - The

Looks like you need the following updates to help solve this
problem:

1. Give users a way to look up items by nid and pnid to get
their locations in the folder tree, without having to know in
advance what folder in the folder tree contains them. I
have far too many items stored to search the entire folder tree
for something which might be stored in more than one folder.
I did find one item with the right name, but moving it to a
different folder did not help.

2. Modify the error message window to allow users to use
the mouse to copy the text in the error window and paste it
into a post about the error.

3. Modify the error message to allow users on a laptop
without a mouse to use some other method for selecting
the text to copy.

4. In cases where this error occurs for two different
names pointing to the same URL, give the user a chance to
simply delete one of the two without having to look up
what folder contains the item with problems.

Simply downloading what's on the server doesn't look suitable if it will lose any changes made on this machine since the problem started, especially since what's on the server appears to already contain the problem.

I’m frustrated

this answers the question

Add a comment This answers the question
Remove Inappropriate?
Delete or Edit

milesrf replied on November 02, 2009 07:28

The last part of the log file:

Mon Nov 02 01:07:22 2009: Detector [insert_move]: localID: Ehalw2, serverID: 5Wth+
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: p4.fF3
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: dfbY.1
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: q4.fF3
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: o4.fF3
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Phalw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: 9ialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Vhalw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Uhalw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: 3ialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Xhalw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: 1ialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Whalw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Yhalw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Zhalw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: .halw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: +halw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: 0ialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: 2ialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: 6ialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: 4ialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: 5ialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: bialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: cialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: eialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: dialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: fialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: hialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: gialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: qialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: rialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Oialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Qialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Hialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Pialw2
Mon Nov 02 01:07:22 2009: Detector [insert_insert]: localID: Ehalw2, serverID: Ehalw2
Mon Nov 02 01:07:22 2009: Synchronize failed
Mon Nov 02 01:07:22 2009: Unexpected error during synchronization: XmarksException [source: internal, id: -50]: Conflict: duplicate nids detected on insert Ehalw2: , name:carbohydrates Good Carbs Guide the Way - What Should You Eat - The Nut (...), pnid:QyqXc3, name:carbohydrates Good Carbs Guide the Way - What Should You Eat - The Nutrition Source - Harvard School of Public Health, pnid:ZRiRx
Mon Nov 02 01:07:22 2009: Attaching observers
Mon Nov 02 01:09:20 2009: Attaching observers

This computer runs the Xmarks for IE 1.0.11 version under 32-bit Vista SP2 with Internet Explorer 8.0.6001.18828; I also have another computer running the same version under 64-bit Vista Sp1, and a third running the same version under Vista SP2. The two running 64-bit Vista do not show this problem, but one of appears to have recently allowed saving the same URL twice with the same name during the last few days.

I’m frustrated

this answers the question

4 Comments Add a comment This answers the question
Remove
milesrf commented on November 08, 2009 14:55

I found an apparant solution last night.

It seems very likely that a number of functions, including automatic sync, manual sync, download, and the merge after a recovery, fail to handle situations where the log file is enabled and an operation starts which, if it is successful, will more than fill up the log file. After at least a week of failed syncs, I tried to look at the log file, but it was corrupted enough that it could not be converted so that Notepad could get a usable version of it.
I then cleared the log file, tried the sync again, and this time it succeeded, although with the deletion of one of the folder trees (probably due to a failed attempt to restore what was lost from that folder tree by re-importing it from an exported copy).

Workaround: If the problem is seen, clear the log file (possibly after storing a copy), then try the failed operation again.

Suggested permanent fix: Set up two logfile size limits, one for operations on favorites, and a slightly higher one to allow recording error messages about the problem. Modify the code for the various operations so that it checks whether the messages from an operation will exceed the lower limit before writing these messages. If it will, immediately display a clear message saying that the log file must be cleared before continuing, and hold that write and any operations not done yet so that they can be restarted after the clearing of the log file.

Now the two of my computers that run Vista SP2 are in sync; but the one running Vista SP1 has a new problem that may require the same type of solution, when I can find time.
Remove
Colin, (Official Rep), commented on November 09, 2009 00:28

Wow, nice work. I'm concerned about that possible bug you found. We should handle large log files correctly, but it sounds like that isn't always the case. I'm glad you found a work around! I'll dig into the issue and see if I can figure out the root problem. Thanks again!
Remove
milesrf commented on November 09, 2009 05:14

Saving nearly everything on the computer that had the first problem (about 4 MB of Favorites, when I exported all of them to just one file) took long enough that I've barely started on the second one (now with over 5 MB in the export-everything file). If you had an application (either in the Windows version or on your web site for finding multiple links in the same folder that point to the same URL), I'd be able to eliminate a significant percentage of this. Also, a third computer now has an even worse problem - it won't boot properly, but there's no clear sign what caused this.
Remove
milesrf commented on November 10, 2009 15:25

Another day of recovery work. The third computer started working properly after I did a few more reboots, including one after turning off its power for about 10 minutes. Now have about a dozen saved log files created before clearing the log (total for three machines). Lost one because it was already too big to fit in Notepad, and the option to look at the log file insisted that some other editor be used to view it, but did not offer any option on how to make it available to some other editor.

Have seen a few variations of the problem, including one that mentioned putchanges.

Have thought of another possible idea of what is causing the problem: All three of my machines run Norton Internet Security 2010 in the background, and I suspect that that program asks for exclusive access to the files it is about to check for a virus so that it can keep exclusive access if it detects a virus or other security problem. Is Xmarks for IE able to recover from being unable to do some file operation immediately, instead of waiting a minute or so in order to let other programs turn loose of the file it wants to access?

Sun Nov 08 23:45:24 2009: Starting Do_reorder for: 2.gPR1
Sun Nov 08 23:45:24 2009: Removing 2.gPR1 from parent
Sun Nov 08 23:45:24 2009: Inserting 2.gPR1 as child: jXgPR1 [bnid: u.gPR1]
Sun Nov 08 23:45:24 2009: Sending local changes to server
Sun Nov 08 23:45:24 2009: New SyncRequest Initialized [POST]: http://sync.xmarks.com/sync/bookmarks... (cleaned body: {"baserev":"1463","commands":[{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"gLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"iLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"2HsXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"kLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"lLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"mLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"nLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"oLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"pLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"GRlEf3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"uLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"S3pbU2"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"NjiPR1"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"9v7Jz2"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"wLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"xLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"yLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"zLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"ALpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"BLpXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"fv7Jz2"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"dGIX71"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"eEIX71"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"5EIX71"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"eGIX71"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"wEIX71"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"MFtXc3"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"gHIX71"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"hHIX71"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"umiPR1"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"EmiPR1"},{"action":"reorder","args":{"bnid":"B4x7K3"},"nid":"PmiPR1"}],"log":{"mid":"kjd6yw"}}
)
Sun Nov 08 23:45:24 2009: Cleaned SyncRequest response from server: {
"status" : 0,
"toprev" : 1464,
"username" : "milesrf"
}

Sun Nov 08 23:45:25 2009: Cleaned SyncRequest response from server: {
"message" : "Conflict: base revision not the latest",
"status" : 409
}

Sun Nov 08 23:45:25 2009: Unexpected error during synchronization: XmarksException [source: internal, id: -50]: putchanges failed during sync attempt
Sun Nov 08 23:45:25 2009: Recieved WM_COMMAND message: 1066
Remove Inappropriate?
Delete or Edit

john.arnold30 replied on November 09, 2009 12:44

Clearing out the log file worked for me.

this answers the question

1 Comment Add a comment This answers the question
Remove
milesrf commented on November 15, 2009 06:53

Could you mention what version of what (if any) antivirus program you're using, to help determine if that's the problem?
Remove Inappropriate?
Delete or Edit

milesrf replied on November 11, 2009 07:16

Another day of recovery work. Now nearly finished.

Examples of the last few lines in the log file after a few variants of this problem; you may notice that I collect a lot of links related to medical research.

Sun Nov 08 21:17:24 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\medical\cancer\thyroid
Sun Nov 08 21:17:24 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\medical\cancer\Tip

Share Vitamin C Shows Promise as Cancer Treatment.URL
Sun Nov 08 21:17:24 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\medical\cancer\Toward

bold new anti-cancer medicines ( Bold new strategies in the bat (...).url
Sun Nov 08 21:17:24 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\medical\cancer\Tumor

vessels identified by unique molecular markers - Mooshee.url
Sun Nov 08 21:17:24 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\medical\cancer\Turning

Cancer Friend Into Cancer Foe.url
Sun Nov 08 21:17:24 2009: Loading file attrs for file: \\?

\C:\Users\Bobby\Favorites\medical\cancer\University College London Study Shows Beans Beat Cancer.url
Sun Nov 08 21:17:24 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\medical\cancer\US

study uncovers powerful anti-cancer compound - Yahoo! News.url
Sun Nov 08 21:17:25 2009: XmarksException during sync attempt: XmarksException [source: windows, id: 32]:

Error while opening CreateFile [\\?\C:\Users\Bobby\Favorites\medical\cancer\US study uncovers powerful

anti-cancer compound - Yahoo! News.url]
Sun Nov 08 21:17:25 2009: Attaching observers
Sun Nov 08 21:17:42 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:42 2009: Attaching observers
Sun Nov 08 21:17:42 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:42 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:17:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:17:53 2009: Attaching observers
Sun Nov 08 21:18:22 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:22 2009: Attaching observers
Sun Nov 08 21:18:51 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:51 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:52 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:52 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:53 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:54 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:54 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers
Sun Nov 08 21:18:55 2009: Recieved WM_COMMAND message: 1074
Sun Nov 08 21:18:55 2009: Attaching observers

Mon Nov 09 22:03:01 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\AB-prion\Prion protein

amyloidosis. [Brain Pathol. 1996] - PubMed result.url
Mon Nov 09 22:03:01 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\AB-prion\Prion protein

identified as a novel early pancreatic cancer biomarker.url
Mon Nov 09 22:03:01 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\AB-prion\Prion protein

of 106 residues creates an artifical... [Cell. 1999] - P (...).url
Mon Nov 09 22:03:01 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\AB-prion\Prions Link

Cholesterol To Neurodegeneration.url
Mon Nov 09 22:03:03 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\AB-prion\Prions serve

as important source of variation in nature.url
Mon Nov 09 22:03:03 2009: XmarksException during sync attempt: XmarksException [source: windows, id: 32]:

Error while opening CreateFile [\\?\C:\Users\Bobby\Favorites\AB-prion\Prions serve as important source of

variation in nature.url]
Mon Nov 09 22:03:03 2009: Attaching observers
Mon Nov 09 22:08:03 2009: Recieved WM_COMMAND message: 1537
Mon Nov 09 22:08:03 2009: Attaching observers

Tue Nov 10 06:40:36 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\AB-misc\AA-

continue\VITAMIN Reference Guide.url
Tue Nov 10 06:40:36 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\AB-misc\AA-

continue\What Is Amino Acid.url
Tue Nov 10 06:40:36 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\AB-misc\AA-

continue\What you eat 'could raise your risk of Alzheimer's' as discovery paves (...).url
Tue Nov 10 06:40:36 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\AB-misc\AA-

continue\Why Bad Things Can Happen To The Heart When 'Good' Cholesterol Goes Ba (...).url
Tue Nov 10 06:40:37 2009: XmarksException during sync attempt: XmarksException [source: windows, id: 32]:

Error while opening CreateFile [\\?\C:\Users\Bobby\Favorites\AB-misc\AA-continue\Why Bad Things Can Happen

To The Heart When 'Good' Cholesterol Goes Ba (...).url]
Tue Nov 10 06:40:37 2009: Attaching observers
Tue Nov 10 06:40:56 2009: Recieved WM_COMMAND message: 1067

Tue Nov 10 12:47:34 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\stroke\stroke - Mirror

trick shows promise as stroke therapy - Yahoo! News.url
Tue Nov 10 12:47:34 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\stroke\stroke -

Moderate To Severe Sleep Apnea Significantly Raises Stroke Ri (...).url
Tue Nov 10 12:47:35 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\stroke\stroke - New

Evidence Finds An Association Between Periodontal Disease (...).url
Tue Nov 10 12:47:35 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\stroke\stroke - New

Israeli virtual reality program improves stroke rehab - I (...).url
Tue Nov 10 12:47:35 2009: Loading file attrs for file: \\?\C:\Users\Bobby\Favorites\stroke\stroke -

newsdaily Ginkgo extract offers promise to cut stroke damage.url
Tue Nov 10 12:47:52 2009: XmarksException during sync attempt: XmarksException [source: windows, id: 32]:

Error while opening CreateFile [\\?\C:\Users\Bobby\Favorites\stroke\stroke - newsdaily Ginkgo extract

offers promise to cut stroke damage.url]
Tue Nov 10 12:47:52 2009: Attaching observers
Tue Nov 10 12:52:52 2009: Recieved WM_COMMAND message: 1537
Tue Nov 10 12:52:52 2009: Attaching observers

I’m undecided

this answers the question

1 Comment Add a comment This answers the question
Remove
milesrf commented on November 12, 2009 01:33

Another day of recovery work.

Another variation of the problem:

An error occurred during synchronization. If the error message below doesn't
explain how to fix the problem, please note the error's source and click Help for
additional support.

Unexpected error during synchronization; XmarksException [source: internal: id:
-50]; No solution converged after 1000 iterations

This one was NOT handled adequately by clearing the log file and trying again; instead, I first had to remove some excess folders using another of my machines.

I can't copy parts of the log files for the laptop; it uses a touchpad instead of a mouse, and does not have a usable way of selecting what text to copy other than the entire file.

While trying to find the missing folder in the backups, I found that it had been missing at least a week before this set of problems started, with enough other problems that I decided to describe them in a separate thread.
Remove Inappropriate?
Delete or Edit

milesrf replied on November 15, 2009 06:22

Another variation of this error; looks like about two more days of fixup work.

An error occured during synchronization. If the error message below doesn't
explain how to fix the problem, please note the error's source and click help for
additional support.

Unexpected error during synchronization: XmarksException [source: internal, id:
-50]: Conflict: duplicate nids detected on insert SvNCt , bnid: name: diabetes,
bnid: Crx86, name: diabetes

Initially, the logfile was too big to save. However, a logfile clear, then
two downloads didn't fix the problem; they both failed with the same error
message, and the second one gave this at the end of the logfile:

Sat Nov 14 23:44:30 2009: Detector [insert_insert]: localID: SvNCt, serverID: pZrpl3
Sat Nov 14 23:44:30 2009: Detector [insert_insert]: localID: SvNCt, serverID: g8hm82
Sat Nov 14 23:44:30 2009: Detector [insert_insert]: localID: SvNCt, serverID: hp21h1
Sat Nov 14 23:44:30 2009: Detector [insert_insert]: localID: SvNCt, serverID: SvNCt
Sat Nov 14 23:44:30 2009: Synchronize failed
Sat Nov 14 23:44:30 2009: Unexpected error during synchronization: XmarksException [source: internal, id:

-50]: Conflict: duplicate nids detected on insert SvNCt: , bnid:, name:diabetes?, bnid:Crx86,

name:diabetes
Sat Nov 14 23:44:33 2009: Attaching observers
Sat Nov 14 23:45:11 2009: Attaching observers
Sat Nov 14 23:46:12 2009: Attaching observers
Sat Nov 14 23:49:42 2009: Attaching observers

I'm running some of the alpha test and beta test BOINC projects, and after
comparing error rates of Xmarks for IE v1.0.11 to the error rates of those
projects, I'd say that Xmarks for IE v1.0.11 should definitely be labelled
as in alpha test.

No clear information on whether it's the rather large size of my links file (currently 6,981 KB when I exported it on the machine with the latest problem), running Xmarks and Norton Internet Security 2010 on the same machine, or something else, that's causing the problem.

It not longer looks like just the size of the logfile, though; I'm getting various sizes at the point of the problem.

I’m frustrated

this answers the question

Add a comment This answers the question
Remove Inappropriate?
Delete or Edit

milesrf replied on November 16, 2009 07:12

Since the last error message did not suggest how to fix the problem, I decided to do some work on a computer properly synchronized to reduce the number of duplicate URLs with different names. For no obvious reason that turned the last error into this one:

An error occurred during synchronization. If the error message below doesn't
explain how to fix the problem, please note the error's source and click Help for
additional support.

Unexpected error during synchronization: XmarksException [source: internal, id:
-50]: Conflict: duplicate nids detected on insert U7hm82: , bnid:, name:[Chromium
as an essential element][Cas Lek Cesk. 2003] - Pubmed resul[...], bnid: SV8Ew1,
name:[Chromium as an essential element][Cas Lek Cesk. 2003] - Pubmed result

For this error, is there any good reason for not assigning one of the conflicting items a new nid and going on?

The logfile was too big to open in Notepad again, and no other way was provided to reach it, so I can't show you the effect on the logfile.

I've thought of adding a second browser to this machine, in order to get access to some of the new features not provided in the Xmarks for IE version yet. Can you suggest a second browser for which a good set of features is available and it WON'T interfere with keeping IE as the main browser on the machine? Will I have to pay more to get Xmarks for that browser also?

Since that error didn't suggest any fix either, I decided to eliminate a few more duplicates using the other machine. This changed the error on the machine that wouldn't synchronize again, this time to:

An error occurred during synchronization. If the error message below doesn't
explain how to fix the problem, please note the error's source and click Help for
additional support.

Unexpected error during synchronization: XmarksException [source: internal,id:
-50]: Conflict: duplicate nids detected on insert S7hm82: , name:A
comparison of the insulin-sensitive transport of...[J Inorg Biochem[...],
bnid: SV8Ew1. name:Acomparison of the insulin-sensitive transport of...[J Inorg

Sun Nov 15 13:07:06 2009: Detector [insert_reorder]: localID: S7hm82, serverID: ObLXK3
Sun Nov 15 13:07:06 2009: Detector [insert_reorder]: localID: S7hm82, serverID: fXB3m
Sun Nov 15 13:07:06 2009: Detector [insert_reorder]: localID: S7hm82, serverID: I6hm82
Sun Nov 15 13:07:06 2009: Detector [insert_insert]: localID: S7hm82, serverID: U7hm82
Sun Nov 15 13:07:06 2009: Detector [insert_insert]: localID: S7hm82, serverID: S7hm82
Sun Nov 15 13:07:06 2009: Synchronize failed
Sun Nov 15 13:07:06 2009: Unexpected error during synchronization: XmarksException [source: internal, id:

-50]: Conflict: duplicate nids detected on insert S7hm82: , bnid:, name:A comparison of the insulin-

sensitive transport of... [J Inorg Biochem (...), bnid:SV8Ew1, name:A comparison of the insulin-sensitive

transport of... [J Inorg Biochem. 2004] - PubMed result
Sun Nov 15 13:07:06 2009: Attaching observers

More work on the other machine only made the error type alternate between the last two. I have another machine with sync problems; haven't started doing much for that one.

I’m frustrated

this answers the question

Add a comment This answers the question
Remove Inappropriate?
Delete or Edit

milesrf replied on November 17, 2009 16:02

I saw the notice that the new 1.1.3 version is now available, and installed it on two of my machines. Apparantly, it does not handle the duplicate nids problem any better, at least if installed when the previous version has this problem.

The following was AFTER a reboot, a Clear Logfile, a Download, and a Synchronize Now:

An error occured during synchronization. If the error message below doesn't
explain how to fix the problem, please note the error's source and click Help for
additional support.

Unexpected error during synchronization: XmarksException [source: internal, id:
-50]: Conflict: duplicate nids detected on insert S7hm82 , bnid:, name:A
comparison of the insulin sensitive transport of... {J Inorg Biochem [...],
bnid: SV8Ew1, name:A comparison of the insulin-sensitive transport of... [J Inorg

For this error, the logfile was too large for Notepad to open it.

An error occured during synchronization. If the error message below doesn't
explain how to fix the problem, please note the error's source and click Help for
additional support.

Unexpected error during synchronization: XmarksException [source: internal, id:
-50]: Conflict: duplicate nids detected on insert U7hm82: , bnid:, name:[Chromium
as an essential element][Cas Lek Cesk. 2003] - Pubmed resul [...],bnid:SV8Ew1,
name:[Chromium as an essential element][Cas Lek Cesk. 2003] - Pubmed result

Again, the logfile was too large for Notepad to open it.

From a different occurence of the problem:

Tue Nov 17 06:46:39 2009: Detector [insert_reorder]: localID: T7hm82, serverID: xfx86
Tue Nov 17 06:46:39 2009: Detector [insert_reorder]: localID: T7hm82, serverID: 3iFXj1
Tue Nov 17 06:46:39 2009: Detector [insert_reorder]: localID: T7hm82, serverID: PbLXK3
Tue Nov 17 06:46:39 2009: Detector [insert_insert]: localID: T7hm82, serverID: U7hm82
Tue Nov 17 06:46:39 2009: Detector [insert_insert]: localID: T7hm82, serverID: S7hm82
Tue Nov 17 06:46:39 2009: Detector [insert_insert]: localID: T7hm82, serverID: T7hm82
Tue Nov 17 06:46:39 2009: Synchronize failed
Tue Nov 17 06:46:39 2009: Unexpected error during synchronization: XmarksException [source: internal, id: -50]: Conflict: duplicate nids detected on insert T7hm82: , bnid:, name:Chromium, glucose intolerance and diabetes. [J Am Coll Nutr. 1998] - P (...), bnid:JAIX71, name:Chromium, glucose intolerance and diabetes. [J Am Coll Nutr. 1998] - PubMed result

From another try:

An error occured during synchronization. If the error message below doesn't
explain how to fix the problem, please note the error's source and click Help for
additional support.

Unexpected orror during synchronization: XmarksException [source: internal, id:
-50]: Conflict: duplicate nids detected on insert T7hm82 , name:Chromium,
glucose intolerance and diabetes. [J Am Coll Nutr. 1998] - P [...], bnid:JAIX71,
name:Cnromium. glucose intolerance and diabetes. [J Am Coll Nutr. 1998] -

Tue Nov 17 09:15:48 2009: Detector [insert_reorder]: localID: S7hm82, serverID: xfx86
Tue Nov 17 09:15:48 2009: Detector [insert_reorder]: localID: S7hm82, serverID: 3iFXj1
Tue Nov 17 09:15:48 2009: Detector [insert_reorder]: localID: S7hm82, serverID: PbLXK3
Tue Nov 17 09:15:48 2009: Detector [insert_insert]: localID: S7hm82, serverID: U7hm82
Tue Nov 17 09:15:48 2009: Detector [insert_insert]: localID: S7hm82, serverID: S7hm82
Tue Nov 17 09:15:48 2009: Synchronize failed
Tue Nov 17 09:15:48 2009: Unexpected error during synchronization: XmarksException [source: internal, id: -50]: Conflict: duplicate nids detected on insert S7hm82: , bnid:, name:A comparison of the insulin-sensitive transport of... [J Inorg Biochem (...), bnid:SV8Ew1, name:A comparison of the insulin-sensitive transport of... [J Inorg Biochem. 2004] - PubMed result
Tue Nov 17 09:15:48 2009: Attaching observers

Looks like the end of the logfile is no longer matching up with the error message, at least after the rather long time needed to display the logfile. Could we have an option to tell it to display only so many lines at the end of the logfile, so Notepad can open this faster? I'm now getting logfiles often over 100,000 KB, even when they're small enough Notepad can open them.

Also, I've spotted a possible cause for getting multiple bookmarks pointing to the same URL. Some versions of either Xmarks or IE appear to have been sometimes adding an invisible character, and not always the same one, to the bookmark name when producing an abbreviated name if the original name was too long to display. The check for duplicate bookmark names does not appear to ignore this invisible character; neither does the IE code for editting the bookmark name.

Also, the IE8 option for displaying the installed add-ons cannot find a company name and version number for Xmarks; therefore I cannot use this to check for signs that at least part of the previous Xmarks version is still installed and causing the current problems. Could this be added?

The increased variation of error messages I'm getting suggest that Xmarks for IE v1.1.3 MAY be assigning a new nid when it detects duplicate nids, but only one for each synchronization attempt. If so, could it be modified so that after this nid change, it immediately does another synchronization or download attempt, unless it is then able to continue with the previous attempt?

I’m frustrated

this answers the question

1 Comment Add a comment This answers the question
Remove
Colin, (Official Rep), commented on November 17, 2009 23:32

You're able to reproduce this by starting fresh with a Download, followed by a Sync? If so, I can try to reproduce this on my machine too. If you want to do that, send an email to support@xmarks.com with your username and a link to this thread (and include my name so it gets directed to me). I'd love to get this sorted out.
Remove Inappropriate?
Delete or Edit

milesrf replied on November 18, 2009 00:16

I am able to reproduce it that way.

I see nothing of the Advanced window or in the logfile indicating that the Download actually did anything to remove the old database or create a new one; you may want to have the Download code send messages to both marking when it started and when it ended.

I’m frustrated

this answers the question

Add a comment This answers the question
Remove Inappropriate?
Delete or Edit

milesrf replied on November 20, 2009 06:41

I finally found what looks like the conflicting items on a computer that still synchronizes, and also a copy of a large folder tree (3674 items) under another directory. I deleted the copy of the large folder tree, and brought up the two conflicting items under IE8, then saved them in another directory, then deleted the conflicting items, synchronized on the computer where I did this, then tried to synchronize on the computer with sync problems. The xmarkssync.exe process appeared to almost freeze for several minutes, with a high page fault rate (up to 60,000 as displayed by Windows Task Manager) even though it was using only about 260 MB of the 2 GB memory this machine has. Then the icon went back to showing an error; a new variation this time:

An error occured during synchronization. If the error message below doesn't
explain how to fix the problem, please note the error's source and click Help for
additional support.

Unexpected error during synchronization: XmarksException [source:internal: id:
-50]: Conflict: duplicate nids detected on insert T7hm82 , bnid:, name:Chromium,
glucose intolerance and diabetes. [J Am Coll Nutr. 1998] - [...], bnid:JAIX71,
name:Chromium, glucose intolerance and diabetes. [J Am Coll Nutr. 1998] -

Note that it appears to be seeing a conflict between two items with the same
name. If their URLs are also identical, why cant it just merge them?

This produced a log file too big for Notepad to open, even though I cleared
the logfile first. It also kept the icon from being able to open the Xmarks
user interface window for those several minutes, and now has apparantly
started another synchronization attempt with a high page fault rate.

I found the conflicting item on the computer that syncs correctly, created a new bookmark for it in another folder, then deleted the original bookmark. I then cleared the logfile, asked for a download, then walked away for about half an hour for breakfast; when I came back, a successful automatic sync had happened.

It looks like part of the problem was that the synchronization attempts were getting far enough to add some new items on the computer with the problem, at least those near the start of the folder list on the server, but not far enough to delete a significant number of the old ones.

Suggestions for a more permanent fix:

1. If there are duplicate nids for an item with both the name and the URL matching, put up a message window asking the user if it's OK to delete the local one; if the user approves, this is equivalent to downloading just that item from the server and replacing the old one. This loses the local item's history, but since the two items are otherwise equivalent, most users would approve.

2. In order to handle similar conflicts for items not quite so equivalent, either allow the user to give the local item a new nid, or move it to a different folder, or at least the ability to look up the entire folder path to the item given the nid from the error message.

3. If you prefer, just modify the error messages in the log file to include the entire folder path of the item the error is about, but make sure that users can still see the relevant part of the logfile even when the logfile is too big to open in Notepad.

I don't think I mentioned that a day or two ago, I walked away from my laptop for an hour or two, and when I came back, it had synchronized successfully. Therefore, all three computers are synchronized again for now; we'll see how long that lasts.

I’m undecided

this answers the question

Add a comment This answers the question

Reply to Rick Turek's question

(Some HTML allowed)

Company participation

The mood in here

Products & Services

This topic is tagged

Related topics in Xmarks

XmarksException [source: internal, id: -50]