Cannot recover the master database.

Hi,
In my computer when sql is starting occur the follow
message in log :
- Error: 9003, Severity: 20, State: 1.
- Cannot recover the master database.
What I do? Why this happened?
Thanks,
Daniela"Daniela" <daniela@.perfilcs.com.br> wrote in message
news:257101c41b18$e6f5f3e0$3a01280a@.phx.gbl...
> Hi,
> In my computer when sql is starting occur the follow
> message in log :
> - Error: 9003, Severity: 20, State: 1.
> - Cannot recover the master database.
> What I do? Why this happened?
>
To fix a corrupted master database run rebuildm.exe. This will destroy your
master, msdb and modle databases and replace them with blank ones. Then
restore your master, msdb and model backups.
Erm... You do have a backup of your system databases, don't you?
If not, then after rebuildm.exe you'll have to execute sp_attach_db or
sp_attach_single_file_db to repopulate your sysdatabases table in Master.
Also you will have to recreate your SQLAgent jobs etc if you do not have a
MSDB backup
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.647 / Virus Database: 414 - Release Date: 29/03/2004|||i hope you been backing up your system database regularly. if you don't. you
are in trouble.
you can't restore a corrupt master.mdb thru GUI.
-- to exclusive use the master database (to restore)
/* start the server in exclusive mode
From a command prompt (the dos prompt, get to the c:\mssql7\binn directory
(adjust accordingly for sql2k), enter:
sqlservr.exe -c (standard)
sqlservr -m (exclusive)
restore master db from the last known good backup
stop server and re-start in normal mode
*/
once the master is restored. you can use Enterprise Manger GUI to restore
the last known good copy of msdb.
Steve Lin
MCDBA
"Daniela" <daniela@.perfilcs.com.br> wrote in message
news:257101c41b18$e6f5f3e0$3a01280a@.phx.gbl...
> Hi,
> In my computer when sql is starting occur the follow
> message in log :
> - Error: 9003, Severity: 20, State: 1.
> - Cannot recover the master database.
> What I do? Why this happened?
> Thanks,
> Daniela
>

Cannot make server as Target server or link from Master Server

Sql Server 7 Standard Edition
My Server was renamed and the normal steps of reinstalling
and running sp_dropserver and sp_addserver were followed.
Everything seems to work fine but jobs from the master server.
I did defect the server as a target server since it appeared as offline
anyway.

On trying to re establish the status of the server as a target server

Failed to make "serverName" a target server
Enlist into Master Server "MasterServerName" Failed(Error 14262)

Your insight is appreciated
Vincento"Vincento Harris" <wumutek@.yahoo.com> wrote in message
news:2fa13ee7.0405100422.632f4324@.posting.google.c om...
> Sql Server 7 Standard Edition
> My Server was renamed and the normal steps of reinstalling
> and running sp_dropserver and sp_addserver were followed.
> Everything seems to work fine but jobs from the master server.
> I did defect the server as a target server since it appeared as offline
> anyway.
>
> On trying to re establish the status of the server as a target server
> Failed to make "serverName" a target server
> Enlist into Master Server "MasterServerName" Failed(Error 14262)
> Your insight is appreciated
> Vincento

Is @.@.SERVERNAME returning the correct (new) name? Error 14262 should be "The
specified %s ('%s') does not exist" - what is the full error message you
see? Are there any name resolution issues, ie. can both servers see each
other (ping.exe or NET VIEW) on the network?

Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message news:<409fc26e$1_1@.news.bluewin.ch>...
> "Vincento Harris" <wumutek@.yahoo.com> wrote in message
> news:2fa13ee7.0405100422.632f4324@.posting.google.c om...
> > Sql Server 7 Standard Edition
> > My Server was renamed and the normal steps of reinstalling
> > and running sp_dropserver and sp_addserver were followed.
> > Everything seems to work fine but jobs from the master server.
> > I did defect the server as a target server since it appeared as offline
> > anyway.
> > On trying to re establish the status of the server as a target server
> > Failed to make "serverName" a target server
> > Enlist into Master Server "MasterServerName" Failed(Error 14262)
> > Your insight is appreciated
> > Vincento
> Is @.@.SERVERNAME returning the correct (new) name? Error 14262 should be "The
> specified %s ('%s') does not exist" - what is the full error message you
> see? Are there any name resolution issues, ie. can both servers see each
> other (ping.exe or NET VIEW) on the network?
> Simon

Thanks for your response.
@.@.servername returns the right value.
I did forget to mention that the master server is sql server 2000 and
target server, sql server 7.
When the master server is pinged from the client it returns packets
with no error.

When originating_server is selected from sysjobs it returns 'local'

I did notice that the target server name has been added as an alias
when you open
the client network utilities.Not sure if that will make any difference

This is the exact error message

Failed to make "serverName" a target server
Enlist into Master Server "MasterServerName" Failed(Error 14262)

Vincento|||"Vincento Harris" <wumutek@.yahoo.com> wrote in message
news:2fa13ee7.0405110339.23cb3558@.posting.google.c om...
> "Simon Hayes" <sql@.hayes.ch> wrote in message
news:<409fc26e$1_1@.news.bluewin.ch>...
> > "Vincento Harris" <wumutek@.yahoo.com> wrote in message
> > news:2fa13ee7.0405100422.632f4324@.posting.google.c om...
> > > Sql Server 7 Standard Edition
> > > My Server was renamed and the normal steps of reinstalling
> > > and running sp_dropserver and sp_addserver were followed.
> > > Everything seems to work fine but jobs from the master server.
> > > I did defect the server as a target server since it appeared as
offline
> > > anyway.
> > > > > > On trying to re establish the status of the server as a target server
> > > > Failed to make "serverName" a target server
> > > Enlist into Master Server "MasterServerName" Failed(Error 14262)
> > > > Your insight is appreciated
> > > Vincento
> > Is @.@.SERVERNAME returning the correct (new) name? Error 14262 should be
"The
> > specified %s ('%s') does not exist" - what is the full error message you
> > see? Are there any name resolution issues, ie. can both servers see each
> > other (ping.exe or NET VIEW) on the network?
> > Simon
>
> Thanks for your response.
> @.@.servername returns the right value.
> I did forget to mention that the master server is sql server 2000 and
> target server, sql server 7.
> When the master server is pinged from the client it returns packets
> with no error.
> When originating_server is selected from sysjobs it returns 'local'
> I did notice that the target server name has been added as an alias
> when you open
> the client network utilities.Not sure if that will make any difference
> This is the exact error message
> Failed to make "serverName" a target server
> Enlist into Master Server "MasterServerName" Failed(Error 14262)
> Vincento

It sounds as if everything is OK - the only thing I can think of is that the
alias in the client network utilities might still have the old server name?
Also, can you create a working linked server from the SQL2000 server to the
SQL7 one? If not, then there is probably sort of name resolution issue. But
if you can, then I have no idea what the issue is - probably time to call
Microsoft.

Simon

Cannot kill process

process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
Thanks a lot in advance for help!Urban,
Try:
KILL <SPID> WITH STATUSONLY.
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
SORRY, forgot to mention, that I tryed KILL 51, of course.
Thanks a lot in advance for help!|||Urban,
STATUSONLY will show you the estimated rollback completion. Is this a test
box, you could try stopping the SQL Server service and then starting the SQL
Server service then the SQL Server Agent service. Any errors reported in
either the SQL logs or the app event logs?
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> SORRY, forgot to mention, that I tryed KILL 51, of course.
>
> Thanks a lot in advance for help!
>|||Query analyser returns:
Status report cannot be obtained. Rollback operation for Process ID 51 is
not in progress.
Kill 51 is making the entries in tempd, but not killing the process.
"Jerry Spivey" wrote:
> Urban,
> Try:
> KILL <SPID> WITH STATUSONLY.
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> > process with status runnable in MASTER db (waiting for lock shown in mmc).
> > as consequence, SQL Server agent is not starting anymore!
> > how can I kill this process?
> > master..sysobjects shows this process as non-blocked (blocked=0).
> > in tempdb the entry is shown with SPID #51 correponding to the running
> > process
> > but it is not terminating since several days.
> >
> > Thanks a lot in advance for help!
> >
>
>|||Restart tried several times, even restatred machine.
No errors reported, Just that Process 51 has been killed, but is a true lie;-)
the process is still alive!
"Jerry Spivey" wrote:
> Urban,
> STATUSONLY will show you the estimated rollback completion. Is this a test
> box, you could try stopping the SQL Server service and then starting the SQL
> Server service then the SQL Server Agent service. Any errors reported in
> either the SQL logs or the app event logs?
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> > process with status runnable in MASTER db (waiting for lock shown in mmc).
> > as consequence, SQL Server agent is not starting anymore!
> > how can I kill this process?
> > master..sysobjects shows this process as non-blocked (blocked=0).
> > in tempdb the entry is shown with SPID #51 correponding to the running
> > process
> > but it is not terminating since several days.
> > SORRY, forgot to mention, that I tryed KILL 51, of course.
> >
> >
> > Thanks a lot in advance for help!
> >
>
>|||How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
using to show you the information?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||Thanks a lot! I'm ashamed, you're right!!!!
It is indeed my own process. I didn't recognize, because I used the run as
command for mmc with the same user that is running SQL-Server, and not my
common user.
I understand, that the prozess is not allowed to kill itself. - Strange,
that it was alive for more than 10 days.
Meanwile, SQL Server Agent was able to start, after about 10 days. This I
don't understand. But even after restarting the databse it works fine.
Propably a problem when patching the server.
Anyway, you have solved my Problem, Tibor. Thanks a lot!
"Tibor Karaszi" wrote:
> How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
> using to show you the information?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> > process with status runnable in MASTER db (waiting for lock shown in mmc).
> > as consequence, SQL Server agent is not starting anymore!
> > how can I kill this process?
> > master..sysobjects shows this process as non-blocked (blocked=0).
> > in tempdb the entry is shown with SPID #51 correponding to the running process
> > but it is not terminating since several days.
> >
> > Thanks a lot in advance for help!
> >
>

Cannot kill process

process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
Thanks a lot in advance for help!
Urban,
Try:
KILL <SPID> WITH STATUSONLY.
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>
|||process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
SORRY, forgot to mention, that I tryed KILL 51, of course.
Thanks a lot in advance for help!
|||Urban,
STATUSONLY will show you the estimated rollback completion. Is this a test
box, you could try stopping the SQL Server service and then starting the SQL
Server service then the SQL Server Agent service. Any errors reported in
either the SQL logs or the app event logs?
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> SORRY, forgot to mention, that I tryed KILL 51, of course.
>
> Thanks a lot in advance for help!
>
|||Query analyser returns:
Status report cannot be obtained. Rollback operation for Process ID 51 is
not in progress.
Kill 51 is making the entries in tempd, but not killing the process.
"Jerry Spivey" wrote:

> Urban,
> Try:
> KILL <SPID> WITH STATUSONLY.
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>
>
|||Restart tried several times, even restatred machine.
No errors reported, Just that Process 51 has been killed, but is a true lie;-)
the process is still alive!
"Jerry Spivey" wrote:

> Urban,
> STATUSONLY will show you the estimated rollback completion. Is this a test
> box, you could try stopping the SQL Server service and then starting the SQL
> Server service then the SQL Server Agent service. Any errors reported in
> either the SQL logs or the app event logs?
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
>
>
|||How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
using to show you the information?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>
|||Thanks a lot! I'm ashamed, you're right!!!!
It is indeed my own process. I didn't recognize, because I used the run as
command for mmc with the same user that is running SQL-Server, and not my
common user.
I understand, that the prozess is not allowed to kill itself. - Strange,
that it was alive for more than 10 days.
Meanwile, SQL Server Agent was able to start, after about 10 days. This I
don't understand. But even after restarting the databse it works fine.
Propably a problem when patching the server.
Anyway, you have solved my Problem, Tibor. Thanks a lot!
"Tibor Karaszi" wrote:

> How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
> using to show you the information?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>

Cannot kill process

process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running proce
ss
but it is not terminating since several days.
Thanks a lot in advance for help!Urban,
Try:
KILL <SPID> WITH STATUSONLY.
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running proce
ss
but it is not terminating since several days.
SORRY, forgot to mention, that I tryed KILL 51, of course.
Thanks a lot in advance for help!|||Urban,
STATUSONLY will show you the estimated rollback completion. Is this a test
box, you could try stopping the SQL Server service and then starting the SQL
Server service then the SQL Server Agent service. Any errors reported in
either the SQL logs or the app event logs?
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> SORRY, forgot to mention, that I tryed KILL 51, of course.
>
> Thanks a lot in advance for help!
>|||Query analyser returns:
Status report cannot be obtained. Rollback operation for Process ID 51 is
not in progress.
Kill 51 is making the entries in tempd, but not killing the process.
"Jerry Spivey" wrote:

> Urban,
> Try:
> KILL <SPID> WITH STATUSONLY.
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>
>|||Restart tried several times, even restatred machine.
No errors reported, Just that Process 51 has been killed, but is a true lie;
-)
the process is still alive!
"Jerry Spivey" wrote:

> Urban,
> STATUSONLY will show you the estimated rollback completion. Is this a tes
t
> box, you could try stopping the SQL Server service and then starting the S
QL
> Server service then the SQL Server Agent service. Any errors reported in
> either the SQL logs or the app event logs?
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
>
>|||How are you looking that this? EM, current activity? Perhaps this is your co
nnection that EM is
using to show you the information?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running pro
cess
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||Thanks a lot! I'm ashamed, you're right!!!!
It is indeed my own process. I didn't recognize, because I used the run as
command for mmc with the same user that is running SQL-Server, and not my
common user.
I understand, that the prozess is not allowed to kill itself. - Strange,
that it was alive for more than 10 days.
Meanwile, SQL Server Agent was able to start, after about 10 days. This I
don't understand. But even after restarting the databse it works fine.
Propably a problem when patching the server.
Anyway, you have solved my Problem, Tibor. Thanks a lot!
"Tibor Karaszi" wrote:

> How are you looking that this? EM, current activity? Perhaps this is your
connection that EM is
> using to show you the information?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>