The Target Principal Name Is Incorrect. Cannot Generate SSPI Context (SQL or AD Issue)?Remote DebuggingError: Cannot Generate SSPI contextI need the reason why we should not install SQL server on the domain controllerThe SQL Server Network Interface library could not deregister the Service Principal NameManaging the Service accounts in large environmentCannot generate SSPI ContextThe target principal name is incorrect. Cannot generate SSPI contextWindows Authentication fails with “Cannot generate SSPI context”Access - SQL Server: cannot generate SSPI contextcannot generate sspi - None of Solution worked!
What do you call a notepad used to keep a record?
"I am [the / an] owner of a bookstore"?
When was this photo of Mission Dolores *actually* taken?
How did Lefschetz do mathematics without hands?
Why isn't UDP with reliability (implemented at Application layer) a substitute of TCP?
Robots in a spaceship
Translation of the Sator Square
Can I use Alchemist's fire to turn my sword into a virtual Flame Blade?
How does mmorpg store data?
Do home values typically rise and fall consistently across different price ranges?
Checkmate in 1 on a Tangled Board
Could you fall off a planet if it was being accelerated by engines?
What verb for taking advantage fits in "I don't want to ________ on the friendship"?
What is the proper markup for a Math operator in boldface?
Bin Packing with Relational Penalization
Why were the first airplanes "backwards"?
Is it okay to fade a human face just to create some space to place important content over it?
Making a wall made from glass bricks
How can I deal with extreme temperatures in a hotel room?
Why wasn't EBCDIC designed with contiguous alphanumeric characters?
How could an armless race establish civilization?
My colleague is constantly blaming me for his errors
How do I create a new column in a dataframe from an existing column using conditions?
Two palindromes are not enough
The Target Principal Name Is Incorrect. Cannot Generate SSPI Context (SQL or AD Issue)?
Remote DebuggingError: Cannot Generate SSPI contextI need the reason why we should not install SQL server on the domain controllerThe SQL Server Network Interface library could not deregister the Service Principal NameManaging the Service accounts in large environmentCannot generate SSPI ContextThe target principal name is incorrect. Cannot generate SSPI contextWindows Authentication fails with “Cannot generate SSPI context”Access - SQL Server: cannot generate SSPI contextcannot generate sspi - None of Solution worked!
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
We had a power outage last night and when the server came back up our domain users could not access our SQL Server 2000 instance name: MASSQL.
We can access using SQL Authentication.
- We tried making sure the user that runs the service has SSPI read and Write
- We tried creating a new user
- We tried running the service using NETWORK SERVICE account
- We tried running as Local System Account
- We tried creating a new Domain Admin account and run service as the new Domain Admin account
I also ran the following command against the problem SQL Server instance:
setspn -L xsql2
Results
Registered ServicePrincipalNames for CN=MASSQL,CN=Computers,DC=ABC,DC=com:
HOST/MASSQL
HOST/MASSQL.ABC.COM
I ran the following command against a non-problem SQL instance:
setspn -L xensql1
Results
Registered ServicePrincipalNames for CN=XENSQL1,CN=Computers,DC=ABC,DC=com:
WSMAN/XENSQL1
WSMAN/XENSQL1.ABC.com
RestrictedKrbHost/XENSQL1
HOST/XENSQL1
RestrictedKrbHost/XENSQL1.ABC.COM
HOST/XENSQL1.ABC.COM
It seems the results for the non-problem instance have more data. I do not know if this has to do with the fact one is 2000 and the other is 2012.
What likely happened? How do I allow domain users login again?
sql-server active-directory
edited Jun 20 at 17:16
Max Vernon
54k13 gold badges117 silver badges242 bronze badges
asked Jun 20 at 17:13
Bill GreerBill Greer
1215 bronze badges
add a comment |
We had a power outage last night and when the server came back up our domain users could not access our SQL Server 2000 instance name: MASSQL.
We can access using SQL Authentication.
- We tried making sure the user that runs the service has SSPI read and Write
- We tried creating a new user
- We tried running the service using NETWORK SERVICE account
- We tried running as Local System Account
- We tried creating a new Domain Admin account and run service as the new Domain Admin account
I also ran the following command against the problem SQL Server instance:
setspn -L xsql2
Results
Registered ServicePrincipalNames for CN=MASSQL,CN=Computers,DC=ABC,DC=com:
HOST/MASSQL
HOST/MASSQL.ABC.COM
I ran the following command against a non-problem SQL instance:
setspn -L xensql1
Results
Registered ServicePrincipalNames for CN=XENSQL1,CN=Computers,DC=ABC,DC=com:
WSMAN/XENSQL1
WSMAN/XENSQL1.ABC.com
RestrictedKrbHost/XENSQL1
HOST/XENSQL1
RestrictedKrbHost/XENSQL1.ABC.COM
HOST/XENSQL1.ABC.COM
It seems the results for the non-problem instance have more data. I do not know if this has to do with the fact one is 2000 and the other is 2012.
What likely happened? How do I allow domain users login again?
sql-server active-directory
edited Jun 20 at 17:16
Max Vernon
54k13 gold badges117 silver badges242 bronze badges
asked Jun 20 at 17:13
Bill GreerBill Greer
1215 bronze badges
Now's a good time to upgrade :) Did the domain controller lose power too? Anything else having similar issues? That's where I'd start
– scsimon
Jun 20 at 17:16
reboot the server again and verify that windows services all came up...
– kevinsky
Jun 20 at 17:17
What does the SQL Server Error log say about registering Service Principal Names?
– Max Vernon
Jun 20 at 17:20
add a comment |
We had a power outage last night and when the server came back up our domain users could not access our SQL Server 2000 instance name: MASSQL.
We can access using SQL Authentication.
- We tried making sure the user that runs the service has SSPI read and Write
- We tried creating a new user
- We tried running the service using NETWORK SERVICE account
- We tried running as Local System Account
- We tried creating a new Domain Admin account and run service as the new Domain Admin account
I also ran the following command against the problem SQL Server instance:
setspn -L xsql2
Results
Registered ServicePrincipalNames for CN=MASSQL,CN=Computers,DC=ABC,DC=com:
HOST/MASSQL
HOST/MASSQL.ABC.COM
I ran the following command against a non-problem SQL instance:
setspn -L xensql1
Results
Registered ServicePrincipalNames for CN=XENSQL1,CN=Computers,DC=ABC,DC=com:
WSMAN/XENSQL1
WSMAN/XENSQL1.ABC.com
RestrictedKrbHost/XENSQL1
HOST/XENSQL1
RestrictedKrbHost/XENSQL1.ABC.COM
HOST/XENSQL1.ABC.COM
It seems the results for the non-problem instance have more data. I do not know if this has to do with the fact one is 2000 and the other is 2012.
What likely happened? How do I allow domain users login again?
sql-server active-directory
edited Jun 20 at 17:16
Max Vernon
54k13 gold badges117 silver badges242 bronze badges
asked Jun 20 at 17:13
Bill GreerBill Greer
1215 bronze badges
We had a power outage last night and when the server came back up our domain users could not access our SQL Server 2000 instance name: MASSQL.
We can access using SQL Authentication.
- We tried making sure the user that runs the service has SSPI read and Write
- We tried creating a new user
- We tried running the service using NETWORK SERVICE account
- We tried running as Local System Account
- We tried creating a new Domain Admin account and run service as the new Domain Admin account
I also ran the following command against the problem SQL Server instance:
setspn -L xsql2
Results
Registered ServicePrincipalNames for CN=MASSQL,CN=Computers,DC=ABC,DC=com:
HOST/MASSQL
HOST/MASSQL.ABC.COM
I ran the following command against a non-problem SQL instance:
setspn -L xensql1
Results
Registered ServicePrincipalNames for CN=XENSQL1,CN=Computers,DC=ABC,DC=com:
WSMAN/XENSQL1
WSMAN/XENSQL1.ABC.com
RestrictedKrbHost/XENSQL1
HOST/XENSQL1
RestrictedKrbHost/XENSQL1.ABC.COM
HOST/XENSQL1.ABC.COM
It seems the results for the non-problem instance have more data. I do not know if this has to do with the fact one is 2000 and the other is 2012.
What likely happened? How do I allow domain users login again?
sql-server active-directory
sql-server active-directory
edited Jun 20 at 17:16
Max Vernon
54k13 gold badges117 silver badges242 bronze badges
asked Jun 20 at 17:13
Bill GreerBill Greer
1215 bronze badges
edited Jun 20 at 17:16
Max Vernon
54k13 gold badges117 silver badges242 bronze badges
asked Jun 20 at 17:13
Bill GreerBill Greer
1215 bronze badges
edited Jun 20 at 17:16
Max Vernon
54k13 gold badges117 silver badges242 bronze badges
edited Jun 20 at 17:16
Max Vernon
54k13 gold badges117 silver badges242 bronze badges
edited Jun 20 at 17:16
Max Vernon
54k13 gold badges117 silver badges242 bronze badges
54k13 gold badges117 silver badges242 bronze badges
asked Jun 20 at 17:13
Bill GreerBill Greer
1215 bronze badges
asked Jun 20 at 17:13
Bill GreerBill Greer
1215 bronze badges
asked Jun 20 at 17:13
Bill GreerBill Greer
1215 bronze badges
1215 bronze badges
Now's a good time to upgrade :) Did the domain controller lose power too? Anything else having similar issues? That's where I'd start
– scsimon
Jun 20 at 17:16
reboot the server again and verify that windows services all came up...
– kevinsky
Jun 20 at 17:17
What does the SQL Server Error log say about registering Service Principal Names?
– Max Vernon
Jun 20 at 17:20
add a comment |
Now's a good time to upgrade :) Did the domain controller lose power too? Anything else having similar issues? That's where I'd start
– scsimon
Jun 20 at 17:16
reboot the server again and verify that windows services all came up...
– kevinsky
Jun 20 at 17:17
What does the SQL Server Error log say about registering Service Principal Names?
– Max Vernon
Jun 20 at 17:20
Now's a good time to upgrade :) Did the domain controller lose power too? Anything else having similar issues? That's where I'd start
– scsimon
Jun 20 at 17:16
Now's a good time to upgrade :) Did the domain controller lose power too? Anything else having similar issues? That's where I'd start
– scsimon
Jun 20 at 17:16
reboot the server again and verify that windows services all came up...
– kevinsky
Jun 20 at 17:17
reboot the server again and verify that windows services all came up...
– kevinsky
Jun 20 at 17:17
What does the SQL Server Error log say about registering Service Principal Names?
– Max Vernon
Jun 20 at 17:20
What does the SQL Server Error log say about registering Service Principal Names?
– Max Vernon
Jun 20 at 17:20
add a comment |
2 Answers
2
active
oldest
votes
The SQL Server SPNs are not set on the computer account per se, but on the account that SQL Server is running under. You will need to create two SPNs for the SQL Server service if the service account does not have permissions to create the SPNs. The following examples assume using the default port of 1433.
SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>" "<DOMAIN><SERVICE_ACCOUNT_NAME>"
SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>:1433" "<DOMAIN><SERVICE_ACCOUNT_NAME>"
See Register a Service Principal Name for Kerberos Connections
To check to see if they are already there:
SetSPN -L ServiceAccountName
However, it seems that you may have bigger issues in play. If you configured SQL Server to run with a domain admin account, it should have had permissions to create the SPNs.
answered Jun 20 at 18:00
Tony HinkleTony Hinkle
3,5391 gold badge7 silver badges25 bronze badges
I will try and report back.
– Bill Greer
Jun 20 at 18:06
add a comment |
Use setspn -X to look for duplicate SPNs for the SQL Server in question.
Remove any duplicate SPNs that don't line up the SQL Server Service account in question.
Service Principal Names for SQL Server take the form of:
MSSQLSvc/server.domain:port
MSSQLSvc/server:port
Assuming your SQL Server is using the default TCP port, 1433, I would expect you need the following servers:
MSSQLSvc/MASSQL.abc.com:1433
MSSQLSvc/MASSQL:1433
You can create those SPNs using the following command:
SETSPN -A MSSQLSvc/MASSQL.abc.com:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:1433 DOMAINAccount
Where DOMAINAccount is the name of the service account used by SQL Server.
If your SQL Server uses a named instance, the SETSPN commands look like:
SETSPN -A MSSQLSvc/MASSQL.abc.com:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL.abc.com:INSTANCENAME DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:INSTANCENAME DOMAINAccount
answered Jun 20 at 17:18
Max VernonMax Vernon
54k13 gold badges117 silver badges242 bronze badges
No duplicates found for that server. I think I should have more SPNs for the server than this: HOST/MASSQL HOST/MASSQL.ABC.COM What do you think?
– Bill Greer
Jun 20 at 18:01
1
I've added details to my answer showing what you need.
– Max Vernon
Jun 20 at 18:42
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%2f241051%2fthe-target-principal-name-is-incorrect-cannot-generate-sspi-context-sql-or-ad%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
The SQL Server SPNs are not set on the computer account per se, but on the account that SQL Server is running under. You will need to create two SPNs for the SQL Server service if the service account does not have permissions to create the SPNs. The following examples assume using the default port of 1433.
SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>" "<DOMAIN><SERVICE_ACCOUNT_NAME>"
SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>:1433" "<DOMAIN><SERVICE_ACCOUNT_NAME>"
See Register a Service Principal Name for Kerberos Connections
To check to see if they are already there:
SetSPN -L ServiceAccountName
However, it seems that you may have bigger issues in play. If you configured SQL Server to run with a domain admin account, it should have had permissions to create the SPNs.
answered Jun 20 at 18:00
Tony HinkleTony Hinkle
3,5391 gold badge7 silver badges25 bronze badges
I will try and report back.
– Bill Greer
Jun 20 at 18:06
add a comment |
The SQL Server SPNs are not set on the computer account per se, but on the account that SQL Server is running under. You will need to create two SPNs for the SQL Server service if the service account does not have permissions to create the SPNs. The following examples assume using the default port of 1433.
SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>" "<DOMAIN><SERVICE_ACCOUNT_NAME>"
SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>:1433" "<DOMAIN><SERVICE_ACCOUNT_NAME>"
See Register a Service Principal Name for Kerberos Connections
To check to see if they are already there:
SetSPN -L ServiceAccountName
However, it seems that you may have bigger issues in play. If you configured SQL Server to run with a domain admin account, it should have had permissions to create the SPNs.
answered Jun 20 at 18:00
Tony HinkleTony Hinkle
3,5391 gold badge7 silver badges25 bronze badges
I will try and report back.
– Bill Greer
Jun 20 at 18:06
add a comment |
The SQL Server SPNs are not set on the computer account per se, but on the account that SQL Server is running under. You will need to create two SPNs for the SQL Server service if the service account does not have permissions to create the SPNs. The following examples assume using the default port of 1433.
SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>" "<DOMAIN><SERVICE_ACCOUNT_NAME>"
SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>:1433" "<DOMAIN><SERVICE_ACCOUNT_NAME>"
See Register a Service Principal Name for Kerberos Connections
To check to see if they are already there:
SetSPN -L ServiceAccountName
However, it seems that you may have bigger issues in play. If you configured SQL Server to run with a domain admin account, it should have had permissions to create the SPNs.
answered Jun 20 at 18:00
Tony HinkleTony Hinkle
3,5391 gold badge7 silver badges25 bronze badges
The SQL Server SPNs are not set on the computer account per se, but on the account that SQL Server is running under. You will need to create two SPNs for the SQL Server service if the service account does not have permissions to create the SPNs. The following examples assume using the default port of 1433.
SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>" "<DOMAIN><SERVICE_ACCOUNT_NAME>"
SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>:1433" "<DOMAIN><SERVICE_ACCOUNT_NAME>"
See Register a Service Principal Name for Kerberos Connections
To check to see if they are already there:
SetSPN -L ServiceAccountName
However, it seems that you may have bigger issues in play. If you configured SQL Server to run with a domain admin account, it should have had permissions to create the SPNs.
answered Jun 20 at 18:00
Tony HinkleTony Hinkle
3,5391 gold badge7 silver badges25 bronze badges
edited Jun 20 at 18:40
answered Jun 20 at 18:00
Tony HinkleTony Hinkle
3,5391 gold badge7 silver badges25 bronze badges
answered Jun 20 at 18:00
Tony HinkleTony Hinkle
3,5391 gold badge7 silver badges25 bronze badges
answered Jun 20 at 18:00
Tony HinkleTony Hinkle
3,5391 gold badge7 silver badges25 bronze badges
3,5391 gold badge7 silver badges25 bronze badges
I will try and report back.
– Bill Greer
Jun 20 at 18:06
add a comment |
I will try and report back.
– Bill Greer
Jun 20 at 18:06
I will try and report back.
– Bill Greer
Jun 20 at 18:06
I will try and report back.
– Bill Greer
Jun 20 at 18:06
add a comment |
Use setspn -X to look for duplicate SPNs for the SQL Server in question.
Remove any duplicate SPNs that don't line up the SQL Server Service account in question.
Service Principal Names for SQL Server take the form of:
MSSQLSvc/server.domain:port
MSSQLSvc/server:port
Assuming your SQL Server is using the default TCP port, 1433, I would expect you need the following servers:
MSSQLSvc/MASSQL.abc.com:1433
MSSQLSvc/MASSQL:1433
You can create those SPNs using the following command:
SETSPN -A MSSQLSvc/MASSQL.abc.com:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:1433 DOMAINAccount
Where DOMAINAccount is the name of the service account used by SQL Server.
If your SQL Server uses a named instance, the SETSPN commands look like:
SETSPN -A MSSQLSvc/MASSQL.abc.com:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL.abc.com:INSTANCENAME DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:INSTANCENAME DOMAINAccount
answered Jun 20 at 17:18
Max VernonMax Vernon
54k13 gold badges117 silver badges242 bronze badges
No duplicates found for that server. I think I should have more SPNs for the server than this: HOST/MASSQL HOST/MASSQL.ABC.COM What do you think?
– Bill Greer
Jun 20 at 18:01
1
I've added details to my answer showing what you need.
– Max Vernon
Jun 20 at 18:42
add a comment |
Use setspn -X to look for duplicate SPNs for the SQL Server in question.
Remove any duplicate SPNs that don't line up the SQL Server Service account in question.
Service Principal Names for SQL Server take the form of:
MSSQLSvc/server.domain:port
MSSQLSvc/server:port
Assuming your SQL Server is using the default TCP port, 1433, I would expect you need the following servers:
MSSQLSvc/MASSQL.abc.com:1433
MSSQLSvc/MASSQL:1433
You can create those SPNs using the following command:
SETSPN -A MSSQLSvc/MASSQL.abc.com:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:1433 DOMAINAccount
Where DOMAINAccount is the name of the service account used by SQL Server.
If your SQL Server uses a named instance, the SETSPN commands look like:
SETSPN -A MSSQLSvc/MASSQL.abc.com:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL.abc.com:INSTANCENAME DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:INSTANCENAME DOMAINAccount
answered Jun 20 at 17:18
Max VernonMax Vernon
54k13 gold badges117 silver badges242 bronze badges
No duplicates found for that server. I think I should have more SPNs for the server than this: HOST/MASSQL HOST/MASSQL.ABC.COM What do you think?
– Bill Greer
Jun 20 at 18:01
1
I've added details to my answer showing what you need.
– Max Vernon
Jun 20 at 18:42
add a comment |
Use setspn -X to look for duplicate SPNs for the SQL Server in question.
Remove any duplicate SPNs that don't line up the SQL Server Service account in question.
Service Principal Names for SQL Server take the form of:
MSSQLSvc/server.domain:port
MSSQLSvc/server:port
Assuming your SQL Server is using the default TCP port, 1433, I would expect you need the following servers:
MSSQLSvc/MASSQL.abc.com:1433
MSSQLSvc/MASSQL:1433
You can create those SPNs using the following command:
SETSPN -A MSSQLSvc/MASSQL.abc.com:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:1433 DOMAINAccount
Where DOMAINAccount is the name of the service account used by SQL Server.
If your SQL Server uses a named instance, the SETSPN commands look like:
SETSPN -A MSSQLSvc/MASSQL.abc.com:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL.abc.com:INSTANCENAME DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:INSTANCENAME DOMAINAccount
answered Jun 20 at 17:18
Max VernonMax Vernon
54k13 gold badges117 silver badges242 bronze badges
Use setspn -X to look for duplicate SPNs for the SQL Server in question.
Remove any duplicate SPNs that don't line up the SQL Server Service account in question.
Service Principal Names for SQL Server take the form of:
MSSQLSvc/server.domain:port
MSSQLSvc/server:port
Assuming your SQL Server is using the default TCP port, 1433, I would expect you need the following servers:
MSSQLSvc/MASSQL.abc.com:1433
MSSQLSvc/MASSQL:1433
You can create those SPNs using the following command:
SETSPN -A MSSQLSvc/MASSQL.abc.com:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:1433 DOMAINAccount
Where DOMAINAccount is the name of the service account used by SQL Server.
If your SQL Server uses a named instance, the SETSPN commands look like:
SETSPN -A MSSQLSvc/MASSQL.abc.com:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:1433 DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL.abc.com:INSTANCENAME DOMAINAccount
SETSPN -A MSSQLSvc/MASSQL:INSTANCENAME DOMAINAccount
answered Jun 20 at 17:18
Max VernonMax Vernon
54k13 gold badges117 silver badges242 bronze badges
edited Jun 20 at 18:41
answered Jun 20 at 17:18
Max VernonMax Vernon
54k13 gold badges117 silver badges242 bronze badges
answered Jun 20 at 17:18
Max VernonMax Vernon
54k13 gold badges117 silver badges242 bronze badges
answered Jun 20 at 17:18
Max VernonMax Vernon
54k13 gold badges117 silver badges242 bronze badges
54k13 gold badges117 silver badges242 bronze badges
No duplicates found for that server. I think I should have more SPNs for the server than this: HOST/MASSQL HOST/MASSQL.ABC.COM What do you think?
– Bill Greer
Jun 20 at 18:01
1
I've added details to my answer showing what you need.
– Max Vernon
Jun 20 at 18:42
add a comment |
No duplicates found for that server. I think I should have more SPNs for the server than this: HOST/MASSQL HOST/MASSQL.ABC.COM What do you think?
– Bill Greer
Jun 20 at 18:01
1
I've added details to my answer showing what you need.
– Max Vernon
Jun 20 at 18:42
No duplicates found for that server. I think I should have more SPNs for the server than this: HOST/MASSQL HOST/MASSQL.ABC.COM What do you think?
– Bill Greer
Jun 20 at 18:01
No duplicates found for that server. I think I should have more SPNs for the server than this: HOST/MASSQL HOST/MASSQL.ABC.COM What do you think?
– Bill Greer
Jun 20 at 18:01
1
1
I've added details to my answer showing what you need.
– Max Vernon
Jun 20 at 18:42
I've added details to my answer showing what you need.
– Max Vernon
Jun 20 at 18:42
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%2f241051%2fthe-target-principal-name-is-incorrect-cannot-generate-sspi-context-sql-or-ad%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
Now's a good time to upgrade :) Did the domain controller lose power too? Anything else having similar issues? That's where I'd start
– scsimon
Jun 20 at 17:16
reboot the server again and verify that windows services all came up...
– kevinsky
Jun 20 at 17:17
What does the SQL Server Error log say about registering Service Principal Names?
– Max Vernon
Jun 20 at 17:20