Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

Historical queries

  • Last UpdatedApr 24, 2025
  • 1 minute read

Windows updates may create incorrect assembly references that affect some historical queries.

Example of a Failed Query

After installing KB5013626, the select Utilities.dbo.GetMySystemID() query may fail with a message stating, in part, "Assembly in host store has a different signature than assembly in GAC".

To resolve incorrect assembly references in historical queries

  1. On the desktop, double-click the Windows PowerShell for DNA shortcut.

    Windows PowerShell for DNA opens.

  2. Execute the following command:

    Publish-DataTierApplications.ps1 -Upgrade -ServerName <server name> -Database Utilities

    Note: You can safely ignore messages that begin as follows: ALTER ASSEMBLY failed because the source assembly is, according to MVID, identical to an assembly that is already registered under the name....