MS Nav 2017 + LS Nav replication errors

navit

Hello,

hope posting in the right forum.

We have a MS Nav 2017 implemented a year ago. It consist of Central Server/database and several remote Servers/databases. The implementer has included LS Nav to serve data replication between servers. Unfortunately we have found that very often (daily) there are a "lost" document ( documents that were marked as replicated in the source, but missing in the destination) , after some digging has been found that LS did not correctly replicate the data.
At the receiver side document come with missing or changed data ( most often number of items being ordered or similar) which caused LS service not to process documents . The implementer explained this problem is something common to LS and LS cannot handle it so errors must be fixed by editing counters and changing values in the data via NAV Dev enviroment.

However I can't believe LS Nav was made to work this way. I tried contacting LS , but coudn't find support line. Could someone give me advice how to troubleshoot the problem ?

Thank you in advance

gvolkov

There is a similar post i just replied to few minutes ago. There are basically a few troubleshooting steps based on your environment, setup and circumstances. Your biggest friend in this process is DD Job Monitor. It should definitely provide you a clue which will lead you to a solution. You also want to narrow down on the problem by replicating in small chunks.

navit

Thank you, we use DD Job Monitor . But it useless(or maybe we don't use it properly) . It only shows if there is communication problem. In our case, communications are OK, DD Job Monitor shows transfers are OK no errors ( on the both sides - transmitting and receiving , but actually some data is missing or altered. I am just too disappointed LS Nav has no ability (as far as I know) to do even simpliest error detection.

kriki

[Topic moved from 'NAV/Navision Classic Client' forum to 'NAV Three Tier' forum]