Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to determine protection level. DTS:ProtectionLevel attribute was not found.. (Path: ) #22

Open
dlukyanov opened this issue Mar 29, 2018 · 2 comments

Comments

@dlukyanov
Copy link

SSISBuild downloaded with nuget command

nuget install SSISBuild -ExcludeVersion

command:

ssisbuild.exe StageSSIS.dtproj -Configuration Dev1-SQL -ProtectionLevel DontSaveSensitive

results:

SSIS Build Engine
Copyright (c) 2017 Roman Tumaykin

Executing SSIS Build with the following arguments:
Project File: C:\git\BusinessIntelligenceProjects\StageSSIS\StageSSIS.dtproj
-ProtectionLevel: DontSaveSensitive
-Configuration: Dev1-SQL

Project parameters:
-------------------------------------------------------------------------------
Starting build. Loading project files from C:\git\BusinessIntelligenceProjects\StageSSIS\StageSSIS.dtproj.
ERROR: Failed to determine protection level. DTS:ProtectionLevel attribute was not found.. (Path: )

the project file does not have namespace prefix DTS:

<SSIS:Project SSIS:ProtectionLevel="EncryptSensitiveWithPassword" xmlns:SSIS="www.microsoft.com/SqlServer/SSIS">
...
@owerkop
Copy link

owerkop commented Nov 27, 2018

You're wrong. This errors is caused by bad configuration of ProtectionLevel for packages.
If You alread set in dtproj SSIS:ProtectionLevel and DTS:ProtectionLevel in all *.dtsx files perhaps there are missing some settings in dtproj.

I had to set proper value in the dtproj project file for each SSIS package:

<SSIS:Property SSIS:Name="ProtectionLevel">0</SSIS:Property>

Value of the ProtectionLevel is a number value of the DTSProtectionLevel Enum
https://docs.microsoft.com/en-us/dotnet/api/microsoft.sqlserver.dts.runtime.dtsprotectionlevel

@NowinskiK
Copy link

I have the same issue. After a few hours, I found the root cause.
I didn't have a definition of ProtectionLevel in some packages:
DTS:ProtectionLevel="0"
Unfortunately, ssis-build module is not helping here not telling what's the path of 'wrong' package.
This is a bug.
If you have plenty of them in the project - best of luck...

NowinskiK pushed a commit to NowinskiK/ssis-build that referenced this issue Jun 6, 2019
…erKey) when it's not explicitly defined in package file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants