I think I have found an alternative solution to this frustrating issue, no matter what and how you try reinstalling, changing registry keys or renaming visual studio folders in application data directory, it might not still solve the issue. I have found out that the issue is only peculiar to the user account in which the error occurred, so what you simply do is to run visual studio on another account, test that you could add a new connection/datasources then you good to go!!! Then u can simply delete that error account and create a new one. Hope this helps!
3 comments:
Didn't work for me - had to delete existing data connections then it let me add a new one
Hi guys,
I think I have found an alternative solution to this frustrating issue, no matter what and how you try reinstalling, changing registry keys or renaming visual studio folders in application data directory, it might not still solve the issue. I have found out that the issue is only peculiar to the user account in which the error occurred, so what you simply do is to run visual studio on another account, test that you could add a new connection/datasources then you good to go!!! Then u can simply delete that error account and create a new one. Hope this helps!
Make sure the new account you are using has an administrator rights and privileges
Post a Comment