I'm unable to reproduce this issue.
Please enable debug mode in your application/config/config.php file with 'debug'=>2 and 'debugsql'=>1 set.
Then save whole page as html file and upload here.

MS sql server 2012 related : each param need a different name. Then maybe something like this

But still : «Columns in the order by list must be unique.» sure, must be fixed :)

I just would like to share that I am currently facing same issue using MS SQL Server 2016. the related select statement get executed includes the column name "group_order" twice within the "order by" clause as per following : ORDER BY [groups].[group_order],[t].[question_order], group_order ASC
which cause execution failure of the query.
At MS SQL SERVER studio, the query get executed successfully after removing the extra "group_order" column from the order by clause. Thus, updating corresponding source file that generate the query to fix the syntax of order by clause may resolve the issue.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=28520

This fix should solve your issue.

Mentioned fix has been applied, however the issue is not yet resolved. will you please verify on that ?
the order by clause is still duplicating the column [groups].[group_order] : "ORDER BY [groups].[group_order],[t].[question_order], groups.group_order ASC"

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=28529

This latest patch should work, I tested it on SQL Server 2017.

https://github.com/LimeSurvey/LimeSurvey/commit/49f76c6b5f74294bc14250e4fb38b45ab533167f

@dominikvitt : i see 2 times groups.group_order in line shown by sdsAdm1n.

[groups].[group_order],[t].[question_order], groups.group_order

I think the 1st two came from https://github.com/LimeSurvey/LimeSurvey/blob/49f76c6b5f74294bc14250e4fb38b45ab533167f/application/models/Survey.php#L1841
And the second one by https://github.com/LimeSurvey/LimeSurvey/blob/49f76c6b5f74294bc14250e4fb38b45ab533167f/application/models/Survey.php#L396

Since we set the group_order in the relation : we don't need it too for other SQL server ;). More : since it must be 1st : we must remove it from relation, since order is not good …

@DenisChenu: It may seems to be logical way to fix it.
But, if order is removed from relations, it would have major impact, on every Question Group in Survey context.
So, it would give very unpredictable results.

Ok, but then : SQL server have bad order in Question list ?

In my opinion , the group_order relation must be removed

1. It was added in a commit unrelated with an order issue : https://github.com/LimeSurvey/LimeSurvey/commit/b2c5563d7267a5ee439ef3b97d4fcc1eb86b7d62
2. Set relation in the JOIN broke real ordering (else we can remove it for all)
3. It don't exist before August 2017

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=28530