How to Troubleshoot Connection Issues Between Kala and Microsoft Navision / Business Central

This documentation section covers troubleshooting the synchronization of various data between Kala and your connected Microsoft Navision or Microsoft 365 Business Central system.

Once a connection has been established between Kala and Navision / Business Central, Kala’s servers will attempt to sync data both ways in a continuous interval of 7-12 minutes. After each synchronization attempt, you can find the latest synchronization log, showing both success and error messages, under Settings > Connections and Services > [Your Connected System].

In this section, each error message line starts with an indication of what type of transfer has failed. You should scroll down through the log and look for lines beginning with ERROR, followed by a descriptive word indicating which type of transfer the error relates to. Once you find a relevant error message line, scroll sideways to the end of the line, as this will often show the specific cause of the error.

For example, ERROR syncing workers means that this error message is related to a problem syncing employees between the systems.

Below, you will find a section for each type of content that Kala attempts to transfer to and from Navision / Business Central.

Troubleshooting the Transfer of Time Entries from Kala to Navision / Business Central

When Kala attempts to transfer time entries to Nav / BC, the system will, by default, try to write to a job journal.
Error messages related to this transfer start with: “ERROR Booking JobJournals”.

Relevant Error Messages Regarding Missing Time Entries in the Journal and Their Meaning

“The current permissions prevented the action. (Name of a permission set)”

This error message relates to the permissions Kala has within your Nav / BC setup. It most often appears when Kala is connected using OAuth, where an application has been created for Kala in Microsoft Active Directory.

Solution: Ensure the application has been assigned the necessary permission sets specified in this guide.
Depending on the additional modules in your Nav / BC setup, extra permissions may be required for Kala to write to the job journal.
If so, the specific missing permission set will be mentioned in the error message.
You must add the specified permissions to Kala’s application permission set within Active Directory.

“Exception has been thrown by the target of an invocation”

This error message typically means that the correct journal does not exist under the correct job journal type.

Solution: Ensure that under the job journal type SAGER, there is a journal named/numbered KALA.
Additionally, ensure that only one journal named KALA exists under the job journal type SAGER and any other job journal types.
Also, ensure that there is only one job journal type named SAGER.