4.18  Resolving Errors

When an error requiring your attention occurs, the app displays an error dialog.  At the bottom left is a button with a life-preserver icon.  Clicking this button generates an email message including additional technical information, addressed to our Support team.  If you would like our support regarding an error, don’t take a screenshot.  Click the life-preserver icon.

Whenever the app or one of its Workers generates an error, it is stored on your Macintosh User Account.  You can re-view past errors by clicking in the application menu > Logs and then clicking the Errors tab.  Errors displayed in this manner likewise have a button with a life-preserver icon.  Again, don’t take a screenshot.  Click the life-preserver icon.

Although the apps generally provides quite informative error dialogs, there are a few that could benefit from further explanation.  The remained of this page does that

       Topics on this Page

4.18.1  Error 144770 : Broken Login Item

Why Error 144770 Occurs

Our older app, Bookdog, came with an accessory named Bookwatchdog, which ran in the background and can conflict with Smarky, Synkmark, Markster or BookMacster.  Therefore, these apps ask macOS for your Login Items, so it can see if Bookwatchdog is a Login Item, and if so remove it.  Unfortunately, if the application required for any of your Login Items (not just Bookwatchdog) is missing, macOS will give the app an incomplete report.  The app then asks for your help to fix it.  To get your help, the app presents Broken Login Item Error 14470.  Yes, it’s annoying, but it’s something that you should fix sooner or later anyhow.  We’re just being helpful.

Steps to Fix Error 144770

The instructions here look ominous, but following them will probably be the easiest thing you do all day.  Here we go…

4.18.2  Error 144762 : Broken Login Item

Why Error 144762 Occurs

Our older app, Bookdog, came with an accessory named Bookwatchdog, which ran in the background and can conflict with Smarky, Synkmark, Markster or BookMacster.  Therefore, these apps ask macOS for your Login Items, so it can see if Bookwatchdog is a Login Item, and if so remove it.  Error 144762 indicates that Smarky, Synkmark, Markster or BookMacster requested that macOS remove Bookdog’s old Bookwatchdog from your Login Items, and macOS said “No” and failed for some reason.

Steps to Fix Error 144762

To solve the problem, since this removal only needs to be done once, do it manually…

4.18.3  Error 3040 : Too Long to Install Browser Extension

Why Error 3040 Occurs

Synkmark, Markster or BookMacster install extensions into some web browsers in order to perform several functions.  You must approve the installation by clicking a button in a popover which appears in the web browser.

Usually it works, but if you don’t notice and/or respond to the popover, or if the browser didn’t display the dialog because they are occupied with some other task, Error 264948 will appear in Synkmark, Markster or BookMacster.

Steps to Fix the Problem

Although Synkmark, Markster or BookMacster will retry the installation later when needed, it is often less frustrating, and thus recommended, if you’ve read this far, to fix the problem immediately, in a manual mode where you have more control.  To do that,

In the end you should see happy green-circled checkmark(s) as shown above.

4.18.4  Errors 3045 : Slow/No Response from Browser during Import/Export

These errors can only occur while the affected browser is running, but our app may launch the browser, as explained here.

4.18.5  Errors 3011, 3012 : Import or Export Safe Sync Limit Exceeded

Why Error 3011 or 3012 Occurs

A disadvantage of syncing data sets such as bookmarks is that an inadvertent change in one data set will be automatically copied to all the others.  The Safe Sync Limit in Smarky, Synkmark and BookMacster prevents that in many cases..  If an Import Safe Sync Limit is tripped, Error 3011 occurs, and if an Export Safe Sync Limit is tripped, Error 3012 occurs.  In either case, syncing is paused in order to prevent the error from recurring.  You at least need to restore sync in your data, and resume syncing.

To resolve Error 3011 or 3012,

4.18.6  Error 3015 : Sync Fight

Why Error 3015 Occurs

After an Export operation to a Client, Smarky, Synkmark, or BookMacster compares the changes it exported to the changes exported in prior exports.  If the app finds that it is exporting the the same changes repeatedly, with no other changes, it is apparent that something must be un-changing what the app changed.  In other words, there’s a fight!  Since the app in turn detects the un-change and syncs again, exporting again, this could go on forever.

Instead, the app disables syncing by pauses syncing or, equivalently, disables Agents, and displays Error 3015 to you.

Steps to Fix the Problem

If you would rather try to resolve the problem yourself, you need to find out what change(s) are being fought over.  You can see this by examining your recent Sync Logs.

In the following example, by clicking the popup menu you can see that there were three recent Exports interspersed with two Imports to Safari…

After a fight over Safari bookmarks is reported, if you click any of the recent Export logs for the errant Client (Safari in this example) you should see exactly the same changes.  Here is an example…

In this example, the bookmark Ant is being moved up to position 0, and bookmark Bird is being moved down to position 1.  That is, BookMacster, say is putting them into alphabetical order.

Conversely, if you click any of the recent Import logs for the errant Client (Safari in this example) you should again see the same changes in each log, but the opposite of what changed during the exports.  Continuing the same example…

In this example, the bookmark Ant is being moved down to position 1, and bookmark Bird is being moved up to position 0.  That is, some other app or service is moving them back, out of alphabetical order.

4.18.7  Errors Exporting to Non-Running Firefox

When Synkmark, Markster or BookMacster needs to export to Firefox while Firefox is not running, or you ask Smarky to export to Firefox even if it is running, the app accesses Firefox’ bookmarks database file directly.  In preparation for the actual export, it opens the database, verifies the expected tables, and performs a checkpoint operation, to flush through any changes pending by other applications.  These are simple operations, and if they fail, this almost always means that the database file is corrupt.  Here is what you need to do.