Juan Segura
Top achievements
Rank 1
Rank 1
Juan Segura
asked on 24 May 2010, 09:08 AM
Hello:
In a new application using Telerik reporting Q1 2010 v4.0.10.423, when I click on the export icon, the system shows a message box with the error “(XamlParseException) [Line: 0 Position: 0]”, followed by several “HRESULT E_FAIL” exceptions. In the same way, if I click on the print button, nothing happens.
I try it with an empty report (only with a static textbox), and the result is the same.
It happens on different computers.
I have another working project, that is using the same reporting version, and it works!
I run the Telerik upgrade wizard several times, and in different computers, but didn’t work.
Regards
Juan Segura
2 Answers, 1 is accepted
0
Accepted
Hi Juan Segura,
Your question has already been answered in the other thread you've opened. Here it is just in case somebody else encounters similar problems:
"As noted in our system requirements, you should have the corresponding RadControls for Silverlight version, available at the time of the Telerik Reporting release in order to use the Silverlight Report Viewer. We see from your download history that your RadControls for Silverlight version does not match the version used for the Q1 SP1 (v. 4.0.10.423) of Telerik Reporting. You should use version 2010.1.422.1030 of RadControls for Silverlight.
Also note that the Upgrade Wizard is detecting and upgrading only Telerik Reporting assemblies and you should take care of the RadControls for Silverlight upgrade manually. To avoid such confusions, you can always reference the assemblies we ship in C:\Program Files\Telerik\Reporting Q1 2010\Examples\CSharp\SilverlightDemo\bin."
We kindly ask you to use just one support channel to contact us. Posting the same questions numerous times slows down our response time because we will need to review and address two tickets instead of one. Moreover threads are handled according to license and time of posting, so if it is an urgent problem, we suggest you use a support ticket, which would be handled before a forum thread.
Thank you for your understanding.
Best wishes,
Steve
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.
Your question has already been answered in the other thread you've opened. Here it is just in case somebody else encounters similar problems:
"As noted in our system requirements, you should have the corresponding RadControls for Silverlight version, available at the time of the Telerik Reporting release in order to use the Silverlight Report Viewer. We see from your download history that your RadControls for Silverlight version does not match the version used for the Q1 SP1 (v. 4.0.10.423) of Telerik Reporting. You should use version 2010.1.422.1030 of RadControls for Silverlight.
Also note that the Upgrade Wizard is detecting and upgrading only Telerik Reporting assemblies and you should take care of the RadControls for Silverlight upgrade manually. To avoid such confusions, you can always reference the assemblies we ship in C:\Program Files\Telerik\Reporting Q1 2010\Examples\CSharp\SilverlightDemo\bin."
We kindly ask you to use just one support channel to contact us. Posting the same questions numerous times slows down our response time because we will need to review and address two tickets instead of one. Moreover threads are handled according to license and time of posting, so if it is an urgent problem, we suggest you use a support ticket, which would be handled before a forum thread.
Thank you for your understanding.
Best wishes,
Steve
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
Juan Segura
Top achievements
Rank 1
Rank 1
answered on 24 May 2010, 04:42 PM
Thanks for your response, and sorry for the double post!