HowTo - Handle 'Database operation error' issues

HowTo - Handle 'Database operation error' issues

The Database operation error issue is one of the most common problems detected after a WebEdition installation. It is a general error which is basically saying that connection to the database server (default, SQL Server) could not be established. 



Common solutions

 There are various reasons why this issue occurs, but most common are:

  • SQL Server was not installed with 'Mixed mode authentication' option

    Web Edition default installation uses 'Mixed mode authentication'  to establish connection to SQL Server database. You could double-check this point using MS SQL Server Management Studio, which is a freetool coming with SQL Server Express Edition installer (see below). 



NOTE

To establish a SQL Server connection using 'Windows authentication' please check this article: FAQ - Ways to access SQL Server in WebEdition


  • Default database connection string does not match SQL Server configuration (because the installation of SQL Server on premises differs than what TBS proposes in the documentation).

    This could be fixed in '{Web Edition folder}\Core\web.config' to fit your SQL Server configuration. Line to be edited is:

    <add key="dbConnString" value="Data Source=.\SQLExpress;Initial Catalog=TBS_BAWSE;User ID=tbsAdmin;Password=***;" />


  • For any other case, we propose to enable logs on server side, force the error to happen and then provide us the logs.

    To enable logs, edit {Web Edition folder}\Core\web.config file, line:

    <add key="logLevel" value="LOG_NONE" />

    must be replaced with

    <add key="logLevel" value="LOG_FULL" />

    Log file will be created by default at following location: 'C:\TBS\BASvcHost.log'.

    Important
    Logging must be turned OFF afterwards, by reverting the above changes!

    • Related Articles

    • FAQ - WebEdition server installation troubleshooting

      Question What are the most frequent problems when installing WebEdition server, and how can I solve them? Answer Installing all WebEdition server components is not a click-and-go experience. It requires several installation steps and skipping or ...

    • HowTo - Handle 'Processing...' error

      BioManager may report 'Processing...' error endlessly after installation/upgrade. This is a generic error indicating an internal component was not installed or configured properly. No standard solution can be given, hence more information is required ...

    • HowTo - Handle 'Access denied' error with WebEdition R10

      To increase system security, from WebEdition version R10 web service authentication is enabled by default. This leads to problems with integrations that do not support security token on web service interface and results in 'Access denied' error. ...

    • HowTo - Handle 'Soap http error - Cannot connect to host'

      BioManager may report " Soap http error - Cannot connect to host" after installation/upgrade. This is an error indicating that BioManager application cannot connect successfully to the Core web services. It can happen due to couple of reasons: either ...

    • HowTo - Handle 'SOAP-ERROR: Parsing WSDL' error in BioManager

      BioManager reports error “SOAP-ERROR: Parsing WSDL” which means connection to RemoteAdmin WSDL resource failed. Solution This error is most of the times caused by: missing ‘WCF Services - HTTP activation’ component (under Windows Features - .Net 4.5 ...