Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.

New answers tagged

1

It seems that I solved my own problem. I do not know exactly what cause it, but here is what i did. It turns out that only one of the projects that we have had the problem I described. That project happened to have multiple packages included. For testing I removed all packages from the project and added one at the time, built the project after each step and ...


2

Here is what I found in regards to this issue. First, I exported the broken package from the server after importing it. I also exported the working package from the server after importing it. I compared the two files side by side and quickly discovered that the script within our package where the errors occurred was missing it's binary data in the ...


1

Does SQL Server Native Client 11.0 exist on the server that is running those packages? What are the arguments being passed to dtexec? If it doesn't have at least /rep ewi add that in there and then kick off the package. What I expect you'll see and why I'm putting this down as an answer. In the output that follows from requesting (Error, Warning, ...


0

Try Setting the ProtectionLevel to "EncryptSensitiveWithPassword" and setting a password in the "PackagePassword" section of the package properties (F4 key). This got me passed the login error for the dtsx package when executing it using Visual Studio.


0

As discussed in the below: Solution: Go to https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftAnalysisServicesModelingProjects and install the latest version, it has a fix in there to resolve this issue. Reference: https://developercommunity.visualstudio.com/content/problem/745991/could-not-load-file-or-assembly-microsoftdatawareh....


Top 50 recent answers are included