-
Notifications
You must be signed in to change notification settings - Fork 27
Error in SSIS Design Warnings Scanner #22
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
Comments
Thanks for reporting. Do you have any custom components in your data flow? In project settings what version of SSIS are you deploying to? I'm Help... About Microsoft Visual Studio what version of the SSIS is installed? |
Deployment Target is SQL 2012. I copied Info from visual Studio versions below: Microsoft Visual Studio Professional 2017 Installed Version: Professional Microsoft Visual Studio Tools for Applications 2017 Visual Basic 2017 Visual C# 2017 Visual C++ 2017 Visual F# 4.1 Application Insights Tools for Visual Studio Package 8.10.01106.1 ASP.NET and Web Tools 2017 15.0.31125.0 ASP.NET Core Razor Language Services 1.0 ASP.NET Web Frameworks and Tools 2017 5.2.51007.0 Azure App Service Tools v3.0.0 15.0.31106.0 Azure Data Lake Node 1.0 Azure Data Lake Tools for Visual Studio 2.3.1000.1 Azure Data Lake Tools for Visual Studio 2.3.1000.1 BI Developer Extensions 2017 Extension 2.1.1 Child Process Debugging Power Tool 1.0 Common Azure Tools 1.10 Fabric.DiagnosticEvents 1.0 GitHub.VisualStudio 2.3.6.391 JavaScript Language Service 2.0 JetBrains ReSharper Ultimate 2017.3.1 Build 111.0.20171221.145902 Microsoft Azure HDInsight Azure Node 2.3.1000.1 Microsoft Azure Hive Query Language Service 2.3.1000.1 Microsoft Azure Service Fabric Tools for Visual Studio 1.8 Microsoft Azure Stream Analytics Language Service 2.3.1000.1 Microsoft Azure Stream Analytics Node 1.0 Microsoft Azure Tools 2.9 Microsoft Continuous Delivery Tools for Visual Studio 0.3 Microsoft JVM Debugger 1.0 Microsoft MI-Based Debugger 1.0 Microsoft Visual C++ Wizards 1.0 Microsoft Visual Studio Tools for Containers 1.1 Microsoft Visual Studio VC Package 1.0 NuGet Package Manager 4.5.0 Project 1.0 Redgate SQL Prompt 1.0 RegexTester 1.0 Show Missing Files 1.0 SQL Server Analysis Services 14.0.1016.240 SQL Server Data Tools 15.1.61710.120 SQL Server Integration Services SQL Server Reporting Services 14.0.1016.233 SsmsVsIntegration 1.0 ToolWindowHostedEditor 1.0 TypeScript Tools 15.5.11025.1 Visual Studio Code Debug Adapter Host Package 1.0 Web Extension Pack 2017 15.0.4 WebJobs Tools v1.0.0 15.0.31201.0 |
Regarding Custom components, the answer is no. but we do use Script Task(s) and Script Component(s). |
@DocGitHub is this still an issue with the latest 2.3.1 release of BI Developer Extensions? |
We whiffed on the test case for the parameter window feature. We will put that on the list to fix up for the next release. Thanks for reporting. |
Is the connection manager in question a project connection manager or package connection manager? That’s one scenario I suspect we haven’t tested for configuration loading. |
2 Other connections are on Project level, the connection in question is a
package connection.
It was used in a disabled configuration only used in Package deployment
mode....still get the error on line 202 after removing dbConfig and old
package config
Op di 14 mei 2019 om 13:35 schreef Greg Galloway <notifications@github.com>:
… Is the connection manager in question a project connection manager or
package connection manager? That’s one scenario I suspect we haven’t tested
for configuration loading.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#22?email_source=notifications&email_token=AIIUCVWLSRHG5X5NYPEBW7DPVKPYBA5CNFSM4ENAZR52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVLGFNA#issuecomment-492200628>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIIUCVRTAEYUIOOXGE54HFTPVKPYBANCNFSM4ENAZR5Q>
.
|
Visual Studio 2017, bi developer extensions 2.1.1
See error in attached screen:

The text was updated successfully, but these errors were encountered: