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.






azure ms-sql







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.






    azure ms-sql







    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.






      azure ms-sql







      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




      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

                    How to make a Squid Proxy server?

                    Image
                    1 I want to set up squid proxy server for monitoring user activity in a network and Internet Web URL filtering for user. I also want to configure the user login, user log, user access group, and block unwanted web sites in my network. Please help me and guide me the full process to do this. server proxy squid share | improve this question edited Jul 31 '12 at 14:45 Jorge Castro 37.1k 107 422 617 asked Jul 31 '12 at 5:16 Goivind Tiwari Goivind Tiwari ...
                    Read more

                    Is this a new Fibonacci Identity?

                    Image
                    6 1 $begingroup$ I have found the following Fibonacci Identity (and proved it). If $F_n$ denotes the nth Fibonacci Number, we have the following identity begin{equation} F_{n-r+h}F_{n+k+g+1} - F_{n-r+g}F_{n+k+h+1} = (-1)^{n+r+h+1} F_{g-h}F_{k+r+1} end{equation} where $F_1 = F_2 = 1$ , $r leq n$ , $h leq g$ , and $n, g, k in mathbb{N}$ . It is not too hard to show that this identity subsumes Cassini's Identity, Catalan's Identity, Vajda's Idenity, and d'Ocagne's identity to name a few. I have done a pretty thorough literature review, and I have not found anything like this, but I am still wondering if anyone has seen this identity before? I found this by accident after noticing some patterns in some analysis work I was doing, so if this is already known I would be curious to see w...
                    Read more

                    19世紀

                    Image
                    この記事は検証可能な参考文献や出典が全く示されていないか、不十分です。 出典を追加して記事の信頼性向上にご協力ください。 （ 2012年3月 ） 千年紀: 2千年紀 世紀: 18世紀 - 19世紀 - 20世紀 十年紀: 1800年代 1810年代 1820年代 1830年代 1840年代 1850年代 1860年代 1870年代 1880年代 1890年代 19世紀に君臨した大英帝国。 19世紀 （じゅうきゅうせいき）は、西暦1801年から西暦1900年までの100年間を指す世紀。 目次 1 19世紀の歴史 1.1 国民国家の成立 1.2 帝国主義の興隆 1.3 列強の植民地争奪戦 2 できごと 2.1 1800年代 2.2 1810年代 2.3 1820年代 2.4 1830年代 2.5 1840年代 2.6 1850年代 2.7 1860年代 2.8 1870年代 2.9 1880年代 2.10 1890年代 2.11 1900年代 3 文化 3.1 文学 3.2 音楽 3.3 思想 3.4 科学 3.5 技術 4 人物 4.1 ヨーロッパ 4.1.1 政治家・王族 4.1.1.1 フランス 4.1.1.2 オーストリア＝ハンガリー 4.1.1.3 ロシア 4.1.1.4 イギリス 4.1.1.5 ドイツ（プロイセンほかドイツ領邦を含む） 4.1.1.6 北欧 4.1.1.7 イタリア 4.1.1.8 スペイン 4.1.1.9 ベルギー 4.1.1.10 ギリシア 4.1.2 軍人 4.1.3 実業家 4.1.4 科学と技術 4.1.5 思想と哲学・人文諸学 4.1.6 宗教 4.1.7 文学 4.1.8 美術 4.1.9 音楽 4.1.10 社会事業家 4.1.11 探検家・旅行家 4.1.12 料...
                    Read more