For one of our integrations we received the following error when it was enabled in production.
Could not establish secure channel for SSL/TLS with authority ''.
The web service requires some certificates to be installed which were correctly installed. The web service was working fine on development machines. Initial investigation did not find anything different between the development/production systems. We then traced the web service calls using Fiddler on both development and production machines and that's when we found out that the number of ciphers are different on both environment. Production did not had the ciphers highlighted below.
A quick search on internet pointed towards a windows KB (3172614) which adds new ciphers. Installing the KB fixed the issue.
Note: The KB requires restart of the machine.
This posting is provided "AS IS" with no warranties. Use code at your own risk.
Sunday, 31 December 2017
Thursday, 21 December 2017
Error "Data at the root level is invalid" when opening a report
Recently users reported that they receive an error when opening a particular report. The error is
"Data at the root level is invalid. Line 1, position 1."
The call stack of the error is
Even opening the report in Visual Studio was throwing the same error as shown below.
This posting is provided "AS IS" with no warranties. Use code at your own risk.
"Data at the root level is invalid. Line 1, position 1."
The call stack of the error is
Even opening the report in Visual Studio was throwing the same error as shown below.
We exported the report from the AOT and analysed it ina text editor. It turned out that there was a CU/KB applied and the report was part of it. However the report was never upgrade and it had comments from the code upgrade tool. Fixing these comments in text editor, re-importing the report in to AX and deploying it fixed the issue.
This posting is provided "AS IS" with no warranties. Use code at your own risk.
Subscribe to:
Posts (Atom)