Azure SQL DW External Table Issue [closed]












0















I have an external table set up in Azure SQL DW that uses a HADOOP data source pointing to wasb://..... This is something we do regularly. However, this time around we are seeing a very interesting error message when we attempt to read from the table (e.g. SELECT or as a CTAS).



I'm hoping someone here may be able to point us in the right direction.



Here is the text of the error message that we receive.



110802;An internal DMS error occurred that caused this operation to fail.


Details: Please use this Error ID when contacting your Administrator for
assistance. EID:()



NativeOdbcConnection.Open, error in OdbcConnectionCreate: SqlState: IM003,
NativeError: 160, 'Error calling: SQLDriverConnect(this->_hdbc, NULL,
(SQLWCHAR*)connectionString, SQL_NTS, NULL, 0, &cbConnStrOut,
SQL_DRIVER_NOPROMPT), SQL return code: -1 | SQL Error Info: Error <1>:
ErrorMsg: Specified driver could not be loaded due to system error 126:
The specified module could not be found. (pdwodbc, sqlncli17e.dll). |
ConnectionPooling: 1 | Error calling: pConn->Create(connectionString,
useConnectionPooling, packetSize, connectionLoginTimeout,
environmentSettings, transactionToken, transactionTokenSize, spid) |
state: FFFF, number: 151, active connections: 4', Connection String:
Driver={pdwodbc};app=TypeC01-DmsNativeWriter:DB143mpdwsvc (40084)-
ODBC;trusted_connection=yes;autotranslate=no;server=\.pipeDB.143-
b52e821913d9sqlquery;database=Distribution_1


Note that this same error does not happen using the same query tools when pointed to an alternate SQL DW instance and this error happens from any workstation or server we've tried up to this point.










share|improve this question













closed as off-topic by music2myear, Twisty Impersonator, Pimp Juice IT, Rajesh S, Anaksunaman Feb 28 at 11:40


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This question is not about computer hardware or software, within the scope defined in the help center." – music2myear, Twisty Impersonator, Pimp Juice IT, Rajesh S, Anaksunaman

If this question can be reworded to fit the rules in the help center, please edit the question.





















    0















    I have an external table set up in Azure SQL DW that uses a HADOOP data source pointing to wasb://..... This is something we do regularly. However, this time around we are seeing a very interesting error message when we attempt to read from the table (e.g. SELECT or as a CTAS).



    I'm hoping someone here may be able to point us in the right direction.



    Here is the text of the error message that we receive.



    110802;An internal DMS error occurred that caused this operation to fail.


    Details: Please use this Error ID when contacting your Administrator for
    assistance. EID:()



    NativeOdbcConnection.Open, error in OdbcConnectionCreate: SqlState: IM003,
    NativeError: 160, 'Error calling: SQLDriverConnect(this->_hdbc, NULL,
    (SQLWCHAR*)connectionString, SQL_NTS, NULL, 0, &cbConnStrOut,
    SQL_DRIVER_NOPROMPT), SQL return code: -1 | SQL Error Info: Error <1>:
    ErrorMsg: Specified driver could not be loaded due to system error 126:
    The specified module could not be found. (pdwodbc, sqlncli17e.dll). |
    ConnectionPooling: 1 | Error calling: pConn->Create(connectionString,
    useConnectionPooling, packetSize, connectionLoginTimeout,
    environmentSettings, transactionToken, transactionTokenSize, spid) |
    state: FFFF, number: 151, active connections: 4', Connection String:
    Driver={pdwodbc};app=TypeC01-DmsNativeWriter:DB143mpdwsvc (40084)-
    ODBC;trusted_connection=yes;autotranslate=no;server=\.pipeDB.143-
    b52e821913d9sqlquery;database=Distribution_1


    Note that this same error does not happen using the same query tools when pointed to an alternate SQL DW instance and this error happens from any workstation or server we've tried up to this point.










    share|improve this question













    closed as off-topic by music2myear, Twisty Impersonator, Pimp Juice IT, Rajesh S, Anaksunaman Feb 28 at 11:40


    This question appears to be off-topic. The users who voted to close gave this specific reason:


    • "This question is not about computer hardware or software, within the scope defined in the help center." – music2myear, Twisty Impersonator, Pimp Juice IT, Rajesh S, Anaksunaman

    If this question can be reworded to fit the rules in the help center, please edit the question.



















      0












      0








      0








      I have an external table set up in Azure SQL DW that uses a HADOOP data source pointing to wasb://..... This is something we do regularly. However, this time around we are seeing a very interesting error message when we attempt to read from the table (e.g. SELECT or as a CTAS).



      I'm hoping someone here may be able to point us in the right direction.



      Here is the text of the error message that we receive.



      110802;An internal DMS error occurred that caused this operation to fail.


      Details: Please use this Error ID when contacting your Administrator for
      assistance. EID:()



      NativeOdbcConnection.Open, error in OdbcConnectionCreate: SqlState: IM003,
      NativeError: 160, 'Error calling: SQLDriverConnect(this->_hdbc, NULL,
      (SQLWCHAR*)connectionString, SQL_NTS, NULL, 0, &cbConnStrOut,
      SQL_DRIVER_NOPROMPT), SQL return code: -1 | SQL Error Info: Error <1>:
      ErrorMsg: Specified driver could not be loaded due to system error 126:
      The specified module could not be found. (pdwodbc, sqlncli17e.dll). |
      ConnectionPooling: 1 | Error calling: pConn->Create(connectionString,
      useConnectionPooling, packetSize, connectionLoginTimeout,
      environmentSettings, transactionToken, transactionTokenSize, spid) |
      state: FFFF, number: 151, active connections: 4', Connection String:
      Driver={pdwodbc};app=TypeC01-DmsNativeWriter:DB143mpdwsvc (40084)-
      ODBC;trusted_connection=yes;autotranslate=no;server=\.pipeDB.143-
      b52e821913d9sqlquery;database=Distribution_1


      Note that this same error does not happen using the same query tools when pointed to an alternate SQL DW instance and this error happens from any workstation or server we've tried up to this point.










      share|improve this question














      I have an external table set up in Azure SQL DW that uses a HADOOP data source pointing to wasb://..... This is something we do regularly. However, this time around we are seeing a very interesting error message when we attempt to read from the table (e.g. SELECT or as a CTAS).



      I'm hoping someone here may be able to point us in the right direction.



      Here is the text of the error message that we receive.



      110802;An internal DMS error occurred that caused this operation to fail.


      Details: Please use this Error ID when contacting your Administrator for
      assistance. EID:()



      NativeOdbcConnection.Open, error in OdbcConnectionCreate: SqlState: IM003,
      NativeError: 160, 'Error calling: SQLDriverConnect(this->_hdbc, NULL,
      (SQLWCHAR*)connectionString, SQL_NTS, NULL, 0, &cbConnStrOut,
      SQL_DRIVER_NOPROMPT), SQL return code: -1 | SQL Error Info: Error <1>:
      ErrorMsg: Specified driver could not be loaded due to system error 126:
      The specified module could not be found. (pdwodbc, sqlncli17e.dll). |
      ConnectionPooling: 1 | Error calling: pConn->Create(connectionString,
      useConnectionPooling, packetSize, connectionLoginTimeout,
      environmentSettings, transactionToken, transactionTokenSize, spid) |
      state: FFFF, number: 151, active connections: 4', Connection String:
      Driver={pdwodbc};app=TypeC01-DmsNativeWriter:DB143mpdwsvc (40084)-
      ODBC;trusted_connection=yes;autotranslate=no;server=\.pipeDB.143-
      b52e821913d9sqlquery;database=Distribution_1


      Note that this same error does not happen using the same query tools when pointed to an alternate SQL DW instance and this error happens from any workstation or server we've tried up to this point.







      azure ms-sql






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 31 at 18:59









      NomadNomad

      1




      1




      closed as off-topic by music2myear, Twisty Impersonator, Pimp Juice IT, Rajesh S, Anaksunaman Feb 28 at 11:40


      This question appears to be off-topic. The users who voted to close gave this specific reason:


      • "This question is not about computer hardware or software, within the scope defined in the help center." – music2myear, Twisty Impersonator, Pimp Juice IT, Rajesh S, Anaksunaman

      If this question can be reworded to fit the rules in the help center, please edit the question.







      closed as off-topic by music2myear, Twisty Impersonator, Pimp Juice IT, Rajesh S, Anaksunaman Feb 28 at 11:40


      This question appears to be off-topic. The users who voted to close gave this specific reason:


      • "This question is not about computer hardware or software, within the scope defined in the help center." – music2myear, Twisty Impersonator, Pimp Juice IT, Rajesh S, Anaksunaman

      If this question can be reworded to fit the rules in the help center, please edit the question.






















          1 Answer
          1






          active

          oldest

          votes


















          0














          this is a Azure bug. MS it probably performs an upgrade of DWH system in your region.
          try to PauseResume or Scale updown your datawarehouse.



          Any of these actions is expected to make your datawarehouse to be placed in a proper location running the correct version of the provider.






          share|improve this answer






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            this is a Azure bug. MS it probably performs an upgrade of DWH system in your region.
            try to PauseResume or Scale updown your datawarehouse.



            Any of these actions is expected to make your datawarehouse to be placed in a proper location running the correct version of the provider.






            share|improve this answer




























              0














              this is a Azure bug. MS it probably performs an upgrade of DWH system in your region.
              try to PauseResume or Scale updown your datawarehouse.



              Any of these actions is expected to make your datawarehouse to be placed in a proper location running the correct version of the provider.






              share|improve this answer


























                0












                0








                0







                this is a Azure bug. MS it probably performs an upgrade of DWH system in your region.
                try to PauseResume or Scale updown your datawarehouse.



                Any of these actions is expected to make your datawarehouse to be placed in a proper location running the correct version of the provider.






                share|improve this answer













                this is a Azure bug. MS it probably performs an upgrade of DWH system in your region.
                try to PauseResume or Scale updown your datawarehouse.



                Any of these actions is expected to make your datawarehouse to be placed in a proper location running the correct version of the provider.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 5 at 16:18









                xxmassixxmassi

                1




                1















                    Popular posts from this blog

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                     ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕