SQL Server Reporting Services (SSRS) via HTTPS in Innovator Release 2023. How to fix?

Hi community,

the release notes of Innovator 26 mentions following fixed issue:

I-050277 Fixed an error that prevented Aras Innovator from connecting to SQL Server Reporting Services via HTTPS.

I did a quick test in Release 2023 and noticed that I cannot create SSRS reports via HTTPS in this release.
When executing the Report, I get following error message: "The provided URI scheme 'https' is invalid; expected 'http'. (Parameter 'via')".

I assume Release 2023 still contains the bug that was patched with Innovator 26.
Release 2023 removed the RSGateway.aspx that was previously used to connect to SSRS. Not sure how Aras calls the reports in the new versions.

Does anyone know how to fix this one? I assume we need to customize the codetree, add some assembly binding or similar. But I have no idea so far how to do it.

Thanks and best regards!


  • Additional remarks:

    I get a browser debugger error message when executing the report. --> Uncaught TypeError: Cannot read properties of null (reading 'appendChild')

    Affected codetree file is .../javascript/aras_object.ts . Here the function Aras.prototype.targetReport throws the error, but I guess the actual error already happens before.

    If somebody has the possibility to compare "aras_object.ts" from Innovator 25 to Release 26, would be happy to know if there are some notable differences! 

  • Can anyone help with this one?

    The error is easy to reproduce. We specify the ReportServer target URL inside the InnovatorServerConfig.xml. If we specify a http URL, report service works. If we specify a https address, following error message appears when executing the report:

    I checked the codetree and didn´t find any obvious bug that can cause this behavior. In worst case, DLLs is affected so it´s not repairable.

    We can even check with direct link without using report inside Innovator.

    https://  myserver / Release2023/Server/RSGateway.aspx?irs:Report=PCBA_BOM

    This direct links works as long there is just a http address specified in config. If we use https, same error messages occurs.

    I hope there is a solution! Any ideas welcomed!


  • I got some info regarding differences between I25 and I26, but there wasn´t any obvious change in the codetree that affects HTTPS. So this one is high likely a DLL issue. But if anyone knows more or even have a patch, I would be happy to know!

    This tiny bug is currently the only issue that prevents me from using Release 2023. Although I am not sure if it really affects the HTTPS connection itself.

    Despite that tiny detail this Release is 99,9% fine, but I want 100% perfection Grin.