Azure SQL DW External Table Issue
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
asked Jan 31 at 18:59
NomadNomad
1
add a comment |
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
asked Jan 31 at 18:59
NomadNomad
1
add a comment |
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
asked Jan 31 at 18:59
NomadNomad
1
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
asked Jan 31 at 18:59
NomadNomad
1
asked Jan 31 at 18:59
NomadNomad
1
asked Jan 31 at 18:59
NomadNomad
1
asked Jan 31 at 18:59
NomadNomad
1
asked Jan 31 at 18:59
NomadNomad
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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.
answered Feb 5 at 16:18
xxmassixxmassi
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400714%2fazure-sql-dw-external-table-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
answered Feb 5 at 16:18
xxmassixxmassi
1
add a comment |
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.
answered Feb 5 at 16:18
xxmassixxmassi
1
add a comment |
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.
answered Feb 5 at 16:18
xxmassixxmassi
1
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.
answered Feb 5 at 16:18
xxmassixxmassi
1
answered Feb 5 at 16:18
xxmassixxmassi
1
answered Feb 5 at 16:18
xxmassixxmassi
1
answered Feb 5 at 16:18
xxmassixxmassi
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400714%2fazure-sql-dw-external-table-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
