Who is this article for?

Users who encounter the issue when interacting with an Audit.

Application server access is required.

When opening an Audit, you may see the error message: "TypeStore found no IEntityType for the uid, {Guid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, Id=x, Mid=EntityType}". This article explains the cause of the error and how to resolve it.

1. Issue
2. Solution

1. Issue

When attempting to access an Audit, you may encounter the below error.

Your desktop application maintains a local copy of infrequently changing system data in its file %localappdata%\vision\[instance name]\LocalData\Vision.bak.

If the file in use was not built from the database that is currently in use (this may happen if a database is restored from another environment), then various IDs will be out of sync between the main and local data stores.

2. Solution

To resolve the issue, rebuild and redeploy the local database file:

1. Open 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 you are using an MSI package, it may be configured to download the latest database from the server on start. In this case, the package should not contain files in the Client\LocalData folder, or these may be used in preference to the downloaded files 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.