Webgility Desktop: Resolving Database connection errors
This article helps Webgility Desktop users in analyzing root causes of database connection errors in Webgility Desktop. It covers common scenarios such as connectivity problems, incomplete or failed database upgrades, and network or SQL service interruptions that can prevent the application from properly accessing or initializing its SQL database.
Root Cause Analysis
This scenario typically involves:
- Database connectivity issues
- Incomplete or failed database upgrades
- Network or SQL service interruptions
These issues may prevent the Webgility application from accessing or initializing the SQL database properly.
Step-by-Step Resolution
1. Verify Network Services
a. Open Windows Services:
- Press Windows key and type Services
- Click on the Services application from search results
b. Restart SQL Services:
- Locate the SQL Server service for Webgility (e.g., SQL Server (UNIFY) or custom instance name)
- Right-click the SQL Server service and choose Restart
- Also restart the SQL Server Browser service the same way
2. Reconnect via Webgility Application
a. Launch Webgility Desktop
- Open the Webgility Desktop application after restarting services
b. Select Existing SQL Server
- When prompted to connect, choose Connect to an existing SQL Server
- In the Locate SQL Server drop-down, select the appropriate instance
- Format: ComputerName\InstanceName
- Common InstanceName: UNIFY or WEBGILITY
c. Use SQL Authentication
- Select Use SQL Server Authentication
- Enter credentials:
- Username: sa
- Password: Webgility2011 (case-sensitive)
- Click Connect
d. If SQL Server Is on Another Machine
- Click Browse more in the SQL Server drop-down
- Wait a few minutes for SQL Server instances to populate
- Select the correct instance
Conclusion
By restarting SQL services and ensuring correct authentication, users can typically resolve the Database already exists or login failure issues. These steps restore connectivity between Webgility and the SQL database.