SmartViews LillyWorks connection - Can't load ProductionExecution "virtual" table schema

SmartViews LillyWorks connection - Can't load ProductionExecution "virtual" table schema



This error does not come from SmartViews, but rather from the web service request. The error in the HTTP message itself is the "real" error, which could be one of many (i.e. it does not have to be "Call frequency cannot be more often than every 5 minutes" like in this example).
    • Related Articles

    • SmartViews - Release Notes

      v462.2001 (8/9/2024) Fixed memory limitations and leaks when loading large amounts of data in a View Turned off automatic syncing upon opening/closing SmartViews when the DisableSync flag is true v462.2000 (7/22/2024) Fixed tracking of versions used ...
    • SmartViews - User Guide

      Prerequisites: Windows Server 2016-2022 Windows 10-11 SQL Server 2012R2-SQL 2019 SQL Server 2017 minimum Cumulative Update (CU) is 31 (14.0.3456.2) Visual 7x-10 .NET 4.6.2 if outgoing ports are blocked at the organization’s firewall, the following ...
    • SmartViews Error “The specified table does not exist [sv_Users]” - On Premise Installations

      SmartViews has an "On Premise" type of installation that allows customers to use a local SQL Server instead of the Azure cloud database.   Depending on the version they are on, they may experience this error after updating to later versions: “The ...
    • Sql Server LocalDB Installation for New SmartViews

      Installation Instructions As of version 462.1000, SmartViews uses LocalDB 2017 in place of the previous local cache. As such, LocalDB 2017 or later needs to be installed on the machine, and an important patch needs to be applied. LOCALDB 2019 ...
    • SmartViews - Error “The specified table does not exist [sv_Users]” - Azure Cloud Database

      Depending on the version of SmartViews a customer is on, they may experience this error after updating to later versions: “The specified table does not exist [sv_Users]” The following steps should be tried in order to solve the issue. Try logging in ...