How to resolve error 203 - Opps! XXX is unable to connect to the database

Hardik Shah -

In general, you will see this error at the time of installing any Emgage product or on the license page in following conditions if product is not able to connect to database.

This may happen due to following reasons:

1. Database(s) names are wrong in your connection strings
If you have manually generated connection string for Emgage database in web application web.config, this may be the problem.


Solutions:

For Upgrade : Need to verify if the connection strings are proper. Create a UDL file and generate connection string by selecting server name, product database and allowing to save password. Edit the UDL file in notepad and verify this connection string with the already inserted connection string. If the connection string does not match then update the connection string in the web config file with proper string. Need to do this check for all 3 connection string. While updating the connection string with the UDL one, take the part starting from password as displayed below.

e.g. Password=Admin@123;Persist Security Info=True;User ID=sa;Initial Catalog=Database Name;Data Source=SQL Instance

For Installation : Deactivate and activate the Emgage licensing feature at web app level in central admin before running installer.

2. Database(s) are no longer accessible because they are locked, offline or detached

  1. If any of the product database is locked, offline or detached by database administrator to perform some maintenance activities.


Solution : The client needs to contact their Database Administrator to get this issue resolved.

 

Do above solutions work for you? If not, please enter a new support ticket.

 

Have more questions? Submit a request

1 Comments

  • -1
    Avatar
    Anna Johnson

    These are not solutions, simply an identification of the problem.  Does not indicate how to resolve.

Please sign in to leave a comment.
Powered by Zendesk