For some reason, Microsoft Visual Studio 2013 keeps giving me the following error:
Not implemented (Exception from HRESULT: x080004001 (E_NOTIMPL))
I receive this error when attempting to make a new SQL table. The way I reproduce this error is by doing the following:
I am attempting to add a new table to a SQL Server 2014 database. I have Microsoft Visual Studio Professional 2013 Version 12.0.31101.00 Update 4
This only happens when Adding a table or opening the definition. I can view data without any errors. I have also tried repairing Visual Studio 2013 with no luck.
EDIT:
Now, When I don't open a project and try adding a table, I am getting:
"The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))".
Found the answer here
Clear out the temporary framework files for your project in:
For Windows 7, the path is: C:\Users\[username]\AppData\Local\Temp\Temporary ASP.NET Files\
For 64 bit systems with 'Framework' in the path the full path is: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\
Usually E_INVALIDARG
returns when there is an application level on with the parameter for example out of range issue or parameter that collide with each other.
As I found; You may receive an E_INVALIDARG
error message when you try to create an instance of a .NET serviced component, You need to modify your Registry of Windows.
Make a new backup of your
Registry of Windows
.
Source: A Microsoft .NET serviced component that is deployed in the COM+ environment.
Source event: An activation request.
Side event : Destroying an old instance of the serviced component.
Side sources : All the other resources that are associated with the old serviced component.
Causes :
Resolution : Downloading the Microsoft .NET Framework 1.1 Service Pack 1.
Registry Edits :
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\System.EnterpriseServices]
"DisableAsyncFinalization"=dword:00000001
I ended up formatting and re-installing Windows which fixed the problem when I installed Visual Studio 2013 again. Repairing Visual Studio did not fix the problem but I'm not sure if re-installing visual studio would have worked.
User contributions licensed under CC BY-SA 3.0