Hyperion Address Affected by URL Used to Open Meridian Enterprise

The Enterprise Server address in Meridian Configurator is affected by the URL you use when opening the Meridian Enterprise site.

The cause of this relates to the removal of all the different locations that used to define Publisher and Explorer addresses to simplify the configuration.

Local administrators of the server or members of Application Administrators group of the Meridian Enterprise Server configuration can change the Hyperion address when accessing the Meridian Enterprise Server console with a different URL. If the Hyperion address will be changed, a warning is displayed in the logs.

The following error message can appear in the program Meridian Configurator, within the Enterprise Server tab:

“Failed to invoke Enterprise Server (ServerName). There was no endpoint listening at HTTPS://... This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details”.

This error message appears depending on the configuration used on the web.config file located in the Webserver at C:\inetpub\wwwroot\BCEnterprise\ .

This error will prevent all the vaults from identifying the rendition and publishing jobs created and will not allow to select any job.

Solution for Meridian 2021 or Later

To solve this issue in Meridian 2021 or later:

When the administrator navigates to the BCEnterprise web address > Settings > System Settings, a dialog appears. This dialog asks if the administrator would like to update the Hyperion address and the current protocol used when accessing the BCEnterprise web address with a protocol different from the protocol that is currently in use (HTTP or HTTPS).

Click Yes.

Solution for Meridian Versions Before 2021

To solve this issue in Meridian versions before 2021, edit the web.config file of the IIS. For example, if you want to use HTTPS:

1. Navigate to the following path:

   C:\inetpub\wwwroot\BCEnterprise\

2. Open the web.config file.

3. Use the Find tool and search for “HTTPS: security mode”.

4. Ensure that the security mode for HTTPS is set to Transport (HTTPS: security mode = Transport).

5. Find the following entry:

   <security mode="TransportCredentialOnly">

6. Change the entry to: <security mode="Transport">

   Save the changes.

   The resulting file will be as follows in this piece of the script:

   <binding name="Binding_ES" closeTimeout="00:10:00" openTimeout="00:01:00" receiveTimeout="00:50:00" sendTimeout="00:50:00" messageEncoding="Text" maxReceivedMessageSize="2147483647">

   <!--HTTPS: security mode = TransportHTTP: security mode = TransportCredentialOnly-->

   <security mode="Transport"><transport clientCredentialType="Windows" realm=""/>

   </security>

   </binding>

   Note:

   If <security mode= is set to: "TransportCredentialOnly">, it will reverse the behavior.

7. As an optional final step, the users must be prevented from accessing the BCEnterprise web address via HTTP protocol in the internet browser.

Avoid Accidental Changes to the Hyperion Address

To mitigate against accidental changes to the Hyperion address that could potentially cause issues with Meridian applications, we recommend that Administrators:

• only use the valid DNS name in the URL
• remove previous bookmarks and/or modify the shortcuts
• avoid manually typing URLs.

It might be possible to set up an email alert from the server if the event log contains a warning of the address being changed. This kind of event is logged by Windows Server in Event Viewer > Applications and Services Logs > BC Application Events.

For example, if the event log contains the message “The Hyperion address was updated to https:// ...”:

1. Select this event.

2. In the Event Viewer, select Attach Task to This Event...

3. Select the Send an e-mail.