Kenny

Hey Issam The first thing I noticed is that your final command "..\bin\symadmin" --engine interm 001 open-registration web 002 is missing a hyphen between interm and 001, "interm-001". I don't know if this is a typo on support or if this is the actual command you used. If it is the command you used, add the hypen and try the command again. Another thing to note is, where are you attempting to send that command from? This command should be sent from your Web node location. If neither of these fixes...

Hey Raj The first thing I noticed is that your final command "..\bin\symadmin" --engine interm 001 open-registration web 002 is missing a hyphen between interm and 001, "interm-001". I don't know if this is a typo on support or if this is the actual command you used. If it is the command you used, add the hypen and try the command again. Another thing to note is, where are you attempting to send that command from? This command should be sent from your Web node location. If neither of these fixes...

Hey Nixon There are 2 ways to achieve this easily enough. The first would be to add "SYNC_ON_INCOMING_BATCH"=1, to your trigger on the CORP node. This will cause the CORP node to sync the STORE nodes when any STORE pushes an update to CORP. Be careful turning this on, because an update loop is possible. The second would be to create a new group link from STORE_TO_STORE (source_node_group_id, target_node_group_id, data_event_action) values ('store', 'store', 'P'); Check out the documentation for more...

Thanks for the additional information Wayne. The first thing you can do is update your Symmetric version to 3.8.31. Then, in order to use file staging in a clustered envirnoment, you will need to setup a shared drive and set cluster.lock.enabled to true. Hope this helps

Thanks for the additional information Wayne. The first thing you can do is update your Symmetric version to 3.8.31. Then, in order to use file staging in a clustered envirnoment, you will need to setup a shared drive and set cluster.lock.enabled to enabled. Hope this helps

Hey Wayne Can you give us some more information on your setup? Are you in a clustered environment?

Hey Dellph and Shan Can either of you post the full stack trace of the error and a few more details about your setup? I would, also, reccomend in the meantime upgrading to the latest version on SymmetricDS (currently 3.8.29) and see if this fixes your issue. I believe that this issue may have been resolved in a subsquent version of SymmetricDS. Thanks Kenny