turfnsurf4me (10/19/2010)
What I neglected to articulate is that I use the ADSI Edit snap-in and edit the service principal name property ( of the service account) directly while on the domain controller. I don't use the command line interface to create or modify the property. You see what I'm saying? Trust me...the SPN is correct. I've been doing this for years.When I'm done doing what I just said, the SPN is...
MSSQLsvc/sq01:1433
MSSQLsvc/sq01.virt.local:1433
I see, the SPN above is what you see via ADSIEDIT against the service account. I wrongly assumed you had listed against the computer account. You would be surprised how many people do not understand that the SPN should be bound to the service account and not the computer account when running the service under the context of a low privilege user account!
turfnsurf4me (10/19/2010)
And even if I did have the SPN hosed, it still wouldn't explain why the process doesn't start
I never said or implied that it did, my reference was to the seemingly incorrect SPN binding.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉