April 17, 2012 at 1:26 am
I have two servers called
DBP01 (Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) )
DBT01 (Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) )
The servers live in a domain called London.
The Dev team and myself live in a Domain called Berlin
DBP01 uses windows account called WinUserDBP01 for the MSSQLSERVER service and is available to users in both London and Berlin Domains
When DBT01 uses this windows account it is not available to users in the Berlin domain, however it is available to users in the Berlin domain when running under local system account.
I am sure I am overlooking something really obvious, but I just cannot see it.
Any help would be greatly appreciated.
Thanks Ian
PS
I will not be able to restart server/ services until the Dev team go home, this is not an urgent call for help 😉
April 17, 2012 at 1:41 am
Silly question I know, but are the 2x domains in the same forrest?
Also, is there a reason for using the same service account for both servers?
April 17, 2012 at 1:47 am
SQLDBA360 (4/17/2012)
Silly question I know, but are the 2x domains in the same forrest?Also, is there a reason for using the same service account for both servers?
yes I believe so, but I have just emailed the SysAdmins to be sure.
April 17, 2012 at 1:59 am
SQLDBA360 (4/17/2012)
Also, is there a reason for using the same service account for both servers?
DBT01 does have its own service account, which also produces the same error, I tested again with the DBP01 service account to eliminate the possibility of differences with the accounts
April 17, 2012 at 2:09 am
One more silly question, hopefully my last, but the SQL Server Services are starting ok with the domain accounts?
April 17, 2012 at 2:33 am
SQLDBA360 (4/17/2012)
One more silly question, hopefully my last, but the SQL Server Services are starting ok with the domain accounts?
Yes both servers start OK with the domain accounts.
April 17, 2012 at 4:22 am
440692 I am just a number (4/17/2012)
SQLDBA360 (4/17/2012)
One more silly question, hopefully my last, but the SQL Server Services are starting ok with the domain accounts?Yes both servers start OK with the domain accounts.
:blush: Actually that may not be true,
checking the event logs I have located the following
The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
At last I have something to start googling.
thanks for your help
Ian
April 25, 2012 at 7:14 am
Ian did you check the relationship between the 2x domains
April 25, 2012 at 8:04 am
SQLDBA360 (4/25/2012)
Ian did you check the relationship between the 2x domains
The two domains are in the same forest.
The latest stand is, under a local system account we can log into the server via SSMS with both windows and server authentication.
using the windows account we can log in with server authentication, but receive the following error message when using windows authentication.
TITEL: Verbindung mit Server herstellen
------------------------------
Es kann keine Verbindung mit 'DBT01' hergestellt werden.
------------------------------
ZUSÄTZLICHE INFORMATIONEN:
Der SSPI-Kontext kann nicht generiert werden. (Microsoft SQL Server, Fehler: 0)
Hilfe erhalten Sie durch Klicken auf: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=0&LinkId=20476
------------------------------
(all servers PC etc are German)
After googling this a little further I decided it was an issue with the permissions given to the windows user and passed it over to our sysadmins to look at.
they said it was a sqlserver configuration issue and passed it back.
Thanks very much for taking the time to come back and check on me.
much appreciated
Ian
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply