Can't complete SQL Server 2005 installation!!!

An err occurs when the installation of SQL Server 2005 ,"failed to start" SQL Server , the err msg asks me to query online menually,includes "SQL Server 2005 Setup Log Files and Starting SQL Server Manually." but I don't know what is the problem. Can you help me?

You first need to look at the SQL Server summary log file located at: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\summary.txt. This should direct you to which component is failing and the log file for that component. When looking at the component log files you can easily locate the trouble area by searching the file for "value 3" - this will jump you to the area of the log file that contains the error. Reply back with the section of the log file that contains the error.

If this log file doesn't specify a particular component you need to look at the core log file located at: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\*core*.log. You should find the error at the bottom of this log file. If there error is in this log file please reply back with the section of the log file that contains the error.

Thanks,

Dan

|||Hello,Dan：
I found the two files, and i knew that what component is failing, but I don't know clearly you mean "value 3."

this is the failing component in summary.txt
--
Machine : PROJECTTEAM
Product : Microsoft SQL Server 2005 CTP
Product Version : 9.00.1116
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_PROJECTTEAM_SQL.log
Error Number : 2147944003

The file is the component log file,I don't know how to find the
cause of error,can you help me?
http://ms.ntcb.edu.tw/~s8856094/SQL/SQLSetup0013_PROJECTTEAM_SQL.log
Thank you..|||Okay, the service is failing to start. I need to direct you to yet another log file. In the middle of setup you will find a log file for the SQL Server DB Engine under the installation folder for this component. If you are installing on a clean machine it will be under c:\program files\microsoft sql server\mssql.1\log. This file will specify why the service couldn't start up.

Dan

p.s. "Value 3" is nothing special other than the MSI return code for failures. It's an easy thing to search on to find the actual text of the error message in the log. In your case it pointed me to the following error:

Error 29523. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067)|||I'm going to close out this thread since there hasn't been a response to my question in three weeks.
Dan|||Most of the above applies to my case as well.
The best clue I have to the failure is this event log item:
Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 5603
Date: 8/10/2005
Time: 8:16:07 AM
User: WINGS\rheitzman
Computer: PC3090-060
Description:
A provider, SQLServerEventProvider, has been registered in the WMI namespace, root\Microsoft\SqlServer\ServerEvents\SQLEXPRESS, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
The SQLExpress install proceeds OK to the midpoint of installing the Database Services that halts with the message that began this thread.
I tried to restart the service beore canceling the install to no avail. Canceling the install backs out the install so the directions to start manually are bogus since the service(s) is removed.
Beta 1 was installed and the removal tool has been used; serveral times.
SQL Server 2000 reporting services was installed at one time and was also problematic. It was removed via add/remove.
Any help would be appreciated!

Cant Auto-Start Agent

I have a SQL Server 2000 that failed to start after a Windows reboot.
Agent properties are checked to auto start if stopped. Under the Agent
Error Log, I have the following data:

Information:
SQL Agent stopping because of Windows shutdown.
SQL Agent terminated normally.

Error:
SQL Server Error: 1115, cannot generate SSPI context SQLState HY000.
Logon to server(local) failed.

Help apprecaited. Thanks
Frank

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Frank Py <fpy@.proactnet.com> wrote in message news:<3f843998$0$202$75868355@.news.frii.net>...
> I have a SQL Server 2000 that failed to start after a Windows reboot.
> Agent properties are checked to auto start if stopped. Under the Agent
> Error Log, I have the following data:
> Information:
> SQL Agent stopping because of Windows shutdown.
> SQL Agent terminated normally.
> Error:
> SQL Server Error: 1115, cannot generate SSPI context SQLState HY000.
> Logon to server(local) failed.
> Help apprecaited. Thanks
> Frank
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

You might find these KB articles helpful:

http://support.microsoft.com/defaul...9&Product=sql2k
http://support.microsoft.com/defaul...4&Product=sql2k

Simon|||I am having this problem, too. Have you found a solution?

Cant add "ComputerName\ASPNET user

I see a lot of people have this same problem, but I still can't find a solution. I keep getting a "SqlException: Login failed for user 'domain\user name'Error when I try and access my SQL db from my web app. I've tried adding the ASPNET user to my db, but am unable to. Here are the steps I took:

SQL 2000 ent manager
-Windows NT
-Logins (right Click)
-New login
-Name <click>
but once I'm here, I can't find the ASPNET user name, and I am unable to create it here, or under the database users. Any help? It works fine on my local machine.

Do I need to install the .NET framework on my SQL server?

You don't need--exactly speaking you can not create a Windows account in SQL, what you can do is just adding existing Windows account to SQL logins. So just input myserver\ASPNETas login name while choosing Windows Authenticaiton. If you can't add myserver\ASPNET and get an error saying "Windows user or group can not be found...", then check the login failure error message from .NET. What's the login name in the error message? Is it myserver\ASPNET?If you're using IIS 6.0, the login name should be 'NT AUTHROITY\NETWORK SERVICE'

Can't access default database on start up

Help!
The default database failed on the restore, and was marked
as in load. After trying to get the database out of that
state, the server was stoped and restarted. On the
restart, we now get the message that the default database
can not be accessed, so we can't connect. For some
unknown reason the default database for the admin group
was not Master, but the database that is marked in Load.
How can I know connect to the server?
Thanks
Mike Allen
Novice DBA|
| The default database failed on the restore, and was marked
| as in load. After trying to get the database out of that
| state, the server was stoped and restarted. On the
| restart, we now get the message that the default database
| can not be accessed, so we can't connect. For some
| unknown reason the default database for the admin group
| was not Master, but the database that is marked in Load.
|
| How can I know connect to the server?
|
--
Hi Mike,
If you connect using osql, you can use the /d switch to specify another
database as the default. For more information, please consult your SQL
Server Books Online on the topic "default database."
Hope this helps,
--
Eric Cárdenas
SQL Server support|||Thanks for your help. Even after changing the default db, for the Admin group, I was not able to get connect through EM. So I added my individual userid with a default db of master, and that worked. Now I get to 'fix' the bad database.
Thanks.
>--Original Message--
>| >| The default database failed on the restore, and was marked >| as in load. After trying to get the database out of that >| state, the server was stoped and restarted. On the >| restart, we now get the message that the default database >| can not be accessed, so we can't connect. For some >| unknown reason the default database for the admin group >| was not Master, but the database that is marked in Load.
>| >| How can I know connect to the server?
>| >--
>Hi Mike,
>If you connect using osql, you can use the /d switch to specify another >database as the default. For more information, please consult your SQL >Server Books Online on the topic "default database."
>Hope this helps,
>--
>Eric C=E1rdenas
>SQL Server support
>.
>sql

can't (re)start SQLServerAgent after changing its logon credentials

Since Copy Databas Wizard failed to copy anything from remote SS20005 (both are with SP2 3054) in any combination,
I changed SQLServerAgent(myinstance_name) to run under Network from Local System with the help of SQL Server Configuration Manager

For this change it was restarted, failed to start again and continues to be stopped giving
"SQLServerAgent could not be started (reason: Unable to connect to server '<mymachine_name>\<myinstance_name>'; SQLServerAgent cannot start)."

I changed SQL Server Agent (myinstance_name) back to Local Service, then to Local System and still can't start it.

So, my questions:
1)
What has happened and how can I start SQLServerAgent?

2)
Why cannot I start it under Network Service? since it apparently should access remote resources for CDW to copy from remote SS2005

This is on MS Windows XP SP2

PS
After few trials I amnaged to restart it again under Local System but still cannot change to any different one

If you change the account under which SQL Agent starts you need to make sure that the account has permissions within SQL server or else each tim eit tries to access SQL Server it will fail. Have a look at these:

http://support.microsoft.com/kb/283811

http://support.microsoft.com/kb/907557

|||

You can verify the permissions, windows group membership required, etc for the service accounts in the following books online topic:

Setting Up Windows Service Accounts

http://msdn2.microsoft.com/en-us/library/ms143504.aspx

The NT Rights and Privleges section has the local windows group membership requirements - that one often gets overlooked for some reason. The help topic is pretty thorough and does a good job of covering the requirements.

Also note that as the article states, using Network Service isn't recommended. A domain account can provide the same network access but in a more secure manner. Otherwise you open some holes - network service means you give permissions needed for the CDW to the machine account. And then other apps, services running under network service get the permissions as well as they would be operating under the machine account.

-Sue

cannot start trace

After going through all the configurations in Trace Properties, I clicked
Run, then I got this error back:
Failed to start a trace. SQL server does not exist or access denied.
The user I'm connecting to the server has full privileges on the databases.
Where should I check?
Thanks for any help,
Bingbing wrote:
> After going through all the configurations in Trace Properties, I
> clicked Run, then I got this error back:
> Failed to start a trace. SQL server does not exist or access denied.
> The user I'm connecting to the server has full privileges on the
> databases. Where should I check?
> Thanks for any help,
> Bing
You're not even getting to the server. Either the server name is
mistyped or your login name/password is incorrect.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Oh? In SQL Profiler, clicking File->New->Trace, then a window with title
'Connect to Server' pops up, in this window, SQL Server is set to local,
Connecting using Windows authentication. Clicking Ok in this window brings
up another window Trace Properties.
I think at this point I've already connected to the server fine. No?
Anyway, I tried changing server name from local to its hostname, it worked.
Odd, I was doing all this on the database server, how doesn't 'local' work?
Bing
"David Gugick" wrote:
> bing wrote:
> > After going through all the configurations in Trace Properties, I
> > clicked Run, then I got this error back:
> >
> > Failed to start a trace. SQL server does not exist or access denied.
> >
> > The user I'm connecting to the server has full privileges on the
> > databases. Where should I check?
> >
> > Thanks for any help,
> >
> > Bing
> You're not even getting to the server. Either the server name is
> mistyped or your login name/password is incorrect.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||bing wrote:
> Oh? In SQL Profiler, clicking File->New->Trace, then a window with
> title 'Connect to Server' pops up, in this window, SQL Server is set
> to local, Connecting using Windows authentication. Clicking Ok in
> this window brings up another window Trace Properties.
> I think at this point I've already connected to the server fine. No?
> Anyway, I tried changing server name from local to its hostname, it
> worked. Odd, I was doing all this on the database server, how doesn't
> 'local' work?
"(local)" not "local". I prefer using the real server name just as you
ended up doing. I'm not exacly sure what the problem was. The error
message you posted indicated you never made it to the server (my
username/pwd comment aside). But if what you're saying is you get past
the login screen, then you are in fact logging in successfully to the
server. It's just that at that point the trace has not started. You have
only verified with Profiler that you have a valid admin login to the
server. Just stick with the real server name and you should be fine.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Sorry about not being precise. It's my typo. Yes, it is '(local)' rather
than 'local'.
Bing
"David Gugick" wrote:
> bing wrote:
> > Oh? In SQL Profiler, clicking File->New->Trace, then a window with
> > title 'Connect to Server' pops up, in this window, SQL Server is set
> > to local, Connecting using Windows authentication. Clicking Ok in
> > this window brings up another window Trace Properties.
> >
> > I think at this point I've already connected to the server fine. No?
> >
> > Anyway, I tried changing server name from local to its hostname, it
> > worked. Odd, I was doing all this on the database server, how doesn't
> > 'local' work?
> "(local)" not "local". I prefer using the real server name just as you
> ended up doing. I'm not exacly sure what the problem was. The error
> message you posted indicated you never made it to the server (my
> username/pwd comment aside). But if what you're saying is you get past
> the login screen, then you are in fact logging in successfully to the
> server. It's just that at that point the trace has not started. You have
> only verified with Profiler that you have a valid admin login to the
> server. Just stick with the real server name and you should be fine.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>

Cannot start SQL 2000

I installed a SQL6.5 to a server which is already have a
SQL 2000 running. However, both sql 6.5 and 2000 are
failed to start. Anyone have an idea?
Thanks.What errors are you getting in the SQL Server error logs and the event
viewer?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Charles Lee" <leech@.dnb.com> wrote in message
news:21d3a01c45cfd$bcbd2450$a601280a@.phx.gbl...
I installed a SQL6.5 to a server which is already have a
SQL 2000 running. However, both sql 6.5 and 2000 are
failed to start. Anyone have an idea?
Thanks.|||Hi,
If you have an default instance of SQL 2000 installed already, then you can
not start the SQL 6.5 service and run in parellel.
To trobleshoot , Go to command prompt and go to the SQL 6.5 folder
(\MSSQL\BINN folder).
Now execute
SQLSERVR -m
THis will give you the correct error mesasge to troubleshoot.
Do the same for SQL 2000 as well.
Right way to do is :-
1. Install SQL 6.5
2. Install SQL 2000 Named instance.
So both the services can run in parellel.
Thanks
Hari
MCDBA
"Charles Lee" <leech@.dnb.com> wrote in message
news:21d3a01c45cfd$bcbd2450$a601280a@.phx.gbl...
> I installed a SQL6.5 to a server which is already have a
> SQL 2000 running. However, both sql 6.5 and 2000 are
> failed to start. Anyone have an idea?
> Thanks.|||Hi,
If you have an default instance of SQL 2000 installed already, then you can
not start the SQL 6.5 service and run in parellel.
To trobleshoot , Go to command prompt and go to the SQL 6.5 folder
(\MSSQL\BINN folder).
Now execute
SQLSERVR -m
THis will give you the correct error mesasge to troubleshoot.
Do the same for SQL 2000 as well.
Right way to do is :-
1. Install SQL 6.5
2. Install SQL 2000 Named instance.
So both the services can run in parellel.
Thanks
Hari
MCDBA
"Charles Lee" <leech@.dnb.com> wrote in message
news:21d3a01c45cfd$bcbd2450$a601280a@.phx.gbl...
> I installed a SQL6.5 to a server which is already have a
> SQL 2000 running. However, both sql 6.5 and 2000 are
> failed to start. Anyone have an idea?
> Thanks.|||The message is:
The system is older than SQL Ssrver 7.0 RTM version and
is not supported by this server.
>--Original Message--
>What errors are you getting in the SQL Server error logs
and the event
>viewer?
>--
>HTH,
>Vyas, MVP (SQL Server)
>http://vyaskn.tripod.com/
>Is .NET important for a database professional?
>http://vyaskn.tripod.com/poll.htm
>
>"Charles Lee" <leech@.dnb.com> wrote in message
>news:21d3a01c45cfd$bcbd2450$a601280a@.phx.gbl...
>I installed a SQL6.5 to a server which is already have a
>SQL 2000 running. However, both sql 6.5 and 2000 are
>failed to start. Anyone have an idea?
>Thanks.
>
>.
>|||The message is:
The system is older than SQL Ssrver 7.0 RTM version and
is not supported by this server.
Now, I just want to get rid of 6.5 and keep 2000 since
there are database in 2000.
Thanks.
>--Original Message--
>Hi,
>If you have an default instance of SQL 2000 installed
already, then you can
>not start the SQL 6.5 service and run in parellel.
>To trobleshoot , Go to command prompt and go to the SQL
6.5 folder
>(\MSSQL\BINN folder).
>Now execute
>SQLSERVR -m
>THis will give you the correct error mesasge to
troubleshoot.
>Do the same for SQL 2000 as well.
>Right way to do is :-
>1. Install SQL 6.5
>2. Install SQL 2000 Named instance.
>So both the services can run in parellel.
>Thanks
>Hari
>MCDBA
>
>
>
>"Charles Lee" <leech@.dnb.com> wrote in message
>news:21d3a01c45cfd$bcbd2450$a601280a@.phx.gbl...
>> I installed a SQL6.5 to a server which is already have
a
>> SQL 2000 running. However, both sql 6.5 and 2000 are
>> failed to start. Anyone have an idea?
>> Thanks.
>
>.
>|||Charles
You can install diferent versions of SQL Server on the same server, however you need to install them in the right order. That is 6.5 first, then 7 and finally 2000. As you already had 2000 installed that is why you can not run 6.5. Also if you have mutiple versions of SQL Server you can only run one of them at a time. When you have mutiple versions you get the option to switch between them on your start menu.
You need to uninstall 6.5. If you really want it on the same server. After uninstall, take a backup of your 2000 master and detach all your user databases. Uninstall 2000. Install 6.5. Install 2000. Make sure 2000 is the active service and restore your master database (this is to synch user ID's and loggin's), attach your user databases and you should be up and running. You can then switch between 2000 and 6.5.
If you have some SQL jobs, you can either script them out before uninstalling 2000 or backup and recover the msdb database like the master.
Hope this helps
John|||John,
Thanks for your detailed description. However, I tried
to uninstall 6.5 but it doesn't provide me an option to
do that. It only provide me a install option. Do you
have any idea?
Thanks.
>--Original Message--
>Charles
>You can install diferent versions of SQL Server on the
same server, however you need to install them in the
right order. That is 6.5 first, then 7 and finally 2000.
As you already had 2000 installed that is why you can not
run 6.5. Also if you have mutiple versions of SQL Server
you can only run one of them at a time. When you have
mutiple versions you get the option to switch between
them on your start menu.
>You need to uninstall 6.5. If you really want it on the
same server. After uninstall, take a backup of your 2000
master and detach all your user databases. Uninstall
2000. Install 6.5. Install 2000. Make sure 2000 is the
active service and restore your master database (this is
to synch user ID's and loggin's), attach your user
databases and you should be up and running. You can then
switch between 2000 and 6.5.
>If you have some SQL jobs, you can either script them
out before uninstalling 2000 or backup and recover the
msdb database like the master.
>Hope this helps
>John
>.
>|||Hi,
Please select the SETUP program from SQL 6.5 program group and run the
setup. If you go 2 screens further you have "REMOVE SQL SERVER Option".
If you do not have setup program in SQL Server 6.5 program groups then
select the EXE from \MSSQL\BINN folder of SQL 6.5 installation folder.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:2277001c45d78$98986780$a301280a@.phx.gbl...
> John,
> Thanks for your detailed description. However, I tried
> to uninstall 6.5 but it doesn't provide me an option to
> do that. It only provide me a install option. Do you
> have any idea?
> Thanks.
> >--Original Message--
> >Charles
> >
> >You can install diferent versions of SQL Server on the
> same server, however you need to install them in the
> right order. That is 6.5 first, then 7 and finally 2000.
> As you already had 2000 installed that is why you can not
> run 6.5. Also if you have mutiple versions of SQL Server
> you can only run one of them at a time. When you have
> mutiple versions you get the option to switch between
> them on your start menu.
> >
> >You need to uninstall 6.5. If you really want it on the
> same server. After uninstall, take a backup of your 2000
> master and detach all your user databases. Uninstall
> 2000. Install 6.5. Install 2000. Make sure 2000 is the
> active service and restore your master database (this is
> to synch user ID's and loggin's), attach your user
> databases and you should be up and running. You can then
> switch between 2000 and 6.5.
> >
> >If you have some SQL jobs, you can either script them
> out before uninstalling 2000 or backup and recover the
> msdb database like the master.
> >
> >Hope this helps
> >
> >John
> >.
> >|||Hi,
I tried it but it is grey. I can't select it.
>--Original Message--
>Hi,
>Please select the SETUP program from SQL 6.5 program
group and run the
>setup. If you go 2 screens further you have "REMOVE SQL
SERVER Option".
>If you do not have setup program in SQL Server 6.5
program groups then
>select the EXE from \MSSQL\BINN folder of SQL 6.5
installation folder.
>
>Thanks
>Hari
>MCDBA
><anonymous@.discussions.microsoft.com> wrote in message
>news:2277001c45d78$98986780$a301280a@.phx.gbl...
>> John,
>> Thanks for your detailed description. However, I tried
>> to uninstall 6.5 but it doesn't provide me an option to
>> do that. It only provide me a install option. Do you
>> have any idea?
>> Thanks.
>> >--Original Message--
>> >Charles
>> >
>> >You can install diferent versions of SQL Server on the
>> same server, however you need to install them in the
>> right order. That is 6.5 first, then 7 and finally
2000.
>> As you already had 2000 installed that is why you can
not
>> run 6.5. Also if you have mutiple versions of SQL
Server
>> you can only run one of them at a time. When you have
>> mutiple versions you get the option to switch between
>> them on your start menu.
>> >
>> >You need to uninstall 6.5. If you really want it on
the
>> same server. After uninstall, take a backup of your
2000
>> master and detach all your user databases. Uninstall
>> 2000. Install 6.5. Install 2000. Make sure 2000 is the
>> active service and restore your master database (this
is
>> to synch user ID's and loggin's), attach your user
>> databases and you should be up and running. You can
then
>> switch between 2000 and 6.5.
>> >
>> >If you have some SQL jobs, you can either script them
>> out before uninstalling 2000 or backup and recover the
>> msdb database like the master.
>> >
>> >Hope this helps
>> >
>> >John
>> >.
>> >
>
>.
>|||How about in your SQL Server 2000 group? Or the "SQL Server 2000 - Switch" group?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Charles Lee" <leech@.dnb.com> wrote in message news:2279f01c45d7e$b92c57d0$a301280a@.phx.gbl...
> Hi,
> I tried it but it is grey. I can't select it.
> >--Original Message--
> >Hi,
> >
> >Please select the SETUP program from SQL 6.5 program
> group and run the
> >setup. If you go 2 screens further you have "REMOVE SQL
> SERVER Option".
> >
> >If you do not have setup program in SQL Server 6.5
> program groups then
> >select the EXE from \MSSQL\BINN folder of SQL 6.5
> installation folder.
> >
> >
> >
> >Thanks
> >Hari
> >MCDBA
> >
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:2277001c45d78$98986780$a301280a@.phx.gbl...
> >> John,
> >>
> >> Thanks for your detailed description. However, I tried
> >> to uninstall 6.5 but it doesn't provide me an option to
> >> do that. It only provide me a install option. Do you
> >> have any idea?
> >>
> >> Thanks.
> >>
> >> >--Original Message--
> >> >Charles
> >> >
> >> >You can install diferent versions of SQL Server on the
> >> same server, however you need to install them in the
> >> right order. That is 6.5 first, then 7 and finally
> 2000.
> >> As you already had 2000 installed that is why you can
> not
> >> run 6.5. Also if you have mutiple versions of SQL
> Server
> >> you can only run one of them at a time. When you have
> >> mutiple versions you get the option to switch between
> >> them on your start menu.
> >> >
> >> >You need to uninstall 6.5. If you really want it on
> the
> >> same server. After uninstall, take a backup of your
> 2000
> >> master and detach all your user databases. Uninstall
> >> 2000. Install 6.5. Install 2000. Make sure 2000 is the
> >> active service and restore your master database (this
> is
> >> to synch user ID's and loggin's), attach your user
> >> databases and you should be up and running. You can
> then
> >> switch between 2000 and 6.5.
> >> >
> >> >If you have some SQL jobs, you can either script them
> >> out before uninstalling 2000 or backup and recover the
> >> msdb database like the master.
> >> >
> >> >Hope this helps
> >> >
> >> >John
> >> >.
> >> >
> >
> >
> >.
> >|||Hi Tiber/Charles Lee,
It seems your SQL 6.5 is not installed properly, Might be a registrry issue.
In this case only solution is
remove manually. But this may not make your SQl 2000 server as default. So
solution to
make your SQL 2000 up is:- Since your SQl 2000 service is down you can
detach aswell.
1. Remove SQL 6.5 manually and tr restarting SQL 2000. If it fails then:-
2. Copy the MDF and LDF (including system databases) to a safe location.
3. Remove SQL 2000 (Use control panel add remove programs)
4. Install SQl 2000 in the same folder structure as old
5. Install the service pack saem as old
6. Stop sql server
7. COpy the MDF and LDF (taken in step -2) to the same folders
8. Start SQl server service.
Link to manually remove sql 6.5
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:
80/support/kb/articles/q198/6/80.asp&NoWebContent=1
Thanks
Hari
MCDBA
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:#of30aaXEHA.2364@.TK2MSFTNGP12.phx.gbl...
> How about in your SQL Server 2000 group? Or the "SQL Server 2000 - Switch"
group?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Charles Lee" <leech@.dnb.com> wrote in message
news:2279f01c45d7e$b92c57d0$a301280a@.phx.gbl...
> > Hi,
> >
> > I tried it but it is grey. I can't select it.
> >
> > >--Original Message--
> > >Hi,
> > >
> > >Please select the SETUP program from SQL 6.5 program
> > group and run the
> > >setup. If you go 2 screens further you have "REMOVE SQL
> > SERVER Option".
> > >
> > >If you do not have setup program in SQL Server 6.5
> > program groups then
> > >select the EXE from \MSSQL\BINN folder of SQL 6.5
> > installation folder.
> > >
> > >
> > >
> > >Thanks
> > >Hari
> > >MCDBA
> > >
> > ><anonymous@.discussions.microsoft.com> wrote in message
> > >news:2277001c45d78$98986780$a301280a@.phx.gbl...
> > >> John,
> > >>
> > >> Thanks for your detailed description. However, I tried
> > >> to uninstall 6.5 but it doesn't provide me an option to
> > >> do that. It only provide me a install option. Do you
> > >> have any idea?
> > >>
> > >> Thanks.
> > >>
> > >> >--Original Message--
> > >> >Charles
> > >> >
> > >> >You can install diferent versions of SQL Server on the
> > >> same server, however you need to install them in the
> > >> right order. That is 6.5 first, then 7 and finally
> > 2000.
> > >> As you already had 2000 installed that is why you can
> > not
> > >> run 6.5. Also if you have mutiple versions of SQL
> > Server
> > >> you can only run one of them at a time. When you have
> > >> mutiple versions you get the option to switch between
> > >> them on your start menu.
> > >> >
> > >> >You need to uninstall 6.5. If you really want it on
> > the
> > >> same server. After uninstall, take a backup of your
> > 2000
> > >> master and detach all your user databases. Uninstall
> > >> 2000. Install 6.5. Install 2000. Make sure 2000 is the
> > >> active service and restore your master database (this
> > is
> > >> to synch user ID's and loggin's), attach your user
> > >> databases and you should be up and running. You can
> > then
> > >> switch between 2000 and 6.5.
> > >> >
> > >> >If you have some SQL jobs, you can either script them
> > >> out before uninstalling 2000 or backup and recover the
> > >> msdb database like the master.
> > >> >
> > >> >Hope this helps
> > >> >
> > >> >John
> > >> >.
> > >> >
> > >
> > >
> > >.
> > >
>

CANNOT SET PARTNER 'NT AUTHORITY\ANONYMOUS LOGON.' failed

i tried to set up mirroring having only principal and mirror. mirroring endpoints were easily created for both servers. when i try to add the partner name it responds with
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://machine1.domain.com:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.
On the log of machine1 i see,
Database Mirroring login attempt by user 'NT AUTHORITY\ANONYMOUS LOGON.' failed with error: 'Connection handshake failed. The login 'NT AUTHORITY\ANONYMOUS LOGON' does not have CONNECT permission on the endpoint. State 84.'.

i have similar problems as in

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1020144&SiteID=1

i am a sysadmin on both SQL Servers and have connect permission on both end points.
Both the endpoints are in started state and listening to all IP's
Both services are as 'Local System'
As per what was mentioned in the above post to add a 'domain/machine$' user did not help.
Tried using setspn.exe to add a new SPN MSSQLsvc/<HOST>:<MIRRORINGPORT> did not work. an ERROR comes 'not enough privileges'
setup shows the following SPN only on both
HOST/Machine name
HOST/Machine name.Domin.com
MSSQLSvc/Machine name.Domin.com:1433
SMTPSVC/Machine name
SMTPSVC/machine name.Domain.com

and on second machine
HOST/Machine name

HOST/Machine name.Domin.com

MSSQLSvc/Machine name.Domin.com:1433

any Clues?

Udit Ghai wrote:

Tried

using setspn.exe to add a new SPN

MSSQLsvc/<HOST>:<MIRRORINGPORT> did not work. an ERROR

comes 'not enough privileges'

This is probably your problem. Run this command from an account with enough priviledges on the Active Directory. One easy trick is to run this command as the LocalSystem of the machine <HOST>. To achieve this, you must start a command prompt as LocalSystem on <HOST>. Use the AT service for this, scheduling an interactive CMD.EXE one minute in future. E.g. if the clock is 11:45, run this:
at 11:46 /interactive cmd.exe
In one minute a command prompt running as LocalSystem will popup. From this, run the SETSPN. You must do this on all machines involved (principal, witness, mirror if any)

HTH,
~ Remus

P.S. This assumes you're running the SQL Server service as LocalSystem or as NETWORK SERVICE.