Upgrade Smart Connector from V2.1.83 to V2.2.108

[sesa145614_brid]

I tried to upgrade my Smart Connector from V2.1.83 to V2.2.108 and encountered the following issue:

After upgrading, the hosted EWS server became unable so I did the “Host EWS Object…” again. When I did that, the bindings of the graphic
were disappeared. I needed to do the binding again. Is this worked as it is or a bug.

Thanks!

[JeffBowman]

As for why the EWS Server became disabled, any information on that? Could you not restart the server, were there any errors in the log?

As far as the SBO losing it's bindings on the rehost.. I am guessing this is designed bevior.. if you deleted and rehosted.. once you delete the points the bindings go away as well.. However.. if you didn't delete.. I am  guessing this is what SBO does behind the scenes.. doesn't seem like the best thing to do.. But SmartConnector has no say in what happens there.

[sesa180908_brid]

When you upgrade SmartConnector, the installer needs to stop the running service.  When it restarted, SmartConnector will look for a valid license.  If none is found, it will automatically stop any EWS Servers, REST Endpoints, and running Processors until it has one. 

Once you install a valid framework license, you are again able to manually start these items (restarting the service would do the same).

This may explain why your EWS Server wasn't running after the upgrade.

As to the other issues, I think Jeff's reply is appropriate.