BioManager ENTERPRISE
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. ...
FAQ - Client Registration procedure in BME with device and BCS
This article explains the registration procedure for Clients (Devices, BCS) in BME. The registration process has been simplified in the BME using the activation code. During registration, the certificate, license and other details are automatically ...
FAQ - BME Database migration to another MS SQL Server
Question How can I migrate the BME server database to another MS SQL server? How can I migrate the WebEdition database to another MS SQL server and update & connect to BME server? Answer This article describes how to move BME server database to ...
FAQ - Guidelines for Configuring BME with a Public IP
This article provides recommendations on configuring BME with a public IP address or Fully Qualified Domain Name (FQDN). There are different approaches to making BME accessible beyond the internal network. Below are some of these options along with ...
FAQ - Guidelines for activating Clients in Miniserver BME
This article provides the guidelines to activating Clients in BioManager ENTERPRISE (BME) running in MiniServer. In BME, Clients are validated using an activation code, which involves dedicated WebSockets (WS) channel within BME. Once activated, ...
FAQ - Key Considerations and Best Practices for BME upgrade
This article lists the key considerations and best practices when upgrading an existing WebEdition (WE) installation to BME. Upgrading the server software itself is a straight forward procedure that is taken care by the installer. But connecting the ...
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 ...