Dears,
in SSIS 2008 when I try to create new package I get following error :
Error creating package
Failed to save package file "C:\Users\Mehdi\AppData\Local\Temp\tmpA99D.tmp" with error 0x8002801D "Library not registered.
I registered both MSXML4.dll and MSXML6.dll but I still have problem.
I was able to fix my problem doing the following steps:
Repair MSXML 6.0 Parser from Add/Remove Programs
Re-Register the the msxml6.dll and msxml3.dll - http://support.microsoft.com/kb/2416767 (See Resolution Area)
Use the following procedure to resolve the problem:
Manually re-register the MSXML6 Dlls on the system where you are experiencing the problem by executing the following commands at a
command prompt (you need to run these commands from an Administrative
Command prompt on the newer operating systems.)
On a 32-bit machine:
regsvr32 %windir%\system32\msxml6.dll
regsvr32 %windir%\system32\msxml3.dll
I am running WindowsXP Professional, Business Intelligence Studio (Visual Studio) 2008, Microsoft SQLServer 2008 R2
You need to run regsvr on following files (regsvr32 msxml3.dll" & regsvr32 msxml6.dll)
See below link for more details:
http://www.sqlservercentral.com/Forums/Topic947330-391-1.aspx#bm947604
You could also try 'repairing' the MSXML6 installation from add/remove programs, or reinstalling SQL Server
As suggested in the following article:
http://www.bigresource.com/Tracker/Track-ms_sql-SORjbTEz/
I would also try restarting some of the services, and then applying any latest patches as suggested here:
http://www.sqlservercentral.com/Forums/Topic514859-148-1.aspx#bm514865
finally I had to reinstall my windows.
and it solved my issue. I know it's not a good solution :(
Related
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.
I am using
Visual studio 2017, version 15.9.11
MySQL for visual studio 1.2.9
MySQL-8.0.18-win64
mySQL-connector-net-8.0.18-noinstall
If I try to add a connection to a project via Data Sources > Database > Dataset, and set the connection with the right server name, user name, and password, and then select one table, select options and click Next I get the following error
"Failed to open a connection to the database Cannot obtain
provider factory for data provider named 'MySql.Data.MySQLClient'.Check the connection and try again."
Also, when I connect to a local MySQL database using Tools > Connect to database... and I create the connection, which successfully seems to be done in the server explorer, and then in the same server explorer panel, if I go Data Connections > localhost > tables > double-click on the table, this is the error I get:
Cannot create a design window for the selected object.
How can I solve this?
The problem
As I said in my question I had mysql-connector-net-8.0.18-noinstall extracted. I tend to extract binaries instead of installing things. Don't really have a good reason for this behavior.
After checking Vignesh solution and before uninstalling anything, I decided to give a try to the mysql-installer-community-8.0.18.0.msi installer, since I had the mysql-connector-net-8.0.18-noinstall extracted in one folder and then I added a reference in the project, which was not working. Perhaps there was a way to use this folder (binaries, global references, etc) properly, but I couldn't find one. Maybe I was the problem.
The solution
However, after installing via the msi file, everything is working now. So if you ran into this problem, having similar versions than the ones I'm using and had the no-install version extracted, you can safely close Visual Studio, and install the same version via the msi installer, this worked for me! Worst case scenario, you can uninstall it via the same msi file, and try Vignesh's or other's solution.
This error will be fixed by uninstalling Connector current version and installing Connector 6.9.8
Download Connector 6.9.8
Visual Studio 2015: Visual Studio 2015 Community + DotNet Connector 6.9.8 + MySQL for Visual Studio 2.0.3 is working combination.
Visual Studio 2017: Visual Studio 2017 Community + DotNet Connector 6.9.8 + MySQL for Visual Studio 1.2.7 is working.
I have a domain controller on which I have SQL Server installed. All databases are setup to automatically backup everyday. Recently the error found in the footer started popping up whenever I login to an instance of the SQL Server Management Studio, and hence it disabled the automated backups. I searched the internet for a solution and the majority of the solutions were to "format" the pc! which I can't due to many complications.
I read somewhere on microsoft support blog that the solution was to "Uninstall SP1"
What SP1? can anyone help?
The error
TITLE: Microsoft SQL Server Management Studio
The type initializer for 'Microsoft.SqlServer.Management.Dmf.PolicyStore' threw an exception. (Microsoft.SqlServer.Dmf)
ADDITIONAL INFORMATION:
Could not load file or assembly 'Microsoft.SqlServer.Diagnostics.STrace, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. (Microsoft.SqlServer.Dmf)
Instead of formatting your PC, just fire up the installer package for your version of SQL Server (in my case, I accidentally uninstalled VS 2010 Shell, which it SQL Server Management Studio needs).
From the SQL Server Installation Center:
Maintenance Section
Repair
That should fix any problems you're having.
I had this problem when I uninstalled SQL Server Management Studio. Reinstalling fixed.
Just install the Shared Management Objects MSI file (32 or 64-bit based on your system architecture) It'll surely fix this issue.
We've got a a series of SQL Server Integration Services packages that copy data from a few MS Access databases into a SQL Server 2008 database. There is one parent package that calls the various sub-packages, and that parent package is initiated by a user that runs a .bat file that executes the package like so:
dtexec /f "\\networkshare\package.dtsx" /CHECKPOINTING OFF /REPORTING EWCDI
This has worked fine for several years. Our IT department has begun upgrading our 32-bit Windows XP workstations to 64-bit Windows 7 and since they've upgraded the workstations of these users, the package has been failing, giving the error
-1071607037,0x,SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR. The requested OLE DB provider MICROSOFT.JET.OLEDB.4.0 is not registered -- perhaps no 64-bit provider is available. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
My workstation has not yet been upgraded from Windows XP and I'm still able to run the packages but my ability to postpone the upgrade is running out and I need to figure out a solution as soon as possible. I've found many articles and posts related to this in my efforts to resolve the issue. Among the things I've tried are:
After ensuring that the users had the Client Tools and Business Intelligence Development Studio installed and that the path is valid, changing the contents of the .bat file to specifically reference “C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dtexec.exe” in the hope that the 32-bit JET provider would be used
Researched the Run64BitRuntime setting but this appears to only have an effect while debugging and won't help me
Researched adding the /X86 flag to the command line but according to the MSDN article on dtexec, this only has an effect if the SQL Server Agent is running the task
The last thing I've tried was to install the Microsoft Access Database Engine 2010 Redistributable and change the connection string from "Provider=Microsoft.Jet.OLEDB.4.0;" to "Provider=Microsoft.ACE.OLEDB.12.0;". I can't seem to get off the ground with this one. If I try to create a new connection in BIDS and set the provider to "Microsoft Office 12.0 Access Database Engine OLE DB Provider" and test the connection, I get the error "Test connection failed because of an error in initializing provider. Unspecified error".
I'm just about at a loss for what else I can try and looking for any help at all, even if it's trying the things I've already tried, maybe I've configured something wrong while trying them originally, not sure.
Any help would be immensely appreciated!
In SQL Agent job or by just executing the package by itself there is a tab called "Execution options", you can select "Use 32 bit runtime" option
By default, SQL Server puts the 64-bit version of DTEXEC in the path. The 32-bit version should be located somewhere like C:\Program Files(x86)\Microsoft SQL Server\100\DTS\Binn and would need to be called directly. I had the same issue with the ACE drivers and Excel files.
See this for more information.
I was able to run it successfully by changing debugging setting in project property page. Property to change is Run64BitRuntime -> set this to false.
I have moved my packages to another server. Now on that server when I am executing my packages on visual studio then it is working fine. But when I am deploying the same package and try to execute it both via integration services engine or SQL Job.. I am getting below error
An error occurred with the following error message: "Cannot bulk load. The file "C:\ABC\PQR\XYZ\myFile.txt" does not exist.".
Edit
Somehow that issue is resolved but now I am into one more issue
Packages installed in MSDB is working fine when I am clicking on Run Package. But when I am creating SQL Agent job for the same packages it is not working.
I have tried setting "rely on server encryption" but no luck :-(
I would suggest to check whether folder C:\ABC\PQR\XYZ\ have read permissions for an account used to run SQL Agent jobs.
If this is **C:\ABC\PQR\XYZ** mapped drive connection then use the UNC path it worked fine through the server agent.