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

How to Resolve “Database 'UnifyDB' Already Exists” Error in Webgility Desktop

This article helps Webgility Desktop users troubleshoot and resolve the “Database 'UnifyDB' already exists” error encountered when logging in. This issue typically arises from database corruption or SQL Server conflicts. The guide provides steps to restore access to Webgility Desktop and ensure normal order processing.

Causes of Issues

  • Corruption in the UnifyDB SQL database

  • Duplicate or conflicting entries during login

  • Previous failed installation or restoration attempts

Step-by-Step Instructions

1. Confirm the Error

  • Attempt to log in to Webgility Desktop.

  • Note the exact error message: “Database 'UnifyDB' already exists.”

2. Assess Database Integrity

  • Open SQL Server Management Studio (SSMS).

  • Connect to the correct SQL Server instance.

  • Locate the UnifyDB database.

  • Review its status (e.g., SUSPECT, RECOVERY_PENDING) to confirm corruption.

3. Back Up Existing Data (If Accessible)

  • If the database opens, right-click UnifyDB > Tasks > Back Up.

  • Save the backup to a safe location for recovery purposes.

4. Remove or Rename the Database

  • In SSMS, right-click UnifyDB:

    • Choose Delete, or

    • Choose Rename (e.g., UnifyDB_Old) if you plan to keep it for analysis.

5. Create a New Database via Webgility

  • Launch Webgility Desktop.

  • The software will detect the missing database and prompt for creation.

  • Follow the on-screen instructions to recreate a fresh UnifyDB.

6. Restart SQL Services (If Required)

  • Press Win + R, type services.msc, and press Enter.

  • Locate SQL Server (InstanceName).

  • Right-click > Restart to refresh services.

7. Verify Access to Webgility Desktop

  • Reopen Webgility Desktop.

  • Log in and confirm successful access.

  • Navigate to Orders and validate functionality.

8. Post Orders Manually (If Needed)

  • Go to Orders > Post Orders Manually.

  • Select and process any previously unposted orders.

Best Practices

  • Regularly back up your Webgility database.

  • Keep documentation of changes made to your SQL configuration.

  • Only delete the UnifyDB if all backup attempts fail or if advised by support.

Note:

If issues persist even after creating a new database, check the SQL Server configuration or consider restoring from a previous .bak backup if available.