Background
The following error message can appear in Meridian Enterprise Configurator after enabling the Enable BlueCielo Publisher extension option of a vault in Meridian Enterprise Administrator:
The UI extension page "BlueCieloECM.InnoCielo.Meridian.Extensions.BCPageSink" is not initialized
It can have multiple causes, not limited to:
- A MET file was imported from a vault created on another server
- The Meridian Enterprise server was renamed
- The Meridian Enterprise Server connection is not configured.
- The vault configuration was copied for testing purposes without following the correct steps
This error occurs only in Meridian Enterprise 2017 and 2017 SP1. This issue is resolved in Meridian Enterprise 2017 SP1 Update 1.
Description
This error can be prevented by a software patch for Meridian Enterprise 2017 SP1 that is available upon request from Accruent Support. The name of the patch is Patch 3.9.15.3 (SR-5119)MeridianUI.
After patch installation, the error message will no longer be shown in Meridian Enterprise Configurator. Instead, clicking the Enterprise Server tab on the Vault Settings page will produce the following error message:
An error occurred during validation of “Enterprise Server” settings. There was no endpoint listening at http://<ServerName>/BCEnterprise/Services/ConfigurationService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
To fix the most common problems that can cause the error message, perform the following tasks on the Meridian Enterprise server:
- Ensure that all server installation prerequisites are met, as described in the Accruent Meridian Enterprise Administrator's Guide.
- Ensure the Meridian Enterprise Server name is properly set in the EDM Server properties as described in the Accruent Meridian Enterprise Administrator's Guide.
-
If the server was renamed or was copied from another environment (e.g. a virtual machine), ensure the Meridian Enterprise Server configuration, including any connection strings to SQL Server, was cleared as described in How to copy an Enterprise Server environment for testing or development.
Note:After clearing the Meridian Enterprise Server configuration and connection strings, open the Meridian Enterprise Server Administration Console using the fully qualified server name set in step 2 and not ‘localhost’.
- Ensure the Meridian Enterprise Server configuration is connected to a valid SQL Server or Oracle configuration database.
