Cannot move quorum after disk replacement

We actually replaced the controller card on one of our clustered
servers (was the system controller not SAN controller). Ever since
then we have been getting these two errors when I try to move the SQL
group to that node. These are the only errors we are getting...
All records are there in DNS (forward and reverse).
Event Type: Warning
Event Source: ClusSvc
Event Category: Network Name Resource
Event ID: 1119
Date: 11/3/2007
Time: 11:11:55 AM
User: N/A
Computer: DB
Description:
The registration of DNS name sql.xxxxxxx.local for resource 'SQL
Network Name (SQL)' over adapter 'Local Area Connection' failed for
the following reason:
DNS bad key.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 39 23 00 00 9#..
Event Type: Warning
Event Source: ClusSvc
Event Category: Network Name Resource
Event ID: 1119
Date: 11/3/2007
Time: 11:11:55 AM
User: N/A
Computer: DB
Description:
The registration of DNS name cluster.xxxxxx.local for resource
'Cluster Name' over adapter 'Local Area Connection' failed for the
following reason:
DNS bad key.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 39 23 00 00 9#..
Try this:
http://support.microsoft.com/kb/871111
Regards,
John
Visit my blog: http://msmvps.com/blogs/jtoner
"Kat99" <katrina.allsup@.gmail.com> wrote in message
news:1194106983.471543.188530@.o38g2000hse.googlegr oups.com...
> We actually replaced the controller card on one of our clustered
> servers (was the system controller not SAN controller). Ever since
> then we have been getting these two errors when I try to move the SQL
> group to that node. These are the only errors we are getting...
> All records are there in DNS (forward and reverse).
> Event Type: Warning
> Event Source: ClusSvc
> Event Category: Network Name Resource
> Event ID: 1119
> Date: 11/3/2007
> Time: 11:11:55 AM
> User: N/A
> Computer: DB
> Description:
> The registration of DNS name sql.xxxxxxx.local for resource 'SQL
> Network Name (SQL)' over adapter 'Local Area Connection' failed for
> the following reason:
> DNS bad key.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 39 23 00 00 9#..
>
> Event Type: Warning
> Event Source: ClusSvc
> Event Category: Network Name Resource
> Event ID: 1119
> Date: 11/3/2007
> Time: 11:11:55 AM
> User: N/A
> Computer: DB
> Description:
> The registration of DNS name cluster.xxxxxx.local for resource
> 'Cluster Name' over adapter 'Local Area Connection' failed for the
> following reason:
> DNS bad key.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 39 23 00 00 9#..
>

Cannot install June CTP on Windows 2003 DC !!!

I am trying to install Sql Server 2005 June CTP on a Windows Server
2003 SP1 primary domain controller with IIS/ASP installed.

I get this error (when Sql Server Database Services is being installed:
"SQL Server Setup was unable add user NT AUTHORITY\NETWORK SERVICE to
local group SQLServer2005MSSQLServerADHelp­erUser".
And I am not alone!
See http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=18788

Any workaround or update to be able to install it on a domain controller, Microsoft?

Thanks!

Anybody?

Our environment requires installation of SQL 2005 on a server with Active Directory... so this is really a big issue.

Please, can somebody from MS look into this?|||We are a few days later now, and still, nowhere on the Internet I can find a solution.

Can somebody from Microsoft please respond?|||

Currently SQL Server 2005 will not install on a Domain Controller or on Windows Small Business Server. There is no known work around at this time other than installing on a machine that is not configured as a domain controller. This is a known issue and we're working on resolving it.

Dan

|||Yikes, this is a huge issue. I have this issue too on a single Win2K3 Server Standard with SP1, AD/DC. Active Directory and DC are required before setting up TFS.
|||I've been in contact with the TFS team on this issue. As long as you use the April CTP that shipped with TFS Beta 2 you're okay. You just can't use the June CTP.

Cannot generate SSPI context

Hi - I am trying to run a test environment with Windows Server 2003
(computer A) as my domain controller and a XP Pro machine (computer B). What
I want to do is to log in to sql server on A through B using windows
authentication. Everything works fine when I use sql server authentication,
but if I switch to windows authentication I get the error saying that it
"Cannot generate SSPI context."
I can use windows authentication fine if sql server is on the same
machine, it only doesn't work if I am trying to connect remotely.
The Sql Server service is running under the local system account, but I
have also tried to run it under a domain account (administrative) and the
same error occurs.
Any help will be appreciated,
MaerI've had this problem before, when i use a laptop on a domain. Win Auth
works. However, if i detact the laptop from the network, and try connecting
to a local instance (on the laptop) using WinAuth, i get the SSPI Context
error. I can however connect using SQL Auth.
I have therefore concluded that the SSPI Context error is usual due to some
kind of DNS error. Check your DNS is working correctly between machine A &
B, and that he XP machine is correctly on the domain (you might try removing
and adding it back onto the domain). You may find that you can't rejoin the
domain because of some connectivity or DNS issue.
Good luck.
O
"Maer" <maer@.auditleverage.com> wrote in message
news:OvMlclQvEHA.2876@.TK2MSFTNGP12.phx.gbl...
> Hi - I am trying to run a test environment with Windows Server 2003
> (computer A) as my domain controller and a XP Pro machine (computer B).
> What I want to do is to log in to sql server on A through B using windows
> authentication. Everything works fine when I use sql server
> authentication, but if I switch to windows authentication I get the error
> saying that it "Cannot generate SSPI context."
> I can use windows authentication fine if sql server is on the same
> machine, it only doesn't work if I am trying to connect remotely.
> The Sql Server service is running under the local system account, but I
> have also tried to run it under a domain account (administrative) and the
> same error occurs.
> Any help will be appreciated,
> Maer
>

Cannot Generate SSPI Context

Win Server 2003
SQL Server 2000 SP4
SharePoint Server

Win Server 2000 (Domain Controller / Active Drectory)

Clients: Win XP / Access XP

I have two clients that can access the SQL Server and one that can not. All clients can access SharePoint (SLQ Server Back end) and directories controlled by AD.

The one that cannot access the SQL Server errors: "Cannot Generate SSPI Context". I have verified:
1) date and time
2) occurances of Security.DLL (win/system32; program file/common files/AOL...; Service Pack Files/i386 (x2))
3) Not using cached credentials

we recently moved our network and did not change any settings on any of the computers. I read KB811889; those suggestions did not resolve the issue.

Please assist me in touble shooting this connection problem. Also, how does changing the SQL Server Port on the server affect SharePoints connection to its database?

Hi,

When NT authentication is used to connect to SQL Server, we use a security API called SSPI (Security Support Provider Interface). In general, it's a tool that allows for a "server" to verify (usually with an AD domain) that a "client" is the same as he/she claims to be. This is done with exchanging of security package via a secure connection. More details can be found in the MSDN (see Platform SDK: Authentication).

In order SSPI to be functioning normally, you need to follow the instructions at KB 811889, please go through them once again. In addition, the following post from Nan is very useful:

http://blogs.msdn.com/sql_protocols/archive/2005/10/19/482782.aspx

Regarding changing the port that SQL Server listens on: Microsoft has been given a standard port (1433) by the internet task force and by default, a Default SQL Server instance listens on it. Given that, the client APIs when detecting you are trying to connect to a "Default" instance automatically assume the port is 1433. Unlike this, Named SQL instances by default determine port dynamically - usually select an available one and if not set otherwise, every time upon startup attempt to reuse it. However, note that the client has no means of telling what the named instance port is or a modified default instance port is. The options are:

(1) Manually specify port at client (either via alias or via data source definition like Data Source=myserver,myport)

(2) Use discovery mechanism provided by SQL Browser (SQL 2005) or a special "listener" thread (in SQL 2000). The thread is "listening" on UDP port 1434 and upon request provides information about the settings of the SQL instances installed on the machine.

Note that if you change the port of a default instance, you cannot use the SQL Browser/Listener approach, because for default instances we do not make a roundtrip to Browser - for perf reasons. You could create an alias or specify port when connecting.

If you could avoid changing the default 1433 port of SQL Server, that'd be great. BTW - changing the port may be related to your SSPI errors.

HTH,

Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Cannot generate SSPI context

Hi - I am trying to run a test environment with Windows Server 2003
(computer A) as my domain controller and a XP Pro machine (computer B). What
I want to do is to log in to sql server on A through B using windows
authentication. Everything works fine when I use sql server authentication,
but if I switch to windows authentication I get the error saying that it
"Cannot generate SSPI context."
I can use windows authentication fine if sql server is on the same
machine, it only doesn't work if I am trying to connect remotely.
The Sql Server service is running under the local system account, but I
have also tried to run it under a domain account (administrative) and the
same error occurs.
Any help will be appreciated,
Maer
I've had this problem before, when i use a laptop on a domain. Win Auth
works. However, if i detact the laptop from the network, and try connecting
to a local instance (on the laptop) using WinAuth, i get the SSPI Context
error. I can however connect using SQL Auth.
I have therefore concluded that the SSPI Context error is usual due to some
kind of DNS error. Check your DNS is working correctly between machine A &
B, and that he XP machine is correctly on the domain (you might try removing
and adding it back onto the domain). You may find that you can't rejoin the
domain because of some connectivity or DNS issue.
Good luck.
O
"Maer" <maer@.auditleverage.com> wrote in message
news:OvMlclQvEHA.2876@.TK2MSFTNGP12.phx.gbl...
> Hi - I am trying to run a test environment with Windows Server 2003
> (computer A) as my domain controller and a XP Pro machine (computer B).
> What I want to do is to log in to sql server on A through B using windows
> authentication. Everything works fine when I use sql server
> authentication, but if I switch to windows authentication I get the error
> saying that it "Cannot generate SSPI context."
> I can use windows authentication fine if sql server is on the same
> machine, it only doesn't work if I am trying to connect remotely.
> The Sql Server service is running under the local system account, but I
> have also tried to run it under a domain account (administrative) and the
> same error occurs.
> Any help will be appreciated,
> Maer
>