Home > ssis error code dts_e_oledberror

How do you fix an SSIS error code DTS_E_OLEDBERROR?

Alton Alexander
By Alton AlexanderUpdated on June 4th, 2022

The SSIS error code DTS_E_OLEDBERROR occurs when there is an OLE DB error. This error can occur for many reasons, including the following:

-The provider did not return a connection string.

-The provider did not return a provider name.

-The connection string is not valid.

-The provider name is not valid.

-The provider is not registered.

-The OLEDB service is not installed.

-The provider is not specified in the connection string.

-The connection string uses an OLEDB provider that is not installed on the computer.

You are here because you have a question about:

  • ssis error code 0x80004005
  • ssis error code dts_e_oledberror

1. Check that the SQL Server is running and that you have the correct login information

The first step is to ensure that SQL Server is running. To do this, open SQL Server Management Studio (SSMS). In SSMS, connect to the server where SQL Server is installed. In the Connections pane, right-click the server name and select Properties. In the Properties window, click the Security tab. In the Security tab, under Server name, click the Login button. In the Login window, enter the correct login information. If the login information is correct, you will see a message stating that the server is running. If the login information is incorrect, you will see an error message stating that the server cannot be accessed. Next, you need to verify that you have the correct login information for the account that is running SSMS. To do this, open the Windows Security Settings for the computer on which SSMS is installed. In the Windows Security Settings, under Local Policies, click User Rights Assignment. In the User Rights Assignment window, under Local Users and Groups, click the Edit button. In the Edit User Rights Assignment window, under USERS, click the Add button. In the Add User Rights Assignment window, enter the appropriate login information. If the login information is correct, you will see a message stating that the user rights assignment has been successful. If the login information is incorrect, you will see an error message stating that the user rights assignment cannot be completed.

2. Verify that the SSIS service is running

  1. Verify that the SSIS service is running.
  2. Check the SSIS service log for errors.
  3. Verify that the SSIS service is using the correct ports.
  4. Verify that the SSIS service is running on the correct computer.
  5. Verify that the SSIS service is using the correct installation.

3. Make sure that you are using the correct version of SQL Server

  1. Open SQL Server Management Studio and connect to the SQL Server instance where the problem is occurring.
  2. Right-click on the database that is experiencing the issue and select "Troubleshoot Database".
  3. In the "Troubleshooting Options" window, select "Check Database for Errors".
  4. If the error is detected, select the correct fix from the list and click on " Apply " to apply the fix.
  5. If the error is not detected, then the database is probably correct and no fix is required.

4. Try changing the "Run64BitRuntime" property to false

  1. Open the Configuration Manager console
  2. In the console tree, under Configuration Manager, select Sites and Services
  3. In the Sites and Services pane, select the site where you want to change the property
  4. On the General tab, under Site Settings, select Properties
  5. In the Properties pane, under the Configuration Manager section, select the Run64BitRuntime property
  6. In the Run64BitRuntime property, set the value to false
  7. Click OK to save the change

Some users might also have success with the following opitons:

  1. Try changing the ProtectionLevel property to DontSaveSensitive.
  2. Try changing the value of the MaxBufferSize property.
  3. Try changing the value of the MaxBufferRows property.
  4. Try changing the value of the RetainSameConnection property to true.
  5. Try using a different OLEDB provider.