Cause. This is a very common mistake when setting up a package in a 64-bit environment, and the package often uses Microsoft providers that are not normally available in a 64-bit environment (such as the Microsoft JET provider and Microsoft Professional for Oracle).
First published on MSDN November 9, 2009.
This will be a very common mistake and can happen for a number of reasons. I document everything that is most often associated with them based on case studies. See and description of some error codes for each of the personal errors.
“DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. OLE DB entry available.
A hexadecimal value for which the error number is 0x80040E4D.
If you create a package on your personal local machine and create a bandwidth service there, you have the option to store the password for a particular connection. However, this method encrypts this password by default, so it can only be decrypted if you actually run the package on the same machine with the same account. This only applies if the connection manager is using SQL authentication or connecting to a database.A data path that does not support Integrated Windows Authentication (such as Oracle).
So in the scenario above, if the package is deployed to a remote SQL server with a remote key, it will fail with a “Connection Failed..” error because this element cannot decrypt the entire password. (Note: it works fine if deployed on local sql server.)
What is OLE DB error?
OLE DB Error: OLE DB or ODBC error: A network-related error occurred while connecting to SQL Server, possibly instance-specific. Server not found or unavailable. Make sure the instance name is the most appropriate and that SQL Server is packaged to resolve remoteconnections.
To eliminate irritation, you must choose one of three options:
Step 1: Modify all login handlers included in the package to use OS authentication.
Note. This is not possible when communicating with additional data sources that do not provide Windows authentication, such as Oracle.
2. Encrypt the “EncryptSensitiveWithPassword” package with “EncryptAllWithPassword” and provide the package password whenever a user wants to change/tamper with your package.
3. Create configuration content to provide connection information duringpackage execution time.
Procedure: Adding a package configuration:
Setting your own protection level for packages:
Is SSIS part of SQL Server?
SSIS stands for SQL Server Integration Services. SSIS is a Microsoft SQL Server file software task used for many computer file transfer tasks. It is essentially dts_e_oledberror an ole db error has occurred ETL tool that is part of the Microsoft Business Intelligence suite and is mostly preferred for data integration.
0xC0202009 in package, connection manager ‘
Result: 0x80040154 Description: “Class not registered.”
The hexadecimal value of this skill’s error number is 0x80040154.
This is a very common mistake when a package is deployed to this 64-bit environment and the package only uses Microsoft providers that are not only available in the 64-bit environment (eg.Mer, Microsoft JET Provider, and Microsoft Provider for Oracle).
The Integration Design Services environment is typically a 32-bit environment, and you only encounter 32-bit providers when developing a package. So you can only configure the connection manager for a specific 64-bit provider if you have the 32-bit version of the same provider installed. The correct version is implemented at runtime, and it doesn’t matter which 32-bit version you specify to the vendor at design time. The 64-bit version of the provider may work even if the field is running in Business Intelligence Development Studio. Both provider versions have the same identifier. To specify that the Integration Services runtime uses the available 64-bit version of the entire provider, set the Run64BitRuntime field of the Integration Services project. If the Run64BitRuntime property is set to true, the runtime will find and use the 64-bit provider; If Run64BitRuntime is set to false, the runtime will find the 32-bit provider and help you use it.
What is error code in SSIS?
When an error occurs in SQL Server Integration Services (SSIS) data delivery, you can pass the error to the error stream. The system will provide you with the appropriate error code and the ID of the column that caused the error. However, for our logging purposes, we also need a column name, such as
If the package is deployed as a task to a 64-bit SQL Server, it will surely fail with the above error because it contains the 64-bit DTExec.exe (C:\Program Files\Microsoft Sql Server\DTS\Binn\DTExec. exe) did the job and will certainly be able to recognize 32-bit providers in general.
1. If a particular package does not work as a task, we can offer two solutions:
A) Edit the job step of the Disappointment package, change “Type” to “Operating System” (cmdExec) and manually edit the query string to run via 32-BIT DTExec.exe. Before ordering, you must specify the full path generated by 32-bit DTExec.exe (usually, if it is not paid, the path will be specified during installation at (C:\Program Files (x86)\Microsoft Sql Server \DTS\Binn\DTExec.exe) . ).