Can't start SQL Server 2000

We are trying to move msdb, model and master. We added the -c -m and -T3608
to the startup parameters. When we try to restart SQL fails to start. The
error is that it cannot find master database and will not start. We cannot
get back into Enterprise Manager to reset the startup parameters. How can
we reset the parameters and, more importantly, restart SQL Server?
Thanks very much in advance.First step is to look in SQL Servers errorlog file for the reason why SQL Server won't start.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Moishe Much" <MoisheMuch@.discussions.microsoft.com> wrote in message
news:C69EDED1-03A5-4B92-B5D4-DFE80C2B1A19@.microsoft.com...
> We are trying to move msdb, model and master. We added the -c -m and -T3608
> to the startup parameters. When we try to restart SQL fails to start. The
> error is that it cannot find master database and will not start. We cannot
> get back into Enterprise Manager to reset the startup parameters. How can
> we reset the parameters and, more importantly, restart SQL Server?
> Thanks very much in advance.
>|||> We are trying to move msdb, model and master. We added the -c -m
> and -T3608
> to the startup parameters. When we try to restart SQL fails to start. The
> error is that it cannot find master database and will not start. We
> cannot
> get back into Enterprise Manager to reset the startup parameters. How
> can
> we reset the parameters and, more importantly, restart SQL Server?
The parameters for a default SQL 2000 instance are in the registry under:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer\Parameters
If it SQL Server can't find master at startup, you probably didn't specify
the correct master database path parameter.
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Moishe Much" <MoisheMuch@.discussions.microsoft.com> wrote in message
news:C69EDED1-03A5-4B92-B5D4-DFE80C2B1A19@.microsoft.com...
> We are trying to move msdb, model and master. We added the -c -m
> and -T3608
> to the startup parameters. When we try to restart SQL fails to start. The
> error is that it cannot find master database and will not start. We
> cannot
> get back into Enterprise Manager to reset the startup parameters. How
> can
> we reset the parameters and, more importantly, restart SQL Server?
> Thanks very much in advance.
>

Can't start SQL Server 2000

We are trying to move msdb, model and master. We added the -c -m and -T3608
to the startup parameters. When we try to restart SQL fails to start. The
error is that it cannot find master database and will not start. We cannot
get back into Enterprise Manager to reset the startup parameters. How can
we reset the parameters and, more importantly, restart SQL Server?
Thanks very much in advance.
> We are trying to move msdb, model and master. We added the -c -m
> and -T3608
> to the startup parameters. When we try to restart SQL fails to start. The
> error is that it cannot find master database and will not start. We
> cannot
> get back into Enterprise Manager to reset the startup parameters. How
> can
> we reset the parameters and, more importantly, restart SQL Server?
The parameters for a default SQL 2000 instance are in the registry under:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\ MSSQLServer\Parameters
If it SQL Server can't find master at startup, you probably didn't specify
the correct master database path parameter.
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Moishe Much" <MoisheMuch@.discussions.microsoft.com> wrote in message
news:C69EDED1-03A5-4B92-B5D4-DFE80C2B1A19@.microsoft.com...
> We are trying to move msdb, model and master. We added the -c -m
> and -T3608
> to the startup parameters. When we try to restart SQL fails to start. The
> error is that it cannot find master database and will not start. We
> cannot
> get back into Enterprise Manager to reset the startup parameters. How
> can
> we reset the parameters and, more importantly, restart SQL Server?
> Thanks very much in advance.
>
sql

can't rebuild msdb

Hello,
After running dbcc checkdb i'm getting:
"..54 consistency errors in database 'msdb'"
i want to rebuild the msdb database via
instmsdb.sql but i can't delete the database...
Which is the right way to do it avoiding rebuild the
master database?
Many Thank in Advance,
Galit.Galit
Do you have a last backup of msdb database?
If you do so try to restote it.
"Galit" <galitm@.ladpc.co.il> wrote in message
news:059101c3b7e1$3cd6f1b0$a301280a@.phx.gbl...
> Hello,
> After running dbcc checkdb i'm getting:
> "..54 consistency errors in database 'msdb'"
> i want to rebuild the msdb database via
> instmsdb.sql but i can't delete the database...
> Which is the right way to do it avoiding rebuild the
> master database?
> Many Thank in Advance,
> Galit.
>|||There's a section in below KB article on how you can detach the msdb database:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;224071
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Galit" <galitm@.ladpc.co.il> wrote in message news:059101c3b7e1$3cd6f1b0$a301280a@.phx.gbl...
> Hello,
> After running dbcc checkdb i'm getting:
> "..54 consistency errors in database 'msdb'"
> i want to rebuild the msdb database via
> instmsdb.sql but i can't delete the database...
> Which is the right way to do it avoiding rebuild the
> master database?
> Many Thank in Advance,
> Galit.
>|||Tibor Karaszi wrote:
> There's a section in below KB article on how you can detach the msdb
> database:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;224071
following tibors link, after you have detached msdb, if you want to use
a blank msdb, look in the msde sp3 sql2ksp3\MSDE\Setup directory. You
will see a cabinet file sqlrun.cab. From this extract the two files
msdbdata.mdfXXXXXX and msdblog.ldfXXXXXX (both of these files are named
with a string of characters -which I think is a checksum, you can
simply rename them both to their correct respective names msdbdata.mdf
and msdblog.ldfXXXXXX)
Dont overwrite your existing msdb (just in case) rename them to *.old
for them time being till you are happy.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============|||Mark,
Wouldn't running instmsdb.sql also be an option at this stage? (Instead of attaching, as there will
be a problem if the template file doesn't have the same collation as the other system databases...)
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Mark Broadbent" <no-spam-please_mark.broadbent@.virgin.net> wrote in message
news:ecPhp5BuDHA.1680@.TK2MSFTNGP12.phx.gbl...
> Tibor Karaszi wrote:
> > There's a section in below KB article on how you can detach the msdb
> > database:
> >
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;224071
> following tibors link, after you have detached msdb, if you want to use
> a blank msdb, look in the msde sp3 sql2ksp3\MSDE\Setup directory. You
> will see a cabinet file sqlrun.cab. From this extract the two files
> msdbdata.mdfXXXXXX and msdblog.ldfXXXXXX (both of these files are named
> with a string of characters -which I think is a checksum, you can
> simply rename them both to their correct respective names msdbdata.mdf
> and msdblog.ldfXXXXXX)
> Dont overwrite your existing msdb (just in case) rename them to *.old
> for them time being till you are happy.
> --
> Br,
> Mark Broadbent
> mcdba , mcse+i
> =============|||Tibor Karaszi wrote:
> Mark,
> Wouldn't running instmsdb.sql also be an option at this stage?
> (Instead of attaching, as there will be a problem if the template
> file doesn't have the same collation as the other system databases...)
Yes very good point. Been staring at my monitor for too long #:-)
--
Br,
Mark Broadbent
mcdba , mcse+i
=============|||That's what i did.
Many many thanks,
Galit.
>--Original Message--
>Tibor Karaszi wrote:
>> Mark,
>> Wouldn't running instmsdb.sql also be an option at this
stage?
>> (Instead of attaching, as there will be a problem if
the template
>> file doesn't have the same collation as the other
system databases...)
>Yes very good point. Been staring at my monitor for too
long #:-)
>--
>Br,
>Mark Broadbent
>mcdba , mcse+i
>=============>.
>

Cant modify or delete an existing job

Folks, i have rebuilt my old server machine and i've restored the MSDB over the new machine. Now when i try to edit or delete any of the jobs that come from the RESTORE; i get the following error message:

I never setup multiserver administration.
However i can create and delete new jobs.
How do i remove these older jobs.

Howdy!This happened to me once, when a machine was renamed. I think it is as simple as updating the sysjobs table to reflect the new server name (originating_server column). Make sure you have a good backup, before you do this, however.|||sorry: the error message is:
error 14274: Cannot add, update, or delete a job that originated from anMSX server.

Thanx, MCrowley. I would try this when the users are off the machine.

Howdy.|||My experience was the exact same as MCrowley's; I think I went in and hand-edited the jobs in the msdb database (through EM; it was a long time ago). You may need to set the switch to allow updating of system tables, but I don't recall that I had to do that.

Regards,

hmscott

sorry: the error message is:
error 14274: Cannot add, update, or delete a job that originated from anMSX server.

Thanx, MCrowley. I would try this when the users are off the machine.

Howdy.|||i am squared. thanx.

USE MASTER
GO
sp_configure 'allow updates' ,1
GO
RECONFIGURE WITH OVERRIDE
GO
USE MSDB
go
update sysjobs set originating_server='myserver'
GO
USE MASTER
GO
sp_configure 'allow updates' ,0
GO
RECONFIGURE WITH OVERRIDE

--HOWDY!|||Just had the same problem on a rebuilt server - the above script sorted it out.

thanks,
Paul.