Skip to content
  • There are no suggestions because the search field is empty.

Resolving Missing Stored Procedures (e.g., SP_GET_ORDER_COUNT) After Webgility Desktop Upgrade

This article helps Webgility Desktop users in resolving database connectivity issues in Webgility Desktop caused by missing stored procedures such (SP_GET_ORDER_COUNT) often resulting from incomplete application upgrades where database objects weren’t properly synchronized. It guides to run the Webgility-provided Database Upgrade and Unified Database Utility tools to restore the missing stored procedures and fix connectivity problems.

Overview

Missing stored procedures can cause application errors and disrupt database connections. Instead of manual database script updates, customers must run specific utilities provided within their Webgility installation folder that handle database object synchronization and upgrades automatically.

Symptoms

  • Errors such as:
    Could not find stored procedure 'SP_GET_ORDER_COUNT'

  • Unstable or failed database connections

  • Application errors referencing missing stored procedures or database calls

Root Cause

These issues occur because required stored procedures and database objects have not been installed or updated correctly. The fix requires running Webgility’s Database Upgrade and Unified Database Utility programs, which are designed to update and synchronize all necessary database components.

Resolution Workflow

1. Verify the Issue

  • Check application and SQL Server logs for missing stored procedure errors.

  • Confirm the specific stored procedure name causing the error.

2. Run the Webgility Database Upgrade Utility

  • Ask the customer to locate the Webgility installation folder, typically at:

    makefile
    CopyEdit
    C:\Program Files\Webgility\Webgility Desktop\

  • Inside this folder, locate the executable named WebgilityDBUpgrade.exe or similar.

  • Run this utility as Administrator by right-clicking and selecting Run as administrator.

  • The tool will detect missing or outdated database objects and upgrade them accordingly.

  • Wait for the process to complete and ensure no errors appear.

Help Center Reference:
To run the DB Upgrade utility, navigate to the Webgility installation directory, right-click on WebgilityDBUpgrade.exe, and select Run as administrator. Follow any on-screen prompts until completion.

3. Run the Unified Database Utility

  • From the same installation directory, find and run the Unified Database Utility application.

  • Run it as Administrator to synchronize stored procedures, functions, and schemas.

  • Monitor the output for success messages or errors.

4. Restart SQL Services

  • Once both utilities have run successfully, restart the SQL Server service to refresh database metadata.

  • This can be done through Services in Windows or via command prompt:

    arduino
    CopyEdit
    net stop MSSQLSERVER
    net start MSSQLSERVER

    (Replace MSSQLSERVER with the actual instance name if needed.)

5. Validate Resolution

  • Retry the previously failing application operations.

  • Confirm that the missing stored procedure errors no longer occur and that database connectivity is stable.