synchronize replica failed "workspace is not connected"

[AlexMahrou]

My Environment: ArcGIS server 10.03
ArcMap 10.03

I've published a Geodata service from the cloud for replication. I successfully created a two-way replica on my office computer ArcSDE/PostGres from the geodata service. When I edit existing features and try to synchronize, I get the error "synchronize replica failed  "workspace is not connected"". Does this has something to do with the fact that my Parent Geodatabase on the server is in ArcSDE/SQLExpress and my Child gdb is in ArcSDE/Postgresql?

Both are using the same service pack... I'm at my wit's end at this point.

[HeatherMcCracken]

Are you connected as the owner of the replica on both geodatabases?
I'm wondering if you are running into a bug that will be addressed in 10sp5 where synchronization fails with "The workspace is not connected" when you try to synchronize as the admin/SDE user.

NIM080354: Synchronization error "The workspace is not connected."

The workaround is to connect as the replica owner. 

Can you look at replica manager for both the parent and child replica geodatabases, and tell me who the owner is on either side?
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/A_quick_tour_of_replica_management/002...

Thanks,
Heather

[AlexMahrou]

Office (local - child replica / postgresql/sde)
[ATTACH=CONFIG]14858[/ATTACH]

Cloud (parent replica / sqlexpress/sde)
[ATTACH=CONFIG]14859[/ATTACH]

Heather, I think that you may be on to something. If I'm exhibiting the behavior you describe, what should I do next?

[HeatherMcCracken]

What permissions does the ArcGISSoc user have on your SqlExpress geodatabase?
Can you try making it a Server Administrator (that way it'll be dbo)?  Since the replica is owned by dbo (your windows login must be a server admin), then I think this should sync.

Try it and let me know...
Thanks,
Heather

[AlexMahrou]

Hi Heather, everything is working now. But not with a Postgresql child replica-- I attempted to create a replica with a personal sde sqldatabase and everything worked; I was able to make geometric edits, synchronize, and propagate changes back to the parent via a geodata service. Therefore can we be safe in assuming the issue is on the child side with Postgresql? I'm okay with this temp fix, however I'd like to have a more robust rdbms hosting my child replica. I'd be happy to grant you access for you to create a connection and debug a postgres child replica on your end if you like (I'll pm you the connection details).

[HeatherMcCracken]

There is nothing inherently wrong with having a Postgresql database as the child (or any DBMS flavor) - Replication was built on top of the geodatabase, and can therefore seemlessly support replicating between any geodatabase, no matter their underlying DBMS.

That said - i think you're right - the issue is something to do with the Child, since when you swapped it out all is well.
Can you confirm that the connection you were using to sync the replica on the Postgres Child was the same as the replica owner.  From your earlier image - i believe SDE was the owner on Postgres.  Can you confirm you were connected as the SDE user when you are syncing? 

Thanks,
Heather

[AlexMahrou]

Heather, thanks for your help up to this point!

Yes I am confirming that I was connected as the sde user in PostGresql, what's next? I tried to look up the issue number that your referenced in the upcoming sp5 release announcement but it isn't present in the list. http://downloads2.esri.com/support/downloads/other_/185410.0_SP5_Announcement.pdf

[AlexMahrou]

Now I just tried to create new features in the sqlexpress child replica and I'm getting the error "synchronize replica failed" version not found. I went to my temp directory on the client machine, and nothing was written to the replicalog.dat, also a zip file containing an xml was created. I check the server log and there are no warnings or errors either. This was just working yesterday!

Perhaps something is going on with my virtual directories and security? I feel as though the zip payload that's being generated on the child side is getting blocked somehow on the parent side, but I have no way of telling how or why.