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

Resolving UPS Error 25002 After Updating to UPS Auth 2.0 in Webgility Desktop

This article helps Webgility Desktop users resolve UPS error 25002 encountered during shipping label generation after updating to UPS Auth 2.0. It provides step-by-step guidance on reviewing shipping settings, reauthorizing UPS Direct and re-registering with UPS using existing credentials in Webgility Desktop.

Overview

This article provides step-by-step guidance to resolve UPS error 25002 encountered during shipping label generation after updating to UPS Auth 2.0. The resolution process includes reviewing shipping settings, reauthorizing UPS Direct, addressing DLL dependencies, and re-registering with UPS using existing credentials.

Prerequisites

  • Access to admin-level Webgility credentials
  • Updated UPS Auth 2.0 configuration
  • Communication line with both technical and Webgility teams if escalations are required

Understanding Error 25002

Error 25002 typically indicates authentication or communication issues with UPS services after system or middleware updates (common after UPS Auth 2.0 updates).

Step-by-Step Resolution Procedure

1. Verify Shipping Settings

  • Go to Webgility > Shipping > Shipping Settings
  • Confirm that all UPS-related settings and credentials reflect the current account configuration.

2. Reauthorize UPS Direct Integration

  • Navigate to Connections > Shipping > Shipping Settings.
  • Click Reauthorize and follow the prompts
  • Test connection after reauthorization. Attempt to generate a shipping label. If the error persists, continue.

3. Update the Relevant DLL File

  • Coordinate with the Webgility support team to identify and retrieve the latest DLL file related to UPS communication.
  • Replace the outdated DLL on the affected server/workstation, following change management processes.
  • Restart the Webgility application and attempt label generation again.

4. Create a New UPS Registration (With Existing Credentials)

  • In Webgility, Connection > Shipping > Shipping settings, select Register New UPS Account.
  • When prompted, use the existing account credentials (do not create a new UPS account; use the same UPS credentials as before).
  • Complete the registration wizard. This step often resets the integration handshake and resolves lingering auth issues.

5. Confirm Issue Resolution

  • Generate a test UPS shipping label.
  • Confirm that error 25002 no longer appears.