Collation difference between SQL 6.5 server and SQL 2000 server

Hello,
We are facing the following problem:
We have installed SQL 6.5 server Enterprise edition on Windows 2000
Advanced server. On this system, in the regional settings, the Locale
is Japanese and in Office 2003 Language settings also, we have added
Japanese.
We have another system with Windows 2000 server on which we have
installed SQL 2000 server Enterprise edition with SP4. On this system,
in the regional settings, the Locale is Japanese and in Office 2003
Language settings also, we have added Japanese.

>From the front end VB code, a query is formed which contains Japanese
value. This works in the SQL 6.5 environment but does not work in the
SQL 2000 environment. If we directly execute the query in SQL 2000
server, it is returning the row. But the VB front end is not
recognizing the row.
The query is like this:
SELECT * FROM Tstar_Currency WHERE Currency =3D N'=C6=CE=DD'
This query works when the VB client connects to the SQL 6.5 server and
the front end fetches one row. But when the VB client connects to SQL
2000 server, the front end is not fetching any row. However, if we
directly execute this in query analyzer in SQL 2000 server, it returns
one row.
Any idea why this is happening? What collation setting should we give
in the SQL 2000 server? Do we need to do anything in the front end
application?
Any help will be greatly appreciated. This is very urgent. Please also
mail to ravi.meenakshi@.gmail.com
Thanks!I would sugest running the VB app in debug mode and see what happens when
the VB app issues the select statment. In addition at the same time you may
open Profiler.
The collation you are using in sql 6.5 works well for you so I would try to
keep the same collation with sql 2000.
Be aware that with sql2000 you have collation at three levels: server,
database and columns.
Verify that you have installed sql 2000 with the desired collation.
Yaniv
--
<Ravi.Meenakshi@.gmail.com> wrote in message
news:1135763223.233337.224300@.g49g2000cwa.googlegroups.com...
Hello,
We are facing the following problem:
We have installed SQL 6.5 server Enterprise edition on Windows 2000
Advanced server. On this system, in the regional settings, the Locale
is Japanese and in Office 2003 Language settings also, we have added
Japanese.
We have another system with Windows 2000 server on which we have
installed SQL 2000 server Enterprise edition with SP4. On this system,
in the regional settings, the Locale is Japanese and in Office 2003
Language settings also, we have added Japanese.

>From the front end VB code, a query is formed which contains Japanese
value. This works in the SQL 6.5 environment but does not work in the
SQL 2000 environment. If we directly execute the query in SQL 2000
server, it is returning the row. But the VB front end is not
recognizing the row.
The query is like this:
SELECT * FROM Tstar_Currency WHERE Currency = N''
This query works when the VB client connects to the SQL 6.5 server and
the front end fetches one row. But when the VB client connects to SQL
2000 server, the front end is not fetching any row. However, if we
directly execute this in query analyzer in SQL 2000 server, it returns
one row.
Any idea why this is happening? What collation setting should we give
in the SQL 2000 server? Do we need to do anything in the front end
application?
Any help will be greatly appreciated. This is very urgent. Please also
mail to ravi.meenakshi@.gmail.com
Thanks!|||(Ravi.Meenakshi@.gmail.com) writes:
> We have installed SQL 6.5 server Enterprise edition on Windows 2000
> Advanced server. On this system, in the regional settings, the Locale
> is Japanese and in Office 2003 Language settings also, we have added
> Japanese.
> We have another system with Windows 2000 server on which we have
> installed SQL 2000 server Enterprise edition with SP4. On this system,
> in the regional settings, the Locale is Japanese and in Office 2003
> Language settings also, we have added Japanese.
>
> value. This works in the SQL 6.5 environment but does not work in the
> SQL 2000 environment. If we directly execute the query in SQL 2000
> server, it is returning the row. But the VB front end is not
> recognizing the row.
> The query is like this:
> SELECT * FROM Tstar_Currency WHERE Currency = N''
> This query works when the VB client connects to the SQL 6.5 server and
> the front end fetches one row. But when the VB client connects to SQL
> 2000 server, the front end is not fetching any row. However, if we
> directly execute this in query analyzer in SQL 2000 server, it returns
> one row.
Wait a minute, that query does not even have legal syntax for
SQL 6.5. Is the N really there?
What does sp_helpsort return on SQL 6.5?
On SQL 2000, what does SELECT Serverproperty('Collation') return?
If you run sp_help on Tstar_Currency on SQL 2000, which is the
data type, and which is the collation for that column?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||The N is there in the query only in SQL 2000, not in 6.5
The data type of Currency column in Tstar_Currency in SQL 6.5 is
char(20) and in SQL 2000 is nchar(20)
The collation of this column in SQL 2000 is Japanese_CI_AS
The only change in the VB code is the inclusion of N before the
Japanese value.
Any clues on how to solve the problem?|||I ran profiler for the 2000 environment. In the query I first saw in
the profiler, I saw boxes. Then I changed the font in the Profiler to
Japanese. Then the query displayed like this:
SELECT MSCICode FROM Tstar_Currency WHERE Currency =3D N'=EF=BE=86=EF=BE=8E=
=EF=BE=9D'
When I executed this query in query analyzer, it did not return any
rows.
Please note that the client PC on which the VB application is running,
the regional settings is changed to Japanese.
I can't understand why the Japanese value was not passed correctly from
VB to SQL Server.
Any clues?|||(Ravi.Meenakshi@.gmail.com) writes:
> The N is there in the query only in SQL 2000, not in 6.5
> The data type of Currency column in Tstar_Currency in SQL 6.5 is
> char(20) and in SQL 2000 is nchar(20)
> The collation of this column in SQL 2000 is Japanese_CI_AS
> The only change in the VB code is the inclusion of N before the
> Japanese value.
> Any clues on how to solve the problem?
I asked you these questions:
What does sp_helpsort return on SQL 6.5?
On SQL 2000, what does SELECT Serverproperty('Collation') return?
It's difficult to give clues, if I don't get any.
But it does sound funny to me that the sole difference should be the
addition of the N. If the characters in the string are Unicode, it would
not work on 6.5. Since it works on 6.5, I suspect that the string is in
some other character set. In which case it will of course not work with
a Unicode column.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||The output of sp_helpsort in 65. is:
Character Set = 1, iso_1
ISO 8859-1 (Latin-1) - Western European 8-bit character set.
Sort Order = 52, nocase
Case-insensitive dictionary sort order for use with several We
stern-European languages including English, French, and German
. Uses the ISO 8859-1 character set.
The output of SELECT Serverproperty('Collation') in SQL 2000 is
SQL_Latin1_General_CP1_CI_AS
The collation setting of the SQL 2000 server is the default setting.
The collation for the database that the front end code is accessing is
Japanese_CI_AS|||(Ravi.Meenakshi@.gmail.com) writes:
> The output of sp_helpsort in 65. is:
> Character Set = 1, iso_1
> ISO 8859-1 (Latin-1) - Western European 8-bit character set.
> Sort Order = 52, nocase
> Case-insensitive dictionary sort order for use with several We
> stern-European languages including English, French, and German
> . Uses the ISO 8859-1 character set.
> The output of SELECT Serverproperty('Collation') in SQL 2000 is
It sounds like a miracle if you get Japanese text correcly into that
server. Or at least a great deal of luck.

> SQL_Latin1_General_CP1_CI_AS
> The collation setting of the SQL 2000 server is the default setting.
> The collation for the database that the front end code is accessing is
> Japanese_CI_AS
I have not really managed to fully understand at what collation the
client APIs looks at when they convert data between character sets,
but I suspect that's the server collation. In which case Japanese text
that is the ANSI code page, will be mangled before it's sent to SQL Server.
Apparently you are building a an entire command string in VB. Try to use
parameterised command instead, as then you can declare the type of the
parameter.
You could also try to install an instance of SQL 2000 that has
Japanese_CI_AS as its server collation.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspxsqlsql

Co-exist of SQL 2000 and 2005

Dear all,

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,

1. Click Start, click Run, type regedit, and then click OK. 2. Locate the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup

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.

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,

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,

1.

Click Start, click Run, type regedit, and then click OK.

2.

Locate the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup

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.

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,

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,

1.

Click Start, click Run, type regedit, and then click OK.

2.

Locate the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup

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.

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

Clustering, sending mail from SQL Server in a cluster

We consolidated sending SQL Server mail from one box in our enterprise,
which has worked out well for us. Now we'd like to consolidate
servers/databases and put it under a clustered environment. But how do we
handle the mail ?
Thanx.
-Cqlboy
Try xpsmtp from www.sqldev.net. It isn't a seamless drop-in, but it is a
lot easier to handle than Outlook on a cluster node. It IS a very stable
component.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
news:CC3E45B3-D309-49A9-95D0-0B05C9541665@.microsoft.com...
> We consolidated sending SQL Server mail from one box in our enterprise,
> which has worked out well for us. Now we'd like to consolidate
> servers/databases and put it under a clustered environment. But how do we
> handle the mail ?
> Thanx.
> -Cqlboy
|||Or you could try this if you have iis smtp server installed on the box.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23hk$d6k%23EHA.3756@.TK2MSFTNGP14.phx.gbl...
> Try xpsmtp from www.sqldev.net. It isn't a seamless drop-in, but it is a
> lot easier to handle than Outlook on a cluster node. It IS a very stable
> component.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Cqlboy" <Cqlboy@.discussions.microsoft.com> wrote in message
> news:CC3E45B3-D309-49A9-95D0-0B05C9541665@.microsoft.com...
>
begin 666 sp_SendCDONTSEmail.sql
M04Q415(@.4%)/0T5$55)%('-P7U-E;F1#1$].5%-%;6%I; T*0$9R;VT@.=F%R
M8VAA<B@.Q,# I+ T*0%1O('9A<F-H87(H,3 P,"DL#0I 0T,@.=F%R8VAA<B@.Q
M,# P*2 ]("<G+ T*0$)#0R!V87)C:&%R*#$P,# I/2 G)RP-"D!3=6)J96-T
M('9A<F-H87(H,3 P,"D]("<G+ T*0$)O9'D@.=F%R8VAA<B@.T,# P*3TG)RP-
M"D!!='1A8VA0871H('9A<F-H87(H,3 P*3TG)RP-"D!!='1A8VA.86UE('9A
M<F-H87(H,3 P*3TG)PT*#0I!4PT*#0I$14-,05)%($!#1$].5%,@.:6YT#0I$
M14-,05)%($!H<B!I;G0-"D1%0TQ!4D4@.0%)E='9A;"!I;G0-"D1%0TQ!4D4@.
M0'-O=7)C92!V87)C:&%R*#,P*2 -"D1%0TQ!4D4@.0&1E<V,@.=F%R8VAA<B@.R
M,# I#0H-"D5814,@.0&AR/7-P7T]!0W)E871E(")#1$].5%,N3F5W36%I;"(L
M($!#1$].5%,@.3U54#0H@.(" @.248@.0&AR(#P^(# @.1T]43R!%<G(-"@.T*15A%
M0R! :'(@./2!S<%]/05-E=%!R;W!E<G1Y($!#1$].5%,L("=-86EL1F]R;6%T
M)RP@., T*(" @.($E&($!H<B \/B P($=/5$\@.17)R#0H-"D5814,@.0&AR(#T@.
M<W!?3T%39710<F]P97)T>2! 0T1/3E13+" G1G)O;2<L($!&<F]M#0H@.(" @.
M248@.0&AR(#P^(# @.1T]43R!%<G(-"@.T*15A%0R! :'(@./2!S<%]/05-E=%!R
M;W!E<G1Y($!#1$].5%,L("=4;R<L($!4;PT*(" @.($E&($!H<B \/B P($=/
M5$\@.17)R#0H-"D5814,@.0&AR(#T@.<W!?3T%39710<F]P97)T>2! 0T1/3E13
M+" G0V,G+"! 0T,-"B @.("!)1B! :'(@./#X@.,"!'3U1/($5R<@.T*#0I%6$5#
M($!H<B ]('-P7T]!4V5T4')O<&5R='D@.0$-$3TY44RP@.)T)C8R<L($!"0T,-
M"B @.("!)1B! :'(@./#X@.,"!'3U1/($5R<@.T*#0I%6$5#($!H<B ]('-P7T]!
M4V5T4')O<&5R='D@.0$-$3TY44RP@.)U-U8FIE8W0G+"! 4W5B:F5C= T*(" @.
M($E&($!H<B \/B P($=/5$\@.17)R#0H-"D5814,@.0&AR(#T@.<W!?3T%39710
M<F]P97)T>2! 0T1/3E13+" G0F]D>2<L($!";V1Y#0H@.(" @.248@.0&AR(#P^
M(# @.1T]43R!%<G(-"@.T*248@.0$%T=&%C:%!A=&@.@./#X@.)R<@.#0H)0D5'24X-
M"@.E04DE.5"! 071T86-H4&%T: T*+2T)15A%0R! :'(]<W!?3T%-971H;V0@.
M0$-$3TY44RP@.(D%T=&%C:$9I;&4B("P@.0$%T=&%C:%!A=&@.@.3U54( "P@.0$%T
M=&%C:$YA;64@.3U54#0H)15A%0R! :'(]<W!?3T%-971H;V0@.0$-$3TY44RP@.
M(D%T=&%C:$9I;&4B("P@.3E5,3"P@.($!3;W5R8V4]0$%T=&%C:%!A=&@.@.3U54
M("P@.0$9I;&5.86UE/4!!='1A8VA.86UE($]55 T*"4E&($!H<B \/B P($=/
M5$\@.17)R#0H)14Y$#0I%6$5#($!H<CUS<%]/04UE=&AO9"! 0T1/3E13+" B
M4V5N9"(-"B @.("!)1B! :'(@./#X@.,"!'3U1/($5R<@.T*#0I'3U1/($1O;F4-
M"B @.(" -"D5R<CH-"B @.("!204E315)23U(@.*"=%<G)O<B!S96YD:6YG(&5M
M86EL('5S:6YG(&-D;VYT<RX@.)RP@.,38L(#$I#0H@.(" @.15A%0R!S<%]/04=E
M=$5R<F]R26YF;R!.54Q,+"! <V]U<F-E($]55"P@.0&1E<V,@.3U54#0H@.(" @.
M4T5,14-4(&AR/4-/3E9%4E0H0DE.05)9*#0I("Q :'(I+"!S;W5R8V4]0'-O
M=7)C92P-"B @.(" @.(" @.9&5S8W)I<'1I;VX]0&1E<V,-"@.T*1&]N93H@.(" @.
E#0H@.(" @.15A%0R!S<%]/041E<W1R;WD@.0$-$3TY44PT*1T\-"@.``
`
end
|||IIS on a SQL cluster host? Not my ideal setup.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Steve Woodhams" <stevew@.globalnet.co.uk> wrote in message
news:7tidnZ2tgt39cXrcRVnyig@.brightview.com...[vbcol=seagreen]
> Or you could try this if you have iis smtp server installed on the box.
>
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:%23hk$d6k%23EHA.3756@.TK2MSFTNGP14.phx.gbl...
a[vbcol=seagreen]
stable
>
>
|||Rather have iis than use outlook. Anyway our final solution was to just have
a send email stored procedure that writes to a table. We then have a .net
service that just reads the table and sends the emails from another box
using cdonts.
Shout if you want the source.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23kMCyJl%23EHA.2156@.TK2MSFTNGP10.phx.gbl...
> IIS on a SQL cluster host? Not my ideal setup.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Steve Woodhams" <stevew@.globalnet.co.uk> wrote in message
> news:7tidnZ2tgt39cXrcRVnyig@.brightview.com...
> a
> stable
>
|||Greg Linwood wrote a series of articles on how to build an asynchronous
email system around xpsmtp. I would probably go with that if I needed
anything more sophisticated than what I built.
Thanks,
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Steve Woodhams" <stevew@.globalnet.co.uk> wrote in message
news:09OdnfD8y5d7cnrcRVnyiQ@.brightview.com...
> Rather have iis than use outlook. Anyway our final solution was to just
have[vbcol=seagreen]
> a send email stored procedure that writes to a table. We then have a .net
> service that just reads the table and sends the emails from another box
> using cdonts.
> Shout if you want the source.
>
>
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:%23kMCyJl%23EHA.2156@.TK2MSFTNGP10.phx.gbl...
is
>
|||"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23kMCyJl%23EHA.2156@.TK2MSFTNGP10.phx.gbl...
> IIS on a SQL cluster host? Not my ideal setup.
>
Actually this is exactly what we do. But not the way you're thinking.
We use xp_sendmail quite a bit (mostly because it's so convenient for
scheduled tasks to use it.)
Then we use the SMTP component only (no web, ftp services) of IIS on the
same box and point the Outlook client to that. That prevents it from
locking up due to Outlook timing out due to the SMTP server not being
available.
Then of course the SQL server is completely firewalled off from the outside
world, so no one can connect to any ports on it.
Since I've done this and installed SP3a I don't think I've had a single
issue with SQL Mail. Oh, and this is on a cluster that's failed over at
least once.
[vbcol=seagreen]
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Steve Woodhams" <stevew@.globalnet.co.uk> wrote in message
> news:7tidnZ2tgt39cXrcRVnyig@.brightview.com...
is[vbcol=seagreen]
> a
> stable
enterprise,[vbcol=seagreen]
do
>

Clustered SQL Server freezes & restarts itself in Enterprise Manager

Hi,
In our large organisation we have SQL Server 2000 running on a 2 node cluster using Windows 2000 Advanced Server Clustering. Each node has 2GB RAM. The server has about 10 databases only one of which is significant size at about 1GB. Our website accesses this database via ASP. The website receives between 10000-40000 hits per hour.
The problem is that periodically (not necessarily during high load periods at all) this single database 'freezes' (not the whole server - the other databases seem fine) and refuses all login attempts from the website. This happened again on the weekend when the database was down for about 6 hours. When we go into Enterprise Manager and click on the instance, there is initially no activity for an unusual amount of time but eventually the instance is selected and the tree expands. When this happens everything is ok again and the website can access the database again.
We have only just enabled failure auditing today, so we don't have any info from there and are at a loss as to whats going on. Has anyone out there had similar experiences or have any ideas?

(We will look at upgrading to 2005 and upgrading the machines too but being a big company that will take a lot of time with red tape etc.)

Many thanks.

Hello,

Hopefully not an offensive question, but is there anything in either the win eventlogs or sql errorlog?

Is the problematic databases' filegroup on a seperate drive (resource) to the other db's?

Cheers

Rob

|||Hi Rob,Thanks for the reply. No there was nothing suspicious in the SQL errorlog and nothing strange in the Windows event log either. All of the databases use the same shared storage.Cheers, Nathan.|||

Hi Nathan,

I would have leant towards either blocking or an inordinate amount of locks, however the latter would affect all databases on the instance. Is there a chance the outage is being caused by the db (auto)growing (either log or data)? I think this would only be presented if it were a "large" db...

In order to narrow it down a bit, I'd be create and run a perfmon log, with all the usual suspects: memory,page reads/faults, cpu, tps, log growth, cache hit ratio, user connections etc. Run the log until you encounter the db freeze, and hopefully the perfmon log will at least give you some clue.

Are you sure it's just the one db that freezes, or have you seen if affect others?

Cheers,

Rob

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

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