Visual Studio 2013 Error Message: 0x80004001 (E_NOTIMPL) - exception

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:
Open my project (from Team Explorer)
Open the Data Connection in Server Explorer.
Right click on Tables and click Add New Table
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\
http://www.solutioncottage.com/ShowSolution.aspx?solID=59

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 :
This destruction may not be successful or
COM+ may not clean up the associated resources.
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.

Related

Why do I get the error: "cannot communicate with the debug host process" when attempting to execute an SSIS package?

I create a new package in SSIS and when I try to run the package, SSIS returns the following error (displayed in a Visual Studio Error Dialog):
"Cannot communicate with the debug host process. The IDtsHost interface is not registered. (Microsoft.DataTransformationServices.VsIntegration"
Environment: VS 2019 with newest SSIS Extension Installed. The package appears to be created correctly and the build succeeds.
The error happens even if the package is trivial "hello world" type of package.
I found no solution to this after a fairly extensive search.
Thanks to EmersioN (https://stackoverflow.com/users/707267/emersion) for the solution. The problem in this case was the selected targeted version of SQL Server. My project was configured to target "SQL Server 2017", but was connected to a server running SQL Server 2012.
If you're seeing this error, this may be the reason.
Go to the properties page of the Integration Services project that contains the affected package. In the Property Pages dialog, navigate to Configuration Properties > General. Under the property group, Deployment Target Version, in the TargetServerVersion property drop-down, select the SQL Server version that matches the one you're connected to.
I just came across this as well in VS2019 SSDT. In my case it was a working SSIS package that after going to sleep for the night, the machine woke up and wouldn't execute the same scripts. These were my steps. Hope they help you or someone else who stumbles across this.
Open each connection within the script, Test Connection and Save
Clean the solution
Rebuild the solution
My context
Working through an SSIS tutorial using SQL Server 2019 Developer (v15.0.2080.9) and VS2019 Community (v16.11.9) to create packages using SSDT (SSIS Projects v3.15).
Packages in VS have executed without issue in the past. I then upgraded my machine from Windows 10 Pro to 11. Now, when running the same - possibly any - package I get the following error:
===================================
Failed to start project (Microsoft Visual Studio)
===================================
Cannot create a debug host for the package. (Microsoft.DataTransformationServices.VsIntegration)
------------------------------
Program Location:
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.LaunchVsDebugger(Boolean isRemoteTest, IVsDebugger iVsDebugger, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.ValidateAndRunDebugger(Int32 flags, IOutputWindow outputWindow, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, ProjectItem startupProjItem, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchActivePackage(Int32 launchOptions)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.Launch(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
===================================
Cannot communicate with the debug host process. The IDtsHost interface is not registered. (Microsoft.DataTransformationServices.VsIntegration)
------------------------------
Program Location:
at Microsoft.DataTransformationServices.Project.DebugEngine.DebugEngine.LaunchDtsDebugHost(Process& process, Boolean run64bit)
at Microsoft.DataTransformationServices.Project.DebugEngine.DtsProgramNode.CreateRuntimePackageInternal(IDtsHost& host, Process& process, Package& dtsPackage)
...and the package does not execute.
What was tried
I tried/checked all 3 answers posted here.
Error persists.
This VS Dev Community's post recommended upgrading the VS extension, SSIS Projects. Since I had the most recent version installed an upgrade was not applicable, so I chose the repair option from the installer.
Error persists.
I then ran a repair on the VS2019 install. This, in turn, required another repair on SSIS Projects. (I still had both installers on my machine which made this easy.)
Error persists.
This MSDN post recommended re-registering DtsDebugHost.exe, failing that, re-installing SQL Server.
I ran the DtsDebugHost.exe /regserver command.
Error persists.
My Solution
I then chose to repair my SQL Server installation instead of re-installing. This was accomplished via the SQL Server Installation Center > Maintenance > Repair option. In my case, I chose the default instance, MSSQLSERVER.
VS now runs without the error and successfully executes the package.
I couldn't say whether my solution was solely based on the repaired SQL Server instance or a combination of other things tried and my last action. So I offer the path I took in the case of the latter.
Aside: The other choices during the SQL Server repair on my system were (1) another server instance, SQLSERVER2019, and (2) "shared components". Selecting either of those may have resolved the issue as well, but I couldn't confirm that.
In Project Property, turn off Azure-Enabled as seen in the image below. Your package will execute afterwards.
I encountered this error after upgrading to Windows 11.
I referred to the post by #steveb and went straight to his solution of repairing SQL Server (SQL Server Installation Center > Maintenance > Repair), without doing any of the other steps he tried.
And that solution worked.
I'm posting this because #steveb said he was unsure if any of his previous steps had affected the ultimate solution, and in my experience they were not necessarily needed.

Visual studio 2013 deploying sql server 2008 database project

I have recently migrated my visual studio 2010 projects to 2013 but my database project looks unhappy about it. I have a TFS build definition which helps me deploy the database project and i have specified the (.sln) solution file and the .proj separate file which helps e drop the file to some location. This has been working well when I was using 2010 but right now its giving me the following error.
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I replaced .sln file with the .sqlproj and this seems to fix the failing build definition but I don't get any deployment files.
Do you have any suggestions please, this is blocking my work right now.
You need to set the environment variable VisualStudioVersion=12.0 when building from the command line if you are using VS2013. SQL Projects rely on this to detect whether to use the VS2012 (v11.0) or VS2013 (v12.0) targets file when building.
Normally when a new Visual Studio version is released there's an accompanying .Net version update that changes the default VisualStudioVersion default value, but with VS2013 this didn't happen. Hence SQL Projects (and some other resources with similar version-specific dependencies) require 12.0 to be explicitly set as the version, since 11.0 is the default.
Also when running on a build server you must have a version of Visual Studio 2013 installed that includes the SQL Server tools. Full instructions on setting up a build server are in the whitepaper and presentation on the SQL Server tools team blog.

SSDT 2012 Value does not fall within the expected range. (mscorlib)

I've got a solution with a 2012 SSIS project included. I've also got a 2010 SSIS project included. Both was working well I was duplicating functionality from one project to another. After going offline from TFS i got the following error:
Cannot show the editor for this task. (Microsoft Visual Studio)
Value does not fall within the expected range. (mscorlib)
In EventViewer I got the following error this morning:
Microsoft SSIS Service:
Registry setting specifying configuration file does not exist.
My research showed me it could be a permissions problem and I changed my Integration Services instance to use the NetworkService account.
I've also edited my registry key to reflect the correct path to the MsDtsSrvr.ini.xml file.
The error did not appear again however the problem still persists.
I've done a repair. Deleted SSDT 2012 along with the Data Tools enu and Build Utilities. Nothing helped.
PLEASE HELP!

ReportViewer problems

I've been trying to get a report running through Microsoft ReportViewer in Visual Studio 2012. Here is my situation.
I have a report (.rdl file) that was originally created through Microsoft Reporting Services running on a SQL Server 2008 R2 server.
I originally tried moving it into a VB.NET project running through Visual Studio 2005, but when I converted the .rdl file to .rdlc and tried to bring it into the VS 2005, I could not view the .rdlc file in design time. A while after that, I figured out that this was due to schema compatibility issues because of the fact that the report was created on a SQL Server 2008 server.
So then I tried creating a project through Visual Studio 2012 instead, which we also had in house. This time I was successfull at being able to view the report in design time. However after that, I ran into run time issues because I was using Version 8 of the Microsoft.ReportViewer.Winforms dll. I believe that this was also due to a schema comaptibility issue
So now, I'm trying to move up to using a newer version of the Microsoft.ReportViewer.Winforms dll (Version 11). When I remove the Version 8 and add the version 11 instead in my references, everything appears to be fine at first, no errors present. However, when I try to build my project I get the many compile errors all over the place like the following:
Type 'Microsoft.Reporting.WinForms.ReportViewer' is not defined.
The wierdest part is that if I were to remove and re-add the reference, or check one of the Microsoft.Reporting references in the Imported namespace, all the errors go away. But when I rebuild the project the errors come back, and I'm stuck.
I'm currently running the Microsoft .NET framework 4.5 on my computer, and I'm using Microsoft Visual Studio Professional 2012 as my development platform.
Any help would be appreciated
Thanks,
Doug
This might help: How to edit SSRS 2008R2 Reports in Visual Studio 2012?

How do I build report projects using Visual Studio 2012 on the command line?

I have a solution with several ".rptproj" projects that build fine when I am running the IDE, but when I try to run devenv on the command line I get the following error for each report project:
Error: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
A quick search reveals several people are having the same problem but there are no solutions yet. I have Business Intelligence for Visual Studio 2012 installed, which is how we are able to build from the IDE.
Note: there is a Microsoft Connect ticket for this problem.
Here is a workaround that I came up with out of necessity to move on. It's not very nice but it allowed me to get what I needed in CI.
To work around this issue I excluded all of my report projects from my normal Solution Configurations and added a new ReportOnly configuration that only builds the report projects. Then on my CI server I build the non-Report configurations against Visual Studio 2012 and the ReportOnly configuration against Visual Studio 2010.
Up to date conversation and additional workarounds (if discovered) can be found in the Microsoft Connect ticket.