HowTo - Handle HTTP Error 500.30 in BioManager

HowTo - Handle HTTP Error 500.30 in BioManager

BioManager reports error “HTTP Error 500.30 - ASP.NET Core App failed to start” when accessing it. The following error is reported on the web browser.



Solution

The error "HTTP 500.30 - ASP.NET Core app failed to start" can have multiple root causes. It is typically reported when there is either a connection error to the database server or a mismatch between the database schema and the application server version. To troubleshoot this issue, follow the below recommendations in given order:

(1) Ensure that the SQL server database instance is running correctly and is accessible from the application server. You can verify accessibility by running the DB Installer Tool (located in the BME Installation directory under Tools/DBInstaller) and select the option to 'Relink to existing TBS database'. If this step is successful, it indicates that the database connection is functioning properly.

Notes
For versions prior to R20.4.0, special characters such as quotes in the 'tbsAdmin' database user password caused connection issues. This problem was resolved starting with version R20.4.0.





















(2) Verify that the database schema matches the application server version, especially if the BME software was recently updated or the database was migrated from another machine. You can update the database schema by running the DB Installer Tool and selecting the option to 'Update existing TBS database'.

If the error persists, please create a ticket in the help center with detailed information (available only to registered partners).


    • Related Articles

    • 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 ...

    • HowTo - Handle 'Invalid License key' error in BioManager

      BioManager reports error “Invalid License Key” after applying the license key. Solution In few installations, we observed that this error is caused by local Windows IIS server rejecting the 'PUT' REST call which is invoked when the license is applied ...

    • 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 '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 '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. ...