All Collections
Webgility Desktop
Advice & troubleshooting
Database 'UnifyDB' already exists. Choose a Different Database Name
Database 'UnifyDB' already exists. Choose a Different Database Name

'UnifyDB' already exists. Choose a Different Database Name

David Pond avatar
Written by David Pond
Updated over a week ago

Database 'UnifyDB' already exists. Choose a Different Database Name

The error message "Database 'UnifyDB' already exists. Choose a different database name" occurs when attempting to create a new database with the same name as an existing database in the same SQL Server instance.

To resolve this error, you can choose a different name for the new database, or you can delete the existing database with the same name before attempting to create the new one. You could also check if the database already exists before attempting to create it by running a query such as "SELECT name FROM sys.databases WHERE name = 'UnifyDB';". If the query returns a result, it means the database already exists, and you should choose a different name for the new database.

Error Message:

Database 'UnifyDB' already exists. Choose a different database name

Troubleshooting

1). Check the SQL services on the Webgility server, to see whether they are on “Network Service”. If not, then move the services to Network.

2). Restart “SQL Server Unify/Webgility” and “SQL Server browser.” by doing a right a click on each one separately.

3). Check whether the Unify DB exists in this C:\Program Files\Microsoft SQL Server\MSSQL13.WEBGILITY1\MSSQL\DATA location or not.

4). Run UnifyDBUpgrade.exe by going into the Webgility folder or reference this help article for more guidance: UnifyDBUpgrade.exe. Once you find the folder, search for UnifyDBUpgrade.exe and double-click on it.

5). Once you double-click on it, it may take some time to run and complete. Once it finishes, you will receive a success message.

6). Now, log in to Webgility and connect to the existing database to see if the same error message is still showing. If you receive the same error message, try to connect to SQL with an IP Address instead of a computer name, reboot the server, and then check whether the issue has been resolved.

NOTE: If rebooting the server and performing the above troubleshooting steps don’t resolve the issue, the database may be suspended. Our Webgility Support Team will need to fix the DB. If you are comfortable with databases you may install the SQL Server Management Studio so that the Webgility Support Team can run the query to alter the database.

Query:

ALTER DATABASE UnifyDB SET EMERGENCY

GO

DBCC checkdb('UnifyDB')

GO

ALTER DATABASE UnifyDB SET SINGLE_USER WITH ROLLBACK IMMEDIATE

GO

DBCC CheckDB('UnifyDB', REPAIR_ALLOW_DATA_LOSS)

GO

ALTER DATABASE UnifyDB SET MULTI_USER

If the issue persists, please contact our Webgility Support Team.

Did this answer your question?