Hello,
it has been a long time since I got this error happening randomly on my production enviorment and not been able to solve it.... I got this error message when opening a report with 2 parameters (int, datetime) :
Value cannot be null.
Parameter name : Instance.......
Consider that there' approximatelly 400 ppl using this application, I don't know it if it's something related to concurrency or what... I can just say that one time it happens it continue till I do an iisreset
I got this problem with Q2, can't move immediatly to Q3 since we got scheduled deploys..... any suggestion?
Thanks
Paolo
22 Answers, 1 is accepted
Thanks
We've not been able to reproduce this error locally and the fact that it occurs randomly on your end is even more baffling. If you can isolate this in a sample runnable project where the error can be observed, then we would be able to pinpoint the problem. Otherwise without being able to reproduce it and sample project, we can only guess what is the culprit.
Regards,
Steve
the Telerik team
How can we fix that
thanks
We cannot stress on the fact that we cannot reproduce the problem locally and need to look into your specific project to find the culprit. Recently another customer provided us with such project and we identified his problem in old Telerik Reporting assemblies in the app bin folder that do not match the version from the references. Additionally there were some messed up references to MS Enterprise library, which once removed made the report designer appear correctly once again.
Check your project for such occurrences and if the problem differs, open a support ticket and attach your problematic project (or report if a single one).
Best wishes,
Steve
the Telerik team
I've just deployed a new version of my portal that uses Q3... I got again the problem of Value cannot be null but this time it shows me the message "The operation completed sucessfully" .... I've got pression from my superior about this problem.... can you please tell me where to start from investigating? You can't say "we were unable to reproduce this problem" ... give me some starting point to look at...I wish to spot the problem.... Thanks
Paolo
I am using Q1 2010 (4.0.10.423) version of Telerik Reporting in a Silverlight 3 application. I have some observation regarding it. The reports work fine. But after running for one or two hours it shows this error. We have arround 70-80 concurrent report users. To resolve this problem, I need to restart the Web Application where the reporting service is resided and also need to recycle the Application Pool memory. Which makes this application unused as I have arround 60-100 concurrent Transaction users who access the WCF service that resides in the same web application. After restarting the web application and recycling the ApplicationPool memory, the reports start to works again.
I would like to add up here that we are in a Mission Critical Situation please suggest us at the earliest.
I've got your exact situation........ I've a wilder range of users... from 20 to 400 and after 1-2 hours I've do to an iisreset.... please Telerik scale up the problem.....before the Q3 release I had the hope that after Q3 it would be ok.... now that I've updated what should I say? at our vendor the problem doesn't happen?
Even I with an IIS-Reset resolve the iussue.... Thanks
We understand that there is clearly a problem on your end, but please understand that the information you've provided so far is not sufficient for us to make a test scenario on our end that would effectively help us pinpoint this one out. In all of our previous replies we ask for a sample project which would make this task a breeze. Note that we do not need your exact data, any test data that exhibits the problem would suffice.
We also need exact settings (OS, IIS, Application Pool type, .NET framework, type of application etc.), setup of the report (i.e. 2 parameters, 4 groups, aggregates etc) and full steps to reproduce (1. click here, 2. select this etc.).
Since this is a forum thread and you cannot attach projects here and if you provide a link it would be visible for other community members, it would be best if you open a ticket with all of the information we asked for. Once we create a test scenario and replicate the problem on our end, we would be able to provide more information on it or issue a hotfix for the problem
Looking forward to your reply.
Greetings,
Steve
the Telerik team
I'm going to develop you a sample solution that reflects at most the real situation.... you've to do the stress load yourself since the problem occurrs with ~80 concurrent users....
I'll reply in the ticket I've opened... Do you also need a database or can I generate dummy data in the service?
"Note that we do not need your exact data, any test data that exhibits the problem would suffice."
In this line of thoughts we do not care what the data would be, as long as we are able to run the reports and replicate the issue.
Greetings,
Steve
the Telerik team
Our clients are getting mad because we have to restart the IIS after 5-6hours of work because at this point all the reports become unusable due to the "The operation completed successfully" problem. And this results in application downtime during work hours which results in money losses for our clients.
Please find a good solution to this as soon as possible if you want your reports to be applicable for business use and not only applicable for school type projects...
And since you will probably ask for a sample solution (like you always do, w/o even trying to make one yourselves) you can download one from here: https://backup.tangrasoft.com/ReportingStressTest.rar
You know it is not that hard to make a big loop that simulates simultaneous connections to your service...
We understand your confusion and the importance of the problem. Thanks to your colleague - Plamen - we were able to find the source of the problem. Currently the XAML rendering extension that is responsible for rendering the report for the Silverlight/WPF report viewers depends on WPF and this seems to be the problem. The solution is to break this dependency. Now that we have a clear view on the situation we need some time to implement and test the fix. Once we are ready, we will let you know immediately.
Greetings,
Svetoslav
the Telerik team
Can be solved by Telerik reporting upgrade wizard.
Madhuraj.M
with wich version?
Thanks
Paolo
We've made the changes my colleague Svetoslav talked about in the last post and they are part of the Q1 2011 SP1 release, namely "Fixed: An error occurs when rendering in multi-threaded environment". You can upgrade and let us know how it goes.
Greetings,
Steve
the Telerik team
Is there something I need to do other than just copying the project from one computer to another to prevent this error from occurring?
Thank you,
Jack Helfrich
If on the second machine you intend to work with other Telerik Reporting version, you will have to close all report designers, run the Upgrade Wizard, rebuild the project and reopen the reports.
Let us know if you need any further help.
Regards,
Stef
Telerik
New HTML5/JS REPORT VIEWER with MOBILE AND TOUCH SUPPORT available in Telerik Reporting Q3 2013! Get the new Reporting version from your account or download a trial.
Hi,
The issue with Telerik Winforms RadForm based forms "Designer error: Value cannot be null. Parameter name: instance" still persists. Is there any permanent solution to the issue?
Such error can occur in the VS Report Designer, if the report is designed with a version of Telerik Reporting that is not installed on the dev machine. Running the Upgrade Wizard and restarting the VS Report Designer should resolve the issue, where the project will be updated to use the selected Telerik Reporting version.
On a side note, if you use SubReport items or actions targeting reports, we recommend re-configuring them to use the 'Type name' option in the 'Load Report' dialog.
If I am misunderstanding the issue, please post further details where and when you observe the error, and which version of Telerik Reporting is used. Include details about the project as well - target .NET framework, reports and viewers settings.
You can open also a support ticket to post this information privately.
Regards,
Stef
Telerik by Progress
Recently I have caught into the Parameter Value Error In MS Access . At that time I came to know this error. The main reason for the occurrence of this Parameter Value error is that when a field, form, criteria, an expression, control in a query, or report; references a name that Access can’t find. I searched a lot for the fixes and finally get this helpful post. So, i just want to share it with you all .....!
For the fixes you can check out this link:
http://www.accessrepairnrecovery.com/blog/fix-ms-access-parameter-value-error