Installing SQL Server 2005 is not creating the SPNs

After installing SQL Server 2005 x64 as Administrator in Windows Server 2003, I run setspn -L serviceaccountname and the install is only creating 1 entry on the domain controller (Windows Server 2003 x86). It should create multiple from what I understand. I also know that I can create these manually but I shouldn't have to and this is telling me that something is wrong. Any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PberSolutions ArchitectCommented:
Is the sql server running under a domain account?  If so do this:
...specifically: Step 3: Configure the SQL Server service to create SPNs dynamically

This too:
PberSolutions ArchitectCommented:
Also I found that is usually only registers the FQDN SPN.  You can also manually add  the NetBIOS SPN as needed as per the second link above.

setspn -A MSSQLSvc/ MYDOMAIN\sqlsvc
setspn -A MSSQLSvc/myserver:1433 MYDOMAIN\sqlsvc

If SQL is running under the local system it should register it's own SPN's.  In this case for Constrained Delegation, you would then delegate the computer account to a remote service as opposed to delegating the service account as you would do if it would be running under a domain account.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Chris24Author Commented:
I wiped and rebuilt my domain controller, setup my domain, joined the SQL server to the domain, trusted that server for delegation, ran the SQL Server 2005 x64 install installing ALL options Analysis, Reporting, etc... and it created ONE SPN on my DC. I ran and installed a new instance and it created just ONE additional SPN for that instance. My DB guy here says there should be more than the one??? Is this correct? It obviously has permission to create if it created one. Should there be more than one SPN per instance? Each SPN is pointing to the correct port number

Server 1: SQL Server 2005 - Windows 2003 R2 x64 - Dell PowerEdge 2900
Domain Controller: Windows 2003 R2 x86

We've been going round and round with this for two weeks now.

PberSolutions ArchitectCommented:
Are you running SQL under a domain service account or local system?
What rights does the SQL service account have?  (Normal user, domain admin).

From my experience, SQL will only create one FQDN SPN for each instance even if you allow dynamic SPN registration (as per my previous post)

Are you just trying to setup Kerberos double hop Authentication?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.