Sometimes, SmartConnector doesn't start at Windows Startup

[mike_meirovitz]

Sometimes (for example, once in 9 Windows restarts), the SmartConnector doesn't start at Windows startup.

If you look at the service status is looks like it is running, but our processor that is defined as "Runs On Start = True" doesn't start.

Only if I stop/start the SmartConnector service our processor will start.

The SmartConnector service is defined with 2 dependent services:

SQL-Server

Building Operation 3.1 Enterprise Server.

Any idea what to do?

Thank you.

Mike

[JeffBowman]

Hi Michael,

I am not sure what would cause this! Some questions.

- What version of Smart Connector is this occurring on?

- Is this new behavior?

- Is there anything in the log that may show what is happening here?

- What type of processor is this? Is it long running?

- Is this processor also running on a schedule?

Best Regards,

-Jeff

[mike_meirovitz]

Hi Jeff,

Thank you for your answer. See my answers below.

1. The version of the SmartConnector is 2.4.25.

2. I saw it also in the past.

3. See the attached log file. I didn't see anything special.

4. This is the setup processor that is part of our EBO-OPC Client EWS Server. The setup processor is defined as "Runs on Start = True" and "Run on Schedule = False". The Setup processor starts the Update processor after it completes creating the EWS folders and items. The Update processor is defined as "Runs on Start = True" and "Run on Schedule = False".

5. Yes. The Update processor is long running.

6. No, both processors are not running on Schedule.

7. If I start the Setup processor manually, it will start and work properly.

Thanks.

Mike

[mike_meirovitz]

Hi Jeff,

Still struggling with this issue. I noticed this error in the SmartConnector log file after I have restarted windows (at 10:55:56).

Any idea what is causing this error? The SmartConnector log file is attached.

2021-03-18 10:56:00.8025,Debug,EwsConsume,<no principal>,GetAlarmEvents,6614d29b-845d-4798-b546-1e80c509ca04,Response,{"GetAlarmEventsResponseStatus":{"MoreDataAvailable":false,"MoreDataRef":"","LastUpdate":"8d62ea0e-7f47-457a-8db4-cc93586e23ce|1097","NeedsRefresh":false},"GetAlarmEventsAlarmEvents":{"AlarmEvent":[{"ID":"/Server 1|/Server 1/MyValues/Building/18thTemp Out of Range Alarm|c600f85b-0b60-4d4e-931b-548f7771f032","SourceID":"02/Server 1/MyValues/Building/18thTemp Out of Range Alarm","SourceName":"18thTemp Out of Range Alarm","Acknowledgeable":"0","TimeStampOccurrence":"2021-01-11T16:21:37Z","TimeStampTransition":"2021-01-11T16:23:39Z","Priority":"100","State":"2","Type":"","Message":"18th floor. Temperature too high"},{"ID":"/Server 1|/Server 1/MyValues/Building/BuildingTempratureReport Change of State Alarm|34c5c783-c53b-48ec-859c-c17297a2c375","SourceID":"02/Server 1/MyValues/Building/BuildingTempratureReport Change of State Alarm","SourceName":"BuildingTempratureReport Change of State Alarm","Acknowledgeable":"0","TimeStampOccurrence":"2021-01-11T16:25:11Z","TimeStampTransition":"2021-01-11T16:25:58Z","Priority":"100","State":"2","Type":"","Message":"Temp. Report"},{"ID":"/Server 1|/Server 1/EBO OPC Client*8601|3bcf49cf-2327-46e0-8fdc-ee7219ba1309","SourceID":"02/Server 1/EBO OPC Client*8601","SourceName":"EBO OPC Client","Acknowledgeable":"1","TimeStampOccurrence":"2021-03-12T18:59:10Z","TimeStampTransition":"2021-03-12T19:05:01Z","Priority":"100","State":"1","Type":"System alarm","Message":"System alarm: SOAP-ENV:Sender.EWSv1232:SCWS.EWSv1232:INVALID_SUBSCRIPTION Gsoap_Communication__Error: 12 Invalid SubscriptionId parameter: CWS Value Poll failed [8601]"},{"ID":"/Server 1|/Server 1/9 Tags/Analog Value Out of Range Alarm|7c26c588-d40b-4d25-8f44-830773cacd27","SourceID":"02/Server 1/9 Tags/Analog Value Out of Range Alarm","SourceName":"Analog Value Out of Range Alarm","Acknowledgeable":"0","TimeStampOccurrence":"2021-01-19T14:44:49Z","TimeStampTransition":"2021-03-13T16:47:32Z","Priority":"100","State":"2","Type":"","Message":"Too low"},{"ID":"/Server 1|/Server 1/MyValues/Building/11thTemp Out of Range Alarm|a90ee17a-db51-4082-9ed5-29b96d7591c0","SourceID":"02/Server 1/MyValues/Building/11thTemp Out of Range Alarm","SourceName":"11thTemp Out of Range Alarm","Acknowledgeable":"1","TimeStampOccurrence":"2021-03-14T18:46:25Z","TimeStampTransition":"2021-03-14T18:48:19Z","Priority":"100","State":"3","Type":"","Message":""},{"ID":"/Server 1|/Server 1/MyValues/Building/10thTemp Out of Range Alarm|7c37cc1d-9d56-41a4-9a70-8c829d1fca2c","SourceID":"02/Server 1/MyValues/Building/10thTemp Out of Range Alarm","SourceName":"10thTemp Out of Range Alarm","Acknowledgeable":"1","TimeStampOccurrence":"2021-03-13T18:23:25Z","TimeStampTransition":"2021-03-16T06:31:35Z","Priority":"100","State":"1","Type":"","Message":"10th floor. Temperature too high"},{"ID":"/Server 1|/Server 1*7|2adb61fd-49ad-4e91-a0c5-6b78653d891d","SourceID":"02/Server 1*7","SourceName":"Server 1","Acknowledgeable":"1","TimeStampOccurrence":"2021-03-13T17:10:51Z","TimeStampTransition":"2021-03-16T18:19:24Z","Priority":"100","State":"1","Type":"System alarm","Message":"System Alarm: System warm start [7]"}],"Metadata":null},"version":"1.2"},

Thank you!

Mike

[JeffBowman]

Hi Michael,

From the log, this is not a Smart Connector error, but an alarm that your Smart Connector processor is receiving from EBO.

What this means is likely that when EBO sent out an EWS GetNotifications request, it got an INVALID_SUBSCRIPTION error. This should cause the EBO EWS client to resubscribe to the same points.

Best Regards,

-Jeff

[mike_meirovitz · Accepted solution]

Hi Jeff,

Thank you. 

Regards,

Mike