CFMessagePortCreateLocal(): failed to name Mach port

• Andy Lee CFMessagePortCreateLocal(): failed to name Mach port Jun 03 2005, 17:03
  Anybody else seeing messages like this in their logs?
  
  2005-06-03 10:18:56.256 AppKiDo[1488] CFLog (0): CFMessagePort:
  bootstrap_register(): failed 1103 (0x44f), port = 0x3f03, name =
  'com.digitalspokes.AppKiDo.ServiceProvider'
  See /usr/include/servers/bootstrap_defs.h for the error codes.
  2005-06-03 10:18:56.273 AppKiDo[1488] CFLog (99):
  CFMessagePortCreateLocal(): failed to name Mach port
  (com.digitalspokes.AppKiDo.ServiceProvider)
  2005-06-03 10:18:56.455 AppKiDo[1488] Trouble registering connection
  CPNoteBook AppKiDo Channel.
  
  The last line started appearing after I installed Circus Ponies
  Notebook.  The earlier lines appeared later -- I don't remember if it
  was when I upgraded to Tiger.
  
  --Andy
• Chris Parker Re: CFMessagePortCreateLocal(): failed to name Mach port Jun 03 2005, 18:00
  Hi Andy,
  
  On Jun 3, 2005, at 8:03 AM, Andy Lee wrote:
  
  

  > Anybody else seeing messages like this in their logs?
  >
  >
  > 2005-06-03 10:18:56.256 AppKiDo[1488] CFLog (0): CFMessagePort:
  > bootstrap_register(): failed 1103 (0x44f), port = 0x3f03, name =
  > 'com.digitalspokes.AppKiDo.ServiceProvider'
  > See /usr/include/servers/bootstrap_defs.h for the error codes.
  > 2005-06-03 10:18:56.273 AppKiDo[1488] CFLog (99):
  > CFMessagePortCreateLocal(): failed to name Mach port
  > (com.digitalspokes.AppKiDo.ServiceProvider)
  > 2005-06-03 10:18:56.455 AppKiDo[1488] Trouble registering
  > connection CPNoteBook AppKiDo Channel.
  >
  >
  > The last line started appearing after I installed Circus Ponies
  > Notebook.  The earlier lines appeared later -- I don't remember if
  > it was when I upgraded to Tiger.
  

  
  This condition existed in Panther, we just weren't logging it. You
  wouldn't happen to have a second instance of the AppKiDo application
  running?
  
  The first instance becomes the service provider - the second instance
  comes along and tries to register to provide the same service, but
  can't because the first is already offering it. It's the second
  instance that's doing the logging.
  
  Although now that I'm reading your message again, it looks like
  Circus Ponies Notebook has some kind of AppKiDo "channel" - perhaps
  it's trying to register also...?
  
  .chris
  
  --
  Chris Parker
  Cocoa Frameworks Engineer
  Apple Computer, Inc.
• Andy Lee Re: CFMessagePortCreateLocal(): failed to name Mach port Jun 03 2005, 21:21
  On Jun 3, 2005, at 12:00 PM, Chris Parker wrote:
  

  > This condition existed in Panther, we just weren't logging it. You
  > wouldn't happen to have a second instance of the AppKiDo
  > application running?
  

  
  As a matter of fact I do.  I'm the developer of AppKiDo, so I have
  one copy running for my own use, and the other that I'm testing and
  debugging.
  
  

  > The first instance becomes the service provider - the second
  > instance comes along and tries to register to provide the same
  > service, but can't because the first is already offering it. It's
  > the second instance that's doing the logging.
  

  
  Does this mean the error message will appear when I try to run two
  instances of *anything*?
  
  

  > Although now that I'm reading your message again, it looks like
  > Circus Ponies Notebook has some kind of AppKiDo "channel" - perhaps
  > it's trying to register also...?
  

  
  I think I'm going to have to ask Circus Ponies about that.
  
  Thanks for shedding some light!
  
  --Andy