Problem updating Fortify LIM from v22 to v24.2 (not docker)

Hello,

we are upgrading our Fortify LIM installation from version 22 to version 24.2, and are following the instructions in this document: portal.microfocus.com/.../KM000035098

This is a Windows installation without Docker.
The server where the LIM is installed has a default browsing proxy configured, while the LIM must use a different proxy to access the internet, reachable via http (not https) on port 80.

After installing and initializing the LIM and setting the correct proxy, upon activation (i.e. after pressing the "ACTIVATE" button) we receive the following GUI error:

----
Error
The following error has occurred:
Internal server error
Error message detail
Http failure response for controllerdast.collaudo.sum.testfactory.copergmps/.../server-license: 500 OK
----

Inside the file "C:\ProgramData\Fortify\Fortify License and Infrastructure Manager\logs\2024-12-10.log" we find this error:

----
ERROR | 2024-12-10 11:55:54.4601 | LIM.FortifyLicenseService.LicensingSOAPService | You cannot specify an explicit Proxy Address as well as UseDefaultWebProxy=true in your HTTP Transport Binding Element. System.InvalidOperationException: You cannot specify an explicit Proxy Address as well as UseDefaultWebProxy=true in your HTTP Transport Binding Element.
at System.ServiceModel.Channels.HttpChannelFactory`1..ctor(HttpTransportBindingElement bindingElement, BindingContext context)
at System.ServiceModel.Channels.HttpsChannelFactory`1..ctor(HttpsTransportBindingElement httpsBindingElement, BindingContext context)
at System.ServiceModel.Channels.HttpsTransportBindingElement.BuildChannelFactory[TChannel](BindingContext context)
at System.ServiceModel.Channels.BindingContext.BuildInnerChannelFactory[TChannel]()
at System.ServiceModel.Channels.MessageEncodingBindingElement.InternalBuildChannelFactory[TChannel](BindingContext context)
at System.ServiceModel.Channels.TextMessageEncodingBindingElement.BuildChannelFactory[TChannel](BindingContext context)
at System.ServiceModel.Channels.BindingContext.BuildInnerChannelFactory[TChannel]()
at System.ServiceModel.Channels.Binding.BuildChannelFactory[TChannel](BindingParameterCollection parameters)
at System.ServiceModel.Channels.ServiceChannelFactory.BuildChannelFactory(ServiceEndpoint serviceEndpoint, Boolean useActiveAutoClose)
at System.ServiceModel.ChannelFactory.CreateFactory()
at System.ServiceModel.ChannelFactory.OnOpening()
at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)
at System.Runtime.TaskHelpers.WaitForCompletion(Task task)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open()
at System.ServiceModel.ChannelFactory.EnsureOpened()
at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)
at System.ServiceModel.ChannelFactory`1.CreateChannel()
at System.ServiceModel.ClientBase`1.CreateChannel()
at System.ServiceModel.ClientBase`1.CreateChannelInternal()
at System.ServiceModel.ClientBase`1.get_Channel()
at LicensingSoap.LicensingServiceSoapClient.ActivateLicenseServerAsync(LicenseServerActivationRequest activationRequest)
at LIM.FortifyLicenseService.LicensingSOAPService.ActivateLicenseServerAsync(LicenseServerActivationRequest activationRequest) | url: controllerdast.collaudo.sum.testfactory.copergmps/.../server-license | action: ActivateLicenseServer
----

Has anybody ever encountered the same? How could it be solved?

Thanks,

Giampaolo

  • 0  

    There are a number of reasons for the 500 error:

    1. Missing runtime requirements.
    2. Installing in default site instead of creating a new site or trying to upgrade a site. My recommendation would be to install in a new site and let the LIM initializer create the site.
    3. Issue with bindings in IIS
      1. Verify there is a host name
      2. Certificate is valid

    Can you try a test installation to http instead of https?

  • 0 in reply to   

    We tried all the things you suggested (new site, check hostname, check certificate, http instead of https) but nothing worked.

    The problem seems to originate inside the asp application:
      "You cannot specify an explicit Proxy Address as well as UseDefaultWebProxy=true in your HTTP Transport Binding Element"

    The problem is that neither us nor the support were able to find where and how to set that UseDefaultWebProxy variable.

    We are starting to thinks that is declared inside the code and cannot be overridden.

  • 0   in reply to 

    Can you provide me your ticket number?

  • 0   in reply to   

    Thank you for supplying me with your ticket number. Is the only issue you are encountering is licensing the LIM instance? If so, a workaround would be to uncheck the option that the LIM has access to the Internet and then license the application via our offline activation method.

    I'm also reaching out to the support person assigned to your case.