Rank 1
Value cannot be null. Parameter name: instance
I tried reinstalling the latest version of reporting but that did not fix it.
The designer worked before, the error began happening randomly one day.
Any suggestions?
1 Answer, 1 is accepted
Hi Darin and Jonathan,
I'm sorry to hear that you are experiencing issues with our product.
The error Value cannot be null. Parameter name: instance can occur due to different reasons:
- Telerik Reporting extension might not be installed on the machine. Go to Extensions -> Manage extensions in Visual Studio and check for Telerik Reporting Tools;
- the installed version of Telerik Reporting and the version used in the reports may differ. In this case, check whether the reports to be opened in the designer have the same version as the one installed on the computer. If not, you may use the Upgrade Wizard to upgrade or downgrade to the necessary version (must be installed on the machine). After running the Upgrade Wizard, restart Visual Studio. You can also delete the bin and obj folders and rebuild the project once again.
- the project might use a version of Telerik Reporting that is not registered in Visual Studio. This might be due to Telerik Reporting being installed before the installation of Visual Studio 2017. For a solution, check Value cannot be null. Parameter name instance. when trying to open the Report Designer in Visual Studio 2017 KB article, which is also valid for Visual Studio 2019.
Check if the issue is reproducible with our demos which can be found at C:\Program Files (x86)\Progress\Telerik Reporting[Version]\Examples\CSharp, the reports are placed in CSharp.ReportLibrary project. In addition, make sure that the version of Telerik Reporting is compatible with the version of Visual Studio.
If possible, open a new support ticket with the problematic report.
Regards,
Progress Telerik
Rank 1
Hello Tim,
You may run the custom application that utilizes Telerik Reporting without installing the product. You need just references to our assemblies.
You need to install the product only if you will use the Visual Studio Report Designer to edit the report definitions. We cannot guarantee that the Visual Studio designer for the old version will work in VS 2017. You may need to use an older Visual Studio, for example, one that was available when the product had been released.
For the installation, you need to find the MSI file of the corresponding version of the product, for example under your Telerik account. If it is not available there, you need to contact our Sales department that can grant you access.
Regards,
Todor
Progress Telerik
There is no reason why upgrading to the latest version should cause such an error. Does downgrading to the previous version you've used work? Try closing the report designer, delete the .resx file of the report, rebuild the project and try opening the designer again. You can also try running the project on another machine to see if it is not a machine specific issue.
If still having problems, please open a support ticket and send us a sample project that exhibits the problem.
Best wishes,
Steve
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
at Microsoft.VisualStudio.Design.VSDesignSurface.CreateDesigner(IComponent component, Boolean rootDesigner)
at System.ComponentModel.Design.DesignerHost.AddToContainerPostProcess(IComponent component, String name, IContainer containerToAddTo)
at System.ComponentModel.Design.DesignerHost.Add(IComponent component, String name)
at System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.CreateComponent(Type componentType, String name)
at System.ComponentModel.Design.Serialization.DesignerSerializationManager.CreateInstance(Type type, ICollection arguments, String name, Boolean addToContainer)
at System.ComponentModel.Design.Serialization.DesignerSerializationManager.System.ComponentModel.Design.Serialization.IDesignerSerializationManager.CreateInstance(Type type, ICollection arguments, String name, Boolean addToContainer)
at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, CodeTypeDeclaration declaration)
at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)
How did the error start to occur - after upgrade or some change? Have you tried the suggestion from our previous post? Any additional information in reproducing this on our end would be highly appreciated.
Greetings,
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.
Most of us (i.e. Telerik Reporting team) are using 64 bit machines and we have not been able to produce such a problem. Since you claim the very same report works on your colleagues machine, have you tested on another 64 bit machine to see if the error would be persisted?
If this is the case, please zip your report and attach it to a support ticket so that we can investigate what is the culprit.
As kindly asked in our previous post, any additional information in reproducing this on our end would be highly appreciated.
Sincerely yours,
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.
Getting the same error?
I tried to delete the RESX
Nothing helped.... any ideas?
Just started
thanks
Same Error updating to the latest Telerik dll (Telerik Reporting Q1 2001)
VS2008, x86 ,Windows Vista
Delete the resx file .. did not help
Solution was:
Removing and adding again my References inside the Project after the update
@Jon: As stated in the previous posts, we are not able to reproduce the error locally by ourselves, so we would appreciate if you provide us with a sample project where the problem can be reproduced. Once we review it, we would be able to provide more information.
@Michael: This sounds like improper upgrade of Telerik Reporting. Can you try starting manually the Upgrade Wizard from the Telerik Reporting Menu the next time this happens and see if this helps?
Kind regards,
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.
Did you try using the Upgrade Wizard as my colleague suggested? If you still experience difficulties send us a sample runnable project via the support system that shows the issue and we will advise you accordingly.
Regards,Peter
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.
I solved it running Telerik Reporting Upgrade Wizard to Q1 2010
It's in Visual Studio menu bar.
Thank you.
Bye.
en el menu Telerik-Reporting-- Upgrade Wizard
Luego, siguiente , seleccionas el proyecto que deseas actualizar y listo con eso queda
Value cannot be null. Parameter name: instance
I AM NEW ABOUT TELERIK
PLEASE HELP ME OUT WHAT IS THE CAUSE FOR ERROR
Thanks
Telerik Team.
I'm using the version Q2 2012.
DLL Version: 6.1.12.611
Regards
I could fix the bug. I had a mistake in creating my model, the OnContextCreated. Solving this, my report worked perfectly.
Experienced the same issue. I’ve tried and failed on the following:
1. 1) Removed the .suo and rebuilt
2. 2) Removed the .resx (and unable to rebuild)
3. 3) Removed the Telerik references (.reporting, .reportviewer.webform, & .web.ui) and reloaded the references.
4. 4) Opened up the project -> Telerik -> Reporting -> Upgrade Wizard -> etc… -> Reload.
I succeeded in finding a solution and fixed the issue with this (with the original build undergone none of the above):
· Open up the project -> Telerik -> Reporting -> Upgrade Wizard -> etc… -> Ignore.
If your Visual Studio doesn't have telerik and the your project you are working on has a Telerik report, when you try to bring up the report designer, you get the error. I'd venture to guess between Telerik upgrade/downgrade you might get the same error.
Hope this helps.
Anyone fixed this issue ?
So maybe the refernce update should be market / highligted as solution to this problem?
​
Thanks! Your solution helped!
We had the same exact issue with a WinForms project after a upgrade from 2014.3 to 2015.1, removing the Telerik references and adding them back resolved the issue!
We had this problem also, our project is winforms, the solution is change base class from RadForm to Form(.NET Form),Build with error, change it back to RadForm then it works.
may this help you all.
As of Jan 14th 2016 , this problem still exist.
I just upgraded Windows UI from the Telerik Control Panel, and then when I open my project I get an the same error Value cannot be null. Parameter name: instance.
After a while, I solved it by just selecting the Telerik Upgrade Wizard option in Visual Studio. Deleting the .resx file was not necessary and only led to file not found.
I would like to know is this something we have to do every time there is a upgrade?
Deleting the RESX file may prevent some issues as they may contain serialized data for data sources and resources used in reports. Still a small change in the report designer will re-create the RESX file.
In general, on installing new version of Telerik Reporting, you need to run the Upgrade Wizard to update reports (project references, configuration and resx settings).
I hope this helps.
Regards,
Stef
Telerik
Hello Stef,
This is regarding the Value cannot be null....Designer no longer displays...issue. I manually updated Telerik.Reporting.dll from 7.2.13.1016 to 10.1.16.504 - I have done all things mentioned above except running the Upgrade Wizard - because I am nervous that other aspects of the solution will be impacted and everything else works well. I inherited this project and it is rather large, and last time I ran through the wizard it did not go well and so I rolled everything back. Is it possible to run the UW on just the Reporting project in my solution and leave other Projects alone? I've attached a screen shot of the development machine I have to use. It is VS 2010 and I apologize for the size but that is what I was given to work on.
Hello Stef,
This is regarding the Value cannot be null....Designer no longer displays...issue. I manually updated Telerik.Reporting.dll from 7.2.13.1016 to 10.1.16.504 - I have done all things mentioned above except running the Upgrade Wizard - because I am nervous that other aspects of the solution will be impacted and everything else works well. I inherited this project and it is rather large, and last time I ran through the wizard it did not go well and so I rolled everything back. Is it possible to run the UW on just the Reporting project in my solution and leave other Projects alone? I've attached a screen shot of the development machine I have to use. It is VS 2010 and I apologize for the size but that is what I was given to work on.
You can check the answer in the support ticket 1046794 you opened on the same question.
For other community members interested in this topic below is the reply from the support ticket:
"This error occurs if the projects having references to Telerik Reporting are not upgraded. Please check if you run successfully the Upgrade Wizard and restart Visual Studio - Upgrading Telerik Reporting Projects.
Note, that Upgrade Wizard will only update Telerik Reporting assemblies to the selected version, the project’s config file, / and resource files () with references to the Telerik Reporting assemblies.
When you start the Wizard there is also an option to choose which project needs to be updated (step 2 of the Wizard Upgrade Settings).
Also, to be used in the Designer the report must have a default parameterless constructor. In the provided code, the report has only a custom constructor used for passing parameters to report. In general, we do not recommend to use custom constructors. Instead, you can pass values for parameters via Report Source Parameters collection which is mapped by key to parameters.
Also, check if all the external assemblies (with data object, user functions) are references in the reports project."
Let's continue our discussion in one of the threads to keep a better track of the exchanged information.
Regards,
Katia
Telerik
Hello.
I also saw an identical error to this in a Telerik WinForms project, when trying to open a form in the Designer. For me, it came immediately after changing the referenced Telerik DLLs to an older version of Telerik. (Not ideal, but for various reasons I had to make my plugin code match the libraries used by an older product.)
With the Telerik downgrade, none of the ideas suggested here solved it for me (unless I missed it), even after a restart of Visual Studio and a re-build of the project. If it helps anyone, I found that the issue was resolved once I cleaned up the project by deleting everything in the obj/ and bin/ folders.
I guess the build process was failing to overwrite the newer versions of those DLLs with older versions, or something like that, which presumably prevented the designer from working properly.
I had the same problem - I had an older version of Telerik on my machine, and I pulled an SVN project that was built on a machine with a newer version. When I opened any form I got the 'null instance' error.
The solution for me was to run the Telerik Upgrade Wizard. After that, no problems.
Hello. (Earlier Mike here again, from the Sep 2017 post.)
I have to say we've found it challenging managing different versions of Telerik for reasons like this. Are there any guidelines around for how to handle Telerik versioning between multiple developers and multiple products?
At a glance our scenario is that we have multiple products and often have to maintain older releases of some products, which might have been built with earlier Telerik versions. Even if the specific referenced Telerik DLLs are included in the source control for building that older branch of the product against, the VS designer fails to work, for reasons of this thread, because we might have a different version installed on the developer machine... which usually means a tedious figuring out which Telerik version is needed on the machine, finding it and installing it, possibly after uninstalling an existing version... often for what might just be a minor bugfix.
Sometimes we also just run into problems of one developer updating Telerik when another doesn't, and hilarity ensues. We could possibly look at a policy of just telling everyone to install the latest version all the time (except when they can't for the earlier reasons), but that causes other problems as we sometimes develop on machines which, for various reasons, involve a lot of parallel snapshots. (Upgrading frequently is tedious if it has to be done on every snapshot, and then again every few months for each of them.)
Thanks for any tips.
Mike.
The best option I see would be to update Telerik Reporting installations used by all developers in your team to a single version and update the version used by the application as well. When there are multiple developers working on the reporting part and all have different versions of the product it will make the project sharing harder due to the issues related to version mismatch.
Regards,
Katia
Progress Telerik
August of 2019 and this is still a problem that makes this Telerik Controls unusable.
Bought this tool set 2 years ago, have used it in one project in those 2 years.
That project is a disaster, every time we open it, the Telerik Controls are trashed and we spend more time trying to fix Telerik bugs than we do writing out own code.