Error with newly created EcoStruxures Web Service

[AQ]

Good day,

I've created an interface for SmartConnector (EcoStruxure Web Service). Given service URL (localhost or it's IP address) and login are correct, communication is enabled, but after a few seconds it goes offline. I also cannot host EWS objects through System/Hardware/... - do you have any idea how to solve this issue?

Regards

[ardak]

Hi,

Just so I understand you correctly:

"I've created an interface for SmartConnector (EcoStruxure Web Service)."

This is an interface in EBO? Does that mean you have set up a EWS Server in smartconnector that you are trying to connect to?

Could you provide a more detailed description of what you are trying to do and attach some screenshots showing the issues you are having?

[AQ]

The interface was created in EBO. I've attached screenshots.

EWS server is enabled. 

After creating an interface to handle SmartConnector, and configuring it seemingly properly, it almost instantly goes offline. I also cannot host EWS object through System/Hardware/... 

I really don't know how to be any more detailed here. I think screenshots should tell the whole story. 

[ardak]

Hi again,

The EBO part looks fine, but how does the Smartconnector side look? I ask again, have you set up an EWS Server in smartconnector? Are you trying to use an existing extension or have you wiritten your own code? Do the credentials in the Smartconnector EWS Server match the ones in the EBO Client(interface)?

BR

Armend

[AQ]

SmartConnector looks like this (as in attached Screenshots):

-EWS Server is up and running,

-It's confugration is attached,

-Processors are running as shown. 

[AQ]

There's also error in System logs in EBO. It's "Digest authentication failed. EWS-Server doesn't support digest. Access_Denied: 401. Screenshot attached. 

[ardak]

Thanks for all the screenshots! 

Could you enable "Ews Serve" logging in the portal (Setup -> Logging filters), try to add the server in EBO again and attach the resulting logs?

The logs are in %ProgramData%\SmartConnector\Logs

Thanks!

[ardak · Accepted solution]

And just to be sure, could you:

In smartconnector portal, find your EWS server, edit it and remove all digest algorithms. Stop the server, reselect them all, save it and start the server and try again.

Thanks again,

Armend

[AQ]

I've turned all hashing algorithms and restarted server - no effect.

Logs have been added. I will look to them monday. 

Thank you for helping 🙂

[AQ]

So far, I got those logs (I've added other data logging options):

2021-07-26 10:03:14.4551,Trace,Database,<no principal>,Setting Database Execution Strategy to SqlAzureExecutionStrategy.,
2021-07-26 10:03:18.1856,Status,Service,<no principal>,SmartConnector is starting,
2021-07-26 10:03:18.2010,Status,Service,<no principal>,Intializing User DB context,
2021-07-26 10:03:18.5710,Info,Service,<no principal>,Cleaning up orphaned ParameterSet instances,
2021-07-26 10:03:18.8485,Status,Service,<no principal>,Ensuring Service Broker is enabled,
2021-07-26 10:03:18.8947,Status,Service,<no principal>,Spinning up WorkerManager,
2021-07-26 10:03:18.8947,Status,WorkerManager,<no principal>,Mongoose WorkerManager running with 5 Processor threads.,
2021-07-26 10:03:19.0026,Status,WorkerManager,<no principal>,Worker manager has started.,
2021-07-26 10:03:19.5268,Status,Service,<no principal>,Instantiating EWS Servers,
2021-07-26 10:03:19.5884,Info,WorkerThread,<no principal>,EBO-OPC Client Update Processor,Started,
2021-07-26 10:03:19.5884,Info,WorkerThread,<no principal>,EBO-OPC Client Setup Processor,Started,
2021-07-26 10:03:19.6038,Status,Service,<no principal>,Starting EWS Server http://localhost:5300/EcoStruxure/DataExchange,
2021-07-26 10:03:19.7734,Status,Service,<no principal>,Attaching context listeners,
2021-07-26 10:03:19.9126,Info,Processor,<no principal>,EBO OPC Client - StartApplication,
2021-07-26 10:03:19.9584,Status,Service,<no principal>,Starting REST Providers,
2021-07-26 10:03:19.9892,Status,Service,<no principal>,Starting PortalAddress,
2021-07-26 10:03:20.0046,Info,Processor,<no principal>,EBO OPC Client - InitApplication,
2021-07-26 10:03:20.6710,Info,WorkerThread,<no principal>,EBO-OPC Client Setup Processor,Ended successfully,
2021-07-26 10:03:20.6710,Info,WorkerThread,<no principal>,EBO-OPC Client Setup Processor,Next run will be at next SmartConnector startup,
2021-07-26 10:07:06.5065,Info,Api,admin,Ping,Get,ET=0 mSec,
2021-07-26 10:07:11.4692,Info,Api,admin,Ping,Get,ET=0 mSec,

Regards.

[AQ]

Ardak has contacted me directly through private message and asked if we can connect remotely. After short conversation he advised me to allow only MD5 and SHA-256 algorithms and then restart SmartConnector service. It worked great and after short while connection has been estabilished.

BIG THANKS TO YOU Armend 🙂