"DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user '
This error is interesting in that the user name and credentials are entered correct in the SSIS Connection but you still get this error.
There are whole lot of reasons you may find on Internet. But no one sequence worked for me. What made this go away in my package was:
a.) Set "DelayValidation" to true, as I was seeking connection at run time from database/xml file.
b.) Set "Protection Level" property to "EncryptSensitiveWithPassword" and provide a package password.
I found a good explanation for various causes, though unrelated to my issue, here:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/11/09/ssis-error-code-dts-e-oledberror-an-ole-db-error-has-occurred-reasons-and-troubleshooting.aspx
2 comments:
I came across the same issue. Solved it by using the "EncryptSensitiveWithPassword" option. I didn't have to use "DelayValidation" though.
Thanks for posting!
There are actually a number of details like that to take into consideration. That may be a nice point to carry up. I offer the thoughts above as common inspiration however clearly there are questions like the one you bring up where the most important thing will probably be working in sincere good faith. I don?t know if finest practices have emerged round issues like that, however I am certain that your job is clearly identified as a good game. Each girls and boys feel the influence of just a moment’s pleasure, for the remainder of their lives. online casino gambling
Post a Comment