22-08-23 01:43 PM
Hi Team
One of my customers asks me about an issue with the schedule monitor. I want to clarify this one.
They are using the latest v1.3.0. The log file is below. Could you please give me any ideas to address the issue? I am guessing the issue may cause SQL server version incompatibility.
2023-08-22T08:09:10.9115500Z|INFO|Initiating
2023-08-22T08:09:11.2723428Z|INFO|Opening connection to database
2023-08-22T08:09:11.7582956Z|INFO|Database connection opened
2023-08-22T08:09:12.0150408Z|INFO|Querying database for misfired schedules
2023-08-22T08:09:12.1352776Z|FATAL|'STRING_AGG' doesn't recognize an embedded function.
the keyword 'AS' may have inappropriate statements.
2023-08-22T08:09:12.1483474Z|INFO|--------------------------- recorded below.
They are using BP 6.8.1 and sql server 2016.
Thank you
Keiichi
23-08-23 06:04 PM
Hello,
This is likely due to a compatibility issue between SQL Server and the Schedule Monitor. The STRING_AGG() function that the Schedule Monitor relies on was introduced in SQL Server 2017 (v14.x and later) so this problem will occur in SQL Server versions older than that.
The long term solution will be an update to the Schedule Monitor for compatibility with pre-2017 SQL Server environments. I am looking into the development of that currently.
24-08-23 02:07 AM
Hi Charles
Thank you for your reply.
I could recognize the issue came from the sql server compatibility. It would be appreciated if you could put the software compatibility information in the user document from the next release.
@charliekovacs
Thank you
------------------------------
Keiichi Furue
Blue Prism
------------------------------