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

Webgility Database Migration: Common Errors and How to Resolve Them

This article addresses common database-related errors encountered during Webgility Desktop installation or migration, including permission denials, failed SQL connections, and performance issues. It explains typical causes such as SQL Server misconfigurations and permission restrictions, and provides detailed step-by-step solutions to ensure a smooth migration and optimal performance.

Overview

When installing or migrating Webgility Desktop, users may encounter database-related errors such as:

  • "CREATE DATABASE permission denied in database 'master'"
  • Failed SQL connections
  • Performance degradation post-migration

These issues typically arise due to SQL Server misconfigurations, permission restrictions, or missing updates.

This article provides a complete step-by-step solution to resolve such issues and ensure seamless migration and optimized performance.

Common Symptoms

  • Webgility Desktop is unable to create a new database.
  • SQL Server fails to install during setup.
  • Existing database instance cannot be located.
  • The application becomes sluggish or unresponsive post-migration.

Root Cause

  • Insufficient permissions during SQL Server setup
  • SQL Server not properly installed
  • Webgility instance or services not configured correctly
  • Backup restoration not completed

Resolution Steps

Step 1: Manually Install SQL Server

If automatic installation fails:

  1. Download SQL Server 2022 Express from Microsoft
  2. Launch the installer
  3. Choose Custom Installation
  4. Set Instance Name as UNIFY (or UNIFYNEW if updating)
  5. Select Mixed Mode Authentication:
    • Username: sa
    • Password: Webgility2011
  6. Ensure services are set to Automatic Start

🔗 Refer to the full SQL Server Installation Guide (Insert actual link)

Step 2: Launch Webgility Desktop

  • If prompted with database configuration, proceed to the next step.

Step 3: Connect to an Existing SQL Server

  1. Choose: Connect Webgility database to an existing SQL Server
  2. Use dropdown: Browse for More (wait 2–3 minutes)
  3. Select your new SQL Server instance (e.g., YourPC\UNIFY)
  4. Enter credentials:
    • Username: sa
    • Password: Webgility2011
  5. Click Connect

Step 4: Restore the Database

  1. When prompted, browse to the .bak backup file from your previous setup
  2. Click Open and begin restore
  3. Wait for success confirmation

Step 5: Run the DB Upgrade Utility

  1. Close Webgility Desktop
  2. Go to: C:\Webgility\UnifyEnterprise
  3. Run: UnifyDBUpgrade.exe
  4. Wait for the success popup
  5. Reopen Webgility and verify data

Additional Recommendations

  • Disable unnecessary Webgility notifications for better speed
  • Keep Windows OS up to date
  • Restart SQL services if the app hangs:
    • Go to Windows Services
    • Restart SQL Server (UNIFY) and SQL Server Browser
  • Ensure at least 20% free space on the C: drive