Hub/spoke same name?

[Mark Stuller]

Hello

We received this error today from a spoke that had just the day before completed (successfully) that spoke's initial sync. It seems curious, but thought I'd run this by the community.

Thanks, Mark

Nov 02, 2016 1:43:51 PM com.prosc.mirror.config.server.SyncServer$3 call
SEVERE: Sync between filemaker8.oda.state.or.us / BeFoodSafe5 (FileMaker Server) and bcripe iPad BeFoodSafe( username 'developer', running Go_iPad 15.0.2 on 70.57.121.30, ping time: 558 ms, machine name: 'bcripe' )
Last sync failed: com.prosc.sync.AbortException: The hub database has the same identifier as one of the spokes: '2'. Please get a new offline spoke database for syncing, and then try again.

[Jesse Barnum]

Hey Mark - I responded to this in our issue system.

[caryd12]

I'm having this same issue today with one of my remote workers.  The sync worked a couple of hours ago and now is giving this exact same error message.

[Jesse Barnum]

What version of MirrorSync are you running?

[caryd12]

3.17, build 9239

[Jesse Barnum]

Can you send that particular worker a new offline database? The problem should not reoccur with a new offline file.

[caryd12]

I suppose so, however I will have to recover the work he's done.  I was hoping for a fix that didn't involve downloading a new copy of the file.