Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.
Already have an account? Login
You can subscribe to this forum after you log in or create your free account..
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.
Already have an account? Login
Hi,
We have a customer who is using our EWS server and having a problem. In the SmartConnector log file we this error every 1 minute:
2022-06-08 00:00:15.9354,Error,EwsServe,admin,Operation not supported
at Ews.Server.Contract.Processor.RequestProcessorBase`2.AssertOperationIsAllowed()
at Ews.Server.Contract.Processor.RequestProcessorBase`2.ValidateRequest(TRequest request)
at Ews.Server.Contract.Processor.PagedResultsProcessor`5.ValidateRequest(TOuterRequest request)
at Ews.Server.Contract.Processor.GetAlarmEventsProcessor`1.ValidateRequest(GetAlarmEventsRequest1 request)
at Ews.Server.Contract.Processor.RequestProcessorBase`2.ProcessRequest(TRequest request)
,[3,"028a96dc-2657-469c-8de8-f878f0ac8bd0"],
The SmartConnector log file is attached.
Any idea what is the cause for this error and what are the implications?
SmartConnector version is 2.5.4.
EBO version is 3.0.3.11
Thank you.
Mike
Hello,
You could check if the EWS server has all needed methods enabled. Here's where you can see it:
The one we're interested in is GetAlarmEvents
Hi Armend,
The value of the GetAlarmEvents method is false. It is also false on my computer, but on my computer I don't get this error (Error,EwsServe,admin,Operation not supported) in my SmartConnector log file...
Any idea why we see this error only at the customer's site?
Thank you.
Mike
This means that the GetAlarmEvents method in the EWS server is turned off.
Any client trying to use that method will get a not supported response. If you have an EBO client connected to both machines, I would guess that maybe alarm polling(in the EWS interface in EBO) is enabled on your customers machine but not on yours.
Hi Armend,
Thank you for your answer.
See the screen capture from the customer. He has the same settings as we have in our office, but we don't see this error in our SmartConnector log file...
Please advise.
Thank you.
Mike
Ok!
Step one would be to make sure that that's the only EWS client connected to the EWS server. To make sure of that, you could wireshark it with a filter like
xml&&(frame contains "GetAlarmEvents")
There you should see where the requests are coming from. If it's from the expected EBO system we can start looking further into why these requests are sent.
Another option would be to enable the alarm methods. If you have no alarms configured in your EWS server, nothing should change except the error messages go away 🙂
Hi Armend,
The system integrator (Fleischmann, Chile) have enabled the alarms methods and still, the error repeats every minute in the SmartConnector log file. See below.
2022-06-10 12:11:15.5601,Error,EwsServe,admin,Operation not supported
at Ews.Server.Contract.Processor.RequestProcessorBase`2.AssertOperationIsAllowed()
at Ews.Server.Contract.Processor.RequestProcessorBase`2.ValidateRequest(TRequest request)
at Ews.Server.Contract.Processor.PagedResultsProcessor`5.ValidateRequest(TOuterRequest request)
at Ews.Server.Contract.Processor.GetAlarmEventsProcessor`1.ValidateRequest(GetAlarmEventsRequest1 request)
at Ews.Server.Contract.Processor.RequestProcessorBase`2.ProcessRequest(TRequest request)
,[3,"cb3bc52c-3c43-463b-bb1d-d96a503a2ef3"],
Please advise what can be done to stop this error.
Thank you.
Mike
Your picture shows that alarm polling is enabled in EBO. If you have no alarms configured in your EWS server, that can be turned off and the errors would go away.
If the EWS server is setup correctly with the supported method and still throws the same error, you can try
1 Restarting the EWS server in Smartconnector, and if that doesn't seem to work
2 Restart Smartconnector
Hi Armend,
Thank you for your answer. It was off before. You suggested that we should turn it on. In either case the error continue to be displayed in the log file. Restart of the EWS server nor SmartConnector doesn't help...
I have asked the WireShark log file and I will send it to you.
Thank you.
Mike
Hi Mike,
I was referring to the methods in the Smartconnector EWS server, under "supported methods"
BR
Armend
Hi Armend,
Thank you for your answer.
See the attached screen capture of the supported methods in the EWS Server. Any thing we should change to here to stop the errors?
Mike
Yes, the ones that have Alarm in them can be turned on. If you don't have any alarms defined in your EWS server, it will make no difference, only stop the error messages.
--Armend
Hi Armend,
The customer have turned all the methods with "alarm" to "true" but still the error persists. See the attached log file.
In addition we see this error:
2022-06-14 21:41:51.7016,Debug,Service,<no principal>,No Flexera license found for smartconnector.service, status was UnknownError. Continuing to check for native Smart Connector license.,No valid client license available.
(Error -83: Version of vendor daemon is too old.),
Is it a license issue?
Thank you.
Mike
You can ignore the licensing error.
If you have made sure that this is indeed the correct EWS server and restarting it doesn't work, please send me the EwsServers table from the database.
You can also turn on debug logging and turn on the "database" filter in logging filters, and then start and stop the server in the interface.
You should see logging output in the style of:
User | Count |
---|---|
164 | |
34 | |
33 | |
19 | |
14 | |
11 |
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.