Trying to bind to a WCF service and I'm getting the message "Error: Sys.ArgumentException: Cannot
deserialize. The data does not correspond to valid JSON". Saw the post about the HttpHandler possibly being the problem, but I added it via the Smart Tag again and it still doesn't work. The syntax checker for the web.config is complaining that the required attribute "name" is missing from the tag. What should the proper handler entry be?
deserialize. The data does not correspond to valid JSON". Saw the post about the HttpHandler possibly being the problem, but I added it via the Smart Tag again and it still doesn't work. The syntax checker for the web.config is complaining that the required attribute "name" is missing from the tag. What should the proper handler entry be?
2 Answers, 1 is accepted
0
Hello Larry,
Can you provide some more details how to replicate this behavior?
Bellow demo seems to be working perfectly with WCF services:
http://demos.telerik.com/aspnet-ajax/grid/examples/clientbinding/defaultcs.aspx
All the best,
Nikolay
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Can you provide some more details how to replicate this behavior?
Bellow demo seems to be working perfectly with WCF services:
http://demos.telerik.com/aspnet-ajax/grid/examples/clientbinding/defaultcs.aspx
All the best,
Nikolay
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
Larry
Top achievements
Rank 1
Rank 1
answered on 22 Apr 2010, 01:48 PM
Hi Nickolay,
The error has been resolved. Thank you for the followup. After making some changes, the problem went away. It had nothing to do with JSON, but rather the way the service was being accessed from the code.
Thanks,
Larry
The error has been resolved. Thank you for the followup. After making some changes, the problem went away. It had nothing to do with JSON, but rather the way the service was being accessed from the code.
Thanks,
Larry