Greetings!
I'm trying to install SQL Server 2000 (Standard edition) on a new server to
mirror the version on an older server. The trouble I'm having is with
identifying the settings I need in order to match collations.
The instance of SQL Server on the old server has a collation described as
'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
case-insensitive and accent-sensitive respectively, but what does 'CP1'
relate to?
I've searched through various resources but they all seem to avoid
describing that one crucial bit of information! Can anyone help?
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
|||In setup you should select "Dictionary order, case-insensitive, for use
with 1252 character set" in the collation selection dialog. This is the
default collation for U.S. English SQL Servers.
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: "Adam Machanic" <amachanic@.hotmail._removetoemail_.com>
References: <O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl>
Subject: Re: Collation Confusion
Date: Thu, 24 Jun 2004 13:08:24 -0400
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <uAyDd3gWEHA.1468@.TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.sqlserver.server
NNTP-Posting-Host: firewall.getconnected.com 207.31.238.50
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftn gxa06.phx.gbl!TK2MSFTNGX
A01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx. gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347579
X-Tomcat-NG: microsoft.public.sqlserver.server
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described
as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
sqlsql
Showing posts with label install. Show all posts
Showing posts with label install. Show all posts
Sunday, March 25, 2012
Thursday, March 22, 2012
Collation Confusion
Greetings!
I'm trying to install SQL Server 2000 (Standard edition) on a new server to
mirror the version on an older server. The trouble I'm having is with
identifying the settings I need in order to match collations.
The instance of SQL Server on the old server has a collation described as
'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
case-insensitive and accent-sensitive respectively, but what does 'CP1'
relate to?
I've searched through various resources but they all seem to avoid
describing that one crucial bit of information! Can anyone help?Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>|||In setup you should select "Dictionary order, case-insensitive, for use
with 1252 character set" in the collation selection dialog. This is the
default collation for U.S. English SQL Servers.
--
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: "Adam Machanic" <amachanic@.hotmail._removetoemail_.com>
References: <O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl>
Subject: Re: Collation Confusion
Date: Thu, 24 Jun 2004 13:08:24 -0400
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <uAyDd3gWEHA.1468@.TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.sqlserver.server
NNTP-Posting-Host: firewall.getconnected.com 207.31.238.50
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGX
A01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347579
X-Tomcat-NG: microsoft.public.sqlserver.server
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described
as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
I'm trying to install SQL Server 2000 (Standard edition) on a new server to
mirror the version on an older server. The trouble I'm having is with
identifying the settings I need in order to match collations.
The instance of SQL Server on the old server has a collation described as
'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
case-insensitive and accent-sensitive respectively, but what does 'CP1'
relate to?
I've searched through various resources but they all seem to avoid
describing that one crucial bit of information! Can anyone help?Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>|||In setup you should select "Dictionary order, case-insensitive, for use
with 1252 character set" in the collation selection dialog. This is the
default collation for U.S. English SQL Servers.
--
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: "Adam Machanic" <amachanic@.hotmail._removetoemail_.com>
References: <O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl>
Subject: Re: Collation Confusion
Date: Thu, 24 Jun 2004 13:08:24 -0400
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <uAyDd3gWEHA.1468@.TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.sqlserver.server
NNTP-Posting-Host: firewall.getconnected.com 207.31.238.50
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGX
A01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347579
X-Tomcat-NG: microsoft.public.sqlserver.server
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described
as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
Collation Confusion
Greetings!
I'm trying to install SQL Server 2000 (Standard edition) on a new server to
mirror the version on an older server. The trouble I'm having is with
identifying the settings I need in order to match collations.
The instance of SQL Server on the old server has a collation described as
'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
case-insensitive and accent-sensitive respectively, but what does 'CP1'
relate to?
I've searched through various resources but they all seem to avoid
describing that one crucial bit of information! Can anyone help?Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>|||In setup you should select "Dictionary order, case-insensitive, for use
with 1252 character set" in the collation selection dialog. This is the
default collation for U.S. English SQL Servers.
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: "Adam Machanic" <amachanic@.hotmail._removetoemail_.com>
References: <O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl>
Subject: Re: Collation Confusion
Date: Thu, 24 Jun 2004 13:08:24 -0400
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <uAyDd3gWEHA.1468@.TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.sqlserver.server
NNTP-Posting-Host: firewall.getconnected.com 207.31.238.50
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGX
A01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347579
X-Tomcat-NG: microsoft.public.sqlserver.server
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described
as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
I'm trying to install SQL Server 2000 (Standard edition) on a new server to
mirror the version on an older server. The trouble I'm having is with
identifying the settings I need in order to match collations.
The instance of SQL Server on the old server has a collation described as
'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
case-insensitive and accent-sensitive respectively, but what does 'CP1'
relate to?
I've searched through various resources but they all seem to avoid
describing that one crucial bit of information! Can anyone help?Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>|||In setup you should select "Dictionary order, case-insensitive, for use
with 1252 character set" in the collation selection dialog. This is the
default collation for U.S. English SQL Servers.
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: "Adam Machanic" <amachanic@.hotmail._removetoemail_.com>
References: <O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl>
Subject: Re: Collation Confusion
Date: Thu, 24 Jun 2004 13:08:24 -0400
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <uAyDd3gWEHA.1468@.TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.sqlserver.server
NNTP-Posting-Host: firewall.getconnected.com 207.31.238.50
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGX
A01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347579
X-Tomcat-NG: microsoft.public.sqlserver.server
Code page 1
"Mario" <someone.else@.microsoft.com> wrote in message
news:O3bumugWEHA.1368@.TK2MSFTNGP10.phx.gbl...
> Greetings!
> I'm trying to install SQL Server 2000 (Standard edition) on a new server
to
> mirror the version on an older server. The trouble I'm having is with
> identifying the settings I need in order to match collations.
> The instance of SQL Server on the old server has a collation described
as
> 'SQL_Latin1_General_CP1_CI_AS'. I realise that 'CI' and 'AS' refer to
> case-insensitive and accent-sensitive respectively, but what does 'CP1'
> relate to?
> I've searched through various resources but they all seem to avoid
> describing that one crucial bit of information! Can anyone help?
>
Tuesday, March 20, 2012
Collation
Hi,
what diff between SQL_Latin1_General_CP1_CI_AS and SQL_Latin1_General_CI_AS?
Why on win2003 install msde, the master database will have
SQL_Latin1_General_CI_AS instead of
SQL_Latin1_General_CP1_CI_AS?
Please advice. Thanks.> Why on win2003 install msde, the master database will have
> SQL_Latin1_General_CI_AS instead of
> SQL_Latin1_General_CP1_CI_AS?
SQL_Latin1_General_CI_AS is not a valid collation. Can you explain where
you are seeing this?
On 8.00.2039 I ran the following script:
SELECT 'foo' COLLATE SQL_Latin1_General_CI_AS
GO
--
Server: Msg 448, Level 16, State 1, Line 1
Invalid collation 'SQL_Latin1_General_CI_AS'.
To explain why databases have different *valid* collations, keep in mind
that you can create a database and specify a specific collation, otherwise
it will get the server default (which you set when you install SQL Server).
CREATE DATABASE foobar1 COLLATE SQL_Latin1_General_CP1_CI_AS
GO
CREATE DATABASE foobar2 COLLATE SQL_Latin1_General_CI_AS
GO
--
The CREATE DATABASE process is allocating 0.63 MB on disk 'foobar1'.
The CREATE DATABASE process is allocating 0.49 MB on disk 'foobar1_log'.
Server: Msg 448, Level 16, State 3, Line 2
Invalid collation 'SQL_Latin1_General_CI_AS'.
My suggestion is to use the server default when possible (which means
leaving the COLLATE keyword off of the CREATE DATABASE statement).|||Sorry, it is: Latin1_General_CI_AS on win2003,
but it will be SQL_Latin1_General_CP1_CI_AS on win2000. Why? I don't specify
any option during the installtion.
Please help.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ubLzwSIuFHA.3864@.TK2MSFTNGP12.phx.gbl...
> SQL_Latin1_General_CI_AS is not a valid collation. Can you explain where
> you are seeing this?
> On 8.00.2039 I ran the following script:
> SELECT 'foo' COLLATE SQL_Latin1_General_CI_AS
> GO
> --
> Server: Msg 448, Level 16, State 1, Line 1
> Invalid collation 'SQL_Latin1_General_CI_AS'.
> To explain why databases have different *valid* collations, keep in mind
> that you can create a database and specify a specific collation, otherwise
> it will get the server default (which you set when you install SQL
> Server).
> CREATE DATABASE foobar1 COLLATE SQL_Latin1_General_CP1_CI_AS
> GO
> CREATE DATABASE foobar2 COLLATE SQL_Latin1_General_CI_AS
> GO
> --
> The CREATE DATABASE process is allocating 0.63 MB on disk 'foobar1'.
> The CREATE DATABASE process is allocating 0.49 MB on disk 'foobar1_log'.
> Server: Msg 448, Level 16, State 3, Line 2
> Invalid collation 'SQL_Latin1_General_CI_AS'.
> My suggestion is to use the server default when possible (which means
> leaving the COLLATE keyword off of the CREATE DATABASE statement).
>|||> but it will be SQL_Latin1_General_CP1_CI_AS on win2000. Why?
I'm not sure, I don't have any Win2000 servers around, only Windows 2003.
It may be the default collation when installing on Windows 2000, or it may
be the product of a SQL Server 7.0 upgrade.
The collations themselves are essentially the same, see the following:
SELECT name,description
FROM ::fn_helpcollations()
WHERE name IN
(
'Latin1_General_CI_AS',
'SQL_Latin1_General_CP1_CI_AS'
)
However, note that the SQL_Latin1 variation is used for backward
compatibility only. Going forward, SQL Server will be moving toward the
less verbose Latin1_ variations. See Go|URL|architec.chm::/8_ar_da_3xbn.htm
in Books Online for more information.
> Please help.
What exactly are trying to solve? If you are having collation conflicts
when merging/retrieving data across a linked server, you can set the
collations to be "compatible" using the following statement on each side:
EXEC master..sp_serveroption
@.server = 'Other_Linked_Server_Name',
@.optname = 'Collation Compatible',
@.optvalue = 'true'
You can use the same technique temporarily if you want to migrate the data
from the existing "badly collated" database to a new database with the right
collation.|||Thanks Aaron,
That's I'm looking for...
"Aaron Bertrand [SQL Server MVP]" wrote in message:
> What exactly are trying to solve? If you are having collation conflicts
> when merging/retrieving data across a linked server, you can set the
> collations to be "compatible" using the following statement on each side:
> EXEC master..sp_serveroption
> @.server = 'Other_Linked_Server_Name',
> @.optname = 'Collation Compatible',
> @.optvalue = 'true'
> You can use the same technique temporarily if you want to migrate the data
> from the existing "badly collated" database to a new database with the
> right collation.
>|||"Aaron Bertrand wrote:
> What exactly are trying to solve? If you are having collation conflicts
> when merging/retrieving data across a linked server, you can set the
> collations to be "compatible" using the following statement on each side:
> EXEC master..sp_serveroption
> @.server = 'Other_Linked_Server_Name',
> @.optname = 'Collation Compatible',
> @.optvalue = 'true'
>
Can I chanage the master, model, tempdb, msdb's collation without
rebuild(through option or property)? Thaks|||> Can I chanage the master, model, tempdb, msdb's collation without
> rebuild(through option or property)?
I don't think so.
If you can, I doubt it's supported.
I would feel much safer recommending detaching your database(s) and
reinstalling SQL Server. You're going to have to migrate the data to the
new collation anyway.|||Thanks Aaron.
what diff between SQL_Latin1_General_CP1_CI_AS and SQL_Latin1_General_CI_AS?
Why on win2003 install msde, the master database will have
SQL_Latin1_General_CI_AS instead of
SQL_Latin1_General_CP1_CI_AS?
Please advice. Thanks.> Why on win2003 install msde, the master database will have
> SQL_Latin1_General_CI_AS instead of
> SQL_Latin1_General_CP1_CI_AS?
SQL_Latin1_General_CI_AS is not a valid collation. Can you explain where
you are seeing this?
On 8.00.2039 I ran the following script:
SELECT 'foo' COLLATE SQL_Latin1_General_CI_AS
GO
--
Server: Msg 448, Level 16, State 1, Line 1
Invalid collation 'SQL_Latin1_General_CI_AS'.
To explain why databases have different *valid* collations, keep in mind
that you can create a database and specify a specific collation, otherwise
it will get the server default (which you set when you install SQL Server).
CREATE DATABASE foobar1 COLLATE SQL_Latin1_General_CP1_CI_AS
GO
CREATE DATABASE foobar2 COLLATE SQL_Latin1_General_CI_AS
GO
--
The CREATE DATABASE process is allocating 0.63 MB on disk 'foobar1'.
The CREATE DATABASE process is allocating 0.49 MB on disk 'foobar1_log'.
Server: Msg 448, Level 16, State 3, Line 2
Invalid collation 'SQL_Latin1_General_CI_AS'.
My suggestion is to use the server default when possible (which means
leaving the COLLATE keyword off of the CREATE DATABASE statement).|||Sorry, it is: Latin1_General_CI_AS on win2003,
but it will be SQL_Latin1_General_CP1_CI_AS on win2000. Why? I don't specify
any option during the installtion.
Please help.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ubLzwSIuFHA.3864@.TK2MSFTNGP12.phx.gbl...
> SQL_Latin1_General_CI_AS is not a valid collation. Can you explain where
> you are seeing this?
> On 8.00.2039 I ran the following script:
> SELECT 'foo' COLLATE SQL_Latin1_General_CI_AS
> GO
> --
> Server: Msg 448, Level 16, State 1, Line 1
> Invalid collation 'SQL_Latin1_General_CI_AS'.
> To explain why databases have different *valid* collations, keep in mind
> that you can create a database and specify a specific collation, otherwise
> it will get the server default (which you set when you install SQL
> Server).
> CREATE DATABASE foobar1 COLLATE SQL_Latin1_General_CP1_CI_AS
> GO
> CREATE DATABASE foobar2 COLLATE SQL_Latin1_General_CI_AS
> GO
> --
> The CREATE DATABASE process is allocating 0.63 MB on disk 'foobar1'.
> The CREATE DATABASE process is allocating 0.49 MB on disk 'foobar1_log'.
> Server: Msg 448, Level 16, State 3, Line 2
> Invalid collation 'SQL_Latin1_General_CI_AS'.
> My suggestion is to use the server default when possible (which means
> leaving the COLLATE keyword off of the CREATE DATABASE statement).
>|||> but it will be SQL_Latin1_General_CP1_CI_AS on win2000. Why?
I'm not sure, I don't have any Win2000 servers around, only Windows 2003.
It may be the default collation when installing on Windows 2000, or it may
be the product of a SQL Server 7.0 upgrade.
The collations themselves are essentially the same, see the following:
SELECT name,description
FROM ::fn_helpcollations()
WHERE name IN
(
'Latin1_General_CI_AS',
'SQL_Latin1_General_CP1_CI_AS'
)
However, note that the SQL_Latin1 variation is used for backward
compatibility only. Going forward, SQL Server will be moving toward the
less verbose Latin1_ variations. See Go|URL|architec.chm::/8_ar_da_3xbn.htm
in Books Online for more information.
> Please help.
What exactly are trying to solve? If you are having collation conflicts
when merging/retrieving data across a linked server, you can set the
collations to be "compatible" using the following statement on each side:
EXEC master..sp_serveroption
@.server = 'Other_Linked_Server_Name',
@.optname = 'Collation Compatible',
@.optvalue = 'true'
You can use the same technique temporarily if you want to migrate the data
from the existing "badly collated" database to a new database with the right
collation.|||Thanks Aaron,
That's I'm looking for...
"Aaron Bertrand [SQL Server MVP]" wrote in message:
> What exactly are trying to solve? If you are having collation conflicts
> when merging/retrieving data across a linked server, you can set the
> collations to be "compatible" using the following statement on each side:
> EXEC master..sp_serveroption
> @.server = 'Other_Linked_Server_Name',
> @.optname = 'Collation Compatible',
> @.optvalue = 'true'
> You can use the same technique temporarily if you want to migrate the data
> from the existing "badly collated" database to a new database with the
> right collation.
>|||"Aaron Bertrand wrote:
> What exactly are trying to solve? If you are having collation conflicts
> when merging/retrieving data across a linked server, you can set the
> collations to be "compatible" using the following statement on each side:
> EXEC master..sp_serveroption
> @.server = 'Other_Linked_Server_Name',
> @.optname = 'Collation Compatible',
> @.optvalue = 'true'
>
Can I chanage the master, model, tempdb, msdb's collation without
rebuild(through option or property)? Thaks|||> Can I chanage the master, model, tempdb, msdb's collation without
> rebuild(through option or property)?
I don't think so.
If you can, I doubt it's supported.
I would feel much safer recommending detaching your database(s) and
reinstalling SQL Server. You're going to have to migrate the data to the
new collation anyway.|||Thanks Aaron.
Sunday, March 11, 2012
Co-exist of SQL 2000 and 2005
Dear all, 1. Click Start, click Run, type regedit, and then click OK. 2. Locate the following registry subkey: 3. Right-click the ClientSetup registry subkey, point to New, and then click String Value. 4. Rename the registry subkey that you just created SqlPath, and then press ENTER. 5. Double-click the SqlPath registry subkey, and then type C:\Program Files\Microsoft SQL Server\80\Tools in the Value data box. 6. Click OK, and then close Registry Editor. 7. Click Start, click Run, type regsvr32 "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmmc.dll", and then click OK.
I have SQL 2000 Enterprise mgr and Query Analyzer in my desktop, and I install SQL2005 Express Edition + Mgm Studio today, however, my SQL 2000 Enterprise mgr disappear and all my registered servers disappear too when I open up the SQL 2005 Mgm Studio. Is it mean that I no longer able to use SQL 2000? How can I rollback the installation of SQL 2005 because I still have to use Enterprise mgr to manage my existing database and clients. (Yes, I give up SQL 2005 now)
Thanks,
The 2 should work side by side just fine, there is no need to uninstall. What do you mean Enterprise Manager disapears? Did you do a sidebyside install or an upgrade?|||
You say 'when I open up 2005 Management Studio..'
If you did a sidebyside install, all your 2000 stuff is till there, but you still use 2000 EM for them, they aren't in Management Studio. Your old EM should still be available from the programs menu, and 2005 have it's own start menu.
/Kenneth
|||Hi Ken,Thanks for your advice, Maybe I select "upgrade" SQL 2000 to SQL 2005 in the installation process (is there an option like this?)... so everything gone and I can't see my SQL 2000 Enterprice Manaager and Query Analyzer (you know, these 2 tools are the best friend of DBA ;)
I tried to uninstall SQL 2005 and select "side by side" installation (is there a option like this?) but it create another problem: here.
My original database in SQL 2000 disappear even I re-install SQL 2000 EM, but the MDF and LDF are still in my machine, so I want to "attach" these database immediately, but I can't do so.. do you know why?
(Installation of SQL 2005 is quite problematic... and bring some other problems as well in my opinion.. I can use my EM and QA smoothly over the last few years)
Thanks!
|||So it sounds like you did an upgrade to SQL 2005. For the tools you can uninstall 2005 and then re-install 2000 and it should work, HOWEVER for your data this is a problem. Once a database has been touched by a 2005 server it can not be attached or restored on a 2000 machine. Your only choice is to export the data from a 2005 running copy of the database, out to csv/text etc and then load that on on the other side.|||
Oh my god... I just un-install the SQL 2005 and re-install SQL 2000, that's fine. I want to make everything back to normal first.
Next, I install a lite version of SQL 2005 Express instead (Yes, I'm afraid the SQL 2005 now), and I specifically choose NOT upgrade my existing database (Well, the upgrade option is disabled by default due to the limitation of SQL 2005 Express anyway, so I'm pretty sure it WON'T affect my existing SQL 2000 DBs and Enterprise Mgr, alright?)
However, the result is - It break all of my databases AGAIN. And an error message come out when I try to open my SQL 2000 Ent. Mgr:
Microsoft Management Console
Snap-in failed to initialize.
Name:<unknown>
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I'm pretty sure the co-existence of SQL 2000 and SQL 2005 (any edition) is very poor.. I can't do any project against my SQL 2000 nor SQL 20005 db now. :(
Thanks,
|||Sorry but you are wrong, SQL 2000 and 2005 work just fine together, it is unfortunate that you are having problems, btu I run 4 machiens with this config and they all work fine, as do 10,000s of others.
What do you mean the databases are broken, is there an error message?
To fix the mmc problem try and run regsvr32 on sqlmmc.dll
|||I'm also running a few servers running both SQL2k and 2005 without problems. Servers did not upgrade the existing sql2k 's. I installed the 2005's as new instances.
Eralper
http://www.kodyaz.com
|||Euan Garden wrote:
To fix the mmc problem try and run regsvr32 on sqlmmc.dll
I have more than 1 machine with SQL 2005 installed, and nearly 50% of them are facing various problem. I understand that there're 10000s installation successed, but you should be aware that there're also have another 10000s installation failed and looking for help here or other NGs everyday. This is a pain. Even 1 installation failed, this product is buggy.
The databases can't be attached or re-used anymore if SQL 2005 "touch" the db from SQL 2000, that's a famous bug since beta age.
The regsvr32 sqlmmc.dll and sqldmo.dll are no good...
Thanks,
|||Sorry peter but there are not 1000's of installations which are failed.
Correct once a DB is touched by 2005 it can not be moved back, this is not a bug this is by design, we have to upgrade the format to be able to use the new features of SQL 2000, this has been this way for the last 4 versions of SQL Server and I believe is also true for other DB vendors.
When you say that sqlmmc and sqldmo are no good are you saying that you tried to re-reg and ti did not work?
|||We have to buy all license and upgrade to SQL 2005 immmediately and we don't have any backward compatiability if we're using SQL 2000? Compatiability and stability are two of the key factors for any DB system.
re-reg doesn't help, SQL 2000 Enterprise Manager still messed up.
(Please see this MSDN blog for more info about this bug)
Thanks,
|||First of all you don't have to buy new licenses and upgrade, SQL 2000 is a fine product and will be support for several years to come. However if you want to upgrade and get the new version you can.
Your definition of Back Compat differs from mine (and that of the SQL Server Team), apps that work against SQL2000/7 should work against SQL 2005 without changes, thats significant. SQL 2005 can used SQL 2000 as a linked server, it can consume backups, database files and data via OLE DB and ADO.Net. All of that is pretty impressive.
Your issue is that you have taken a SQL Server 2000 DB, and attached it to SQL 2005, obviously wanting to leverage the new features of SQL 2005, to do that means changes to the file format, making it impossible to use the file on 2000(but you can script out) just as if you had used one of the new T-SQL commands in your app, that would not run against a 2000 server. Just like a Winforms 2.0 app will not run against .Net 1.1, just as a etc etc. I'm sorry you disagree with the principle, but this decision/position does not imply anything related to the stability of the system, which is just fine.
I am very familiar with the "bug" and the blog entry you reference(hint take a look at the author of the entry), this is not the same bug. Re-registering DMO fixes the CTP bug you reference.
Now back to the original problem of EM not working. When you re-reg sqlmmc and sqldmo to they both register correctly or is there an error message? If they register correctly has the error message you get when trying to start EM the same or has it changed from the original post? Have you tried applying SP4 of SQL 2000 again?
|||Sorry to post this bug here, but this is the problem after my installation of SQL 2005. I don't want to upgrade my SQL 2000 database to SQL 2005 in fact, if you read my posts above.The wizard drive me to this stage and now, the database can't be rollbacked to its original state, which is a backward process. Sorry that you have another definition of backward compatibility, but please be considerate when you reading post here, even you have your own definition in your own mind. You can't force others to follow your own definion and you don't have problem in the installation doesn't mean other 10000 people are as lucky as you.
The problem and error messages and all service pack installed. Please read the posts but don't just focus on what you like to see but ignore others' opinion.
Thanks,
|||
If you are playing around with
various versions or instances of MS SQL Server
you may hit the problem of
Microsoft Management Console
Snap-in failed to initialize.
Name:<unknown>
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
To fix the problem,
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
Good Luck,
Alfred.
|||well. . . unfortunately we have the same problem as well.
after having both SQL 2000 and 2005 we tried to uninstall 2005.
buggered the sql 2000 as noted
running the fix outlined above (as well as the othere method outlined in the kb article the above was copied from) we get:
DllRegisterServer in C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmmc.dll failed.
Return code was: 0x8011041a
We need to get back to a totally clean state so we can do an install of just SQL 2000.
And dont just copy that other kb article 290991 as that didnt work either
Co-exist of SQL 2000 and 2005
Dear all,1. Click Start, click Run, type regedit, and then click OK. 2. Locate the following registry subkey: 3. Right-click the ClientSetup registry subkey, point to New, and then click String Value. 4. Rename the registry subkey that you just created SqlPath, and then press ENTER. 5. Double-click the SqlPath registry subkey, and then type C:\Program Files\Microsoft SQL Server\80\Tools in the Value data box. 6. Click OK, and then close Registry Editor. 7. Click Start, click Run, type regsvr32 "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmmc.dll", and then click OK.
I have SQL 2000 Enterprise mgr and Query Analyzer in my desktop, and I install SQL2005 Express Edition + Mgm Studio today, however, my SQL 2000 Enterprise mgr disappear and all my registered servers disappear too when I open up the SQL 2005 Mgm Studio. Is it mean that I no longer able to use SQL 2000? How can I rollback the installation of SQL 2005 because I still have to use Enterprise mgr to manage my existing database and clients. (Yes, I give up SQL 2005 now)
Thanks,The 2 should work side by side just fine, there is no need to uninstall. What do you mean Enterprise Manager disapears? Did you do a sidebyside install or an upgrade?|||
You say 'when I open up 2005 Management Studio..'
If you did a sidebyside install, all your 2000 stuff is till there, but you still use 2000 EM for them, they aren't in Management Studio. Your old EM should still be available from the programs menu, and 2005 have it's own start menu.
/Kenneth
|||Hi Ken,Thanks for your advice, Maybe I select "upgrade" SQL 2000 to SQL 2005 in the installation process (is there an option like this?)... so everything gone and I can't see my SQL 2000 Enterprice Manaager and Query Analyzer (you know, these 2 tools are the best friend of DBA ;)
I tried to uninstall SQL 2005 and select "side by side" installation (is there a option like this?) but it create another problem: here.
My original database in SQL 2000 disappear even I re-install SQL 2000 EM, but the MDF and LDF are still in my machine, so I want to "attach" these database immediately, but I can't do so.. do you know why?
(Installation of SQL 2005 is quite problematic... and bring some other problems as well in my opinion.. I can use my EM and QA smoothly over the last few years)
Thanks!|||So it sounds like you did an upgrade to SQL 2005. For the tools you can uninstall 2005 and then re-install 2000 and it should work, HOWEVER for your data this is a problem. Once a database has been touched by a 2005 server it can not be attached or restored on a 2000 machine. Your only choice is to export the data from a 2005 running copy of the database, out to csv/text etc and then load that on on the other side.|||
Oh my god... I just un-install the SQL 2005 and re-install SQL 2000, that's fine. I want to make everything back to normal first.
Next, I install a lite version of SQL 2005 Express instead (Yes, I'm afraid the SQL 2005 now), and I specifically choose NOT upgrade my existing database (Well, the upgrade option is disabled by default due to the limitation of SQL 2005 Express anyway, so I'm pretty sure it WON'T affect my existing SQL 2000 DBs and Enterprise Mgr, alright?)
However, the result is - It break all of my databases AGAIN. And an error message come out when I try to open my SQL 2000 Ent. Mgr:
Microsoft Management Console
Snap-in failed to initialize.
Name:<unknown>
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I'm pretty sure the co-existence of SQL 2000 and SQL 2005 (any edition) is very poor.. I can't do any project against my SQL 2000 nor SQL 20005 db now. :(
Thanks,
|||Sorry but you are wrong, SQL 2000 and 2005 work just fine together, it is unfortunate that you are having problems, btu I run 4 machiens with this config and they all work fine, as do 10,000s of others.
What do you mean the databases are broken, is there an error message?
To fix the mmc problem try and run regsvr32 on sqlmmc.dll
|||I'm also running a few servers running both SQL2k and 2005 without problems. Servers did not upgrade the existing sql2k 's. I installed the 2005's as new instances.
Eralper
http://www.kodyaz.com
|||
Euan Garden wrote:
To fix the mmc problem try and run regsvr32 on sqlmmc.dll
I have more than 1 machine with SQL 2005 installed, and nearly 50% of them are facing various problem. I understand that there're 10000s installation successed, but you should be aware that there're also have another 10000s installation failed and looking for help here or other NGs everyday. This is a pain. Even 1 installation failed, this product is buggy.
The databases can't be attached or re-used anymore if SQL 2005 "touch" the db from SQL 2000, that's a famous bug since beta age.
The regsvr32 sqlmmc.dll and sqldmo.dll are no good...
Thanks,
|||Sorry peter but there are not 1000's of installations which are failed.
Correct once a DB is touched by 2005 it can not be moved back, this is not a bug this is by design, we have to upgrade the format to be able to use the new features of SQL 2000, this has been this way for the last 4 versions of SQL Server and I believe is also true for other DB vendors.
When you say that sqlmmc and sqldmo are no good are you saying that you tried to re-reg and ti did not work?
|||We have to buy all license and upgrade to SQL 2005 immmediately and we don't have any backward compatiability if we're using SQL 2000? Compatiability and stability are two of the key factors for any DB system.
re-reg doesn't help, SQL 2000 Enterprise Manager still messed up.
(Please see this MSDN blog for more info about this bug)
Thanks,
|||First of all you don't have to buy new licenses and upgrade, SQL 2000 is a fine product and will be support for several years to come. However if you want to upgrade and get the new version you can.
Your definition of Back Compat differs from mine (and that of the SQL Server Team), apps that work against SQL2000/7 should work against SQL 2005 without changes, thats significant. SQL 2005 can used SQL 2000 as a linked server, it can consume backups, database files and data via OLE DB and ADO.Net. All of that is pretty impressive.
Your issue is that you have taken a SQL Server 2000 DB, and attached it to SQL 2005, obviously wanting to leverage the new features of SQL 2005, to do that means changes to the file format, making it impossible to use the file on 2000(but you can script out) just as if you had used one of the new T-SQL commands in your app, that would not run against a 2000 server. Just like a Winforms 2.0 app will not run against .Net 1.1, just as a etc etc. I'm sorry you disagree with the principle, but this decision/position does not imply anything related to the stability of the system, which is just fine.
I am very familiar with the "bug" and the blog entry you reference(hint take a look at the author of the entry), this is not the same bug. Re-registering DMO fixes the CTP bug you reference.
Now back to the original problem of EM not working. When you re-reg sqlmmc and sqldmo to they both register correctly or is there an error message? If they register correctly has the error message you get when trying to start EM the same or has it changed from the original post? Have you tried applying SP4 of SQL 2000 again?
|||Sorry to post this bug here, but this is the problem after my installation of SQL 2005. I don't want to upgrade my SQL 2000 database to SQL 2005 in fact, if you read my posts above.The wizard drive me to this stage and now, the database can't be rollbacked to its original state, which is a backward process. Sorry that you have another definition of backward compatibility, but please be considerate when you reading post here, even you have your own definition in your own mind. You can't force others to follow your own definion and you don't have problem in the installation doesn't mean other 10000 people are as lucky as you.
The problem and error messages and all service pack installed. Please read the posts but don't just focus on what you like to see but ignore others' opinion.
Thanks,|||
If you are playing around with
various versions or instances of MS SQL Server
you may hit the problem of
Microsoft Management Console
Snap-in failed to initialize.
Name:<unknown>
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
To fix the problem,
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
Good Luck,
Alfred.
|||well. . . unfortunately we have the same problem as well.
after having both SQL 2000 and 2005 we tried to uninstall 2005.
buggered the sql 2000 as noted
running the fix outlined above (as well as the othere method outlined in the kb article the above was copied from) we get:
DllRegisterServer in C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmmc.dll failed.
Return code was: 0x8011041a
We need to get back to a totally clean state so we can do an install of just SQL 2000.
And dont just copy that other kb article 290991 as that didnt work either
Co-exist of SQL 2000 and 2005
Dear all,1. Click Start, click Run, type regedit, and then click OK. 2. Locate the following registry subkey: 3. Right-click the ClientSetup registry subkey, point to New, and then click String Value. 4. Rename the registry subkey that you just created SqlPath, and then press ENTER. 5. Double-click the SqlPath registry subkey, and then type C:\Program Files\Microsoft SQL Server\80\Tools in the Value data box. 6. Click OK, and then close Registry Editor. 7. Click Start, click Run, type regsvr32 "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmmc.dll", and then click OK.
I have SQL 2000 Enterprise mgr and Query Analyzer in my desktop, and I install SQL2005 Express Edition + Mgm Studio today, however, my SQL 2000 Enterprise mgr disappear and all my registered servers disappear too when I open up the SQL 2005 Mgm Studio. Is it mean that I no longer able to use SQL 2000? How can I rollback the installation of SQL 2005 because I still have to use Enterprise mgr to manage my existing database and clients. (Yes, I give up SQL 2005 now)
Thanks,The 2 should work side by side just fine, there is no need to uninstall. What do you mean Enterprise Manager disapears? Did you do a sidebyside install or an upgrade?|||
You say 'when I open up 2005 Management Studio..'
If you did a sidebyside install, all your 2000 stuff is till there, but you still use 2000 EM for them, they aren't in Management Studio. Your old EM should still be available from the programs menu, and 2005 have it's own start menu.
/Kenneth
|||Hi Ken,Thanks for your advice, Maybe I select "upgrade" SQL 2000 to SQL 2005 in the installation process (is there an option like this?)... so everything gone and I can't see my SQL 2000 Enterprice Manaager and Query Analyzer (you know, these 2 tools are the best friend of DBA ;)
I tried to uninstall SQL 2005 and select "side by side" installation (is there a option like this?) but it create another problem: here.
My original database in SQL 2000 disappear even I re-install SQL 2000 EM, but the MDF and LDF are still in my machine, so I want to "attach" these database immediately, but I can't do so.. do you know why?
(Installation of SQL 2005 is quite problematic... and bring some other problems as well in my opinion.. I can use my EM and QA smoothly over the last few years)
Thanks!|||So it sounds like you did an upgrade to SQL 2005. For the tools you can uninstall 2005 and then re-install 2000 and it should work, HOWEVER for your data this is a problem. Once a database has been touched by a 2005 server it can not be attached or restored on a 2000 machine. Your only choice is to export the data from a 2005 running copy of the database, out to csv/text etc and then load that on on the other side.|||
Oh my god... I just un-install the SQL 2005 and re-install SQL 2000, that's fine. I want to make everything back to normal first.
Next, I install a lite version of SQL 2005 Express instead (Yes, I'm afraid the SQL 2005 now), and I specifically choose NOT upgrade my existing database (Well, the upgrade option is disabled by default due to the limitation of SQL 2005 Express anyway, so I'm pretty sure it WON'T affect my existing SQL 2000 DBs and Enterprise Mgr, alright?)
However, the result is - It break all of my databases AGAIN. And an error message come out when I try to open my SQL 2000 Ent. Mgr:
Microsoft Management Console
Snap-in failed to initialize.
Name:<unknown>
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I'm pretty sure the co-existence of SQL 2000 and SQL 2005 (any edition) is very poor.. I can't do any project against my SQL 2000 nor SQL 20005 db now. :(
Thanks,
|||Sorry but you are wrong, SQL 2000 and 2005 work just fine together, it is unfortunate that you are having problems, btu I run 4 machiens with this config and they all work fine, as do 10,000s of others.
What do you mean the databases are broken, is there an error message?
To fix the mmc problem try and run regsvr32 on sqlmmc.dll
|||I'm also running a few servers running both SQL2k and 2005 without problems. Servers did not upgrade the existing sql2k 's. I installed the 2005's as new instances.
Eralper
http://www.kodyaz.com
|||
To fix the mmc problem try and run regsvr32 on sqlmmc.dll
I have more than 1 machine with SQL 2005 installed, and nearly 50% of them are facing various problem. I understand that there're 10000s installation successed, but you should be aware that there're also have another 10000s installation failed and looking for help here or other NGs everyday. This is a pain. Even 1 installation failed, this product is buggy.
The databases can't be attached or re-used anymore if SQL 2005 "touch" the db from SQL 2000, that's a famous bug since beta age.
The regsvr32 sqlmmc.dll and sqldmo.dll are no good...
Thanks,
|||Sorry peter but there are not 1000's of installations which are failed.
Correct once a DB is touched by 2005 it can not be moved back, this is not a bug this is by design, we have to upgrade the format to be able to use the new features of SQL 2000, this has been this way for the last 4 versions of SQL Server and I believe is also true for other DB vendors.
When you say that sqlmmc and sqldmo are no good are you saying that you tried to re-reg and ti did not work?
|||We have to buy all license and upgrade to SQL 2005 immmediately and we don't have any backward compatiability if we're using SQL 2000? Compatiability and stability are two of the key factors for any DB system.
re-reg doesn't help, SQL 2000 Enterprise Manager still messed up.
(Please see this MSDN blog for more info about this bug)
Thanks,
|||First of all you don't have to buy new licenses and upgrade, SQL 2000 is a fine product and will be support for several years to come. However if you want to upgrade and get the new version you can.
Your definition of Back Compat differs from mine (and that of the SQL Server Team), apps that work against SQL2000/7 should work against SQL 2005 without changes, thats significant. SQL 2005 can used SQL 2000 as a linked server, it can consume backups, database files and data via OLE DB and ADO.Net. All of that is pretty impressive.
Your issue is that you have taken a SQL Server 2000 DB, and attached it to SQL 2005, obviously wanting to leverage the new features of SQL 2005, to do that means changes to the file format, making it impossible to use the file on 2000(but you can script out) just as if you had used one of the new T-SQL commands in your app, that would not run against a 2000 server. Just like a Winforms 2.0 app will not run against .Net 1.1, just as a etc etc. I'm sorry you disagree with the principle, but this decision/position does not imply anything related to the stability of the system, which is just fine.
I am very familiar with the "bug" and the blog entry you reference(hint take a look at the author of the entry), this is not the same bug. Re-registering DMO fixes the CTP bug you reference.
Now back to the original problem of EM not working. When you re-reg sqlmmc and sqldmo to they both register correctly or is there an error message? If they register correctly has the error message you get when trying to start EM the same or has it changed from the original post? Have you tried applying SP4 of SQL 2000 again?
|||Sorry to post this bug here, but this is the problem after my installation of SQL 2005. I don't want to upgrade my SQL 2000 database to SQL 2005 in fact, if you read my posts above.The wizard drive me to this stage and now, the database can't be rollbacked to its original state, which is a backward process. Sorry that you have another definition of backward compatibility, but please be considerate when you reading post here, even you have your own definition in your own mind. You can't force others to follow your own definion and you don't have problem in the installation doesn't mean other 10000 people are as lucky as you.
The problem and error messages and all service pack installed. Please read the posts but don't just focus on what you like to see but ignore others' opinion.
Thanks,|||
If you are playing around with
various versions or instances of MS SQL Server
you may hit the problem of
Microsoft Management Console
Snap-in failed to initialize.
Name:<unknown>
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
To fix the problem,
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
Good Luck,
Alfred.
|||well. . . unfortunately we have the same problem as well.
after having both SQL 2000 and 2005 we tried to uninstall 2005.
buggered the sql 2000 as noted
running the fix outlined above (as well as the othere method outlined in the kb article the above was copied from) we get:
DllRegisterServer in C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmmc.dll failed.
Return code was: 0x8011041a
We need to get back to a totally clean state so we can do an install of just SQL 2000.
And dont just copy that other kb article 290991 as that didnt work either
Sunday, February 19, 2012
Clustering installation issue
I'm trying to install SQL 2000 on a newly clustered Win2000 system.
I'm getting the following error:
The drive chosen for the program files installation path, C:, is not valid on all nodes of the cluster. Choose another drive to install the program files.
I've read Microsoft's explanation of the error, and that the one server can't access the C: drive of the other server if file and print sharing isn't setup correctly. However...
I'm logged on as Administrator, and have full control of both machines.
I'm telling the SQL install to use the administrator account.
If I go to start->run-> and type \\serverB\C$ the share opens just fine.
I've also check the registry entries that MS suggests: HKey_LocalMachine\Software\Microsoft\Windows\Curre ntVersion and make sure that the value for CommonFilesDir and ProgramFilesDir is the same on both the nodes. They're the same
I am trying to install the data files within the same group as the quorom drive, but that should just give me a warning (and it does) and shouldn't be this problem. I'm just trying to install to the system drive (C:) which certainly exists on both machines.
I've seen a couple other posts about this, but no solutions. Any help would be great.
Thanks,
MattReview this http://support.microsoft.com/default.aspx?scid=kb;[LN];Q279642] to take care of further installation.|||Satya,
I tried the link that you provided, but got to a Microsoft page that said that page no longer exists.
If it's the KB article:
Microsoft Knowledge Base Article - 279642
I have already gone through that without any luck. But if it's something else, I'd be happy to try it.
Also, I have since been able to get the installation to work if instead of using the C: drive, I use the drive dedicated to the page file. Obviously, this isn't something I'd want to do, but hopefully it provides more information that might help someone figure out what my issue is.
Thanks,
matt|||You cn install the program files to the C:\ drive, but all data has to be installed on a shared drive. Are you selecting custom install with Data going to a shared drive?|||Further help from here (http://www.sql-server-performance.com/wndows2000_clustering_install_main.asp)
HTH|||Well, I have no idea what this issue was, but to get around it you can:
Install SQL Server locally to one of the nodes of the cluster.
Be sure to put the data files on a drive that is part of the cluster.
Then upgrade the local instance to a clustered instance.
All worked for me, using that strange process.
I'm getting the following error:
The drive chosen for the program files installation path, C:, is not valid on all nodes of the cluster. Choose another drive to install the program files.
I've read Microsoft's explanation of the error, and that the one server can't access the C: drive of the other server if file and print sharing isn't setup correctly. However...
I'm logged on as Administrator, and have full control of both machines.
I'm telling the SQL install to use the administrator account.
If I go to start->run-> and type \\serverB\C$ the share opens just fine.
I've also check the registry entries that MS suggests: HKey_LocalMachine\Software\Microsoft\Windows\Curre ntVersion and make sure that the value for CommonFilesDir and ProgramFilesDir is the same on both the nodes. They're the same
I am trying to install the data files within the same group as the quorom drive, but that should just give me a warning (and it does) and shouldn't be this problem. I'm just trying to install to the system drive (C:) which certainly exists on both machines.
I've seen a couple other posts about this, but no solutions. Any help would be great.
Thanks,
MattReview this http://support.microsoft.com/default.aspx?scid=kb;[LN];Q279642] to take care of further installation.|||Satya,
I tried the link that you provided, but got to a Microsoft page that said that page no longer exists.
If it's the KB article:
Microsoft Knowledge Base Article - 279642
I have already gone through that without any luck. But if it's something else, I'd be happy to try it.
Also, I have since been able to get the installation to work if instead of using the C: drive, I use the drive dedicated to the page file. Obviously, this isn't something I'd want to do, but hopefully it provides more information that might help someone figure out what my issue is.
Thanks,
matt|||You cn install the program files to the C:\ drive, but all data has to be installed on a shared drive. Are you selecting custom install with Data going to a shared drive?|||Further help from here (http://www.sql-server-performance.com/wndows2000_clustering_install_main.asp)
HTH|||Well, I have no idea what this issue was, but to get around it you can:
Install SQL Server locally to one of the nodes of the cluster.
Be sure to put the data files on a drive that is part of the cluster.
Then upgrade the local instance to a clustered instance.
All worked for me, using that strange process.
Clustering failure on install
Hi,
Where can I post issues with SQL 2005 clustering. Is there any prereq that needs to be followed before installing SQL 2005 on a windows cluster?
Thanks
go here http://msdn2.microsoft.com/en-us/library/ms189910.aspx|||
You can certainly post here about any clustering issues you may encounter. The SQL Server 2005 Failover Clustering whitepaper will be released soon (and has full install instructions with screen captures). As far as prereqs, the link that was provided is good. But make sure that your Windows level cluster is rock solid and tested before installing SQL Server. The security is a bit different with SQL Server 2005 failover clustering, so pay attention to that.
Other than that, the install itself is straightforward. No real gotchas there except all nodes do not get the full compliment of client tools. If you install the client tools, they will only go on the server which initiated the install and you will need to install them on the other nodes. If you do not need the full compliment of admin tools on eachnode, then you don't have to worry about it.
If you want even more, the Apress book SQL Server 2005 High Availability is due out later this year. The book covers clustering both Windows (from a SQL perspective) & SQL - not just the SQL piece. It is spread out over two chapters and should be 250 - 300 pages for those two chapters alone.
|||adminup, did the article help?|||Thanks It helped.
Th eonly other question is that before installing the SQL cluster do we need to configure the MSDTC or is there any prereq required after the Windows 2003 cluster is setup?
|||Yes, you should configure the clustered DTC prior to installing SQL Server as per http://support.microsoft.com/kb/301600/en-us and http://support.microsoft.com/kb/817064/en-us.|||
Hi Thanks while actually installing i get this error message I have checked the windows scheduling and it is started.
setup failed to start on the remote machine. Check the task scheduler event log on the reote machine
Why I am getting this error
|||If your other node or nodes do not have access to the CD-ROM or install point, that is a likely cause of this. It could also be a missed configuration step in the preparation, but it's most likely access to the install bits.|||Thanks it was a share from a remote machine. Now the setup is fine I can SQL directories created on both the machine however it fails on database install there is no error log that corresponds to this.
I have enabled MSDTC and all the prereq but still the setup fails at the database creation points.
Any ideas?
Anup
|||sql setup log might give some clues as why it fails.|||As OJ says, the logs should be telling and are VERY descriptive in SQL Server 2005.What part of the DB install does it choke on?
|||Thanks I figured it out it was probably a share from network drive to MSDTC service accont which was causing this but all well now set up completed thanks for all the help|||I had the similar error on 64 bit STD edition installation of default instance , with another named instance already installed without any issues.I had to go ask the Task manager to interact with desktop on but the servers and restart the tast manger service in both. I am still not sure why does the TM needs to interact with desktop on the other (non installation passive node ).
Clustering failure on install
Hi,
Where can I post issues with SQL 2005 clustering. Is there any prereq that needs to be followed before installing SQL 2005 on a windows cluster?
Thanks
go here http://msdn2.microsoft.com/en-us/library/ms189910.aspx|||
You can certainly post here about any clustering issues you may encounter. The SQL Server 2005 Failover Clustering whitepaper will be released soon (and has full install instructions with screen captures). As far as prereqs, the link that was provided is good. But make sure that your Windows level cluster is rock solid and tested before installing SQL Server. The security is a bit different with SQL Server 2005 failover clustering, so pay attention to that.
Other than that, the install itself is straightforward. No real gotchas there except all nodes do not get the full compliment of client tools. If you install the client tools, they will only go on the server which initiated the install and you will need to install them on the other nodes. If you do not need the full compliment of admin tools on eachnode, then you don't have to worry about it.
If you want even more, the Apress book SQL Server 2005 High Availability is due out later this year. The book covers clustering both Windows (from a SQL perspective) & SQL - not just the SQL piece. It is spread out over two chapters and should be 250 - 300 pages for those two chapters alone.
|||adminup, did the article help?|||Thanks It helped.
Th eonly other question is that before installing the SQL cluster do we need to configure the MSDTC or is there any prereq required after the Windows 2003 cluster is setup?
|||Yes, you should configure the clustered DTC prior to installing SQL Server as per http://support.microsoft.com/kb/301600/en-us and http://support.microsoft.com/kb/817064/en-us.|||
Hi Thanks while actually installing i get this error message I have checked the windows scheduling and it is started.
setup failed to start on the remote machine. Check the task scheduler event log on the reote machine
Why I am getting this error
|||If your other node or nodes do not have access to the CD-ROM or install point, that is a likely cause of this. It could also be a missed configuration step in the preparation, but it's most likely access to the install bits.|||Thanks it was a share from a remote machine. Now the setup is fine I can SQL directories created on both the machine however it fails on database install there is no error log that corresponds to this.
I have enabled MSDTC and all the prereq but still the setup fails at the database creation points.
Any ideas?
Anup
|||sql setup log might give some clues as why it fails.|||As OJ says, the logs should be telling and are VERY descriptive in SQL Server 2005.What part of the DB install does it choke on?
|||Thanks I figured it out it was probably a share from network drive to MSDTC service accont which was causing this but all well now set up completed thanks for all the help|||I had the similar error on 64 bit STD edition installation of default instance , with another named instance already installed without any issues.I had to go ask the Task manager to interact with desktop on but the servers and restart the tast manger service in both. I am still not sure why does the TM needs to interact with desktop on the other (non installation passive node ).
Tuesday, February 14, 2012
Clustered SQL Server shut down for third-party application install
Dear Sir,
If I needed to install something to the active then passive node one by one
and required to restart the server serveral times during install, what is the
procedures if I don't want SQL Server to auto startup during reboot?
Steps:
01) Offline "passive" node from cluster admin.
02) Shut down "passive" node server.
03) Offline "active" node SQL Server Group
04) From OS Services, change SQL Server to "Not auto startup"
05) Install application
06) Reboot active server
07) ....
Is the above procedures ok?
Please advise! Thanks!
Henry
cross-posted to microsoft.public.sqlserver.clustering
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Henry wrote:
>Dear Sir,
>If I needed to install something to the active then passive node one by one
>and required to restart the server serveral times during install, what is the
>procedures if I don't want SQL Server to auto startup during reboot?
>Steps:
>01) Offline "passive" node from cluster admin.
>02) Shut down "passive" node server.
>03) Offline "active" node SQL Server Group
>04) From OS Services, change SQL Server to "Not auto startup"
>05) Install application
>06) Reboot active server
>07) ....
> Is the above procedures ok?
>Please advise! Thanks!
>Henry
>
>
If I needed to install something to the active then passive node one by one
and required to restart the server serveral times during install, what is the
procedures if I don't want SQL Server to auto startup during reboot?
Steps:
01) Offline "passive" node from cluster admin.
02) Shut down "passive" node server.
03) Offline "active" node SQL Server Group
04) From OS Services, change SQL Server to "Not auto startup"
05) Install application
06) Reboot active server
07) ....
Is the above procedures ok?
Please advise! Thanks!
Henry
cross-posted to microsoft.public.sqlserver.clustering
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Henry wrote:
>Dear Sir,
>If I needed to install something to the active then passive node one by one
>and required to restart the server serveral times during install, what is the
>procedures if I don't want SQL Server to auto startup during reboot?
>Steps:
>01) Offline "passive" node from cluster admin.
>02) Shut down "passive" node server.
>03) Offline "active" node SQL Server Group
>04) From OS Services, change SQL Server to "Not auto startup"
>05) Install application
>06) Reboot active server
>07) ....
> Is the above procedures ok?
>Please advise! Thanks!
>Henry
>
>
Clustered SQL Server shut down for third-party application install
Dear Sir,
If I needed to install something to the active then passive node one by one
and required to restart the server serveral times during install, what is the
procedures if I don't want SQL Server to auto startup during reboot?
Steps:
01) Offline "passive" node from cluster admin.
02) Shut down "passive" node server.
03) Offline "active" node SQL Server Group
04) From OS Services, change SQL Server to "Not auto startup"
05) Install application
06) Reboot active server
07) ....
Is the above procedures ok?
Please advise! Thanks!
HenryThis is a multi-part message in MIME format.
--030309070404030102020809
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
cross-posted to microsoft.public.sqlserver.clustering
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Henry wrote:
>Dear Sir,
>If I needed to install something to the active then passive node one by one
>and required to restart the server serveral times during install, what is the
>procedures if I don't want SQL Server to auto startup during reboot?
>Steps:
>01) Offline "passive" node from cluster admin.
>02) Shut down "passive" node server.
>03) Offline "active" node SQL Server Group
>04) From OS Services, change SQL Server to "Not auto startup"
>05) Install application
>06) Reboot active server
>07) ....
> Is the above procedures ok?
>Please advise! Thanks!
>Henry
>
>
--030309070404030102020809
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>cross-posted to microsoft.public.sqlserver.clustering</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Henry wrote:
<blockquote cite="midE64C9F95-F0A5-42B5-A7AD-3CE7515EB4FE@.microsoft.com"
type="cite">
<pre wrap="">Dear Sir,
If I needed to install something to the active then passive node one by one
and required to restart the server serveral times during install, what is the
procedures if I don't want SQL Server to auto startup during reboot?
Steps:
01) Offline "passive" node from cluster admin.
02) Shut down "passive" node server.
03) Offline "active" node SQL Server Group
04) From OS Services, change SQL Server to "Not auto startup"
05) Install application
06) Reboot active server
07) ....
Is the above procedures ok?
Please advise! Thanks!
Henry
</pre>
</blockquote>
</body>
</html>
--030309070404030102020809--
If I needed to install something to the active then passive node one by one
and required to restart the server serveral times during install, what is the
procedures if I don't want SQL Server to auto startup during reboot?
Steps:
01) Offline "passive" node from cluster admin.
02) Shut down "passive" node server.
03) Offline "active" node SQL Server Group
04) From OS Services, change SQL Server to "Not auto startup"
05) Install application
06) Reboot active server
07) ....
Is the above procedures ok?
Please advise! Thanks!
HenryThis is a multi-part message in MIME format.
--030309070404030102020809
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
cross-posted to microsoft.public.sqlserver.clustering
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Henry wrote:
>Dear Sir,
>If I needed to install something to the active then passive node one by one
>and required to restart the server serveral times during install, what is the
>procedures if I don't want SQL Server to auto startup during reboot?
>Steps:
>01) Offline "passive" node from cluster admin.
>02) Shut down "passive" node server.
>03) Offline "active" node SQL Server Group
>04) From OS Services, change SQL Server to "Not auto startup"
>05) Install application
>06) Reboot active server
>07) ....
> Is the above procedures ok?
>Please advise! Thanks!
>Henry
>
>
--030309070404030102020809
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>cross-posted to microsoft.public.sqlserver.clustering</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Henry wrote:
<blockquote cite="midE64C9F95-F0A5-42B5-A7AD-3CE7515EB4FE@.microsoft.com"
type="cite">
<pre wrap="">Dear Sir,
If I needed to install something to the active then passive node one by one
and required to restart the server serveral times during install, what is the
procedures if I don't want SQL Server to auto startup during reboot?
Steps:
01) Offline "passive" node from cluster admin.
02) Shut down "passive" node server.
03) Offline "active" node SQL Server Group
04) From OS Services, change SQL Server to "Not auto startup"
05) Install application
06) Reboot active server
07) ....
Is the above procedures ok?
Please advise! Thanks!
Henry
</pre>
</blockquote>
</body>
</html>
--030309070404030102020809--
Clustered SQL Server shut down for third-party application install
Dear Sir,
If I needed to install something to the active then passive node one by one
and required to restart the server serveral times during install, what is th
e
procedures if I don't want SQL Server to auto startup during reboot?
Steps:
01) Offline "passive" node from cluster admin.
02) Shut down "passive" node server.
03) Offline "active" node SQL Server Group
04) From OS Services, change SQL Server to "Not auto startup"
05) Install application
06) Reboot active server
07) ....
Is the above procedures ok?
Please advise! Thanks!
Henrycross-posted to microsoft.public.sqlserver.clustering
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Henry wrote:
>Dear Sir,
>If I needed to install something to the active then passive node one by one
>and required to restart the server serveral times during install, what is t
he
>procedures if I don't want SQL Server to auto startup during reboot?
>Steps:
>01) Offline "passive" node from cluster admin.
>02) Shut down "passive" node server.
>03) Offline "active" node SQL Server Group
>04) From OS Services, change SQL Server to "Not auto startup"
>05) Install application
>06) Reboot active server
>07) ....
> Is the above procedures ok?
>Please advise! Thanks!
>Henry
>
>
If I needed to install something to the active then passive node one by one
and required to restart the server serveral times during install, what is th
e
procedures if I don't want SQL Server to auto startup during reboot?
Steps:
01) Offline "passive" node from cluster admin.
02) Shut down "passive" node server.
03) Offline "active" node SQL Server Group
04) From OS Services, change SQL Server to "Not auto startup"
05) Install application
06) Reboot active server
07) ....
Is the above procedures ok?
Please advise! Thanks!
Henrycross-posted to microsoft.public.sqlserver.clustering
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Henry wrote:
>Dear Sir,
>If I needed to install something to the active then passive node one by one
>and required to restart the server serveral times during install, what is t
he
>procedures if I don't want SQL Server to auto startup during reboot?
>Steps:
>01) Offline "passive" node from cluster admin.
>02) Shut down "passive" node server.
>03) Offline "active" node SQL Server Group
>04) From OS Services, change SQL Server to "Not auto startup"
>05) Install application
>06) Reboot active server
>07) ....
> Is the above procedures ok?
>Please advise! Thanks!
>Henry
>
>
Clustered SQL 2005 Standard
I just completed an install of SQL 2005 Standard into a newly formed
cluster. I basically installed every option for SQL 2005 Server, however,
the only resources added to the cluster group were SQL Server, SQL Agent and
SQL Server Fulltext.
I would have thought reporting services would have been put in there as
well. Is this something I have to add later, or install on each node
separately?
Also forgot to mention, after the install, it didn't put any of the System
DB's into the drive\folder I specified.
So, now I have to go and move them...
Does anyone know of an online tutorial for the new SQL 2005 Interface?
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:eTJ3ULSHGHA.3624@.TK2MSFTNGP09.phx.gbl...
>I just completed an install of SQL 2005 Standard into a newly formed
>cluster. I basically installed every option for SQL 2005 Server, however,
>the only resources added to the cluster group were SQL Server, SQL Agent
>and SQL Server Fulltext.
> I would have thought reporting services would have been put in there as
> well. Is this something I have to add later, or install on each node
> separately?
>
|||Reporting Services is not failover clusterable. It will need to be
installed on each node separately. Since it is a web service, you are
better off setting up a load-balanced web farm with the databases on a
clustered server.
From your followup question: BOL contains some excellent tutorals including
a section on SQL Server Tools.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:eTJ3ULSHGHA.3624@.TK2MSFTNGP09.phx.gbl...
>I just completed an install of SQL 2005 Standard into a newly formed
>cluster. I basically installed every option for SQL 2005 Server, however,
>the only resources added to the cluster group were SQL Server, SQL Agent
>and SQL Server Fulltext.
> I would have thought reporting services would have been put in there as
> well. Is this something I have to add later, or install on each node
> separately?
>
|||Thanks.
How about moving all the DB's to the appropriate drives now?
Looks like it's a little different then in 2000.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:O2kLMmSHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Reporting Services is not failover clusterable. It will need to be
> installed on each node separately. Since it is a web service, you are
> better off setting up a load-balanced web farm with the databases on a
> clustered server.
> From your followup question: BOL contains some excellent tutorals
> including a section on SQL Server Tools.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Kevin Antel" <kevina@.cqlcorp.com> wrote in message
> news:eTJ3ULSHGHA.3624@.TK2MSFTNGP09.phx.gbl...
>
|||ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/72bb62ee-9602-4f71-be51-c466c1670878.htm
Note: This is a link from the December 2005 BOL Refresh for SQL Server
2005. If you are using the RTM BOL, it may not work correctly.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:e60JnoSHGHA.3408@.TK2MSFTNGP12.phx.gbl...
> Thanks.
> How about moving all the DB's to the appropriate drives now?
> Looks like it's a little different then in 2000.
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:O2kLMmSHGHA.344@.TK2MSFTNGP11.phx.gbl...
>
cluster. I basically installed every option for SQL 2005 Server, however,
the only resources added to the cluster group were SQL Server, SQL Agent and
SQL Server Fulltext.
I would have thought reporting services would have been put in there as
well. Is this something I have to add later, or install on each node
separately?
Also forgot to mention, after the install, it didn't put any of the System
DB's into the drive\folder I specified.
So, now I have to go and move them...
Does anyone know of an online tutorial for the new SQL 2005 Interface?
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:eTJ3ULSHGHA.3624@.TK2MSFTNGP09.phx.gbl...
>I just completed an install of SQL 2005 Standard into a newly formed
>cluster. I basically installed every option for SQL 2005 Server, however,
>the only resources added to the cluster group were SQL Server, SQL Agent
>and SQL Server Fulltext.
> I would have thought reporting services would have been put in there as
> well. Is this something I have to add later, or install on each node
> separately?
>
|||Reporting Services is not failover clusterable. It will need to be
installed on each node separately. Since it is a web service, you are
better off setting up a load-balanced web farm with the databases on a
clustered server.
From your followup question: BOL contains some excellent tutorals including
a section on SQL Server Tools.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:eTJ3ULSHGHA.3624@.TK2MSFTNGP09.phx.gbl...
>I just completed an install of SQL 2005 Standard into a newly formed
>cluster. I basically installed every option for SQL 2005 Server, however,
>the only resources added to the cluster group were SQL Server, SQL Agent
>and SQL Server Fulltext.
> I would have thought reporting services would have been put in there as
> well. Is this something I have to add later, or install on each node
> separately?
>
|||Thanks.
How about moving all the DB's to the appropriate drives now?
Looks like it's a little different then in 2000.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:O2kLMmSHGHA.344@.TK2MSFTNGP11.phx.gbl...
> Reporting Services is not failover clusterable. It will need to be
> installed on each node separately. Since it is a web service, you are
> better off setting up a load-balanced web farm with the databases on a
> clustered server.
> From your followup question: BOL contains some excellent tutorals
> including a section on SQL Server Tools.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Kevin Antel" <kevina@.cqlcorp.com> wrote in message
> news:eTJ3ULSHGHA.3624@.TK2MSFTNGP09.phx.gbl...
>
|||ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/72bb62ee-9602-4f71-be51-c466c1670878.htm
Note: This is a link from the December 2005 BOL Refresh for SQL Server
2005. If you are using the RTM BOL, it may not work correctly.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:e60JnoSHGHA.3408@.TK2MSFTNGP12.phx.gbl...
> Thanks.
> How about moving all the DB's to the appropriate drives now?
> Looks like it's a little different then in 2000.
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:O2kLMmSHGHA.344@.TK2MSFTNGP11.phx.gbl...
>
Friday, February 10, 2012
Cluster/SQL 2005/1 node install
We have setup a MSCS with no problem. Have a SAN with mounted volumes and
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. 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.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
Thanks and God Bless,
ThomBeaux
The service account did not have the:
(local policy) - Act as part of the OS
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:
> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. 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.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. 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.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
Thanks and God Bless,
ThomBeaux
The service account did not have the:
(local policy) - Act as part of the OS
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:
> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. 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.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux
Cluster/SQL 2005/1 node install
We have setup a MSCS with no problem. Have a SAN with mounted volumes and
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. 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.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
--
Thanks and God Bless,
ThomBeauxThe service account did not have the:
(local policy) - Act as part of the OS
--
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:
> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. 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.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. 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.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
--
Thanks and God Bless,
ThomBeauxThe service account did not have the:
(local policy) - Act as part of the OS
--
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:
> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. 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.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux
Subscribe to:
Posts (Atom)