V11 client login error "Could not establish trust relationship for the SSL/TLS secure channel."

Hello,

We just have gone live with V11.0.3 and are having some issues with some of our client workstations. Upon entering their username/password they get a succession of errors (one for each of the REST services, from what I can tell). They all look like this:

 

Error importing XML. ImportString error code: -11

 DataStore.Class: nvo_ds_webservice

DataObject: d_error_messages

DataWindow: 

 XML: <?xml version="1.0" encoding="UTF-8" standalone="no"?>The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

 

Has anybody else seen this? Any ideas on how to correct it?

Thanks!

Jeff

Parents
  • Hi Jeff

    I know this is an old post but I was scouring the forums for some advice. Presumably you were able to fix this error? Did this error crop up within your own domain?

    The situation we have is that we have 4 different sites (venues), each with their own domain but connected on the same network & using the same db. So they can all ping each other, resolve DNS names, etc. We have upgraded our test system. The clients are in different domains, while they can browse to the services urls (https://name.domain.local/ConstituentService/) they get a certificate error & in the application although they make the initial database connection, they get errors while initialising services. It definitely looks like a problem seeing the domain certificate as valid. 

    Just wondering if you could offer any advice? I have a ticket open with support, they are looking into it at the moment.

    Thanks

    Gwen

  • Hi Gwen,

    In our situation it turned out to be a group policy that was preventing the trusted connection. Fortunately our network admin was able to trace it down and remove that particular policy. Once he did, all the issues cleared up.

    If I can remember or dig up the specific policy that caused the issues for us I'll pass it on to you.

    Hope this helps, and good luck!

    Jeff

Reply
  • Hi Gwen,

    In our situation it turned out to be a group policy that was preventing the trusted connection. Fortunately our network admin was able to trace it down and remove that particular policy. Once he did, all the issues cleared up.

    If I can remember or dig up the specific policy that caused the issues for us I'll pass it on to you.

    Hope this helps, and good luck!

    Jeff

Children
No Data