Troubleshooting Dts_e_oledberror An OLE DB Error Has Occurred

Troubleshooting Dts_e_oledberror An OLE DB Error Has Occurred

Fix PC Errors in Minutes

  • 1. Download and install ASR Pro
  • 2. Launch the application and select your language
  • 3. Follow the on-screen instructions to start a scan of your computer
  • Click here to get a complimentary download that will help you speed up your PC.

    Several readers reported last week that they encountered dts_e_oledberror, an Ole DB error.

    First published on MSDN Nov 9, 2009

    This is a seemingly very simple error, and it can appear at once for a number of reasons. Compared to many of them, I document mostly based on case studies. See the number and error codes for each individual error.

    A:

    Error:

    “DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. OLE DB entry available. Source: Microsoft SQL Native Client. Result: Description: 0x80040e4d “. Connection failed for user ““. ”

    Fix PC Errors in Minutes

    Is your computer running slow? Is it plagued with weird error messages and strange system behavior? If so, there's a good chance that you need ASR Pro. This powerful software will quickly and easily repair common Windows errors, protect your data from loss or corruption, and optimize your system for maximum performance. So don't suffer with a slow, frustrating PC any longer - download ASR Pro today!

  • 1. Download and install ASR Pro
  • 2. Launch the application and select your language
  • 3. Follow the on-screen instructions to start a scan of your computer

  • A hexadecimal number worthy of this error number implies 0x80040E4D.

    Because:

    If you create the correct package on your local machine, i.e. establish a connection, you will be able to save your password for that connection. However, this password is encrypted by default, so it can only be decrypted a few times if you run the policy on the same computer with the same account. This is only applicable ifEven if the Connection Manager uses SQL Authentication or connects to a database that does not support Integrated Windows Authentication (such as Oracle).

    So in the above scenario, I would say that if the package is undoubtedly deployed to a remote SQL server, it will fail with the error message “Connection failed ..” because it is not known how to decrypt the password. (Note: it works great when deployed to this particular local SQL server)

    Permission:

    To solve the problem, you need to choose one of the many options:

    1. Definitely change any Windows Authentication connection managers included in the package.

    Note. This is not an option, although communicating with third party data sources also does not support Windows authentication such as Oracle.

    2. Encrypt the package with “EncryptSensitiveWithPassword” or “EncryptAllWithPassword” and enter any package password whenever the user wants to change or manipulate the packagem.

    3. Create a configuration file to provide basic connection information while running packages.

    Links:

    dts_e_oledberror an ole db error has occurred

    How To: Add Package Config: Dts E Oledberror Une Erreur Ole Db S Est Produite
    Dts E Oledberror Se Ha Producido Un Error Ole Db
    Dts E Oledberror Er Is Een Ole Db Fout Opgetreden
    Dts E Oledberror Ett Ole Db Fel Har Intraffat
    Dts E Oledberror Wystapil Blad Ole Db
    Dts E Oledberror Ocorreu Um Erro Ole Db
    Dts E Oledberror Ole Db 오류가 발생했습니다
    Dts E Oledberror Ein Ole Db Fehler Ist Aufgetreten
    Dts E Oledberror Proizoshla Oshibka Ole Db
    Dts E Oledberror Si E Verificato Un Errore Db Ole