I am looking at evaluating the newest eB version. I’m trialing this on a Windows 2016 Server.
I’ve followed the instructions, however when I launch the system Management Console and click on the server it hangs then gives the following error:
There was no endpoint listening at https://serverName/Bentley/eB/Services/DataStorageAdmin/Ws that could accept the message. This is often caused by an incorrect address or SOAP action.
Unable to connect to the remote server. No connection could be made because the target machine actively refused it.
Any suggestions as to what could be wrong?
I am currently working on upgrading our system to version 16 and ran into the same issue. You need to make sure your SSL configuration is set up properly. You can quickly get a temporary certificate set up by opening the Windows Services, right-clicking the eB service Manager and open Properties, Click 'Stop' then enter the following for the start parameters:-D -C -I -RThen from the same properties window click start.That should create a temporary SSL Cert for port 443 that you can work with to get things going. (You will need to close and re-open SMC)
Hi Scott - Thanks for this. I did try this but alas it did not work.
Which version of Windows Server are you using? Is there any other way of validating the existence of the SSL cert
Bentley Support folks - Any ideas?
I have studied the event log and can see that the various scripts are running and that the SSL cert is being bound to the port. I’ve discovered another error message buried in the events which reads:
The remote name could not be resolved: 'ims.bentley.com'
This is kind of expected though as this is an internal server which cannot access external resources. Does this version of eB support an offline installation?
We are installing it on Windows Server 2016. Maybe try unbinding port 443 on that server, and attempt to re-bind it to the eB application? The error you are receiving leads me to believe that the eB application is not bound to port 443.That is a good question though, I am not sure if it is an issue with your server not having external access.
Hi Andy, has this been resolved?