Login lacks connect endpoint permission in SQL Server - Error 18456, State: 149Login failed for user - Error...
Why is Shelob considered evil?
What happens if both players misunderstand the game state until it's too late?
Is it Safe to Plug an Extension Cord Into a Power Strip?
Multiple null checks in Java 8
How to store all ctor parameters in fields
Do the speed limit reductions due to pollution also apply to electric cars in France?
Why is it that Bernie Sanders always called a "socialist"?
Is there a way to pause a running process on Linux systems and resume later?
How can I handle players killing my NPC outside of combat?
Can I legally make a website about boycotting a certain company?
What does an unprocessed RAW file look like?
What if you do not believe in the project benefits?
How can I portray body horror and still be sensitive to people with disabilities?
3D buried view in Tikz
Can someone explain the need for perturbation theory in QM?
Is the tritone (A4 / d5) still banned in Roman Catholic music?
Can a planet be tidally unlocked?
Cryptic cross... with words
Why and/or operations in python statement are behaving unexpectedly?
When distributing a Linux kernel driver as source code, what's the difference between Proprietary and GPL license?
Dot product with a constant
Build ASCII Podiums
Minimum Viable Product for RTS game?
Have any astronauts or cosmonauts died in space?
Login lacks connect endpoint permission in SQL Server - Error 18456, State: 149
Login failed for user - Error 18456 - Severity 14, State 38Login failed for user Error: 18456, Severity: 14, State: 11Login failed for user Error: 18456 State: 10Login failed for user - Error: 18456, Severity: 14, State: 38Error 18456 Serverity 14, State 38Error: 18456, Severity: 14, State: 5; SSMS > Network sever from PCSQL Server Management Studio creates 18456 login error using registered server groupError: 18456, Severity: 14, State: 11. Login-based server access validation failed with an infrastructure errorAzure SQL Server Database Error: 18456, Severity: 14, State: 1Error 18456, Severity 14, State 8
I have a fresh database I've setup, which I can connect to and perform operations like normal via the SQL Server Management Studio. I have two accounts I created for my application to use, and both can log in via SSMS. My program is running java and using the 'mssql-jdbc-6.4.0.jre8.jar' driver, and when I attempt to connect I can see the following error on the database log:
Error: 18456, Severity: 14, Sate: 149
Login failed for user 'application_read_only_user'. Reason:
Login-based server access validation failed with an infrastructure
error. Login lacks connect endpoint permission. [CLIENT: 127.0.0.1]
I have looked at several sources trying to solve this issue. The official Microsoft documentation does not seem to list state 149, nor do any results I've found online.
I have not modified my endpoints from the original settings, so I only have the following items:
- Dedicated Admin Connection
- TSQL Local Machine
- TSQL Named Pipes
- TSQL Default TCP
- TSQL Default VIA
I have tried setting the SQL Server services to run as Local System.
There are a lot of similar questions on this site, and stack overflow, but none of them have been able to help. They all either have a different state, or do not list a state.
sql-server logins sql-server-2017
add a comment |
I have a fresh database I've setup, which I can connect to and perform operations like normal via the SQL Server Management Studio. I have two accounts I created for my application to use, and both can log in via SSMS. My program is running java and using the 'mssql-jdbc-6.4.0.jre8.jar' driver, and when I attempt to connect I can see the following error on the database log:
Error: 18456, Severity: 14, Sate: 149
Login failed for user 'application_read_only_user'. Reason:
Login-based server access validation failed with an infrastructure
error. Login lacks connect endpoint permission. [CLIENT: 127.0.0.1]
I have looked at several sources trying to solve this issue. The official Microsoft documentation does not seem to list state 149, nor do any results I've found online.
I have not modified my endpoints from the original settings, so I only have the following items:
- Dedicated Admin Connection
- TSQL Local Machine
- TSQL Named Pipes
- TSQL Default TCP
- TSQL Default VIA
I have tried setting the SQL Server services to run as Local System.
There are a lot of similar questions on this site, and stack overflow, but none of them have been able to help. They all either have a different state, or do not list a state.
sql-server logins sql-server-2017
Your question prompted me to search the Internet for possible causes and solutions. I'm not sure if this post will help (you may have already seen it), but take a look at Why do I get the infrastructure error for login failures?
– Scott Hodgin
Aug 8 '18 at 10:49
I have seen that article before, Scott, unfortunately it did not help me. I tried all of those suggestions and none worked.
– Seb
Aug 8 '18 at 15:53
add a comment |
I have a fresh database I've setup, which I can connect to and perform operations like normal via the SQL Server Management Studio. I have two accounts I created for my application to use, and both can log in via SSMS. My program is running java and using the 'mssql-jdbc-6.4.0.jre8.jar' driver, and when I attempt to connect I can see the following error on the database log:
Error: 18456, Severity: 14, Sate: 149
Login failed for user 'application_read_only_user'. Reason:
Login-based server access validation failed with an infrastructure
error. Login lacks connect endpoint permission. [CLIENT: 127.0.0.1]
I have looked at several sources trying to solve this issue. The official Microsoft documentation does not seem to list state 149, nor do any results I've found online.
I have not modified my endpoints from the original settings, so I only have the following items:
- Dedicated Admin Connection
- TSQL Local Machine
- TSQL Named Pipes
- TSQL Default TCP
- TSQL Default VIA
I have tried setting the SQL Server services to run as Local System.
There are a lot of similar questions on this site, and stack overflow, but none of them have been able to help. They all either have a different state, or do not list a state.
sql-server logins sql-server-2017
I have a fresh database I've setup, which I can connect to and perform operations like normal via the SQL Server Management Studio. I have two accounts I created for my application to use, and both can log in via SSMS. My program is running java and using the 'mssql-jdbc-6.4.0.jre8.jar' driver, and when I attempt to connect I can see the following error on the database log:
Error: 18456, Severity: 14, Sate: 149
Login failed for user 'application_read_only_user'. Reason:
Login-based server access validation failed with an infrastructure
error. Login lacks connect endpoint permission. [CLIENT: 127.0.0.1]
I have looked at several sources trying to solve this issue. The official Microsoft documentation does not seem to list state 149, nor do any results I've found online.
I have not modified my endpoints from the original settings, so I only have the following items:
- Dedicated Admin Connection
- TSQL Local Machine
- TSQL Named Pipes
- TSQL Default TCP
- TSQL Default VIA
I have tried setting the SQL Server services to run as Local System.
There are a lot of similar questions on this site, and stack overflow, but none of them have been able to help. They all either have a different state, or do not list a state.
sql-server logins sql-server-2017
sql-server logins sql-server-2017
edited Aug 8 '18 at 10:36
Seb
asked Aug 8 '18 at 9:19
SebSeb
1115
1115
Your question prompted me to search the Internet for possible causes and solutions. I'm not sure if this post will help (you may have already seen it), but take a look at Why do I get the infrastructure error for login failures?
– Scott Hodgin
Aug 8 '18 at 10:49
I have seen that article before, Scott, unfortunately it did not help me. I tried all of those suggestions and none worked.
– Seb
Aug 8 '18 at 15:53
add a comment |
Your question prompted me to search the Internet for possible causes and solutions. I'm not sure if this post will help (you may have already seen it), but take a look at Why do I get the infrastructure error for login failures?
– Scott Hodgin
Aug 8 '18 at 10:49
I have seen that article before, Scott, unfortunately it did not help me. I tried all of those suggestions and none worked.
– Seb
Aug 8 '18 at 15:53
Your question prompted me to search the Internet for possible causes and solutions. I'm not sure if this post will help (you may have already seen it), but take a look at Why do I get the infrastructure error for login failures?
– Scott Hodgin
Aug 8 '18 at 10:49
Your question prompted me to search the Internet for possible causes and solutions. I'm not sure if this post will help (you may have already seen it), but take a look at Why do I get the infrastructure error for login failures?
– Scott Hodgin
Aug 8 '18 at 10:49
I have seen that article before, Scott, unfortunately it did not help me. I tried all of those suggestions and none worked.
– Seb
Aug 8 '18 at 15:53
I have seen that article before, Scott, unfortunately it did not help me. I tried all of those suggestions and none worked.
– Seb
Aug 8 '18 at 15:53
add a comment |
2 Answers
2
active
oldest
votes
Analysis
If you have a search for the Error 18456 you will eventually find the following blog post from Aaron Bertrand:
Troubleshooting Error 18456 (SQL Blog / Aaron)
Which lists the following for states 146...149
:
These states replace states 11 and 12 above, but only in SQL Server 2016 or better. The goal was to make the actual underlying issue easier for the sysadmin to diagnose between SQL auth and Windows auth logins, and between connect and endpoint permissions (all without giving any further info to the user trying to log in). For more details, see the latter part of this post.
The this post link in the above quote references the article "Why do I get the infrastructure error for login failures?" over on CSS SQL Server Engineers blog/site.
The article cites these two possible reasons as the cause for the "Login-based server access validation failed with an infrastructure error":
Does the login have the SERVER class permission named CONNECT SQL for this server instance?
Does the login have the ENDPOINT class permission named CONNECT for the specific endpoint on which the client application established the connection?
Because SQL Server 2016+ has new error messages for Level 146...149 errors, you have been presented with the specific error message Login lacks connect endpoint permission. (Level 149), which leads you to the second option from above.
Have a look at your current enpoint permissions with the following script:
SELECT * FROM sys.server_permissions AS sp2
JOIN sys.server_principals AS sp
ON sp2.grantee_principal_id = sp.principal_id
LEFT OUTER JOIN sys.endpoints AS e
on sp2.major_id = e.endpoint_id
WHERE sp2.permission_name = 'CONNECT'
AND sp2.class_desc = 'ENDPOINT'
You should have at least one entry for the combination of GRANT
, public
and TSQL Default TCP
Solution
Check the CONNECT permissions on the ENDPOINT for the SQL Server Login for TCP or simply grant the permission to the account:
GRANT CONNECT ON ENDPOINT::[TSQL Default TCP] TO public;
(replace public
with your <SQL Server Login>
if you only want to assign that permission to a specific account)
To see a list of endpoints run:
select * from sys.endpoints
Further Reading / Reference List
Troubleshooting Error 18456 (SQL Blog / Aaron)
Why do I get the infrastructure error for login failures? (CSS SQL Server Engineers)
Endpoints Catalog Views (Transact-SQL) (Microsoft Docs)
GRANT Endpoint Permissions (Transact-SQL) (Microsoft Docs)
Sorry, hot2use, but this doesn't solve the issue. I've got both SERVER and ENDPOINT connect privileges granted to the user, but I still get the same error.
– Seb
Aug 8 '18 at 15:52
1
Ok, I‘ll dig deeper. Is the user possibly in a group that has been denied permission?
– hot2use
Aug 8 '18 at 16:00
The one I'm testing with is only a member of the default public group on both master and my application database. On the application database he has the db_datareader role. None of these are disabled or had access revoked.
– Seb
Aug 8 '18 at 16:11
Quick one: If you execute my query to list the principal's permissions just without theWHERE ....
part, do you see any entries containing aDENY
in thestate_desc
column?
– hot2use
Aug 9 '18 at 11:11
Nope, nothing has been denied.
– Seb
Aug 9 '18 at 12:26
add a comment |
I've got the same problem because I was trying to connect to port 1434 instead of port 1433. mssql-server is listening to both. I can connect to 1434 and use SA account without problem but that did not work for other accounts.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fdba.stackexchange.com%2fquestions%2f214374%2flogin-lacks-connect-endpoint-permission-in-sql-server-error-18456-state-149%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Analysis
If you have a search for the Error 18456 you will eventually find the following blog post from Aaron Bertrand:
Troubleshooting Error 18456 (SQL Blog / Aaron)
Which lists the following for states 146...149
:
These states replace states 11 and 12 above, but only in SQL Server 2016 or better. The goal was to make the actual underlying issue easier for the sysadmin to diagnose between SQL auth and Windows auth logins, and between connect and endpoint permissions (all without giving any further info to the user trying to log in). For more details, see the latter part of this post.
The this post link in the above quote references the article "Why do I get the infrastructure error for login failures?" over on CSS SQL Server Engineers blog/site.
The article cites these two possible reasons as the cause for the "Login-based server access validation failed with an infrastructure error":
Does the login have the SERVER class permission named CONNECT SQL for this server instance?
Does the login have the ENDPOINT class permission named CONNECT for the specific endpoint on which the client application established the connection?
Because SQL Server 2016+ has new error messages for Level 146...149 errors, you have been presented with the specific error message Login lacks connect endpoint permission. (Level 149), which leads you to the second option from above.
Have a look at your current enpoint permissions with the following script:
SELECT * FROM sys.server_permissions AS sp2
JOIN sys.server_principals AS sp
ON sp2.grantee_principal_id = sp.principal_id
LEFT OUTER JOIN sys.endpoints AS e
on sp2.major_id = e.endpoint_id
WHERE sp2.permission_name = 'CONNECT'
AND sp2.class_desc = 'ENDPOINT'
You should have at least one entry for the combination of GRANT
, public
and TSQL Default TCP
Solution
Check the CONNECT permissions on the ENDPOINT for the SQL Server Login for TCP or simply grant the permission to the account:
GRANT CONNECT ON ENDPOINT::[TSQL Default TCP] TO public;
(replace public
with your <SQL Server Login>
if you only want to assign that permission to a specific account)
To see a list of endpoints run:
select * from sys.endpoints
Further Reading / Reference List
Troubleshooting Error 18456 (SQL Blog / Aaron)
Why do I get the infrastructure error for login failures? (CSS SQL Server Engineers)
Endpoints Catalog Views (Transact-SQL) (Microsoft Docs)
GRANT Endpoint Permissions (Transact-SQL) (Microsoft Docs)
Sorry, hot2use, but this doesn't solve the issue. I've got both SERVER and ENDPOINT connect privileges granted to the user, but I still get the same error.
– Seb
Aug 8 '18 at 15:52
1
Ok, I‘ll dig deeper. Is the user possibly in a group that has been denied permission?
– hot2use
Aug 8 '18 at 16:00
The one I'm testing with is only a member of the default public group on both master and my application database. On the application database he has the db_datareader role. None of these are disabled or had access revoked.
– Seb
Aug 8 '18 at 16:11
Quick one: If you execute my query to list the principal's permissions just without theWHERE ....
part, do you see any entries containing aDENY
in thestate_desc
column?
– hot2use
Aug 9 '18 at 11:11
Nope, nothing has been denied.
– Seb
Aug 9 '18 at 12:26
add a comment |
Analysis
If you have a search for the Error 18456 you will eventually find the following blog post from Aaron Bertrand:
Troubleshooting Error 18456 (SQL Blog / Aaron)
Which lists the following for states 146...149
:
These states replace states 11 and 12 above, but only in SQL Server 2016 or better. The goal was to make the actual underlying issue easier for the sysadmin to diagnose between SQL auth and Windows auth logins, and between connect and endpoint permissions (all without giving any further info to the user trying to log in). For more details, see the latter part of this post.
The this post link in the above quote references the article "Why do I get the infrastructure error for login failures?" over on CSS SQL Server Engineers blog/site.
The article cites these two possible reasons as the cause for the "Login-based server access validation failed with an infrastructure error":
Does the login have the SERVER class permission named CONNECT SQL for this server instance?
Does the login have the ENDPOINT class permission named CONNECT for the specific endpoint on which the client application established the connection?
Because SQL Server 2016+ has new error messages for Level 146...149 errors, you have been presented with the specific error message Login lacks connect endpoint permission. (Level 149), which leads you to the second option from above.
Have a look at your current enpoint permissions with the following script:
SELECT * FROM sys.server_permissions AS sp2
JOIN sys.server_principals AS sp
ON sp2.grantee_principal_id = sp.principal_id
LEFT OUTER JOIN sys.endpoints AS e
on sp2.major_id = e.endpoint_id
WHERE sp2.permission_name = 'CONNECT'
AND sp2.class_desc = 'ENDPOINT'
You should have at least one entry for the combination of GRANT
, public
and TSQL Default TCP
Solution
Check the CONNECT permissions on the ENDPOINT for the SQL Server Login for TCP or simply grant the permission to the account:
GRANT CONNECT ON ENDPOINT::[TSQL Default TCP] TO public;
(replace public
with your <SQL Server Login>
if you only want to assign that permission to a specific account)
To see a list of endpoints run:
select * from sys.endpoints
Further Reading / Reference List
Troubleshooting Error 18456 (SQL Blog / Aaron)
Why do I get the infrastructure error for login failures? (CSS SQL Server Engineers)
Endpoints Catalog Views (Transact-SQL) (Microsoft Docs)
GRANT Endpoint Permissions (Transact-SQL) (Microsoft Docs)
Sorry, hot2use, but this doesn't solve the issue. I've got both SERVER and ENDPOINT connect privileges granted to the user, but I still get the same error.
– Seb
Aug 8 '18 at 15:52
1
Ok, I‘ll dig deeper. Is the user possibly in a group that has been denied permission?
– hot2use
Aug 8 '18 at 16:00
The one I'm testing with is only a member of the default public group on both master and my application database. On the application database he has the db_datareader role. None of these are disabled or had access revoked.
– Seb
Aug 8 '18 at 16:11
Quick one: If you execute my query to list the principal's permissions just without theWHERE ....
part, do you see any entries containing aDENY
in thestate_desc
column?
– hot2use
Aug 9 '18 at 11:11
Nope, nothing has been denied.
– Seb
Aug 9 '18 at 12:26
add a comment |
Analysis
If you have a search for the Error 18456 you will eventually find the following blog post from Aaron Bertrand:
Troubleshooting Error 18456 (SQL Blog / Aaron)
Which lists the following for states 146...149
:
These states replace states 11 and 12 above, but only in SQL Server 2016 or better. The goal was to make the actual underlying issue easier for the sysadmin to diagnose between SQL auth and Windows auth logins, and between connect and endpoint permissions (all without giving any further info to the user trying to log in). For more details, see the latter part of this post.
The this post link in the above quote references the article "Why do I get the infrastructure error for login failures?" over on CSS SQL Server Engineers blog/site.
The article cites these two possible reasons as the cause for the "Login-based server access validation failed with an infrastructure error":
Does the login have the SERVER class permission named CONNECT SQL for this server instance?
Does the login have the ENDPOINT class permission named CONNECT for the specific endpoint on which the client application established the connection?
Because SQL Server 2016+ has new error messages for Level 146...149 errors, you have been presented with the specific error message Login lacks connect endpoint permission. (Level 149), which leads you to the second option from above.
Have a look at your current enpoint permissions with the following script:
SELECT * FROM sys.server_permissions AS sp2
JOIN sys.server_principals AS sp
ON sp2.grantee_principal_id = sp.principal_id
LEFT OUTER JOIN sys.endpoints AS e
on sp2.major_id = e.endpoint_id
WHERE sp2.permission_name = 'CONNECT'
AND sp2.class_desc = 'ENDPOINT'
You should have at least one entry for the combination of GRANT
, public
and TSQL Default TCP
Solution
Check the CONNECT permissions on the ENDPOINT for the SQL Server Login for TCP or simply grant the permission to the account:
GRANT CONNECT ON ENDPOINT::[TSQL Default TCP] TO public;
(replace public
with your <SQL Server Login>
if you only want to assign that permission to a specific account)
To see a list of endpoints run:
select * from sys.endpoints
Further Reading / Reference List
Troubleshooting Error 18456 (SQL Blog / Aaron)
Why do I get the infrastructure error for login failures? (CSS SQL Server Engineers)
Endpoints Catalog Views (Transact-SQL) (Microsoft Docs)
GRANT Endpoint Permissions (Transact-SQL) (Microsoft Docs)
Analysis
If you have a search for the Error 18456 you will eventually find the following blog post from Aaron Bertrand:
Troubleshooting Error 18456 (SQL Blog / Aaron)
Which lists the following for states 146...149
:
These states replace states 11 and 12 above, but only in SQL Server 2016 or better. The goal was to make the actual underlying issue easier for the sysadmin to diagnose between SQL auth and Windows auth logins, and between connect and endpoint permissions (all without giving any further info to the user trying to log in). For more details, see the latter part of this post.
The this post link in the above quote references the article "Why do I get the infrastructure error for login failures?" over on CSS SQL Server Engineers blog/site.
The article cites these two possible reasons as the cause for the "Login-based server access validation failed with an infrastructure error":
Does the login have the SERVER class permission named CONNECT SQL for this server instance?
Does the login have the ENDPOINT class permission named CONNECT for the specific endpoint on which the client application established the connection?
Because SQL Server 2016+ has new error messages for Level 146...149 errors, you have been presented with the specific error message Login lacks connect endpoint permission. (Level 149), which leads you to the second option from above.
Have a look at your current enpoint permissions with the following script:
SELECT * FROM sys.server_permissions AS sp2
JOIN sys.server_principals AS sp
ON sp2.grantee_principal_id = sp.principal_id
LEFT OUTER JOIN sys.endpoints AS e
on sp2.major_id = e.endpoint_id
WHERE sp2.permission_name = 'CONNECT'
AND sp2.class_desc = 'ENDPOINT'
You should have at least one entry for the combination of GRANT
, public
and TSQL Default TCP
Solution
Check the CONNECT permissions on the ENDPOINT for the SQL Server Login for TCP or simply grant the permission to the account:
GRANT CONNECT ON ENDPOINT::[TSQL Default TCP] TO public;
(replace public
with your <SQL Server Login>
if you only want to assign that permission to a specific account)
To see a list of endpoints run:
select * from sys.endpoints
Further Reading / Reference List
Troubleshooting Error 18456 (SQL Blog / Aaron)
Why do I get the infrastructure error for login failures? (CSS SQL Server Engineers)
Endpoints Catalog Views (Transact-SQL) (Microsoft Docs)
GRANT Endpoint Permissions (Transact-SQL) (Microsoft Docs)
edited Aug 8 '18 at 11:27
answered Aug 8 '18 at 11:02
hot2usehot2use
8,34752055
8,34752055
Sorry, hot2use, but this doesn't solve the issue. I've got both SERVER and ENDPOINT connect privileges granted to the user, but I still get the same error.
– Seb
Aug 8 '18 at 15:52
1
Ok, I‘ll dig deeper. Is the user possibly in a group that has been denied permission?
– hot2use
Aug 8 '18 at 16:00
The one I'm testing with is only a member of the default public group on both master and my application database. On the application database he has the db_datareader role. None of these are disabled or had access revoked.
– Seb
Aug 8 '18 at 16:11
Quick one: If you execute my query to list the principal's permissions just without theWHERE ....
part, do you see any entries containing aDENY
in thestate_desc
column?
– hot2use
Aug 9 '18 at 11:11
Nope, nothing has been denied.
– Seb
Aug 9 '18 at 12:26
add a comment |
Sorry, hot2use, but this doesn't solve the issue. I've got both SERVER and ENDPOINT connect privileges granted to the user, but I still get the same error.
– Seb
Aug 8 '18 at 15:52
1
Ok, I‘ll dig deeper. Is the user possibly in a group that has been denied permission?
– hot2use
Aug 8 '18 at 16:00
The one I'm testing with is only a member of the default public group on both master and my application database. On the application database he has the db_datareader role. None of these are disabled or had access revoked.
– Seb
Aug 8 '18 at 16:11
Quick one: If you execute my query to list the principal's permissions just without theWHERE ....
part, do you see any entries containing aDENY
in thestate_desc
column?
– hot2use
Aug 9 '18 at 11:11
Nope, nothing has been denied.
– Seb
Aug 9 '18 at 12:26
Sorry, hot2use, but this doesn't solve the issue. I've got both SERVER and ENDPOINT connect privileges granted to the user, but I still get the same error.
– Seb
Aug 8 '18 at 15:52
Sorry, hot2use, but this doesn't solve the issue. I've got both SERVER and ENDPOINT connect privileges granted to the user, but I still get the same error.
– Seb
Aug 8 '18 at 15:52
1
1
Ok, I‘ll dig deeper. Is the user possibly in a group that has been denied permission?
– hot2use
Aug 8 '18 at 16:00
Ok, I‘ll dig deeper. Is the user possibly in a group that has been denied permission?
– hot2use
Aug 8 '18 at 16:00
The one I'm testing with is only a member of the default public group on both master and my application database. On the application database he has the db_datareader role. None of these are disabled or had access revoked.
– Seb
Aug 8 '18 at 16:11
The one I'm testing with is only a member of the default public group on both master and my application database. On the application database he has the db_datareader role. None of these are disabled or had access revoked.
– Seb
Aug 8 '18 at 16:11
Quick one: If you execute my query to list the principal's permissions just without the
WHERE ....
part, do you see any entries containing a DENY
in the state_desc
column?– hot2use
Aug 9 '18 at 11:11
Quick one: If you execute my query to list the principal's permissions just without the
WHERE ....
part, do you see any entries containing a DENY
in the state_desc
column?– hot2use
Aug 9 '18 at 11:11
Nope, nothing has been denied.
– Seb
Aug 9 '18 at 12:26
Nope, nothing has been denied.
– Seb
Aug 9 '18 at 12:26
add a comment |
I've got the same problem because I was trying to connect to port 1434 instead of port 1433. mssql-server is listening to both. I can connect to 1434 and use SA account without problem but that did not work for other accounts.
New contributor
add a comment |
I've got the same problem because I was trying to connect to port 1434 instead of port 1433. mssql-server is listening to both. I can connect to 1434 and use SA account without problem but that did not work for other accounts.
New contributor
add a comment |
I've got the same problem because I was trying to connect to port 1434 instead of port 1433. mssql-server is listening to both. I can connect to 1434 and use SA account without problem but that did not work for other accounts.
New contributor
I've got the same problem because I was trying to connect to port 1434 instead of port 1433. mssql-server is listening to both. I can connect to 1434 and use SA account without problem but that did not work for other accounts.
New contributor
New contributor
answered 5 mins ago
user1708145user1708145
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- 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%2fdba.stackexchange.com%2fquestions%2f214374%2flogin-lacks-connect-endpoint-permission-in-sql-server-error-18456-state-149%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
Your question prompted me to search the Internet for possible causes and solutions. I'm not sure if this post will help (you may have already seen it), but take a look at Why do I get the infrastructure error for login failures?
– Scott Hodgin
Aug 8 '18 at 10:49
I have seen that article before, Scott, unfortunately it did not help me. I tried all of those suggestions and none worked.
– Seb
Aug 8 '18 at 15:53