SQL2016 ODBC login fail on first attempt
My current SQL server version is:
Microsoft SQL Server 2016 (SP2) (KB4052908) - 13.0.5026.0 (X64)
Mar 18 2018 09:11:49
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows Server 2012 Standard 6.2 (Build 9200: )
I am connecting to SQL through MS Access MDB using ODBC.
Yesterday this worked fine, today not - difference I believe is Server windows update.
Today when Access attempts connection, I get the following error:
Microsoft SQL Server Login
Connection failed: SQL state: S1T00
SQL server error 0
Microsoft ODBC SQL server driver login timeout expired
After Clicking "OK", things connect, and everything works without issue
It is not a DNS issue - using the IP address rather than server name does not resolve. The connection to SQL in SSMS works without issue. I have tried MS SQL sever ODBC driver 13 and 17.
I think it has something to do with the windows/SQL update, because this happened 20 days ago, and after trying many things, I "repaired" SQL Server and the issue went away. Instead of a SQL repair again, I need to find the true cause - any ideas out there?
networking sql-server
migrated from superuser.com Dec 21 '18 at 20:48
This question came from our site for computer enthusiasts and power users.
add a comment |
My current SQL server version is:
Microsoft SQL Server 2016 (SP2) (KB4052908) - 13.0.5026.0 (X64)
Mar 18 2018 09:11:49
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows Server 2012 Standard 6.2 (Build 9200: )
I am connecting to SQL through MS Access MDB using ODBC.
Yesterday this worked fine, today not - difference I believe is Server windows update.
Today when Access attempts connection, I get the following error:
Microsoft SQL Server Login
Connection failed: SQL state: S1T00
SQL server error 0
Microsoft ODBC SQL server driver login timeout expired
After Clicking "OK", things connect, and everything works without issue
It is not a DNS issue - using the IP address rather than server name does not resolve. The connection to SQL in SSMS works without issue. I have tried MS SQL sever ODBC driver 13 and 17.
I think it has something to do with the windows/SQL update, because this happened 20 days ago, and after trying many things, I "repaired" SQL Server and the issue went away. Instead of a SQL repair again, I need to find the true cause - any ideas out there?
networking sql-server
migrated from superuser.com Dec 21 '18 at 20:48
This question came from our site for computer enthusiasts and power users.
add a comment |
My current SQL server version is:
Microsoft SQL Server 2016 (SP2) (KB4052908) - 13.0.5026.0 (X64)
Mar 18 2018 09:11:49
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows Server 2012 Standard 6.2 (Build 9200: )
I am connecting to SQL through MS Access MDB using ODBC.
Yesterday this worked fine, today not - difference I believe is Server windows update.
Today when Access attempts connection, I get the following error:
Microsoft SQL Server Login
Connection failed: SQL state: S1T00
SQL server error 0
Microsoft ODBC SQL server driver login timeout expired
After Clicking "OK", things connect, and everything works without issue
It is not a DNS issue - using the IP address rather than server name does not resolve. The connection to SQL in SSMS works without issue. I have tried MS SQL sever ODBC driver 13 and 17.
I think it has something to do with the windows/SQL update, because this happened 20 days ago, and after trying many things, I "repaired" SQL Server and the issue went away. Instead of a SQL repair again, I need to find the true cause - any ideas out there?
networking sql-server
My current SQL server version is:
Microsoft SQL Server 2016 (SP2) (KB4052908) - 13.0.5026.0 (X64)
Mar 18 2018 09:11:49
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows Server 2012 Standard 6.2 (Build 9200: )
I am connecting to SQL through MS Access MDB using ODBC.
Yesterday this worked fine, today not - difference I believe is Server windows update.
Today when Access attempts connection, I get the following error:
Microsoft SQL Server Login
Connection failed: SQL state: S1T00
SQL server error 0
Microsoft ODBC SQL server driver login timeout expired
After Clicking "OK", things connect, and everything works without issue
It is not a DNS issue - using the IP address rather than server name does not resolve. The connection to SQL in SSMS works without issue. I have tried MS SQL sever ODBC driver 13 and 17.
I think it has something to do with the windows/SQL update, because this happened 20 days ago, and after trying many things, I "repaired" SQL Server and the issue went away. Instead of a SQL repair again, I need to find the true cause - any ideas out there?
networking sql-server
networking sql-server
asked Dec 21 '18 at 15:48
user976402
migrated from superuser.com Dec 21 '18 at 20:48
This question came from our site for computer enthusiasts and power users.
migrated from superuser.com Dec 21 '18 at 20:48
This question came from our site for computer enthusiasts and power users.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Resolved.
Issue was not because of SQL version.
Issue stemmed from firewall and network interface.
If I turned the windows public firewall OFF, things worked (ON not work).
When I force the server connection to=Private - things work (with firewall ON).
Previously Location Type=Not configured
Stack Exchange with detail on this:
How do I make a connection private on Windows Server 2012 R2
answered Dec 23 '18 at 17:26
user502529user502529
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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%2fserverfault.com%2fquestions%2f946324%2fsql2016-odbc-login-fail-on-first-attempt%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
Resolved.
Issue was not because of SQL version.
Issue stemmed from firewall and network interface.
If I turned the windows public firewall OFF, things worked (ON not work).
When I force the server connection to=Private - things work (with firewall ON).
Previously Location Type=Not configured
Stack Exchange with detail on this:
How do I make a connection private on Windows Server 2012 R2
answered Dec 23 '18 at 17:26
user502529user502529
1
add a comment |
Resolved.
Issue was not because of SQL version.
Issue stemmed from firewall and network interface.
If I turned the windows public firewall OFF, things worked (ON not work).
When I force the server connection to=Private - things work (with firewall ON).
Previously Location Type=Not configured
Stack Exchange with detail on this:
How do I make a connection private on Windows Server 2012 R2
answered Dec 23 '18 at 17:26
user502529user502529
1
add a comment |
Resolved.
Issue was not because of SQL version.
Issue stemmed from firewall and network interface.
If I turned the windows public firewall OFF, things worked (ON not work).
When I force the server connection to=Private - things work (with firewall ON).
Previously Location Type=Not configured
Stack Exchange with detail on this:
How do I make a connection private on Windows Server 2012 R2
answered Dec 23 '18 at 17:26
user502529user502529
1
Resolved.
Issue was not because of SQL version.
Issue stemmed from firewall and network interface.
If I turned the windows public firewall OFF, things worked (ON not work).
When I force the server connection to=Private - things work (with firewall ON).
Previously Location Type=Not configured
Stack Exchange with detail on this:
How do I make a connection private on Windows Server 2012 R2
answered Dec 23 '18 at 17:26
user502529user502529
1
answered Dec 23 '18 at 17:26
user502529user502529
1
answered Dec 23 '18 at 17:26
user502529user502529
1
answered Dec 23 '18 at 17:26
user502529user502529
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f946324%2fsql2016-odbc-login-fail-on-first-attempt%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
