Who is this article for?

Users of the desktop application.

Server Adminaccess is required to resolve the issue.

After starting the application, once it loads, you may encounter an "Synchronising the local cache has been attempted more than 11 times" error. This article explains why the error occurs and how to resolve it.

1. Issue
2. Solution

1. Issue

When you start the application, you see the error "Exception has been thrown by the target of an invocation".

Clicking the second message (TngException[Fatal]) shows the main error:  "Synchronising the local cache has been attempted more than 11 times. Please restart the application to try again".

This is because the client is connecting to the service fine and is attempting to sync its local cache with the main database, as is expected. However, the sync is not succeeding, so the client is retrying. The error occurs when the number of allowed retries has been exceeded.

This can be caused by the service timing out or by there being a large number of cacheable changes made since the last rebuild and deployment of the local database.

Be sure to understand whether this issue is affecting all users, or just some out of the users. 

2. Solution

If all users are affected:

1. Restart the service application pool (at the server).
2. Restart the Robot service.
3. Ask users to try connecting again.

If users still cannot connect, then:

1. Go to App Manager.
2. Rebuild the local database.
3. Redeploy the local database to users.
   If you are using ClickOnce to deploy the application, this happens automatically.
   If an MSI package is used:
   • It may be configured to download the latest local database from the server at start, in which case the problem should be resolved.
   • If it is not configured to download the local database from the server at start, the IT team will need to distribute the new file via their usual method.