none
laptop dtsconfig causing azure ssis runtime error RRS feed

  • Question

  • Hi,

         This is really odd and I can replicate this.   I start with a vs 2015 built ssis package.  We have recently upgraded to vs 2017 enterprise, ssdt 15.1.x, ssis 15.x  if I change the label on a task and move the .dtsx file to azure, it runs, so a vs 2017 built .dtsx file runs on our azure.   If I delete one of the current dtsconfigs and add a new one, move that package to azure and run it, it fails with a teradata login error.  Can anyone think of a way that specifying a laptop dtsconfig file can cause an azure runtime execution error?  The dtsconfig files in the azure environment are completely different than our laptop dtsconfig files, we've used them in 1000's of executions so they seem correct.

         In my mind a dtsconfig file just sets variable values for a given ssis session or execution.  A dtsconfig file does not affect the executing logic or code in a .dtsx package.   How specifying a dtsconfig file (I don't even exit and get back in to get the values from the laptop dtsconfig) can affect the azure runtime environment is beyond me.

         Our Azure is the in house kind of Azure, probably pretty old (a couple of years old).

    Friday, June 26, 2020 5:27 PM

All replies

  • Do your configuration files have login information for Teradata connections? Maybe the package can't access the configuration file on the laptop and is using the login information specified at design time?

    If my reply solves your issue, please mark it as the answer

    Friday, June 26, 2020 5:43 PM
  • Jim,   We use what might be called a password vault so DelayValidation is incredibly important.  SSIS jumping the gun on the Teradata login is what is probably causing the error, but why would a dtsconfig file specified at the laptop level affect that?   I would point out that all the Teradata connections worked successfully in the azure environment in the prior execution where I only changed the Task name.


    • Edited by etlman Friday, June 26, 2020 5:56 PM
    Friday, June 26, 2020 5:49 PM
  • Hi eltman,

    The config file might not work if changing the task name, have you tried to delete and recreate the config file?

    Appreciate it if there is anything new to update. If you find any post in the thread is helpful, you could kindly mark it as answer. This would benefit the community, and also encourage the community member to keep working on your issues.

    Best Regards,

    Lily


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Monday, June 29, 2020 6:38 AM
  • Lily,

         There is definitely one dtsconfig file involved here that seems like it is causing problems.  In defense of that dtsconfig file, it works, I can toggle between ldap and td2 teradata id's with that dtsconfig file.   We are now allowed to "Reuse Existing" for dtsconfig so we reuse existing dtsconfig's a lot here.   But I understand what you are saying.   Create a dtsconfig within this package and then copy all the variable information into that and see if that fixes the problem.   I will try that but I have to make sure I have a good test harness for all of this.

    Monday, June 29, 2020 8:35 PM
  • Hi eltman,

    Thank you for your reply. If you find a solution, it's so kind of you to come back and share it with us. By doing so, it will benefit all community members who are having this similar issue. 

    Best Regards,

    Lily


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Tuesday, June 30, 2020 5:58 AM