Question Locked

In VS 2005, "Object reference not set to an instance of an object"

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

In a New Project, when Attempting to add a "database" data source, using the data source configuration wizard in VS 2005 Standard, I receive an "Object reference not set to an instance of an object" error.

This started to occur out of no where. Never experienced this problem before.

I attempted to repair/reinstall and still receive the same. I've been researching a solution for this to no avail.

What can I do to resolve this problem? Any help would be appreciated.

7 replies

by tony hopkinson

A Datasource in one of my projects that no longer existed.

look in the resources node in the soluton Explorer of the project.

I'd renamed mine and it was still there onder it's old ID.

Right click delete, problem solved.

Very annoying...

by jrmarinho

Tony, I really appreciate your reply. I managed to resolve the problem by adding a registry key.

I researched the following solution and posted it here for future reference;

1) Run regedit.exe;
2) Browse to the location "HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}" in the tree;
3) If there is a child node in the tree called "ProgID", then you are indeed experiencing a different problem - let me know if this is the case.

Otherwise, follow these steps to modify the registry:

1) Right click the node and select "New > Key";
2) Enter "ProgID" as the name;
3) Go to the main window and double click "(Default)";
4) Enter the value "MSIDXS.1";

Now if you run Visual Studio, it should be working.

This seemed to solve the problem

John

by tony hopkinson

I'll remember the tip though.

I've run into the error, which is simply a captured av,in several different places in VS. Usually when using 'my' own components, which can be soted with a recompile.

I's interesting that the IDE for writing managed code, suffers from a string of failures regularly seen in unmanaged (badly managed ?) code. :D

by tosachin4u

Hello john,

i am also facing same problem , but i am having this key present in registry.

i am using Office2007 and MS VS2005 (C#).

Please help me to solve this issue , with office 2003 ,it is working fine

thanks

sachin

by tosachin4u

Hello john,

i am also facing same problem , but i am having this key present in registry.

i am using Office2007 and MS VS2005 (C#).

Please help me to solve this issue , with office 2003 ,it is working fine

thanks

sachin

by cityus

John,
I'm running into the problem and find the ProgID is in the registry you specified. What is my problem. This is driving me crazy.
I hope that I can hear from you or anyone soon.
Ming

This discussion is closed to new replies.