https://community.blueprism.com/t5/Digital-Exchange/Schedule-monitor-issue/m-p/65257#M2853 <P>Hello,</P> <P>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.</P> <P>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.</P><BR /><BR />------------------------------<BR />Charlie Kovacs<BR />Sr. Digital Exchange Engineer<BR />Blue Prism<BR />Austin, USA<BR />------------------------------<BR /> Wed, 23 Aug 2023 17:04:00 GMT charliekovacs 2023-08-23T17:04:00Z https://community.blueprism.com/t5/Digital-Exchange/Schedule-monitor-issue/m-p/65256#M2852 <P>Hi Team</P> <P>One of my customers asks me about an issue with the schedule monitor. I want to clarify this one.<BR />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.<BR /><BR />2023-08-22T08:09:10.9115500Z|INFO|Initiating<BR />2023-08-22T08:09:11.2723428Z|INFO|Opening connection to database<BR />2023-08-22T08:09:11.7582956Z|INFO|Database connection opened<BR />2023-08-22T08:09:12.0150408Z|INFO|Querying database for misfired schedules<BR />2023-08-22T08:09:12.1352776Z|FATAL|'STRING_AGG' doesn't recognize an embedded function.<BR />the keyword 'AS' may have inappropriate statements.<BR />2023-08-22T08:09:12.1483474Z|INFO|--------------------------- recorded below.</P> <P><BR />They are using BP 6.8.1&nbsp; and sql server <SPAN>2016.</SPAN></P> <P>Thank you</P> <P>Keiichi</P> <P></P><BR /><BR />------------------------------<BR />Keiichi Furue<BR />Blue Prism<BR />------------------------------<BR /> Tue, 22 Aug 2023 12:43:00 GMT https://community.blueprism.com/t5/Digital-Exchange/Schedule-monitor-issue/m-p/65256#M2852 KeiichiFurue 2023-08-22T12:43:00Z https://community.blueprism.com/t5/Digital-Exchange/Schedule-monitor-issue/m-p/65257#M2853 <P>Hello,</P> <P>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.</P> <P>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.</P><BR /><BR />------------------------------<BR />Charlie Kovacs<BR />Sr. Digital Exchange Engineer<BR />Blue Prism<BR />Austin, USA<BR />------------------------------<BR /> Wed, 23 Aug 2023 17:04:00 GMT https://community.blueprism.com/t5/Digital-Exchange/Schedule-monitor-issue/m-p/65257#M2853 charliekovacs 2023-08-23T17:04:00Z https://community.blueprism.com/t5/Digital-Exchange/Schedule-monitor-issue/m-p/65258#M2854 <P>Hi Charles</P> <P>Thank you for your reply.</P> <P>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.&nbsp;</P> <P><a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/2629">@charliekovacs</a><BR /><BR />Thank you</P> <P><BR /><BR />------------------------------<BR />Keiichi Furue<BR />Blue Prism<BR />------------------------------<BR /></P> Thu, 24 Aug 2023 01:07:00 GMT https://community.blueprism.com/t5/Digital-Exchange/Schedule-monitor-issue/m-p/65258#M2854 KeiichiFurue 2023-08-24T01:07:00Z