Hello. I'm having the exact same problem, just no sollution.

Used to work just fine, but since the recent update (plugin 84) every chrome related stuff is negative. Been trying reinstalling plugins even Chrome and Bookmacster. It tells me to make my profile in Chrome active, but i do not have more than one profile.

Im on ML 10.8.3 - if you need any other info let me know.

Any help is appreciated

Our Chrome plugin has not been working properly in Mac OS X 10.7 in recent BookMacster updates.  Please Activate BookMacster, click in the menu "Check for Update", and update to BookMacster version 1.13.5, published a few minutes ago.  Upon launching, it will prompt you to update the plugin to version 83, which has the problem fixed.

Hi Jerry

> Try to re-test (in Manage Browser Add-Ons) the Chrome Add-On) after this fails.  The Test and the Export use this same mechanism.

Test fails.  Window says extension 104 is OK and plug 82 is OK.

> Also, try to quit Chrome, then Export while Chrome is quit.

No change.  Chrome launches without me launching it, then BookMacster tells me it must be quit.  I quit it, BookMacster tries to relaunch Chrome then I get the usual "Port Send Failed" error message as has always been the case.

> Do you (still) have multiple profiles existing in Chrome

I've never had more than one user in Chrome.

I've also updated everything to latest version as prompted.

What now ?  Perhaps my loopback and/or localhost network connectivity is busted somehow - it's the only thing I can think of .... perhaps BookMacster itself can't talk to the plugin on its internal network port for some reason ?

Hi Jerry,

I have BookMacster recognising Chrome now (I created a bookmark in Chrome to create the missing Bookmarks file, then deleted it).  However I can't export any Bookmarks to Chrome at all, I keep receiving this error :-

______________ SNIP ______________

Please insert any additional information regarding what happened that might help us to investigate this problem:



BookMacster 1.13.1 (1.13.1)
Mac OS X version = 10.7.5
Architecture: Intel

NSError 0x107c717d0
***     code: 694812
***   domain: com.sheepsystems.BookMacster
*** userInfo:
   **Key: Method Name
   Value: -[Extore exportJsonViaIpcForOperation:]
   **Key: Localized Title
   Value: Export failed
   **Key: Timestamp
   Value: 2013-02-01 14:03:06
   **Key: NSLocalizedDescription
   Value: Port send failed
   **Key: Clientoid
   Value: Chrome||thisUser||||
   **Key: dontStopOthersIfError
   Value: 1
   **Key: SSYOperationGroup
   Value: Export01(1)
   **Key: Client's filePath
   Value: /Users/hugh.spencer/Library/Application Support/Google/Chrome/Default/Bookmarks
   **Key: CFBundleVersion
   Value: 1.13.1
   **Key: NSUnderlyingError
   Value:    NSError 0x10a94af40
   ***     code: 653041
   ***   domain: SSYInterappClientErrorDomain
   *** userInfo:
      **Key: Tx Header Byte
      Value: e
      **Key: Port Name
      Value: com.sheepsystems.BookMacster.ExtoreChrome.ToClient
      **Key: Tx Timeout (secs)
      Value: 0.5
      **Key: Rx Timeout (secs)
      Value: 15
      **Key: Tx Data Byte Count
      Value: 38664
      **Key: NSLocalizedDescription
      Value: Interapp messaging error : Server port (com.sheepsystems.BookMacster.ExtoreChrome.ToClient) not found

______________ SNIP ______________

Going to "Manage Browser Add-Ons" in BookMacster tells me that the Chrome extension and NPAPI plug-in are all OK but pressing "Test" returns "No response from Chrome add-on!".  Looks to me like BookMacster can't communicate with Chrome for some reason.

What should I do next to resolve this issue ?

Hi,

My installation of BookMacster isn't detecting my clients properly.  I have Safari and Google Chrome installed perfectly happily, but BookMacster won't detect my Chrome install at all, and as such can't be used to import or export bookmarks to and from Chrome.  This means BookMacster can only manage bookmarks in Safari, rendering it fairly pointless for my uses.

What can I do to make BookMacster recognise my Chrome installation ?  Everything is in the default places you'd expect.