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

Resolving Large Dump Logs from SQL Server 2022 PolyBase and Payout Posting Issues in Webgility Desktop

This article helps Webgility Desktop users resolve two common issues encountered when using Webgility Desktop with SQL Server 2022: excessively large dump log files generated during SQL Server installation, and failed payout postings after re-downloading order data. It explains how these problems are linked to the optional PolyBase feature and inconsistencies during order re-import operations, and provides guidance to address them effectively.

Issue Summary

  • Large Dump Logs: PolyBase generates abnormal dump logs during SQL Server 2022 setup, consuming significant disk space (over 300 GB in some cases).

  • Payout Posting Failures: Occur when an order’s data is partially re-downloaded or becomes inconsistent, especially during refund/payout operations.

Resolution Steps

1. Preventing Large Dump Log Files During SQL Server Installation

Action: Disable the PolyBase feature during SQL Server 2022 installation.

Steps:

  • Launch the SQL Server 2022 Installer.

  • Navigate to the Feature Selection screen.

  • Uncheck PolyBase Query Service for External Data.

  • Continue with the installation.

Result: The SQL Server installation completes without generating large and unnecessary dump log files, preserving disk space and improving system performance.

2. Fixing Payout Posting Failures in Webgility Desktop

  • Confirm and Identify Missing Orders

    • Log in to the Shopify account.

    • Check the Shopify Order History for the specified missing date range.

    • In Webgility Desktop, review which orders:

      • Failed to sync.

      • Failed to post to QuickBooks.

  • Download Orders from the Back Date

    • In Webgility, manually download Shopify orders for the missing date range.

    • Important: Use the Unsync feature before re-downloading any already synced orders to avoid duplicate entries in QuickBooks.

  • Check for Duplicate Orders in QuickBooks

    • In QuickBooks, search for recent transactions or sales receipts.

    • Identify any duplicates using order numbers, transaction IDs, or reference fields.

  • Investigate the Payout Posting Error

    • Attempt to post the Shopify payout from Webgility Desktop.

    • If you see the error “Order has already been posted,” this indicates:

      • A duplicate transaction exists.

      • The order was already posted in QuickBooks.

  • Delete Duplicate Transactions

    • In QuickBooks, find the duplicate transaction tied to the payout.

    • Delete the duplicate carefully, ensuring the original transaction remains.

    • Confirm that the order-to-payout mapping is preserved.

  • Re-Post the Shopify Payout

    • Retry the payout posting from Webgility Desktop.

    • Verify that the payout posts successfully without errors.

    • Review the posted payout and linked orders in both Shopify and QuickBooks.

Post-Incident Best Practices

  • For SQL Server: Only install PolyBase if required for specific external data integrations. Monitor dump log directory for abnormal growth if PolyBase is enabled.

  • For Webgility Desktop: Always verify order data accuracy after performing latest data downloads.

Status

This issue has been resolved through proper configuration and order re-import procedures.