According to some of the documentation I've read the service account for SQL server will create an SPN when the database engine starts up, allowing for kerberos authentication. I haven't been able to find any documentation that states what permission an account would need to create an SPN. So, what permissions would an account need to have (barring domain admin if that's possible) in order to create an SPN?
I'm following Brent Ozar's video on Benchmarking and Baselining, and I've got a data collector set on my local machine set up to hit a remote sql server, but I can't get the collection to start. I right click it to start and the perfmon window locks up for a second. After it stops locking up it still hasn't started, but it's not giving me any error. I've got it running under my windows domain account that is an admin on the sql server.
So, how can i get this working?
edit:
ok, i'm getting a windows security event for a logon failure when i try to run the collection.
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: [Machine$]
Account Domain: [DOMAIN]
Logon ID: 0x3e7Logon Type: 4
Account For Which Logon Failed:
Security ID: NULL SID Account Name: [USERNAME]
Account Domain: [DOMAIN]Failure Information: Failure Reason: The user has not been granted the requested logon type at this machine.
Status: 0xc000015b
Sub Status: 0x0Process Information:
Caller Process ID: 0x434
Caller Process Name: C:\Windows\System32\svchost.exeNetwork Information: Workstation Name: [MACHINE]
Source Network Address: -
Source Port: -Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: - Package Name (NTLM only): -
Key Length: 0This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
[MACHINE] is my computer, [DOMAIN] is our domain, and [USERNAME] is my username.
I've got reporting services and sql server 2005 installed on a windows server 2003 enterprise sp2 server. Reporting services was working just fine until yesterday it started saying "Error- Unable to connect to the remote server". I'm really not sure where to start to look for fixing this.
On a windows server 2003 server, i have a particular service that's causing me a lot of heartache. I was wondering if there was a way to set up performance monitor to track information for the service? the specific service i'm interested in is Project Server Views Notification Service.
So, we're restructuring out development environment. We've installed SQL Server onto it's own server, and we are publishing our internal web applications onto a seperate web server. However, the problem is that for some reason the authentication of the user between the web server and sql server gets lost, resulting in the Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON' error.
Where do i start troubleshooting? SQL Server is set up for TCP and remote connections.