Unable To Perform 39;bidirectional 39; Sync On A Feature Service And Changed To 39;download 39; Sync Only
Sunta Bivings
I am getting error ": Unable to perform bidirectional sync of the geodatabase. The sync direction has been changed to downloadsync. None of the feature layers or tables referencing the geodatabase have the capabilities of create, update or delete required for bidirectional sync. path: /private/var/mobile/Containers/Data/Application/979D7CE0-7D48-4DC9-8FDF-"
unable to perform 39;bidirectional 39; sync on a feature service and changed to 39;download 39; sync only
Download https://lahipconfmu.blogspot.com/?wp=2x7Av0
Is it possible that in the Test environment when the replicas were generated it was defined as download only and not bidirectional? When a download only replica is created it will not create a version, but is associated to default (or whatever version the source service is generated from). This is certainly what you would see in this case, and also trying to do a bidirectional sync would fail.
As I said in my previous post, to me it looks like something weird happened when the replicas were generated and they are not bidirectional replicas. I would try and sync just the one pointing to the child version. However, it is possible that even that one is 'broken.' There are issues with versioned sync and once a replica fails it will never work again.
Use bidirectional replication for situations where data on different nodes is operationally segregated. In other words, suppose that you have a data element changed by an application operating on node A, and that node A performs bidirectional replication with node B. That data element on node A is never changed by any application operating on node B.
Data Sync uses a hub and spoke topology to synchronize data. You define one of the databases in the sync group as the hub database. The rest of the databases are member databases. Sync occurs only between the hub and individual members.
The new private link feature allows you to choose a service managed private endpoint to establish a secure connection between the sync service and your member/hub databases during the data synchronization process. A service managed private endpoint is a private IP address within a specific virtual network and subnet. Within Data Sync, the service managed private endpoint is created by Microsoft and is exclusively used by the Data Sync service for a given sync operation.
In order to use Data Sync private link, both the member and hub databases must be hosted in Azure (same or different regions), in the same cloud type (for example, both in public cloud or both in government cloud). Additionally, to use private link, Microsoft.Network resource providers must be Registered for the subscriptions that host the hub and member servers. Lastly, you must manually approve the private link for Data Sync during the sync configuration, within the "Private endpoint connections" section in the Azure portal or through PowerShell. For more information on how to approve the private link, see Set up SQL Data Sync. Once you approve the service managed private endpoint, all communication between the sync service and the member/hub databases happen over the private link. Existing sync groups can be updated to have this feature enabled.
There may be up to 30 endpoints in a single sync group if there is only one sync group. If there is more than one sync group, the total number of endpoints across all sync groups cannot exceed 30. If a database belongs to multiple sync groups, it is counted as multiple endpoints, not one.
When the sync group is established, the Data Sync service needs to connect to the hub database. When establishing the sync group, the Azure SQL server must have the following configuration in its Firewalls and virtual networks settings:
If you synchronize data within the same region, SQL Data Sync doesn't store/process customer data outside that region in which the service instance is deployed. If you synchronize data across different regions, SQL Data Sync replicates customer data to the paired regions.
The Dynamics 365 bring your own database feature lets administrators export data entities from the application into their own Microsoft Azure SQL database. Data Sync can be used to sync this data into other databases if data is exported using incremental push (full push isn't supported) and enable triggers in target database is set to yes.
Before creating your synced table, there is a setting that allows you to choose who can edit source records. Click Change below the Edit source records toggle to make adjustments based on your needs. This option is specific to the two-way sync feature.
Q: Getting error 'logon failure 0xc000006d' in Windows Shares. Why?
A: In Ver 11.8.3 we deployed new implementation of 'Windows Shares (SMB)' file system.
This is native wire-level implementation of SMB-1 and SMB-2 (but not SMB-3) protocols, its advantages:
(1) It stores Share credentials in GoodSync Account Manager (Server Accounts).
(2) So credentials can be synced between computers using Account Sync.
(3) Credentials would not get stuck in Windows innards, like they do with Windows SMB client.
(4) Our implementations has timeouts on all file operations and will never freeze (unlike Windows client).However there is some work to be done:
Since GS cannot get credentials out of Windows credential store, you would need to enter them anew.
(1) When you get error 'logon failure 0xc000006d' or similar, click 'Change Folder' to go into Browse dialog.
(2) In Browse dialog drill down to your folder, entering its credentials (UserId and Password) on the way.
(3) You enter credentials only once, as they are memorized in GoodSync Account Manager (Server Accounts).You can also go back to the old Windows-based SMB client (say, if you have SMB-3 server):
Tools -> Program Options: Use New SMB implementation: uncheck it and restart GoodSync Q: How to replace SMB (Windows Shares) or AFP (Mac Shares) on NAS with GoodSync Connect?
A: Indeed, SMB has become harder to use, after it was attacked by ransomware and SMB v1 was turned off.
AFP has been discontinued by Apple, and they now tell users to switch to SMB.
GoodSync Connect can replace both SMB and AFP, on Windows, on Mac and on NAS.
GoodSync Connect is global, it works across the Internet, it is not limited to local network.HOWTO: Install GoodSync onto your NAS using one of GoodSync NAS installers.
Configure GoodSync for NAS by going to its Web UI at -nas-ip-address:11000
NAS will appear in GoodSync Connect file system.
Explore it with GoodSync Explorer or sync with GoodSync. Q: How to make my GoodSync Computer (server) visible to my GoodSync client?
A: For computer to appear in GoodSync Connect and become visible to GoodSync clients, you must:
Enroll computer into your GoodSync Account, using GoodSync Account Setup.
Computer must be Serving Files -- an option in GoodSync Account Setup.
Computer must be ON and NOT sleeping.
Computer must be online and connected to Internet.
Computer must be able to connect to server mediator.goodsync.com, gs-server logs show what happens.
Q: Can GoodSync synchronize data files of Outlook, Outlook Express, QuickBooks, Quicken, etc?
A: All these applications (Outlook, Outlook Express, Windows Mail, Thunderbird, QuickBooks, Quicken, ACT!) store data in a database. So many (hundreds, even thousands) logical units (such as individual email, contact, or calendar entry) will be stuffed into a single database file.
GoodSync does not understand internal structure of all these database files. So GoodSync can sync the whole database files, but not individual logical units stored inside these files.
Therefore GoodSync cannot sync two database files on Left and Right if both file were modified. Not seeing the internal structure of these files GoodSync will declare a conflict, as it sees two files both of which have changed.
But if database files have changed only on one side then GoodSync can sync just fine.
These are the scenarios in which GoodSync can synchronize database files that it cannot understand:
* 1-way syncs or backups:
if only one side of the job changes, GoodSync can always propagate these changes to the other side.
* 2-way syncs where each sync goes only one way:
even 2-way sync are possible if each of the syncs goes 1-way:
you have folders A and B, possibly on different computers,
(a) you work on folder A and you do not touch folder B (do not even start your application on side B, because applications update the database files even you did not change nothing).
(b) once you are done with changes in A, you close your application, and you call GoodSync and sync side A to side B propagating change from side A to side B.
(c) then your start your application on side B and work on side B and do not start the application on side A until you are done with the changes in side B.
(d) once you are done with changes on side B, you call GoodSync and sync back to side A.
... and so on.
Q: So how GoodSync decides whether file has changed and it must be synced?
A: If either file modification time or its size has changed then GoodSync assumes that file has changed.
GoodSync propagates the changes that it so found from the folder where they were found to the folder on the other side of the job.
Q: How to sync the same files that have different timestamps?
A: Normally GoodSync considers files to be the same if their lengths are the same and their file modification times are the same. But if you are sure that your files are the same even though their file times are different, you can make file times the same too, without copying the files:
- Perform Analyze
- Select Other -> SameLength DiffTime to view file with same length and different file modification time,
- Right-click middle of the Top node in the tree and select Copy Time L to R or R to L .
- Sync: only file modification time will be copied in the selected direction, not file bodies.