Skip to content

Commit 6e4dd8d

Browse files
authored
Update reporting-rest-service-throws-unable-to-get-parameters-missing-report-name-error.md (#1958)
1 parent 99f6639 commit 6e4dd8d

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

knowledge-base/reporting-rest-service-throws-unable-to-get-parameters-missing-report-name-error.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ res_type: kb
3131

3232

3333
## Description
34-
Rhe report viewer displays an error message saying that the report name is missing, although the report name is set in *reportSource* options in viewer definition. The message is displayed during the first request that tries to resolve the report, which is sent when the report parameters are loaded, that's why the error message starts with "Unable to get parameters".
34+
The report viewer displays an error message saying that the report name is missing, although the report name is set in *reportSource* options in viewer definition. The message is displayed during the first request that tries to resolve the report, which is sent when the report parameters are loaded, that's why the error message starts with "Unable to get parameters".
3535

3636
## Error Message
3737
```
@@ -40,3 +40,4 @@ Rhe report viewer displays an error message saying that the report name is missi
4040

4141
## Solution
4242
This error is due to incorrect deserialization of the *reportSource* name. The cause is that the Newtonsoft.Json is targeting wrong .NET Framework. In our case study the Newtonsoft.Json.dll copied in the \bin folder was targeting .NET 2.0 but the required target framework is .NET 4.0+. Please note that the same version of the Newtonsoft.Json.dll can target different .NET Frameworks. Although the *packages.config* contains the correct target framework for Newtonsoft.Json package, the NuGet package manager fails to overwrite it. The solution is to delete the Newtonsoft.Json.dll manually and rebuild the solution, so the NuGet package manager will download the correct assembly.
43+

0 commit comments

Comments
 (0)