Hello,
We have an integration with Milestone XProtect that allows us, among many things, to trigger alarms in XProtect, via the Alarm Service.
Our integration uses the protocol integration.
We have had some issues with the 2024 R1 version: the AlarmServiceToken, located on http://event-server:22331/Central/AlarmServiceToken?wsdl, raises an internal error. Simply trying to open the wsdl in a browser shows us the error. This happens even before authenticating or using any method in the API. Please find below a screenshot of the error (description in french though).
We have tested multiple versions:
- Express 2023 R3 → No issue
- Express 2024 R1 → Internal error
- Professional 2024 R1 → Internal error
We have reproduced this internal error on several Milestone installations.
Is this error known to you ? Is there an upcoming patch ?
Hi Robin,
You are right that WSDL fetching is not working in 2024 R1. However, the SOAP API itself is fully functional. I would create an issue and fix it for 2024 R2 (WSDL fetching). But your problem should be somewhere else (If the whole API is not working).
The “AlarmServiceToken” APi is used by Smart Client as well. Can you confirm that Alarm manager tab in Smart client cannot fetch alarms as well ?
Hi Petar,
Thanks for your help.
What I meant by “using any method in the API” is that since I can’t create the service by fetching the wsdl, I can’t even try using any API method. I don’t know if it is possible to use the SOAP API without fetching the WSDL before.
I can confirm the Alarm Manager tab in SmartClient correctly works. I have been able to trigger alarms manually.
Hi Robin,
As far as I know, wsdl is usually needed only initially, for the generation of the client. Once client is generated, it could be used without fetching the wsdl. Meaning client could be generated against 23.3 and used pointing to 24.1 later. (API hasn’t ben chnaged between these two versions).
But ofc I have only limited experience with strongly typed languages (like C++, C#, etc). It could turn out that some environments need WSDL to be always available (scripting, weak typed langs).
I would talk to Sustain Engineering team about eventual patch over 24.1. But even if this is approved, it would take time patch to be prepared and distributed. Like few weeks let’s say. Issue would be fixed in the upcoming 24.2 version (it is already in main trunk, well almost :-))
Indeed we could store the Wsdl and use it whenever we face version 24.1. We’ll try and see if it correctly works, despite the wsdl containing references to the event server itself.
I hope a patch will be able to fix this though.
Thank you very much for your help Petar !
Hello!
I was wondering if the wsdl fetching was indeed fixed in 2024 R2? I just tried with Professional+ 2024 R2 and still seem to be getting the internal server error.
Your observations are correct, Emeline.
Fix was removed from 2024R2, as it caused other problems.
So, it is still not available.
Ok, thank you for your answer.
Do you know if it’s planned to be fixed in 2025 R1, and if so if there already is an expected date for that next version?
Well,
WSDL fetching is (currently) working in the main branch.
I’m not sure if there is concrete date for the 2025 R1 release, but I would expect it to be somewhere between Feb and April 2025.
If everything is okay, and we do not rework SOAP APIs hosting again, it should work.
