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.
>
Showing posts with label master. Show all posts
Showing posts with label master. Show all posts
Tuesday, March 27, 2012
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
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
Sunday, March 25, 2012
Can't start engine
SQL Server 2000 cluster
While trying to move the master, model, etc db's I put trace flags into the
startup according to the instruction in:
http://support.microsoft.com/kb/224071
When that didn't work, I tried splitting the 3 args into 3 seperate options.
Now, I can't get in to change it back, the engine refuses to let me in:
Error:
A connection could not be established to _SERVER_
Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
in single user mode. Only one administrator can connect at a time.
I did get into the configuration settings once, though I'm not sure how, and
I thought I removed the options.How about removing "-m" from the startup parameters of your SQL Server
service?
--
Ekrem Önsoy
http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
"Jay" <nospan@.nospam.org> wrote in message
news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2000 cluster
> While trying to move the master, model, etc db's I put trace flags into
> the startup according to the instruction in:
> http://support.microsoft.com/kb/224071
> When that didn't work, I tried splitting the 3 args into 3 seperate
> options. Now, I can't get in to change it back, the engine refuses to let
> me in:
> Error:
> A connection could not be established to _SERVER_
> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
> in single user mode. Only one administrator can connect at a time.
>
> I did get into the configuration settings once, though I'm not sure how,
> and I thought I removed the options.
>|||I can't get in!
"Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
news:FEC71DAB-8E4D-49B8-97B8-386038797D8A@.microsoft.com...
> How about removing "-m" from the startup parameters of your SQL Server
> service?
> --
> Ekrem Önsoy
> http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
> MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into
>> the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to let
>> me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how,
>> and I thought I removed the options.
>|||I think I found the startup parameters in the registry (both nodes of the
cluster) in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\parameters
But I know better than to do more than look in regedit.
"Jay" <nospan@.nospam.org> wrote in message
news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2000 cluster
> While trying to move the master, model, etc db's I put trace flags into
> the startup according to the instruction in:
> http://support.microsoft.com/kb/224071
> When that didn't work, I tried splitting the 3 args into 3 seperate
> options. Now, I can't get in to change it back, the engine refuses to let
> me in:
> Error:
> A connection could not be established to _SERVER_
> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
> in single user mode. Only one administrator can connect at a time.
>
> I did get into the configuration settings once, though I'm not sure how,
> and I thought I removed the options.
>|||With the Windows admin, I tried to remove the -c -m -T3608 from the
registry. The primary node in the cluster refused to let me remove the
parameter and the secondary allowed the delete. When we restarted the
server, it was still in single user and a refresh in regedit on the
secondary showed the deleted options were back.
"Jay" <nospan@.nospam.org> wrote in message
news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2000 cluster
> While trying to move the master, model, etc db's I put trace flags into
> the startup according to the instruction in:
> http://support.microsoft.com/kb/224071
> When that didn't work, I tried splitting the 3 args into 3 seperate
> options. Now, I can't get in to change it back, the engine refuses to let
> me in:
> Error:
> A connection could not be established to _SERVER_
> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
> in single user mode. Only one administrator can connect at a time.
>
> I did get into the configuration settings once, though I'm not sure how,
> and I thought I removed the options.
>|||Stop other services which connect to SQL Server. SQL Server Agent for
example...
Then you'd be the one who connects to SQL Server and then you'd be able to
change the setting?
--
Ekrem Önsoy
http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
"Jay" <nospan@.nospam.org> wrote in message
news:OowRKaaHIHA.4808@.TK2MSFTNGP05.phx.gbl...
>I can't get in!
> "Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
> news:FEC71DAB-8E4D-49B8-97B8-386038797D8A@.microsoft.com...
>> How about removing "-m" from the startup parameters of your SQL Server
>> service?
>> --
>> Ekrem Önsoy
>> http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
>> MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
>>
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into
>> the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to
>> let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
>> is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how,
>> and I thought I removed the options.
>>
>|||I did stop everything else. listed in the SQL Server Service Manager: SQL
agent, DTC, Full Text search and sonething else I don't recall right now.
Unless it's got something to do with the Cluster manager? I know that
sub-system has some control over SQL Server, but I'm really unfamilar with
it, the Windows admin set it up.
"Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
news:E4CA655D-3777-4AAA-BB8F-F305A064816B@.microsoft.com...
> Stop other services which connect to SQL Server. SQL Server Agent for
> example...
> Then you'd be the one who connects to SQL Server and then you'd be able to
> change the setting?
> --
> Ekrem Önsoy
> http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
> MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:OowRKaaHIHA.4808@.TK2MSFTNGP05.phx.gbl...
>>I can't get in!
>> "Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
>> news:FEC71DAB-8E4D-49B8-97B8-386038797D8A@.microsoft.com...
>> How about removing "-m" from the startup parameters of your SQL Server
>> service?
>> --
>> Ekrem Önsoy
>> http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
>> MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
>>
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into
>> the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to
>> let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
>> is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure
>> how, and I thought I removed the options.
>>
>>
>|||Still in need of help.
"Jay" <nospan@.nospam.org> wrote in message
news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2000 cluster
> While trying to move the master, model, etc db's I put trace flags into
> the startup according to the instruction in:
> http://support.microsoft.com/kb/224071
> When that didn't work, I tried splitting the 3 args into 3 seperate
> options. Now, I can't get in to change it back, the engine refuses to let
> me in:
> Error:
> A connection could not be established to _SERVER_
> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
> in single user mode. Only one administrator can connect at a time.
>
> I did get into the configuration settings once, though I'm not sure how,
> and I thought I removed the options.
>|||Single user mode is the -m startup switch. Perhaps you removed that option in the registry from one
of the nodes but no the other. I would connect using regedit and verify the setting for all nodes...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jay" <nospan@.nospam.org> wrote in message news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
> Still in need of help.
> "Jay" <nospan@.nospam.org> wrote in message news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into the startup according to
>> the instruction in: http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate options. Now, I can't get in
>> to change it back, the engine refuses to let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how, and I thought I removed
>> the options.
>|||If regedit allows me to change it, am I changing the registry in the correct
localtion? Sounds like it.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
> Single user mode is the -m startup switch. Perhaps you removed that option
> in the registry from one of the nodes but no the other. I would connect
> using regedit and verify the setting for all nodes...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
>> Still in need of help.
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into
>> the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to
>> let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
>> is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how,
>> and I thought I removed the options.
>>
>|||I'm not sure you want to *change* it using regedit. My gut feeling was to check using regedit to
verify if this was the issue. I would assume that Enterprise Manager would change it for you on all
nodes. Or possibly the cluster support in Windows will take care of that for you (regardless of what
tool you use to make that change). I'd try EM first, and if that doesn't help, use regedit, and
verify all nodes...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jay" <nospan@.nospam.org> wrote in message news:OqUUt58HIHA.4712@.TK2MSFTNGP04.phx.gbl...
> If regedit allows me to change it, am I changing the registry in the correct localtion? Sounds
> like it.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
>> Single user mode is the -m startup switch. Perhaps you removed that option in the registry from
>> one of the nodes but no the other. I would connect using regedit and verify the setting for all
>> nodes...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Jay" <nospan@.nospam.org> wrote in message news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
>> Still in need of help.
>> "Jay" <nospan@.nospam.org> wrote in message news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into the startup according
>> to the instruction in: http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate options. Now, I can't get
>> in to change it back, the engine refuses to let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how, and I thought I
>> removed the options.
>>
>>
>|||OK Tibor, regedit did allow me to remove just the -m flag. I was then able
to get into properties and remove the other two. The genesis of my issue was
that I could not get into the properties in the first place. I would guess
that this is VERY unusual as both you and Ekrem continue to suggest I change
the options via properties\startup options, despite my continuing to repeat
that I couldn't get in.
I'm OK now, thanks Tibor and Ekrem. I suppose I can be a bit of a pill when
stressed.
The part that is very disturbing is that upon researching the command line
options provided and the experience applying them, there are three mistakes
in the Microsoft kb article.
1) The arguments are presented as if you put them all in, one entry when you
need to do each one separately.
2) -T3608 should be /T3608
3) -m is not necessary in SQL Server 2000 (and is what caused so much of the
problem)
The other two Admins (and our manager, who used to be an Admin) got a good
laugh at me for the faith I had in the Microsoft kb article. It seems that
they have gotten bad instructions many times before.
Last, kicking and screaming, I've now learned a little about the Windows
registry.
Thanks,
Jay
PS. I have now moved the model database and will do the others shortly.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
> Single user mode is the -m startup switch. Perhaps you removed that option
> in the registry from one of the nodes but no the other. I would connect
> using regedit and verify the setting for all nodes...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
>> Still in need of help.
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into
>> the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to
>> let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
>> is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how,
>> and I thought I removed the options.
>>
>|||> I would guess that this is VERY unusual as both you and Ekrem continue to suggest I change the
> options via properties\startup options, despite my continuing to repeat that I couldn't get in.
Sorry, I missed that part...
> The part that is very disturbing is that upon researching the command line options provided and
> the experience applying them, there are three mistakes in the Microsoft kb article.
Was it KB 224071?
> 1) The arguments are presented as if you put them all in, one entry when you need to do each one
> separately.
Perhaps the article assumes that you use EM and EM represents the arguments as one on each line,
while you modified the registry directly which represents the information differently? I guess the
KB could have a few words about the difference between EM's representation and how it looks like in
regedit...
> 2) -T3608 should be /T3608
My experience is that dash or slash makes no difference for the various SQL Server exe files that
reads command line options...
A tip: Make sure that you managed to get the proper dbid for model (check sysdatabases). I believe
it need to be 3. As I remember, SQL Server uses the dbid for the model database, not the name of the
database. Which means that you will get whacky behavior when you create new databases if model isn't
3...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jay" <nospan@.nospam.org> wrote in message news:eulAKH9HIHA.4296@.TK2MSFTNGP04.phx.gbl...
> OK Tibor, regedit did allow me to remove just the -m flag. I was then able to get into properties
> and remove the other two. The genesis of my issue was that I could not get into the properties in
> the first place. I would guess that this is VERY unusual as both you and Ekrem continue to suggest
> I change the options via properties\startup options, despite my continuing to repeat that I
> couldn't get in.
> I'm OK now, thanks Tibor and Ekrem. I suppose I can be a bit of a pill when stressed.
> The part that is very disturbing is that upon researching the command line options provided and
> the experience applying them, there are three mistakes in the Microsoft kb article.
> 1) The arguments are presented as if you put them all in, one entry when you need to do each one
> separately.
> 2) -T3608 should be /T3608
> 3) -m is not necessary in SQL Server 2000 (and is what caused so much of the problem)
> The other two Admins (and our manager, who used to be an Admin) got a good laugh at me for the
> faith I had in the Microsoft kb article. It seems that they have gotten bad instructions many
> times before.
> Last, kicking and screaming, I've now learned a little about the Windows registry.
> Thanks,
> Jay
> PS. I have now moved the model database and will do the others shortly.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
>> Single user mode is the -m startup switch. Perhaps you removed that option in the registry from
>> one of the nodes but no the other. I would connect using regedit and verify the setting for all
>> nodes...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Jay" <nospan@.nospam.org> wrote in message news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
>> Still in need of help.
>> "Jay" <nospan@.nospam.org> wrote in message news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into the startup according
>> to the instruction in: http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate options. Now, I can't get
>> in to change it back, the engine refuses to let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how, and I thought I
>> removed the options.
>>
>>
>|||> Was it KB 224071?
yes.
...
> A tip: Make sure that you managed to get the proper dbid for model (check
> sysdatabases). I believe it need to be 3. As I remember, SQL Server uses
> the dbid for the model database, not the name of the database. Which means
> that you will get whacky behavior when you create new databases if model
> isn't 3...
Yes, model is dbid 3.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:eulAKH9HIHA.4296@.TK2MSFTNGP04.phx.gbl...
>> OK Tibor, regedit did allow me to remove just the -m flag. I was then
>> able to get into properties and remove the other two. The genesis of my
>> issue was that I could not get into the properties in the first place. I
>> would guess that this is VERY unusual as both you and Ekrem continue to
>> suggest I change the options via properties\startup options, despite my
>> continuing to repeat that I couldn't get in.
>> I'm OK now, thanks Tibor and Ekrem. I suppose I can be a bit of a pill
>> when stressed.
>> The part that is very disturbing is that upon researching the command
>> line options provided and the experience applying them, there are three
>> mistakes in the Microsoft kb article.
>> 1) The arguments are presented as if you put them all in, one entry when
>> you need to do each one separately.
>> 2) -T3608 should be /T3608
>> 3) -m is not necessary in SQL Server 2000 (and is what caused so much of
>> the problem)
>> The other two Admins (and our manager, who used to be an Admin) got a
>> good laugh at me for the faith I had in the Microsoft kb article. It
>> seems that they have gotten bad instructions many times before.
>> Last, kicking and screaming, I've now learned a little about the Windows
>> registry.
>> Thanks,
>> Jay
>> PS. I have now moved the model database and will do the others shortly.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
>> Single user mode is the -m startup switch. Perhaps you removed that
>> option in the registry from one of the nodes but no the other. I would
>> connect using regedit and verify the setting for all nodes...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
>> Still in need of help.
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags
>> into the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to
>> let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
>> is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure
>> how, and I thought I removed the options.
>>
>>
>>
>|||Just wanted to say thanks to all who contributed to this thread. I ran into
this exact same issue today and was able to fix it the same way Jay
ultimately did. You've saved me potentially countless hours of trial and
error. Many thanks!
"Jay" wrote:
> > Was it KB 224071?
> yes.
> ...
> >
> > A tip: Make sure that you managed to get the proper dbid for model (check
> > sysdatabases). I believe it need to be 3. As I remember, SQL Server uses
> > the dbid for the model database, not the name of the database. Which means
> > that you will get whacky behavior when you create new databases if model
> > isn't 3...
> Yes, model is dbid 3.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://sqlblog.com/blogs/tibor_karaszi
> >
> >
> > "Jay" <nospan@.nospam.org> wrote in message
> > news:eulAKH9HIHA.4296@.TK2MSFTNGP04.phx.gbl...
> >> OK Tibor, regedit did allow me to remove just the -m flag. I was then
> >> able to get into properties and remove the other two. The genesis of my
> >> issue was that I could not get into the properties in the first place. I
> >> would guess that this is VERY unusual as both you and Ekrem continue to
> >> suggest I change the options via properties\startup options, despite my
> >> continuing to repeat that I couldn't get in.
> >>
> >> I'm OK now, thanks Tibor and Ekrem. I suppose I can be a bit of a pill
> >> when stressed.
> >>
> >> The part that is very disturbing is that upon researching the command
> >> line options provided and the experience applying them, there are three
> >> mistakes in the Microsoft kb article.
> >>
> >> 1) The arguments are presented as if you put them all in, one entry when
> >> you need to do each one separately.
> >> 2) -T3608 should be /T3608
> >> 3) -m is not necessary in SQL Server 2000 (and is what caused so much of
> >> the problem)
> >>
> >> The other two Admins (and our manager, who used to be an Admin) got a
> >> good laugh at me for the faith I had in the Microsoft kb article. It
> >> seems that they have gotten bad instructions many times before.
> >>
> >> Last, kicking and screaming, I've now learned a little about the Windows
> >> registry.
> >>
> >> Thanks,
> >> Jay
> >>
> >> PS. I have now moved the model database and will do the others shortly.
> >>
> >> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> >> in message news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
> >> Single user mode is the -m startup switch. Perhaps you removed that
> >> option in the registry from one of the nodes but no the other. I would
> >> connect using regedit and verify the setting for all nodes...
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "Jay" <nospan@.nospam.org> wrote in message
> >> news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
> >> Still in need of help.
> >>
> >> "Jay" <nospan@.nospam.org> wrote in message
> >> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
> >> SQL Server 2000 cluster
> >>
> >> While trying to move the master, model, etc db's I put trace flags
> >> into the startup according to the instruction in:
> >> http://support.microsoft.com/kb/224071
> >>
> >> When that didn't work, I tried splitting the 3 args into 3 seperate
> >> options. Now, I can't get in to change it back, the engine refuses to
> >> let me in:
> >>
> >> Error:
> >>
> >> A connection could not be established to _SERVER_
> >> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
> >> is
> >> in single user mode. Only one administrator can connect at a time.
> >>
> >>
> >> I did get into the configuration settings once, though I'm not sure
> >> how, and I thought I removed the options.
> >>
> >>
> >>
> >>
> >>
> >>
> >
>
>
While trying to move the master, model, etc db's I put trace flags into the
startup according to the instruction in:
http://support.microsoft.com/kb/224071
When that didn't work, I tried splitting the 3 args into 3 seperate options.
Now, I can't get in to change it back, the engine refuses to let me in:
Error:
A connection could not be established to _SERVER_
Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
in single user mode. Only one administrator can connect at a time.
I did get into the configuration settings once, though I'm not sure how, and
I thought I removed the options.How about removing "-m" from the startup parameters of your SQL Server
service?
--
Ekrem Önsoy
http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
"Jay" <nospan@.nospam.org> wrote in message
news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2000 cluster
> While trying to move the master, model, etc db's I put trace flags into
> the startup according to the instruction in:
> http://support.microsoft.com/kb/224071
> When that didn't work, I tried splitting the 3 args into 3 seperate
> options. Now, I can't get in to change it back, the engine refuses to let
> me in:
> Error:
> A connection could not be established to _SERVER_
> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
> in single user mode. Only one administrator can connect at a time.
>
> I did get into the configuration settings once, though I'm not sure how,
> and I thought I removed the options.
>|||I can't get in!
"Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
news:FEC71DAB-8E4D-49B8-97B8-386038797D8A@.microsoft.com...
> How about removing "-m" from the startup parameters of your SQL Server
> service?
> --
> Ekrem Önsoy
> http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
> MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into
>> the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to let
>> me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how,
>> and I thought I removed the options.
>|||I think I found the startup parameters in the registry (both nodes of the
cluster) in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\parameters
But I know better than to do more than look in regedit.
"Jay" <nospan@.nospam.org> wrote in message
news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2000 cluster
> While trying to move the master, model, etc db's I put trace flags into
> the startup according to the instruction in:
> http://support.microsoft.com/kb/224071
> When that didn't work, I tried splitting the 3 args into 3 seperate
> options. Now, I can't get in to change it back, the engine refuses to let
> me in:
> Error:
> A connection could not be established to _SERVER_
> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
> in single user mode. Only one administrator can connect at a time.
>
> I did get into the configuration settings once, though I'm not sure how,
> and I thought I removed the options.
>|||With the Windows admin, I tried to remove the -c -m -T3608 from the
registry. The primary node in the cluster refused to let me remove the
parameter and the secondary allowed the delete. When we restarted the
server, it was still in single user and a refresh in regedit on the
secondary showed the deleted options were back.
"Jay" <nospan@.nospam.org> wrote in message
news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2000 cluster
> While trying to move the master, model, etc db's I put trace flags into
> the startup according to the instruction in:
> http://support.microsoft.com/kb/224071
> When that didn't work, I tried splitting the 3 args into 3 seperate
> options. Now, I can't get in to change it back, the engine refuses to let
> me in:
> Error:
> A connection could not be established to _SERVER_
> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
> in single user mode. Only one administrator can connect at a time.
>
> I did get into the configuration settings once, though I'm not sure how,
> and I thought I removed the options.
>|||Stop other services which connect to SQL Server. SQL Server Agent for
example...
Then you'd be the one who connects to SQL Server and then you'd be able to
change the setting?
--
Ekrem Önsoy
http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
"Jay" <nospan@.nospam.org> wrote in message
news:OowRKaaHIHA.4808@.TK2MSFTNGP05.phx.gbl...
>I can't get in!
> "Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
> news:FEC71DAB-8E4D-49B8-97B8-386038797D8A@.microsoft.com...
>> How about removing "-m" from the startup parameters of your SQL Server
>> service?
>> --
>> Ekrem Önsoy
>> http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
>> MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
>>
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into
>> the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to
>> let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
>> is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how,
>> and I thought I removed the options.
>>
>|||I did stop everything else. listed in the SQL Server Service Manager: SQL
agent, DTC, Full Text search and sonething else I don't recall right now.
Unless it's got something to do with the Cluster manager? I know that
sub-system has some control over SQL Server, but I'm really unfamilar with
it, the Windows admin set it up.
"Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
news:E4CA655D-3777-4AAA-BB8F-F305A064816B@.microsoft.com...
> Stop other services which connect to SQL Server. SQL Server Agent for
> example...
> Then you'd be the one who connects to SQL Server and then you'd be able to
> change the setting?
> --
> Ekrem Önsoy
> http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
> MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:OowRKaaHIHA.4808@.TK2MSFTNGP05.phx.gbl...
>>I can't get in!
>> "Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
>> news:FEC71DAB-8E4D-49B8-97B8-386038797D8A@.microsoft.com...
>> How about removing "-m" from the startup parameters of your SQL Server
>> service?
>> --
>> Ekrem Önsoy
>> http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
>> MCBDA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
>>
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into
>> the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to
>> let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
>> is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure
>> how, and I thought I removed the options.
>>
>>
>|||Still in need of help.
"Jay" <nospan@.nospam.org> wrote in message
news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2000 cluster
> While trying to move the master, model, etc db's I put trace flags into
> the startup according to the instruction in:
> http://support.microsoft.com/kb/224071
> When that didn't work, I tried splitting the 3 args into 3 seperate
> options. Now, I can't get in to change it back, the engine refuses to let
> me in:
> Error:
> A connection could not be established to _SERVER_
> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
> in single user mode. Only one administrator can connect at a time.
>
> I did get into the configuration settings once, though I'm not sure how,
> and I thought I removed the options.
>|||Single user mode is the -m startup switch. Perhaps you removed that option in the registry from one
of the nodes but no the other. I would connect using regedit and verify the setting for all nodes...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jay" <nospan@.nospam.org> wrote in message news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
> Still in need of help.
> "Jay" <nospan@.nospam.org> wrote in message news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into the startup according to
>> the instruction in: http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate options. Now, I can't get in
>> to change it back, the engine refuses to let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how, and I thought I removed
>> the options.
>|||If regedit allows me to change it, am I changing the registry in the correct
localtion? Sounds like it.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
> Single user mode is the -m startup switch. Perhaps you removed that option
> in the registry from one of the nodes but no the other. I would connect
> using regedit and verify the setting for all nodes...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
>> Still in need of help.
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into
>> the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to
>> let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
>> is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how,
>> and I thought I removed the options.
>>
>|||I'm not sure you want to *change* it using regedit. My gut feeling was to check using regedit to
verify if this was the issue. I would assume that Enterprise Manager would change it for you on all
nodes. Or possibly the cluster support in Windows will take care of that for you (regardless of what
tool you use to make that change). I'd try EM first, and if that doesn't help, use regedit, and
verify all nodes...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jay" <nospan@.nospam.org> wrote in message news:OqUUt58HIHA.4712@.TK2MSFTNGP04.phx.gbl...
> If regedit allows me to change it, am I changing the registry in the correct localtion? Sounds
> like it.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
>> Single user mode is the -m startup switch. Perhaps you removed that option in the registry from
>> one of the nodes but no the other. I would connect using regedit and verify the setting for all
>> nodes...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Jay" <nospan@.nospam.org> wrote in message news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
>> Still in need of help.
>> "Jay" <nospan@.nospam.org> wrote in message news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into the startup according
>> to the instruction in: http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate options. Now, I can't get
>> in to change it back, the engine refuses to let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how, and I thought I
>> removed the options.
>>
>>
>|||OK Tibor, regedit did allow me to remove just the -m flag. I was then able
to get into properties and remove the other two. The genesis of my issue was
that I could not get into the properties in the first place. I would guess
that this is VERY unusual as both you and Ekrem continue to suggest I change
the options via properties\startup options, despite my continuing to repeat
that I couldn't get in.
I'm OK now, thanks Tibor and Ekrem. I suppose I can be a bit of a pill when
stressed.
The part that is very disturbing is that upon researching the command line
options provided and the experience applying them, there are three mistakes
in the Microsoft kb article.
1) The arguments are presented as if you put them all in, one entry when you
need to do each one separately.
2) -T3608 should be /T3608
3) -m is not necessary in SQL Server 2000 (and is what caused so much of the
problem)
The other two Admins (and our manager, who used to be an Admin) got a good
laugh at me for the faith I had in the Microsoft kb article. It seems that
they have gotten bad instructions many times before.
Last, kicking and screaming, I've now learned a little about the Windows
registry.
Thanks,
Jay
PS. I have now moved the model database and will do the others shortly.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
> Single user mode is the -m startup switch. Perhaps you removed that option
> in the registry from one of the nodes but no the other. I would connect
> using regedit and verify the setting for all nodes...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
>> Still in need of help.
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into
>> the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to
>> let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
>> is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how,
>> and I thought I removed the options.
>>
>|||> I would guess that this is VERY unusual as both you and Ekrem continue to suggest I change the
> options via properties\startup options, despite my continuing to repeat that I couldn't get in.
Sorry, I missed that part...
> The part that is very disturbing is that upon researching the command line options provided and
> the experience applying them, there are three mistakes in the Microsoft kb article.
Was it KB 224071?
> 1) The arguments are presented as if you put them all in, one entry when you need to do each one
> separately.
Perhaps the article assumes that you use EM and EM represents the arguments as one on each line,
while you modified the registry directly which represents the information differently? I guess the
KB could have a few words about the difference between EM's representation and how it looks like in
regedit...
> 2) -T3608 should be /T3608
My experience is that dash or slash makes no difference for the various SQL Server exe files that
reads command line options...
A tip: Make sure that you managed to get the proper dbid for model (check sysdatabases). I believe
it need to be 3. As I remember, SQL Server uses the dbid for the model database, not the name of the
database. Which means that you will get whacky behavior when you create new databases if model isn't
3...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jay" <nospan@.nospam.org> wrote in message news:eulAKH9HIHA.4296@.TK2MSFTNGP04.phx.gbl...
> OK Tibor, regedit did allow me to remove just the -m flag. I was then able to get into properties
> and remove the other two. The genesis of my issue was that I could not get into the properties in
> the first place. I would guess that this is VERY unusual as both you and Ekrem continue to suggest
> I change the options via properties\startup options, despite my continuing to repeat that I
> couldn't get in.
> I'm OK now, thanks Tibor and Ekrem. I suppose I can be a bit of a pill when stressed.
> The part that is very disturbing is that upon researching the command line options provided and
> the experience applying them, there are three mistakes in the Microsoft kb article.
> 1) The arguments are presented as if you put them all in, one entry when you need to do each one
> separately.
> 2) -T3608 should be /T3608
> 3) -m is not necessary in SQL Server 2000 (and is what caused so much of the problem)
> The other two Admins (and our manager, who used to be an Admin) got a good laugh at me for the
> faith I had in the Microsoft kb article. It seems that they have gotten bad instructions many
> times before.
> Last, kicking and screaming, I've now learned a little about the Windows registry.
> Thanks,
> Jay
> PS. I have now moved the model database and will do the others shortly.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
>> Single user mode is the -m startup switch. Perhaps you removed that option in the registry from
>> one of the nodes but no the other. I would connect using regedit and verify the setting for all
>> nodes...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Jay" <nospan@.nospam.org> wrote in message news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
>> Still in need of help.
>> "Jay" <nospan@.nospam.org> wrote in message news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags into the startup according
>> to the instruction in: http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate options. Now, I can't get
>> in to change it back, the engine refuses to let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure how, and I thought I
>> removed the options.
>>
>>
>|||> Was it KB 224071?
yes.
...
> A tip: Make sure that you managed to get the proper dbid for model (check
> sysdatabases). I believe it need to be 3. As I remember, SQL Server uses
> the dbid for the model database, not the name of the database. Which means
> that you will get whacky behavior when you create new databases if model
> isn't 3...
Yes, model is dbid 3.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:eulAKH9HIHA.4296@.TK2MSFTNGP04.phx.gbl...
>> OK Tibor, regedit did allow me to remove just the -m flag. I was then
>> able to get into properties and remove the other two. The genesis of my
>> issue was that I could not get into the properties in the first place. I
>> would guess that this is VERY unusual as both you and Ekrem continue to
>> suggest I change the options via properties\startup options, despite my
>> continuing to repeat that I couldn't get in.
>> I'm OK now, thanks Tibor and Ekrem. I suppose I can be a bit of a pill
>> when stressed.
>> The part that is very disturbing is that upon researching the command
>> line options provided and the experience applying them, there are three
>> mistakes in the Microsoft kb article.
>> 1) The arguments are presented as if you put them all in, one entry when
>> you need to do each one separately.
>> 2) -T3608 should be /T3608
>> 3) -m is not necessary in SQL Server 2000 (and is what caused so much of
>> the problem)
>> The other two Admins (and our manager, who used to be an Admin) got a
>> good laugh at me for the faith I had in the Microsoft kb article. It
>> seems that they have gotten bad instructions many times before.
>> Last, kicking and screaming, I've now learned a little about the Windows
>> registry.
>> Thanks,
>> Jay
>> PS. I have now moved the model database and will do the others shortly.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
>> Single user mode is the -m startup switch. Perhaps you removed that
>> option in the registry from one of the nodes but no the other. I would
>> connect using regedit and verify the setting for all nodes...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
>> Still in need of help.
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> SQL Server 2000 cluster
>> While trying to move the master, model, etc db's I put trace flags
>> into the startup according to the instruction in:
>> http://support.microsoft.com/kb/224071
>> When that didn't work, I tried splitting the 3 args into 3 seperate
>> options. Now, I can't get in to change it back, the engine refuses to
>> let me in:
>> Error:
>> A connection could not be established to _SERVER_
>> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
>> is
>> in single user mode. Only one administrator can connect at a time.
>>
>> I did get into the configuration settings once, though I'm not sure
>> how, and I thought I removed the options.
>>
>>
>>
>|||Just wanted to say thanks to all who contributed to this thread. I ran into
this exact same issue today and was able to fix it the same way Jay
ultimately did. You've saved me potentially countless hours of trial and
error. Many thanks!
"Jay" wrote:
> > Was it KB 224071?
> yes.
> ...
> >
> > A tip: Make sure that you managed to get the proper dbid for model (check
> > sysdatabases). I believe it need to be 3. As I remember, SQL Server uses
> > the dbid for the model database, not the name of the database. Which means
> > that you will get whacky behavior when you create new databases if model
> > isn't 3...
> Yes, model is dbid 3.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://sqlblog.com/blogs/tibor_karaszi
> >
> >
> > "Jay" <nospan@.nospam.org> wrote in message
> > news:eulAKH9HIHA.4296@.TK2MSFTNGP04.phx.gbl...
> >> OK Tibor, regedit did allow me to remove just the -m flag. I was then
> >> able to get into properties and remove the other two. The genesis of my
> >> issue was that I could not get into the properties in the first place. I
> >> would guess that this is VERY unusual as both you and Ekrem continue to
> >> suggest I change the options via properties\startup options, despite my
> >> continuing to repeat that I couldn't get in.
> >>
> >> I'm OK now, thanks Tibor and Ekrem. I suppose I can be a bit of a pill
> >> when stressed.
> >>
> >> The part that is very disturbing is that upon researching the command
> >> line options provided and the experience applying them, there are three
> >> mistakes in the Microsoft kb article.
> >>
> >> 1) The arguments are presented as if you put them all in, one entry when
> >> you need to do each one separately.
> >> 2) -T3608 should be /T3608
> >> 3) -m is not necessary in SQL Server 2000 (and is what caused so much of
> >> the problem)
> >>
> >> The other two Admins (and our manager, who used to be an Admin) got a
> >> good laugh at me for the faith I had in the Microsoft kb article. It
> >> seems that they have gotten bad instructions many times before.
> >>
> >> Last, kicking and screaming, I've now learned a little about the Windows
> >> registry.
> >>
> >> Thanks,
> >> Jay
> >>
> >> PS. I have now moved the model database and will do the others shortly.
> >>
> >> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> >> in message news:3F379085-1621-4BE3-BC32-93A3A921566D@.microsoft.com...
> >> Single user mode is the -m startup switch. Perhaps you removed that
> >> option in the registry from one of the nodes but no the other. I would
> >> connect using regedit and verify the setting for all nodes...
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "Jay" <nospan@.nospam.org> wrote in message
> >> news:%23ZIDnu8HIHA.3956@.TK2MSFTNGP04.phx.gbl...
> >> Still in need of help.
> >>
> >> "Jay" <nospan@.nospam.org> wrote in message
> >> news:uvHnERaHIHA.4956@.TK2MSFTNGP06.phx.gbl...
> >> SQL Server 2000 cluster
> >>
> >> While trying to move the master, model, etc db's I put trace flags
> >> into the startup according to the instruction in:
> >> http://support.microsoft.com/kb/224071
> >>
> >> When that didn't work, I tried splitting the 3 args into 3 seperate
> >> options. Now, I can't get in to change it back, the engine refuses to
> >> let me in:
> >>
> >> Error:
> >>
> >> A connection could not be established to _SERVER_
> >> Reason: Login failed for user 'DOMAIN\USERNAME'. Reason: Server
> >> is
> >> in single user mode. Only one administrator can connect at a time.
> >>
> >>
> >> I did get into the configuration settings once, though I'm not sure
> >> how, and I thought I removed the options.
> >>
> >>
> >>
> >>
> >>
> >>
> >
>
>
Thursday, March 22, 2012
Can't Send mail using MultiServer Admin
Hi,
I have a Master server which I want to use to handle jobs for our Production Servers. the master server has Outlook installed but the Target servers do not. I need to find a way to get the job to send a mail confirming whether the job has succeeded or failed but without having a mail client installed on any of the target servers. Currently the actual backups do run but the send mail section fails with the following error.
xp_sendmail: Procedure expects parameter @.user, which was not supplied. [SQLSTATE 42000] (Error 17985). The step failed.
I can't see any parameter @.User on BOL, it may be that using sendmail is not the best way foward here
Any ideas anyone?
Hi, I had this problem when I migrated my server to new hardware. I had not yet set up the Outlook account which SQL Server uses to send the mail on the new hardware. You have to login to your box with the same account that you use for the SQL Server startup service and create an outlook profile on that account before you can send the mail using xp_sendmail. Hope this helps!|||Hi Jason,
Thanks for the response, we don't want to install an Outlook client on the target servers which was cauing the problem, I managed to resolve the issue by using smtp instead
Regards
Lisa
|||how do you set up the smtp on your target server? I'd like to do the same but have not any idea, I am a newbie in both SQL and network. Thanks.
|||Try using http://www.sqldev.net/xp/sp_smtp_sendmail.htm
Can't Send mail using MultiServer Admin
Hi,
I have a Master server which I want to use to handle jobs for our Production Servers. the master server has Outlook installed but the Target servers do not. I need to find a way to get the job to send a mail confirming whether the job has succeeded or failed but without having a mail client installed on any of the target servers. Currently the actual backups do run but the send mail section fails with the following error.
xp_sendmail: Procedure expects parameter @.user, which was not supplied. [SQLSTATE 42000] (Error 17985). The step failed.
I can't see any parameter @.User on BOL, it may be that using sendmail is not the best way foward here
Any ideas anyone?
Hi, I had this problem when I migrated my server to new hardware. I had not yet set up the Outlook account which SQL Server uses to send the mail on the new hardware. You have to login to your box with the same account that you use for the SQL Server startup service and create an outlook profile on that account before you can send the mail using xp_sendmail. Hope this helps!|||Hi Jason,
Thanks for the response, we don't want to install an Outlook client on the target servers which was cauing the problem, I managed to resolve the issue by using smtp instead
Regards
Lisa
|||how do you set up the smtp on your target server? I'd like to do the same but have not any idea, I am a newbie in both SQL and network. Thanks.
|||Try using http://www.sqldev.net/xp/sp_smtp_sendmail.htm
Can't Send mail using MultiServer Admin
Hi,
I have a Master server which I want to use to handle jobs for our Production Servers. the master server has Outlook installed but the Target servers do not. I need to find a way to get the job to send a mail confirming whether the job has succeeded or failed but without having a mail client installed on any of the target servers. Currently the actual backups do run but the send mail section fails with the following error.
xp_sendmail: Procedure expects parameter @.user, which was not supplied. [SQLSTATE 42000] (Error 17985). The step failed.
I can't see any parameter @.User on BOL, it may be that using sendmail is not the best way foward here
Any ideas anyone?
Hi, I had this problem when I migrated my server to new hardware. I had not yet set up the Outlook account which SQL Server uses to send the mail on the new hardware. You have to login to your box with the same account that you use for the SQL Server startup service and create an outlook profile on that account before you can send the mail using xp_sendmail. Hope this helps!|||Hi Jason,
Thanks for the response, we don't want to install an Outlook client on the target servers which was cauing the problem, I managed to resolve the issue by using smtp instead
Regards
Lisa
|||how do you set up the smtp on your target server? I'd like to do the same but have not any idea, I am a newbie in both SQL and network. Thanks.
|||Try using http://www.sqldev.net/xp/sp_smtp_sendmail.htm
Thursday, March 8, 2012
Can't restore master db!
Hi:
I've got a problem that's causing me headaches! I'm using Veritas Backup Exec to perform my db backups. I've just
recently taken over the DBA responsibilities and one of the first things I've wanted to do is test those backups since
we've never had occassion to use the backups. I have a test system that I'm using and have it configured exactly as the
production system.
After installing MS SQL Server 7 putting on SP4 and all the security patches I try to restore all the databases. I can
get all my databases restored except the master db that contains all my security info. I keep getting the message
"must be in single user mode". I've tried to set the master db into single user mode and there's just no way to do it!!
I've tried using the EM and the sp_dboption. Without that master db restored I'm in deep doo-doo!
Any ideas how I can handle this? Any help/suggestions is greatly appreciated.
TIA
Cathy
SQL Server 7( SP4), NT4.0
Hi,
To restore the master database you have start the SQL server itself in
Single user mode.
1. Stop the MSSQL server and sql agent service
2. Go to command prompt and execute below command,.
sqlservr.exe -c -m
3. Login to sql server using query analyzer and retore the master database.
4. After the restore .. go to old comamnd prompt and press CONTRL and C to
close the old session
5. Go to control panel and start the MSSQL server and Sql agent service.
Note:
I recommend you to restore the master database first followed with other
databases.
Thanks
Hari
MCDBA
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this? Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0
|||This method will work. I think Hari copied and pasted the answer directly
from Books Online! I would have provided exactly the same answer. I
probably would have also pointed you at Books Online (within your SQL Server
program group). BACKUP and RESTORE information and examples can be found
there. Knowing how to restore the data that you are backing up is
important. Cathy, you are smart to be doing your research now (instead of
when the entire company is waiting for you to restore the data).
Keith
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> To restore the master database you have start the SQL server itself in
> Single user mode.
> 1. Stop the MSSQL server and sql agent service
> 2. Go to command prompt and execute below command,.
> sqlservr.exe -c -m
> 3. Login to sql server using query analyzer and retore the master
database.
> 4. After the restore .. go to old comamnd prompt and press CONTRL and C to
> close the old session
> 5. Go to control panel and start the MSSQL server and Sql agent service.
> Note:
> I recommend you to restore the master database first followed with other
> databases.
> Thanks
> Hari
> MCDBA
>
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
message
> news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Exec to perform my db backups. I've just
> I've wanted to do is test those backups since
> I'm using and have it configured exactly as the
> patches I try to restore all the databases. I can
> security info. I keep getting the message
> single user mode and there's just no way to do it!!
> restored I'm in deep doo-doo!
> appreciated.
>
|||Thanks guys for your prompt reply.
I thought I was starting the SQL Server in single user mode: I'm using the command "net start mssqlserver -m"... Is this not correct?
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Server
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> database.
> message
>
|||No, NET START starts the MSSQLSERVER service, and the -m is a parameter to
NET START, which doesn't take any parameters so it wouldn't know what to do
with it.
You need to run the sqlservr executable, and the pass the -m flag to it as
Hari suggested.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:9542FB0A-84B5-4DDD-8498-87C5F4A91D4A@.microsoft.com...
> Thanks guys for your prompt reply.
> I thought I was starting the SQL Server in single user mode: I'm using
the command "net start mssqlserver -m"... Is this not correct?[vbcol=seagreen]
> "Keith Kratochvil" wrote:
directly[vbcol=seagreen]
Server[vbcol=seagreen]
found[vbcol=seagreen]
of[vbcol=seagreen]
C to[vbcol=seagreen]
service.[vbcol=seagreen]
other[vbcol=seagreen]
Backup[vbcol=seagreen]
things[vbcol=seagreen]
that[vbcol=seagreen]
my[vbcol=seagreen]
|||Keith: I'm still unable to restore the master database...
I tried starting the server as you & Hari instructed; the server started in single user mode. However, the restore has to be issued from the Veritas software interface. Here's the SQL Server log.
*************************************
================================================== ====================
Job server: Test
Job name: MasterDB NoRecov 8-03
Job started: Tuesday, August 03, 2004 at 10:08:07 AM
Job type: Restore
Job Log: BEX41.txt
================================================== ====================
Drive and media information from media mount:
Robotic Library Name:
Drive Name: Quantum 1
Slot: 0
Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
Media Label: Test Wk1 Monday
Overwrite Protection Time Left: None
Append Time Left: Infinite
================================================== ====================
Job Operation - Restore
================================================== ====================
Restoring data to Test .
Storage Media #1: " Media created 8/2/04 08:24:56 PM "
Backup performed on 8/3/04 at 8:12 AM
Backup set #6: " Full Backup "
Restore started on 8/3/04 at 10:10:35 AM.
An error occurred on a query to database master.
^ ^ ^ ^ ^
SQL Server returned the following error message:
RESTORE DATABASE must be used in single user mode when trying to restore the master database.
^ ^ ^ ^ ^
Restore completed on 8/3/04 at 10:13:42 AM.
1 item was skipped.
Processed 0 bytes in 3 minutes and 7 seconds.
Throughput rate: 0.0 MB/min
================================================== ====================
Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
Job completion status: Failed
================================================== ====================
************************************************** **
2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623 (Intel X86)
Nov 27 1998 22:20:07
Copyright (c) 1988-1998 Microsoft Corporation
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft Corporation.
2004-08-03 09:55:16.52 kernel All rights reserved.
2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file 'D:\MSSQL7\log\ERRORLOG'.
2004-08-03 09:55:16.58 kernel initconfig: Number of user connections limited to 32767.
2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread processing
2004-08-03 09:55:17.96 server Directory Size: 10801
2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks
2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed Transaction Coordinator.
2004-08-03 09:55:18.82 spid1 Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
2004-08-03 09:55:18.83 spid1 Warning ******************
2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-08-03 09:55:18.84 spid1 Warning ******************
2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort order and character set.
2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database 'master' (1).
2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database 'master' (1).
2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version '7.00.00.0623'.
2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to listen on '\\.\pipe\sql\query'.
2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to listen on '3180'.
2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to listen on 'AOATESTBOX'.
2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
2004-08-03 09:55:23.55 spid1 Recovery complete.
2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
2004-08-03 09:55:23.57 spid1 comparison style = 196609.
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to execute extended stored procedure 'sp_MSgetversion'.
2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or Ctrl-Break signal.
************************************************** *****
Here's the Veritas log:
************************************************
************************************************
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Server
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> database.
> message
>
|||This may be a problem with Veritas software. Can you get the backup files
from Veritas, and do the restore manually through Query Analyzer?
Restore database master from disk = "C:\whatever"
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this? Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0
|||Try restoring the backup files to disk using Veritas and then restore the
database using T-SQL executed via Query Analyzer.
RESTORE DATABASE foo FROM DISK = 'x:\foo.bak'
(syntax and examples within Books Online)
Keith
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:B6837C91-9566-4CB1-B3D0-73DB610E6232@.microsoft.com...
> Keith: I'm still unable to restore the master database...
> I tried starting the server as you & Hari instructed; the server started
in single user mode. However, the restore has to be issued from the Veritas
software interface. Here's the SQL Server log.
> *************************************
> ================================================== ====================
> Job server: Test
> Job name: MasterDB NoRecov 8-03
> Job started: Tuesday, August 03, 2004 at 10:08:07 AM
> Job type: Restore
> Job Log: BEX41.txt
> ================================================== ====================
> Drive and media information from media mount:
> Robotic Library Name:
> Drive Name: Quantum 1
> Slot: 0
> Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
> Media Label: Test Wk1 Monday
> Overwrite Protection Time Left: None
> Append Time Left: Infinite
> ================================================== ====================
> Job Operation - Restore
> ================================================== ====================
> Restoring data to Test .
> Storage Media #1: " Media created 8/2/04 08:24:56 PM "
> Backup performed on 8/3/04 at 8:12 AM
> Backup set #6: " Full Backup "
> Restore started on 8/3/04 at 10:10:35 AM.
> An error occurred on a query to database master.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> RESTORE DATABASE must be used in single user mode when trying to restore
the master database.
> ^ ^ ^ ^ ^
> Restore completed on 8/3/04 at 10:13:42 AM.
> 1 item was skipped.
>
> Processed 0 bytes in 3 minutes and 7 seconds.
> Throughput rate: 0.0 MB/min
> ================================================== ====================
> Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
> Job completion status: Failed
> ================================================== ====================
> ************************************************** **
> 2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623
(Intel X86)
> Nov 27 1998 22:20:07
> Copyright (c) 1988-1998 Microsoft Corporation
> Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
> 2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft
Corporation.
> 2004-08-03 09:55:16.52 kernel All rights reserved.
> 2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file
'D:\MSSQL7\log\ERRORLOG'.
> 2004-08-03 09:55:16.58 kernel initconfig: Number of user connections
limited to 32767.
> 2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class
'normal'(1 CPU detected).
> 2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread
processing
> 2004-08-03 09:55:17.96 server Directory Size: 10801
> 2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks
> 2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed
Transaction Coordinator.
> 2004-08-03 09:55:18.82 spid1 Failed to obtain
TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
> 2004-08-03 09:55:18.83 spid1 Warning ******************
> 2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode.
Updates allowed to system catalogs.
> 2004-08-03 09:55:18.84 spid1 Warning ******************
> 2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
> 2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
> 2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
> 2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
> 2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort
order and character set.
> 2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database
'master' (1).
> 2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database
'master' (1).
> 2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
> 2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
> 2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
> 2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
> 2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
> 2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
> 2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
> 2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version
'7.00.00.0623'.
> 2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to
listen on '\\.\pipe\sql\query'.
> 2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to
listen on '3180'.
> 2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to
listen on 'AOATESTBOX'.
> 2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
> 2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
> 2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
> 2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
> 2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
> 2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
> 2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
> 2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
> 2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
> 2004-08-03 09:55:23.55 spid1 Recovery complete.
> 2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
> 2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
> 2004-08-03 09:55:23.57 spid1 comparison style = 196609.
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
> 2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
> 2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
> 2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to
execute extended stored procedure 'sp_MSgetversion'.
> 2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or
Ctrl-Break signal.[vbcol=seagreen]
> ************************************************** *****
> Here's the Veritas log:
> ************************************************
> ************************************************
> "Keith Kratochvil" wrote:
directly[vbcol=seagreen]
Server[vbcol=seagreen]
found[vbcol=seagreen]
of[vbcol=seagreen]
C to[vbcol=seagreen]
service.[vbcol=seagreen]
other[vbcol=seagreen]
Backup[vbcol=seagreen]
things[vbcol=seagreen]
that[vbcol=seagreen]
my[vbcol=seagreen]
I've got a problem that's causing me headaches! I'm using Veritas Backup Exec to perform my db backups. I've just
recently taken over the DBA responsibilities and one of the first things I've wanted to do is test those backups since
we've never had occassion to use the backups. I have a test system that I'm using and have it configured exactly as the
production system.
After installing MS SQL Server 7 putting on SP4 and all the security patches I try to restore all the databases. I can
get all my databases restored except the master db that contains all my security info. I keep getting the message
"must be in single user mode". I've tried to set the master db into single user mode and there's just no way to do it!!
I've tried using the EM and the sp_dboption. Without that master db restored I'm in deep doo-doo!
Any ideas how I can handle this? Any help/suggestions is greatly appreciated.
TIA
Cathy
SQL Server 7( SP4), NT4.0
Hi,
To restore the master database you have start the SQL server itself in
Single user mode.
1. Stop the MSSQL server and sql agent service
2. Go to command prompt and execute below command,.
sqlservr.exe -c -m
3. Login to sql server using query analyzer and retore the master database.
4. After the restore .. go to old comamnd prompt and press CONTRL and C to
close the old session
5. Go to control panel and start the MSSQL server and Sql agent service.
Note:
I recommend you to restore the master database first followed with other
databases.
Thanks
Hari
MCDBA
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this? Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0
|||This method will work. I think Hari copied and pasted the answer directly
from Books Online! I would have provided exactly the same answer. I
probably would have also pointed you at Books Online (within your SQL Server
program group). BACKUP and RESTORE information and examples can be found
there. Knowing how to restore the data that you are backing up is
important. Cathy, you are smart to be doing your research now (instead of
when the entire company is waiting for you to restore the data).
Keith
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> To restore the master database you have start the SQL server itself in
> Single user mode.
> 1. Stop the MSSQL server and sql agent service
> 2. Go to command prompt and execute below command,.
> sqlservr.exe -c -m
> 3. Login to sql server using query analyzer and retore the master
database.
> 4. After the restore .. go to old comamnd prompt and press CONTRL and C to
> close the old session
> 5. Go to control panel and start the MSSQL server and Sql agent service.
> Note:
> I recommend you to restore the master database first followed with other
> databases.
> Thanks
> Hari
> MCDBA
>
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
message
> news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Exec to perform my db backups. I've just
> I've wanted to do is test those backups since
> I'm using and have it configured exactly as the
> patches I try to restore all the databases. I can
> security info. I keep getting the message
> single user mode and there's just no way to do it!!
> restored I'm in deep doo-doo!
> appreciated.
>
|||Thanks guys for your prompt reply.
I thought I was starting the SQL Server in single user mode: I'm using the command "net start mssqlserver -m"... Is this not correct?
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Server
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> database.
> message
>
|||No, NET START starts the MSSQLSERVER service, and the -m is a parameter to
NET START, which doesn't take any parameters so it wouldn't know what to do
with it.
You need to run the sqlservr executable, and the pass the -m flag to it as
Hari suggested.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:9542FB0A-84B5-4DDD-8498-87C5F4A91D4A@.microsoft.com...
> Thanks guys for your prompt reply.
> I thought I was starting the SQL Server in single user mode: I'm using
the command "net start mssqlserver -m"... Is this not correct?[vbcol=seagreen]
> "Keith Kratochvil" wrote:
directly[vbcol=seagreen]
Server[vbcol=seagreen]
found[vbcol=seagreen]
of[vbcol=seagreen]
C to[vbcol=seagreen]
service.[vbcol=seagreen]
other[vbcol=seagreen]
Backup[vbcol=seagreen]
things[vbcol=seagreen]
that[vbcol=seagreen]
my[vbcol=seagreen]
|||Keith: I'm still unable to restore the master database...
I tried starting the server as you & Hari instructed; the server started in single user mode. However, the restore has to be issued from the Veritas software interface. Here's the SQL Server log.
*************************************
================================================== ====================
Job server: Test
Job name: MasterDB NoRecov 8-03
Job started: Tuesday, August 03, 2004 at 10:08:07 AM
Job type: Restore
Job Log: BEX41.txt
================================================== ====================
Drive and media information from media mount:
Robotic Library Name:
Drive Name: Quantum 1
Slot: 0
Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
Media Label: Test Wk1 Monday
Overwrite Protection Time Left: None
Append Time Left: Infinite
================================================== ====================
Job Operation - Restore
================================================== ====================
Restoring data to Test .
Storage Media #1: " Media created 8/2/04 08:24:56 PM "
Backup performed on 8/3/04 at 8:12 AM
Backup set #6: " Full Backup "
Restore started on 8/3/04 at 10:10:35 AM.
An error occurred on a query to database master.
^ ^ ^ ^ ^
SQL Server returned the following error message:
RESTORE DATABASE must be used in single user mode when trying to restore the master database.
^ ^ ^ ^ ^
Restore completed on 8/3/04 at 10:13:42 AM.
1 item was skipped.
Processed 0 bytes in 3 minutes and 7 seconds.
Throughput rate: 0.0 MB/min
================================================== ====================
Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
Job completion status: Failed
================================================== ====================
************************************************** **
2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623 (Intel X86)
Nov 27 1998 22:20:07
Copyright (c) 1988-1998 Microsoft Corporation
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft Corporation.
2004-08-03 09:55:16.52 kernel All rights reserved.
2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file 'D:\MSSQL7\log\ERRORLOG'.
2004-08-03 09:55:16.58 kernel initconfig: Number of user connections limited to 32767.
2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread processing
2004-08-03 09:55:17.96 server Directory Size: 10801
2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks
2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed Transaction Coordinator.
2004-08-03 09:55:18.82 spid1 Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
2004-08-03 09:55:18.83 spid1 Warning ******************
2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-08-03 09:55:18.84 spid1 Warning ******************
2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort order and character set.
2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database 'master' (1).
2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database 'master' (1).
2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version '7.00.00.0623'.
2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to listen on '\\.\pipe\sql\query'.
2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to listen on '3180'.
2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to listen on 'AOATESTBOX'.
2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
2004-08-03 09:55:23.55 spid1 Recovery complete.
2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
2004-08-03 09:55:23.57 spid1 comparison style = 196609.
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to execute extended stored procedure 'sp_MSgetversion'.
2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or Ctrl-Break signal.
************************************************** *****
Here's the Veritas log:
************************************************
************************************************
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Server
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> database.
> message
>
|||This may be a problem with Veritas software. Can you get the backup files
from Veritas, and do the restore manually through Query Analyzer?
Restore database master from disk = "C:\whatever"
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this? Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0
|||Try restoring the backup files to disk using Veritas and then restore the
database using T-SQL executed via Query Analyzer.
RESTORE DATABASE foo FROM DISK = 'x:\foo.bak'
(syntax and examples within Books Online)
Keith
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:B6837C91-9566-4CB1-B3D0-73DB610E6232@.microsoft.com...
> Keith: I'm still unable to restore the master database...
> I tried starting the server as you & Hari instructed; the server started
in single user mode. However, the restore has to be issued from the Veritas
software interface. Here's the SQL Server log.
> *************************************
> ================================================== ====================
> Job server: Test
> Job name: MasterDB NoRecov 8-03
> Job started: Tuesday, August 03, 2004 at 10:08:07 AM
> Job type: Restore
> Job Log: BEX41.txt
> ================================================== ====================
> Drive and media information from media mount:
> Robotic Library Name:
> Drive Name: Quantum 1
> Slot: 0
> Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
> Media Label: Test Wk1 Monday
> Overwrite Protection Time Left: None
> Append Time Left: Infinite
> ================================================== ====================
> Job Operation - Restore
> ================================================== ====================
> Restoring data to Test .
> Storage Media #1: " Media created 8/2/04 08:24:56 PM "
> Backup performed on 8/3/04 at 8:12 AM
> Backup set #6: " Full Backup "
> Restore started on 8/3/04 at 10:10:35 AM.
> An error occurred on a query to database master.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> RESTORE DATABASE must be used in single user mode when trying to restore
the master database.
> ^ ^ ^ ^ ^
> Restore completed on 8/3/04 at 10:13:42 AM.
> 1 item was skipped.
>
> Processed 0 bytes in 3 minutes and 7 seconds.
> Throughput rate: 0.0 MB/min
> ================================================== ====================
> Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
> Job completion status: Failed
> ================================================== ====================
> ************************************************** **
> 2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623
(Intel X86)
> Nov 27 1998 22:20:07
> Copyright (c) 1988-1998 Microsoft Corporation
> Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
> 2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft
Corporation.
> 2004-08-03 09:55:16.52 kernel All rights reserved.
> 2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file
'D:\MSSQL7\log\ERRORLOG'.
> 2004-08-03 09:55:16.58 kernel initconfig: Number of user connections
limited to 32767.
> 2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class
'normal'(1 CPU detected).
> 2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread
processing
> 2004-08-03 09:55:17.96 server Directory Size: 10801
> 2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks
> 2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed
Transaction Coordinator.
> 2004-08-03 09:55:18.82 spid1 Failed to obtain
TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
> 2004-08-03 09:55:18.83 spid1 Warning ******************
> 2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode.
Updates allowed to system catalogs.
> 2004-08-03 09:55:18.84 spid1 Warning ******************
> 2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
> 2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
> 2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
> 2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
> 2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort
order and character set.
> 2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database
'master' (1).
> 2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database
'master' (1).
> 2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
> 2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
> 2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
> 2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
> 2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
> 2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
> 2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
> 2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version
'7.00.00.0623'.
> 2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to
listen on '\\.\pipe\sql\query'.
> 2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to
listen on '3180'.
> 2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to
listen on 'AOATESTBOX'.
> 2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
> 2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
> 2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
> 2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
> 2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
> 2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
> 2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
> 2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
> 2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
> 2004-08-03 09:55:23.55 spid1 Recovery complete.
> 2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
> 2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
> 2004-08-03 09:55:23.57 spid1 comparison style = 196609.
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
> 2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
> 2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
> 2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to
execute extended stored procedure 'sp_MSgetversion'.
> 2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or
Ctrl-Break signal.[vbcol=seagreen]
> ************************************************** *****
> Here's the Veritas log:
> ************************************************
> ************************************************
> "Keith Kratochvil" wrote:
directly[vbcol=seagreen]
Server[vbcol=seagreen]
found[vbcol=seagreen]
of[vbcol=seagreen]
C to[vbcol=seagreen]
service.[vbcol=seagreen]
other[vbcol=seagreen]
Backup[vbcol=seagreen]
things[vbcol=seagreen]
that[vbcol=seagreen]
my[vbcol=seagreen]
Can't restore master db!
Hi:
I've got a problem that's causing me headaches! I'm using Veritas Backup Exe
c to perform my db backups. I've just
recently taken over the DBA responsibilities and one of the first things I'v
e wanted to do is test those backups since
we've never had occassion to use the backups. I have a test system that I'm
using and have it configured exactly as the
production system.
After installing MS SQL Server 7 putting on SP4 and all the security patches
I try to restore all the databases. I can
get all my databases restored except the master db that contains all my secu
rity info. I keep getting the message
"must be in single user mode". I've tried to set the master db into single
user mode and there's just no way to do it!!
I've tried using the EM and the sp_dboption. Without that master db restore
d I'm in deep doo-doo!
Any ideas how I can handle this' Any help/suggestions is greatly appreciat
ed.
TIA
Cathy
SQL Server 7( SP4), NT4.0Hi,
To restore the master database you have start the SQL server itself in
Single user mode.
1. Stop the MSSQL server and sql agent service
2. Go to command prompt and execute below command,.
sqlservr.exe -c -m
3. Login to sql server using query analyzer and retore the master database.
4. After the restore .. go to old comamnd prompt and press CONTRL and C to
close the old session
5. Go to control panel and start the MSSQL server and Sql agent service.
Note:
I recommend you to restore the master database first followed with other
databases.
Thanks
Hari
MCDBA
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.
4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this' Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0|||This method will work. I think Hari copied and pasted the answer directly
from Books Online! I would have provided exactly the same answer. I
probably would have also pointed you at Books Online (within your SQL Server
program group). BACKUP and RESTORE information and examples can be found
there. Knowing how to restore the data that you are backing up is
important. Cathy, you are smart to be doing your research now (instead of
when the entire company is waiting for you to restore the data).
Keith
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> To restore the master database you have start the SQL server itself in
> Single user mode.
> 1. Stop the MSSQL server and sql agent service
> 2. Go to command prompt and execute below command,.
> sqlservr.exe -c -m
> 3. Login to sql server using query analyzer and retore the master
database.
> 4. After the restore .. go to old comamnd prompt and press CONTRL and C to
> close the old session
> 5. Go to control panel and start the MSSQL server and Sql agent service.
> Note:
> I recommend you to restore the master database first followed with other
> databases.
> Thanks
> Hari
> MCDBA
>
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
message
> news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.
4ax.com...
> Exec to perform my db backups. I've just
> I've wanted to do is test those backups since
> I'm using and have it configured exactly as the
> patches I try to restore all the databases. I can
> security info. I keep getting the message
> single user mode and there's just no way to do it!!
> restored I'm in deep doo-doo!
> appreciated.
>|||Thanks guys for your prompt reply.
I thought I was starting the SQL Server in single user mode: I'm using the
command "net start mssqlserver -m"... Is this not correct'
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Serv
er
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> database.
> message
>|||No, NET START starts the MSSQLSERVER service, and the -m is a parameter to
NET START, which doesn't take any parameters so it wouldn't know what to do
with it.
You need to run the sqlservr executable, and the pass the -m flag to it as
Hari suggested.
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:9542FB0A-84B5-4DDD-8498-87C5F4A91D4A@.microsoft.com...
> Thanks guys for your prompt reply.
> I thought I was starting the SQL Server in single user mode: I'm using
the command "net start mssqlserver -m"... Is this not correct'[vbcol=seagreen]
> "Keith Kratochvil" wrote:
>
directly[vbcol=seagreen]
Server[vbcol=seagreen]
found[vbcol=seagreen]
of[vbcol=seagreen]
C to[vbcol=seagreen]
service.[vbcol=seagreen]
other[vbcol=seagreen]
Backup[vbcol=seagreen]
things[vbcol=seagreen]
that[vbcol=seagreen]
my[vbcol=seagreen]|||Keith: I'm still unable to restore the master database...
I tried starting the server as you & Hari instructed; the server started in
single user mode. However, the restore has to be issued from the Veritas so
ftware interface. Here's the SQL Server log.
*************************************
========================================
==============================
Job server: Test
Job name: MasterDB NoRecov 8-03
Job started: Tuesday, August 03, 2004 at 10:08:07 AM
Job type: Restore
Job Log: BEX41.txt
========================================
==============================
Drive and media information from media mount:
Robotic Library Name:
Drive Name: Quantum 1
Slot: 0
Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
Media Label: Test Wk1 Monday
Overwrite Protection Time Left: None
Append Time Left: Infinite
========================================
==============================
Job Operation - Restore
========================================
==============================
Restoring data to Test .
Storage Media #1: " Media created 8/2/04 08:24:56 PM "
Backup performed on 8/3/04 at 8:12 AM
Backup set #6: " Full Backup "
Restore started on 8/3/04 at 10:10:35 AM.
An error occurred on a query to database master.
^ ^ ^ ^ ^
SQL Server returned the following error message:
RESTORE DATABASE must be used in single user mode when trying to restore the
master database.
^ ^ ^ ^ ^
Restore completed on 8/3/04 at 10:13:42 AM.
1 item was skipped.
Processed 0 bytes in 3 minutes and 7 seconds.
Throughput rate: 0.0 MB/min
---
========================================
==============================
Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
Job completion status: Failed
========================================
==============================
****************************************
************
2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623 (Intel
X86)
Nov 27 1998 22:20:07
Copyright (c) 1988-1998 Microsoft Corporation
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft Corporatio
n.
2004-08-03 09:55:16.52 kernel All rights reserved.
2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file 'D:\MSSQ
L7\log\ERRORLOG'.
2004-08-03 09:55:16.58 kernel initconfig: Number of user connections limit
ed to 32767.
2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class 'no
rmal'(1 CPU detected).
2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread pr
ocessing
2004-08-03 09:55:17.96 server Directory Size: 10801
2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lo
ck Blocks, [5000] Lock Owner Blocks
2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed Transac
tion Coordinator.
2004-08-03 09:55:18.82 spid1 Failed to obtain TransactionDispenserInterfa
ce: XACT_E_TMNOTAVAILABLE
2004-08-03 09:55:18.83 spid1 Warning ******************
2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode. Upda
tes allowed to system catalogs.
2004-08-03 09:55:18.84 spid1 Warning ******************
2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort order
and character set.
2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database 'm
aster' (1).
2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database 'mast
er' (1).
2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version '7.00.00.0623'.
2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to li
sten on '\\.\pipe\sql\query'.
2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to li
sten on '3180'.
2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to li
sten on 'AOATESTBOX'.
2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
2004-08-03 09:55:23.55 spid1 Recovery complete.
2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
2004-08-03 09:55:23.57 spid1 comparison style = 196609.
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to e
xecute extended stored procedure 'sp_MSgetversion'.
2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or Ctrl-Br
eak signal.
****************************************
***************
Here's the Veritas log:
****************************************
********
****************************************
********
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Serv
er
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> database.
> message
>|||This may be a problem with Veritas software. Can you get the backup files
from Veritas, and do the restore manually through Query Analyzer?
Restore database master from disk = "C:\whatever"
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.
4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this' Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0|||Try restoring the backup files to disk using Veritas and then restore the
database using T-SQL executed via Query Analyzer.
RESTORE DATABASE foo FROM DISK = 'x:\foo.bak'
(syntax and examples within Books Online)
Keith
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:B6837C91-9566-4CB1-B3D0-73DB610E6232@.microsoft.com...
> Keith: I'm still unable to restore the master database...
> I tried starting the server as you & Hari instructed; the server started
in single user mode. However, the restore has to be issued from the Veritas
software interface. Here's the SQL Server log.
> *************************************
> ========================================
==============================
> Job server: Test
> Job name: MasterDB NoRecov 8-03
> Job started: Tuesday, August 03, 2004 at 10:08:07 AM
> Job type: Restore
> Job Log: BEX41.txt
> ========================================
==============================
> Drive and media information from media mount:
> Robotic Library Name:
> Drive Name: Quantum 1
> Slot: 0
> Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
> Media Label: Test Wk1 Monday
> Overwrite Protection Time Left: None
> Append Time Left: Infinite
> ========================================
==============================
> Job Operation - Restore
> ========================================
==============================
> Restoring data to Test .
> Storage Media #1: " Media created 8/2/04 08:24:56 PM "
> Backup performed on 8/3/04 at 8:12 AM
> Backup set #6: " Full Backup "
> Restore started on 8/3/04 at 10:10:35 AM.
> An error occurred on a query to database master.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> RESTORE DATABASE must be used in single user mode when trying to restore
the master database.
> ^ ^ ^ ^ ^
> Restore completed on 8/3/04 at 10:13:42 AM.
> 1 item was skipped.
>
> Processed 0 bytes in 3 minutes and 7 seconds.
> Throughput rate: 0.0 MB/min
> ---
> ========================================
==============================
> Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
> Job completion status: Failed
> ========================================
==============================
> ****************************************
************
> 2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623
(Intel X86)
> Nov 27 1998 22:20:07
> Copyright (c) 1988-1998 Microsoft Corporation
> Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
> 2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft
Corporation.
> 2004-08-03 09:55:16.52 kernel All rights reserved.
> 2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file
'D:\MSSQL7\log\ERRORLOG'.
> 2004-08-03 09:55:16.58 kernel initconfig: Number of user connections
limited to 32767.
> 2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class
'normal'(1 CPU detected).
> 2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread
processing
> 2004-08-03 09:55:17.96 server Directory Size: 10801
> 2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock[/vb
col]
Blocks, [5000] Lock Owner Blocks[vbcol=seagreen]
> 2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed
Transaction Coordinator.
> 2004-08-03 09:55:18.82 spid1 Failed to obtain
TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
> 2004-08-03 09:55:18.83 spid1 Warning ******************
> 2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode.
Updates allowed to system catalogs.
> 2004-08-03 09:55:18.84 spid1 Warning ******************
> 2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
> 2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
> 2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
> 2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
> 2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort
order and character set.
> 2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database
'master' (1).
> 2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database
'master' (1).
> 2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
> 2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
> 2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
> 2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
> 2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
> 2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
> 2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
> 2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version
'7.00.00.0623'.
> 2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to
listen on '\\.\pipe\sql\query'.
> 2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to
listen on '3180'.
> 2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to
listen on 'AOATESTBOX'.
> 2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
> 2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
> 2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
> 2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
> 2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
> 2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
> 2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
> 2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
> 2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
> 2004-08-03 09:55:23.55 spid1 Recovery complete.
> 2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
> 2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
> 2004-08-03 09:55:23.57 spid1 comparison style = 196609.
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
> 2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
> 2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
> 2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to
execute extended stored procedure 'sp_MSgetversion'.
> 2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or
Ctrl-Break signal.[vbcol=seagreen]
> ****************************************
***************
> Here's the Veritas log:
> ****************************************
********
> ****************************************
********
> "Keith Kratochvil" wrote:
>
directly[vbcol=seagreen]
Server[vbcol=seagreen]
found[vbcol=seagreen]
of[vbcol=seagreen]
C to[vbcol=seagreen]
service.[vbcol=seagreen]
other[vbcol=seagreen]
Backup[vbcol=seagreen]
things[vbcol=seagreen]
that[vbcol=seagreen]
my[vbcol=seagreen]
I've got a problem that's causing me headaches! I'm using Veritas Backup Exe
c to perform my db backups. I've just
recently taken over the DBA responsibilities and one of the first things I'v
e wanted to do is test those backups since
we've never had occassion to use the backups. I have a test system that I'm
using and have it configured exactly as the
production system.
After installing MS SQL Server 7 putting on SP4 and all the security patches
I try to restore all the databases. I can
get all my databases restored except the master db that contains all my secu
rity info. I keep getting the message
"must be in single user mode". I've tried to set the master db into single
user mode and there's just no way to do it!!
I've tried using the EM and the sp_dboption. Without that master db restore
d I'm in deep doo-doo!
Any ideas how I can handle this' Any help/suggestions is greatly appreciat
ed.
TIA
Cathy
SQL Server 7( SP4), NT4.0Hi,
To restore the master database you have start the SQL server itself in
Single user mode.
1. Stop the MSSQL server and sql agent service
2. Go to command prompt and execute below command,.
sqlservr.exe -c -m
3. Login to sql server using query analyzer and retore the master database.
4. After the restore .. go to old comamnd prompt and press CONTRL and C to
close the old session
5. Go to control panel and start the MSSQL server and Sql agent service.
Note:
I recommend you to restore the master database first followed with other
databases.
Thanks
Hari
MCDBA
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.
4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this' Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0|||This method will work. I think Hari copied and pasted the answer directly
from Books Online! I would have provided exactly the same answer. I
probably would have also pointed you at Books Online (within your SQL Server
program group). BACKUP and RESTORE information and examples can be found
there. Knowing how to restore the data that you are backing up is
important. Cathy, you are smart to be doing your research now (instead of
when the entire company is waiting for you to restore the data).
Keith
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> To restore the master database you have start the SQL server itself in
> Single user mode.
> 1. Stop the MSSQL server and sql agent service
> 2. Go to command prompt and execute below command,.
> sqlservr.exe -c -m
> 3. Login to sql server using query analyzer and retore the master
database.
> 4. After the restore .. go to old comamnd prompt and press CONTRL and C to
> close the old session
> 5. Go to control panel and start the MSSQL server and Sql agent service.
> Note:
> I recommend you to restore the master database first followed with other
> databases.
> Thanks
> Hari
> MCDBA
>
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
message
> news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.
4ax.com...
> Exec to perform my db backups. I've just
> I've wanted to do is test those backups since
> I'm using and have it configured exactly as the
> patches I try to restore all the databases. I can
> security info. I keep getting the message
> single user mode and there's just no way to do it!!
> restored I'm in deep doo-doo!
> appreciated.
>|||Thanks guys for your prompt reply.
I thought I was starting the SQL Server in single user mode: I'm using the
command "net start mssqlserver -m"... Is this not correct'
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Serv
er
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> database.
> message
>|||No, NET START starts the MSSQLSERVER service, and the -m is a parameter to
NET START, which doesn't take any parameters so it wouldn't know what to do
with it.
You need to run the sqlservr executable, and the pass the -m flag to it as
Hari suggested.
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:9542FB0A-84B5-4DDD-8498-87C5F4A91D4A@.microsoft.com...
> Thanks guys for your prompt reply.
> I thought I was starting the SQL Server in single user mode: I'm using
the command "net start mssqlserver -m"... Is this not correct'[vbcol=seagreen]
> "Keith Kratochvil" wrote:
>
directly[vbcol=seagreen]
Server[vbcol=seagreen]
found[vbcol=seagreen]
of[vbcol=seagreen]
C to[vbcol=seagreen]
service.[vbcol=seagreen]
other[vbcol=seagreen]
Backup[vbcol=seagreen]
things[vbcol=seagreen]
that[vbcol=seagreen]
my[vbcol=seagreen]|||Keith: I'm still unable to restore the master database...
I tried starting the server as you & Hari instructed; the server started in
single user mode. However, the restore has to be issued from the Veritas so
ftware interface. Here's the SQL Server log.
*************************************
========================================
==============================
Job server: Test
Job name: MasterDB NoRecov 8-03
Job started: Tuesday, August 03, 2004 at 10:08:07 AM
Job type: Restore
Job Log: BEX41.txt
========================================
==============================
Drive and media information from media mount:
Robotic Library Name:
Drive Name: Quantum 1
Slot: 0
Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
Media Label: Test Wk1 Monday
Overwrite Protection Time Left: None
Append Time Left: Infinite
========================================
==============================
Job Operation - Restore
========================================
==============================
Restoring data to Test .
Storage Media #1: " Media created 8/2/04 08:24:56 PM "
Backup performed on 8/3/04 at 8:12 AM
Backup set #6: " Full Backup "
Restore started on 8/3/04 at 10:10:35 AM.
An error occurred on a query to database master.
^ ^ ^ ^ ^
SQL Server returned the following error message:
RESTORE DATABASE must be used in single user mode when trying to restore the
master database.
^ ^ ^ ^ ^
Restore completed on 8/3/04 at 10:13:42 AM.
1 item was skipped.
Processed 0 bytes in 3 minutes and 7 seconds.
Throughput rate: 0.0 MB/min
---
========================================
==============================
Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
Job completion status: Failed
========================================
==============================
****************************************
************
2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623 (Intel
X86)
Nov 27 1998 22:20:07
Copyright (c) 1988-1998 Microsoft Corporation
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft Corporatio
n.
2004-08-03 09:55:16.52 kernel All rights reserved.
2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file 'D:\MSSQ
L7\log\ERRORLOG'.
2004-08-03 09:55:16.58 kernel initconfig: Number of user connections limit
ed to 32767.
2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class 'no
rmal'(1 CPU detected).
2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread pr
ocessing
2004-08-03 09:55:17.96 server Directory Size: 10801
2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lo
ck Blocks, [5000] Lock Owner Blocks
2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed Transac
tion Coordinator.
2004-08-03 09:55:18.82 spid1 Failed to obtain TransactionDispenserInterfa
ce: XACT_E_TMNOTAVAILABLE
2004-08-03 09:55:18.83 spid1 Warning ******************
2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode. Upda
tes allowed to system catalogs.
2004-08-03 09:55:18.84 spid1 Warning ******************
2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort order
and character set.
2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database 'm
aster' (1).
2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database 'mast
er' (1).
2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version '7.00.00.0623'.
2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to li
sten on '\\.\pipe\sql\query'.
2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to li
sten on '3180'.
2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to li
sten on 'AOATESTBOX'.
2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
2004-08-03 09:55:23.55 spid1 Recovery complete.
2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
2004-08-03 09:55:23.57 spid1 comparison style = 196609.
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to e
xecute extended stored procedure 'sp_MSgetversion'.
2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or Ctrl-Br
eak signal.
****************************************
***************
Here's the Veritas log:
****************************************
********
****************************************
********
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Serv
er
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> database.
> message
>|||This may be a problem with Veritas software. Can you get the backup files
from Veritas, and do the restore manually through Query Analyzer?
Restore database master from disk = "C:\whatever"
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.
4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this' Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0|||Try restoring the backup files to disk using Veritas and then restore the
database using T-SQL executed via Query Analyzer.
RESTORE DATABASE foo FROM DISK = 'x:\foo.bak'
(syntax and examples within Books Online)
Keith
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:B6837C91-9566-4CB1-B3D0-73DB610E6232@.microsoft.com...
> Keith: I'm still unable to restore the master database...
> I tried starting the server as you & Hari instructed; the server started
in single user mode. However, the restore has to be issued from the Veritas
software interface. Here's the SQL Server log.
> *************************************
> ========================================
==============================
> Job server: Test
> Job name: MasterDB NoRecov 8-03
> Job started: Tuesday, August 03, 2004 at 10:08:07 AM
> Job type: Restore
> Job Log: BEX41.txt
> ========================================
==============================
> Drive and media information from media mount:
> Robotic Library Name:
> Drive Name: Quantum 1
> Slot: 0
> Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
> Media Label: Test Wk1 Monday
> Overwrite Protection Time Left: None
> Append Time Left: Infinite
> ========================================
==============================
> Job Operation - Restore
> ========================================
==============================
> Restoring data to Test .
> Storage Media #1: " Media created 8/2/04 08:24:56 PM "
> Backup performed on 8/3/04 at 8:12 AM
> Backup set #6: " Full Backup "
> Restore started on 8/3/04 at 10:10:35 AM.
> An error occurred on a query to database master.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> RESTORE DATABASE must be used in single user mode when trying to restore
the master database.
> ^ ^ ^ ^ ^
> Restore completed on 8/3/04 at 10:13:42 AM.
> 1 item was skipped.
>
> Processed 0 bytes in 3 minutes and 7 seconds.
> Throughput rate: 0.0 MB/min
> ---
> ========================================
==============================
> Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
> Job completion status: Failed
> ========================================
==============================
> ****************************************
************
> 2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623
(Intel X86)
> Nov 27 1998 22:20:07
> Copyright (c) 1988-1998 Microsoft Corporation
> Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
> 2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft
Corporation.
> 2004-08-03 09:55:16.52 kernel All rights reserved.
> 2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file
'D:\MSSQL7\log\ERRORLOG'.
> 2004-08-03 09:55:16.58 kernel initconfig: Number of user connections
limited to 32767.
> 2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class
'normal'(1 CPU detected).
> 2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread
processing
> 2004-08-03 09:55:17.96 server Directory Size: 10801
> 2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock[/vb
col]
Blocks, [5000] Lock Owner Blocks[vbcol=seagreen]
> 2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed
Transaction Coordinator.
> 2004-08-03 09:55:18.82 spid1 Failed to obtain
TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
> 2004-08-03 09:55:18.83 spid1 Warning ******************
> 2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode.
Updates allowed to system catalogs.
> 2004-08-03 09:55:18.84 spid1 Warning ******************
> 2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
> 2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
> 2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
> 2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
> 2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort
order and character set.
> 2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database
'master' (1).
> 2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database
'master' (1).
> 2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
> 2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
> 2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
> 2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
> 2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
> 2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
> 2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
> 2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version
'7.00.00.0623'.
> 2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to
listen on '\\.\pipe\sql\query'.
> 2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to
listen on '3180'.
> 2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to
listen on 'AOATESTBOX'.
> 2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
> 2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
> 2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
> 2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
> 2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
> 2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
> 2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
> 2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
> 2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
> 2004-08-03 09:55:23.55 spid1 Recovery complete.
> 2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
> 2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
> 2004-08-03 09:55:23.57 spid1 comparison style = 196609.
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
> 2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
> 2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
> 2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to
execute extended stored procedure 'sp_MSgetversion'.
> 2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or
Ctrl-Break signal.[vbcol=seagreen]
> ****************************************
***************
> Here's the Veritas log:
> ****************************************
********
> ****************************************
********
> "Keith Kratochvil" wrote:
>
directly[vbcol=seagreen]
Server[vbcol=seagreen]
found[vbcol=seagreen]
of[vbcol=seagreen]
C to[vbcol=seagreen]
service.[vbcol=seagreen]
other[vbcol=seagreen]
Backup[vbcol=seagreen]
things[vbcol=seagreen]
that[vbcol=seagreen]
my[vbcol=seagreen]
Can't restore master db!
Hi:
I've got a problem that's causing me headaches! I'm using Veritas Backup Exec to perform my db backups. I've just
recently taken over the DBA responsibilities and one of the first things I've wanted to do is test those backups since
we've never had occassion to use the backups. I have a test system that I'm using and have it configured exactly as the
production system.
After installing MS SQL Server 7 putting on SP4 and all the security patches I try to restore all the databases. I can
get all my databases restored except the master db that contains all my security info. I keep getting the message
"must be in single user mode". I've tried to set the master db into single user mode and there's just no way to do it!!
I've tried using the EM and the sp_dboption. Without that master db restored I'm in deep doo-doo!
Any ideas how I can handle this' Any help/suggestions is greatly appreciated.
TIA
Cathy
SQL Server 7( SP4), NT4.0Hi,
To restore the master database you have start the SQL server itself in
Single user mode.
1. Stop the MSSQL server and sql agent service
2. Go to command prompt and execute below command,.
sqlservr.exe -c -m
3. Login to sql server using query analyzer and retore the master database.
4. After the restore .. go to old comamnd prompt and press CONTRL and C to
close the old session
5. Go to control panel and start the MSSQL server and Sql agent service.
Note:
I recommend you to restore the master database first followed with other
databases.
Thanks
Hari
MCDBA
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this' Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0|||This method will work. I think Hari copied and pasted the answer directly
from Books Online! I would have provided exactly the same answer. I
probably would have also pointed you at Books Online (within your SQL Server
program group). BACKUP and RESTORE information and examples can be found
there. Knowing how to restore the data that you are backing up is
important. Cathy, you are smart to be doing your research now (instead of
when the entire company is waiting for you to restore the data).
--
Keith
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> To restore the master database you have start the SQL server itself in
> Single user mode.
> 1. Stop the MSSQL server and sql agent service
> 2. Go to command prompt and execute below command,.
> sqlservr.exe -c -m
> 3. Login to sql server using query analyzer and retore the master
database.
> 4. After the restore .. go to old comamnd prompt and press CONTRL and C to
> close the old session
> 5. Go to control panel and start the MSSQL server and Sql agent service.
> Note:
> I recommend you to restore the master database first followed with other
> databases.
> Thanks
> Hari
> MCDBA
>
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
message
> news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> > Hi:
> >
> > I've got a problem that's causing me headaches! I'm using Veritas Backup
> Exec to perform my db backups. I've just
> > recently taken over the DBA responsibilities and one of the first things
> I've wanted to do is test those backups since
> > we've never had occassion to use the backups. I have a test system that
> I'm using and have it configured exactly as the
> > production system.
> >
> > After installing MS SQL Server 7 putting on SP4 and all the security
> patches I try to restore all the databases. I can
> > get all my databases restored except the master db that contains all my
> security info. I keep getting the message
> > "must be in single user mode". I've tried to set the master db into
> single user mode and there's just no way to do it!!
> > I've tried using the EM and the sp_dboption. Without that master db
> restored I'm in deep doo-doo!
> >
> > Any ideas how I can handle this' Any help/suggestions is greatly
> appreciated.
> >
> > TIA
> >
> > Cathy
> >
> > SQL Server 7( SP4), NT4.0
>|||Thanks guys for your prompt reply.
I thought I was starting the SQL Server in single user mode: I'm using the command "net start mssqlserver -m"... Is this not correct'
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Server
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > To restore the master database you have start the SQL server itself in
> > Single user mode.
> >
> > 1. Stop the MSSQL server and sql agent service
> >
> > 2. Go to command prompt and execute below command,.
> >
> > sqlservr.exe -c -m
> >
> > 3. Login to sql server using query analyzer and retore the master
> database.
> >
> > 4. After the restore .. go to old comamnd prompt and press CONTRL and C to
> > close the old session
> >
> > 5. Go to control panel and start the MSSQL server and Sql agent service.
> >
> > Note:
> >
> > I recommend you to restore the master database first followed with other
> > databases.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> > "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
> message
> > news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> > > Hi:
> > >
> > > I've got a problem that's causing me headaches! I'm using Veritas Backup
> > Exec to perform my db backups. I've just
> > > recently taken over the DBA responsibilities and one of the first things
> > I've wanted to do is test those backups since
> > > we've never had occassion to use the backups. I have a test system that
> > I'm using and have it configured exactly as the
> > > production system.
> > >
> > > After installing MS SQL Server 7 putting on SP4 and all the security
> > patches I try to restore all the databases. I can
> > > get all my databases restored except the master db that contains all my
> > security info. I keep getting the message
> > > "must be in single user mode". I've tried to set the master db into
> > single user mode and there's just no way to do it!!
> > > I've tried using the EM and the sp_dboption. Without that master db
> > restored I'm in deep doo-doo!
> > >
> > > Any ideas how I can handle this' Any help/suggestions is greatly
> > appreciated.
> > >
> > > TIA
> > >
> > > Cathy
> > >
> > > SQL Server 7( SP4), NT4.0
> >
> >
>|||No, NET START starts the MSSQLSERVER service, and the -m is a parameter to
NET START, which doesn't take any parameters so it wouldn't know what to do
with it.
You need to run the sqlservr executable, and the pass the -m flag to it as
Hari suggested.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:9542FB0A-84B5-4DDD-8498-87C5F4A91D4A@.microsoft.com...
> Thanks guys for your prompt reply.
> I thought I was starting the SQL Server in single user mode: I'm using
the command "net start mssqlserver -m"... Is this not correct'
> "Keith Kratochvil" wrote:
> > This method will work. I think Hari copied and pasted the answer
directly
> > from Books Online! I would have provided exactly the same answer. I
> > probably would have also pointed you at Books Online (within your SQL
Server
> > program group). BACKUP and RESTORE information and examples can be
found
> > there. Knowing how to restore the data that you are backing up is
> > important. Cathy, you are smart to be doing your research now (instead
of
> > when the entire company is waiting for you to restore the data).
> >
> > --
> > Keith
> >
> >
> > "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> > news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > Hi,
> > >
> > > To restore the master database you have start the SQL server itself in
> > > Single user mode.
> > >
> > > 1. Stop the MSSQL server and sql agent service
> > >
> > > 2. Go to command prompt and execute below command,.
> > >
> > > sqlservr.exe -c -m
> > >
> > > 3. Login to sql server using query analyzer and retore the master
> > database.
> > >
> > > 4. After the restore .. go to old comamnd prompt and press CONTRL and
C to
> > > close the old session
> > >
> > > 5. Go to control panel and start the MSSQL server and Sql agent
service.
> > >
> > > Note:
> > >
> > > I recommend you to restore the master database first followed with
other
> > > databases.
> > >
> > > Thanks
> > > Hari
> > > MCDBA
> > >
> > >
> > >
> > > "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
> > message
> > > news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> > > > Hi:
> > > >
> > > > I've got a problem that's causing me headaches! I'm using Veritas
Backup
> > > Exec to perform my db backups. I've just
> > > > recently taken over the DBA responsibilities and one of the first
things
> > > I've wanted to do is test those backups since
> > > > we've never had occassion to use the backups. I have a test system
that
> > > I'm using and have it configured exactly as the
> > > > production system.
> > > >
> > > > After installing MS SQL Server 7 putting on SP4 and all the security
> > > patches I try to restore all the databases. I can
> > > > get all my databases restored except the master db that contains all
my
> > > security info. I keep getting the message
> > > > "must be in single user mode". I've tried to set the master db into
> > > single user mode and there's just no way to do it!!
> > > > I've tried using the EM and the sp_dboption. Without that master db
> > > restored I'm in deep doo-doo!
> > > >
> > > > Any ideas how I can handle this' Any help/suggestions is greatly
> > > appreciated.
> > > >
> > > > TIA
> > > >
> > > > Cathy
> > > >
> > > > SQL Server 7( SP4), NT4.0
> > >
> > >
> >
> >|||This may be a problem with Veritas software. Can you get the backup files
from Veritas, and do the restore manually through Query Analyzer?
Restore database master from disk = "C:\whatever"
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this' Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0|||Try restoring the backup files to disk using Veritas and then restore the
database using T-SQL executed via Query Analyzer.
RESTORE DATABASE foo FROM DISK = 'x:\foo.bak'
(syntax and examples within Books Online)
--
Keith
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:B6837C91-9566-4CB1-B3D0-73DB610E6232@.microsoft.com...
> Keith: I'm still unable to restore the master database...
> I tried starting the server as you & Hari instructed; the server started
in single user mode. However, the restore has to be issued from the Veritas
software interface. Here's the SQL Server log.
> *************************************
> ======================================================================> Job server: Test
> Job name: MasterDB NoRecov 8-03
> Job started: Tuesday, August 03, 2004 at 10:08:07 AM
> Job type: Restore
> Job Log: BEX41.txt
> ======================================================================> Drive and media information from media mount:
> Robotic Library Name:
> Drive Name: Quantum 1
> Slot: 0
> Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
> Media Label: Test Wk1 Monday
> Overwrite Protection Time Left: None
> Append Time Left: Infinite
> ======================================================================> Job Operation - Restore
> ======================================================================> Restoring data to Test .
> Storage Media #1: " Media created 8/2/04 08:24:56 PM "
> Backup performed on 8/3/04 at 8:12 AM
> Backup set #6: " Full Backup "
> Restore started on 8/3/04 at 10:10:35 AM.
> An error occurred on a query to database master.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> RESTORE DATABASE must be used in single user mode when trying to restore
the master database.
> ^ ^ ^ ^ ^
> Restore completed on 8/3/04 at 10:13:42 AM.
> 1 item was skipped.
>
> Processed 0 bytes in 3 minutes and 7 seconds.
> Throughput rate: 0.0 MB/min
> ---
> ======================================================================> Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
> Job completion status: Failed
> ======================================================================> ****************************************************
> 2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623
(Intel X86)
> Nov 27 1998 22:20:07
> Copyright (c) 1988-1998 Microsoft Corporation
> Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
> 2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft
Corporation.
> 2004-08-03 09:55:16.52 kernel All rights reserved.
> 2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file
'D:\MSSQL7\log\ERRORLOG'.
> 2004-08-03 09:55:16.58 kernel initconfig: Number of user connections
limited to 32767.
> 2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class
'normal'(1 CPU detected).
> 2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread
processing
> 2004-08-03 09:55:17.96 server Directory Size: 10801
> 2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks
> 2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed
Transaction Coordinator.
> 2004-08-03 09:55:18.82 spid1 Failed to obtain
TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
> 2004-08-03 09:55:18.83 spid1 Warning ******************
> 2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode.
Updates allowed to system catalogs.
> 2004-08-03 09:55:18.84 spid1 Warning ******************
> 2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
> 2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
> 2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
> 2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
> 2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort
order and character set.
> 2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database
'master' (1).
> 2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database
'master' (1).
> 2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
> 2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
> 2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
> 2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
> 2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
> 2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
> 2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
> 2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version
'7.00.00.0623'.
> 2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to
listen on '\\.\pipe\sql\query'.
> 2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to
listen on '3180'.
> 2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to
listen on 'AOATESTBOX'.
> 2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
> 2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
> 2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
> 2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
> 2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
> 2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
> 2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
> 2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
> 2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
> 2004-08-03 09:55:23.55 spid1 Recovery complete.
> 2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
> 2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
> 2004-08-03 09:55:23.57 spid1 comparison style = 196609.
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
> 2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
> 2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
> 2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to
execute extended stored procedure 'sp_MSgetversion'.
> 2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or
Ctrl-Break signal.
> *******************************************************
> Here's the Veritas log:
> ************************************************
> ************************************************
> "Keith Kratochvil" wrote:
> > This method will work. I think Hari copied and pasted the answer
directly
> > from Books Online! I would have provided exactly the same answer. I
> > probably would have also pointed you at Books Online (within your SQL
Server
> > program group). BACKUP and RESTORE information and examples can be
found
> > there. Knowing how to restore the data that you are backing up is
> > important. Cathy, you are smart to be doing your research now (instead
of
> > when the entire company is waiting for you to restore the data).
> >
> > --
> > Keith
> >
> >
> > "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> > news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > Hi,
> > >
> > > To restore the master database you have start the SQL server itself in
> > > Single user mode.
> > >
> > > 1. Stop the MSSQL server and sql agent service
> > >
> > > 2. Go to command prompt and execute below command,.
> > >
> > > sqlservr.exe -c -m
> > >
> > > 3. Login to sql server using query analyzer and retore the master
> > database.
> > >
> > > 4. After the restore .. go to old comamnd prompt and press CONTRL and
C to
> > > close the old session
> > >
> > > 5. Go to control panel and start the MSSQL server and Sql agent
service.
> > >
> > > Note:
> > >
> > > I recommend you to restore the master database first followed with
other
> > > databases.
> > >
> > > Thanks
> > > Hari
> > > MCDBA
> > >
> > >
> > >
> > > "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
> > message
> > > news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> > > > Hi:
> > > >
> > > > I've got a problem that's causing me headaches! I'm using Veritas
Backup
> > > Exec to perform my db backups. I've just
> > > > recently taken over the DBA responsibilities and one of the first
things
> > > I've wanted to do is test those backups since
> > > > we've never had occassion to use the backups. I have a test system
that
> > > I'm using and have it configured exactly as the
> > > > production system.
> > > >
> > > > After installing MS SQL Server 7 putting on SP4 and all the security
> > > patches I try to restore all the databases. I can
> > > > get all my databases restored except the master db that contains all
my
> > > security info. I keep getting the message
> > > > "must be in single user mode". I've tried to set the master db into
> > > single user mode and there's just no way to do it!!
> > > > I've tried using the EM and the sp_dboption. Without that master db
> > > restored I'm in deep doo-doo!
> > > >
> > > > Any ideas how I can handle this' Any help/suggestions is greatly
> > > appreciated.
> > > >
> > > > TIA
> > > >
> > > > Cathy
> > > >
> > > > SQL Server 7( SP4), NT4.0
> > >
> > >
> >
> >
I've got a problem that's causing me headaches! I'm using Veritas Backup Exec to perform my db backups. I've just
recently taken over the DBA responsibilities and one of the first things I've wanted to do is test those backups since
we've never had occassion to use the backups. I have a test system that I'm using and have it configured exactly as the
production system.
After installing MS SQL Server 7 putting on SP4 and all the security patches I try to restore all the databases. I can
get all my databases restored except the master db that contains all my security info. I keep getting the message
"must be in single user mode". I've tried to set the master db into single user mode and there's just no way to do it!!
I've tried using the EM and the sp_dboption. Without that master db restored I'm in deep doo-doo!
Any ideas how I can handle this' Any help/suggestions is greatly appreciated.
TIA
Cathy
SQL Server 7( SP4), NT4.0Hi,
To restore the master database you have start the SQL server itself in
Single user mode.
1. Stop the MSSQL server and sql agent service
2. Go to command prompt and execute below command,.
sqlservr.exe -c -m
3. Login to sql server using query analyzer and retore the master database.
4. After the restore .. go to old comamnd prompt and press CONTRL and C to
close the old session
5. Go to control panel and start the MSSQL server and Sql agent service.
Note:
I recommend you to restore the master database first followed with other
databases.
Thanks
Hari
MCDBA
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this' Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0|||This method will work. I think Hari copied and pasted the answer directly
from Books Online! I would have provided exactly the same answer. I
probably would have also pointed you at Books Online (within your SQL Server
program group). BACKUP and RESTORE information and examples can be found
there. Knowing how to restore the data that you are backing up is
important. Cathy, you are smart to be doing your research now (instead of
when the entire company is waiting for you to restore the data).
--
Keith
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> To restore the master database you have start the SQL server itself in
> Single user mode.
> 1. Stop the MSSQL server and sql agent service
> 2. Go to command prompt and execute below command,.
> sqlservr.exe -c -m
> 3. Login to sql server using query analyzer and retore the master
database.
> 4. After the restore .. go to old comamnd prompt and press CONTRL and C to
> close the old session
> 5. Go to control panel and start the MSSQL server and Sql agent service.
> Note:
> I recommend you to restore the master database first followed with other
> databases.
> Thanks
> Hari
> MCDBA
>
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
message
> news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> > Hi:
> >
> > I've got a problem that's causing me headaches! I'm using Veritas Backup
> Exec to perform my db backups. I've just
> > recently taken over the DBA responsibilities and one of the first things
> I've wanted to do is test those backups since
> > we've never had occassion to use the backups. I have a test system that
> I'm using and have it configured exactly as the
> > production system.
> >
> > After installing MS SQL Server 7 putting on SP4 and all the security
> patches I try to restore all the databases. I can
> > get all my databases restored except the master db that contains all my
> security info. I keep getting the message
> > "must be in single user mode". I've tried to set the master db into
> single user mode and there's just no way to do it!!
> > I've tried using the EM and the sp_dboption. Without that master db
> restored I'm in deep doo-doo!
> >
> > Any ideas how I can handle this' Any help/suggestions is greatly
> appreciated.
> >
> > TIA
> >
> > Cathy
> >
> > SQL Server 7( SP4), NT4.0
>|||Thanks guys for your prompt reply.
I thought I was starting the SQL Server in single user mode: I'm using the command "net start mssqlserver -m"... Is this not correct'
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Server
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > To restore the master database you have start the SQL server itself in
> > Single user mode.
> >
> > 1. Stop the MSSQL server and sql agent service
> >
> > 2. Go to command prompt and execute below command,.
> >
> > sqlservr.exe -c -m
> >
> > 3. Login to sql server using query analyzer and retore the master
> database.
> >
> > 4. After the restore .. go to old comamnd prompt and press CONTRL and C to
> > close the old session
> >
> > 5. Go to control panel and start the MSSQL server and Sql agent service.
> >
> > Note:
> >
> > I recommend you to restore the master database first followed with other
> > databases.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> > "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
> message
> > news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> > > Hi:
> > >
> > > I've got a problem that's causing me headaches! I'm using Veritas Backup
> > Exec to perform my db backups. I've just
> > > recently taken over the DBA responsibilities and one of the first things
> > I've wanted to do is test those backups since
> > > we've never had occassion to use the backups. I have a test system that
> > I'm using and have it configured exactly as the
> > > production system.
> > >
> > > After installing MS SQL Server 7 putting on SP4 and all the security
> > patches I try to restore all the databases. I can
> > > get all my databases restored except the master db that contains all my
> > security info. I keep getting the message
> > > "must be in single user mode". I've tried to set the master db into
> > single user mode and there's just no way to do it!!
> > > I've tried using the EM and the sp_dboption. Without that master db
> > restored I'm in deep doo-doo!
> > >
> > > Any ideas how I can handle this' Any help/suggestions is greatly
> > appreciated.
> > >
> > > TIA
> > >
> > > Cathy
> > >
> > > SQL Server 7( SP4), NT4.0
> >
> >
>|||No, NET START starts the MSSQLSERVER service, and the -m is a parameter to
NET START, which doesn't take any parameters so it wouldn't know what to do
with it.
You need to run the sqlservr executable, and the pass the -m flag to it as
Hari suggested.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:9542FB0A-84B5-4DDD-8498-87C5F4A91D4A@.microsoft.com...
> Thanks guys for your prompt reply.
> I thought I was starting the SQL Server in single user mode: I'm using
the command "net start mssqlserver -m"... Is this not correct'
> "Keith Kratochvil" wrote:
> > This method will work. I think Hari copied and pasted the answer
directly
> > from Books Online! I would have provided exactly the same answer. I
> > probably would have also pointed you at Books Online (within your SQL
Server
> > program group). BACKUP and RESTORE information and examples can be
found
> > there. Knowing how to restore the data that you are backing up is
> > important. Cathy, you are smart to be doing your research now (instead
of
> > when the entire company is waiting for you to restore the data).
> >
> > --
> > Keith
> >
> >
> > "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> > news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > Hi,
> > >
> > > To restore the master database you have start the SQL server itself in
> > > Single user mode.
> > >
> > > 1. Stop the MSSQL server and sql agent service
> > >
> > > 2. Go to command prompt and execute below command,.
> > >
> > > sqlservr.exe -c -m
> > >
> > > 3. Login to sql server using query analyzer and retore the master
> > database.
> > >
> > > 4. After the restore .. go to old comamnd prompt and press CONTRL and
C to
> > > close the old session
> > >
> > > 5. Go to control panel and start the MSSQL server and Sql agent
service.
> > >
> > > Note:
> > >
> > > I recommend you to restore the master database first followed with
other
> > > databases.
> > >
> > > Thanks
> > > Hari
> > > MCDBA
> > >
> > >
> > >
> > > "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
> > message
> > > news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> > > > Hi:
> > > >
> > > > I've got a problem that's causing me headaches! I'm using Veritas
Backup
> > > Exec to perform my db backups. I've just
> > > > recently taken over the DBA responsibilities and one of the first
things
> > > I've wanted to do is test those backups since
> > > > we've never had occassion to use the backups. I have a test system
that
> > > I'm using and have it configured exactly as the
> > > > production system.
> > > >
> > > > After installing MS SQL Server 7 putting on SP4 and all the security
> > > patches I try to restore all the databases. I can
> > > > get all my databases restored except the master db that contains all
my
> > > security info. I keep getting the message
> > > > "must be in single user mode". I've tried to set the master db into
> > > single user mode and there's just no way to do it!!
> > > > I've tried using the EM and the sp_dboption. Without that master db
> > > restored I'm in deep doo-doo!
> > > >
> > > > Any ideas how I can handle this' Any help/suggestions is greatly
> > > appreciated.
> > > >
> > > > TIA
> > > >
> > > > Cathy
> > > >
> > > > SQL Server 7( SP4), NT4.0
> > >
> > >
> >
> >|||This may be a problem with Veritas software. Can you get the backup files
from Veritas, and do the restore manually through Query Analyzer?
Restore database master from disk = "C:\whatever"
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this' Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0|||Try restoring the backup files to disk using Veritas and then restore the
database using T-SQL executed via Query Analyzer.
RESTORE DATABASE foo FROM DISK = 'x:\foo.bak'
(syntax and examples within Books Online)
--
Keith
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:B6837C91-9566-4CB1-B3D0-73DB610E6232@.microsoft.com...
> Keith: I'm still unable to restore the master database...
> I tried starting the server as you & Hari instructed; the server started
in single user mode. However, the restore has to be issued from the Veritas
software interface. Here's the SQL Server log.
> *************************************
> ======================================================================> Job server: Test
> Job name: MasterDB NoRecov 8-03
> Job started: Tuesday, August 03, 2004 at 10:08:07 AM
> Job type: Restore
> Job Log: BEX41.txt
> ======================================================================> Drive and media information from media mount:
> Robotic Library Name:
> Drive Name: Quantum 1
> Slot: 0
> Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
> Media Label: Test Wk1 Monday
> Overwrite Protection Time Left: None
> Append Time Left: Infinite
> ======================================================================> Job Operation - Restore
> ======================================================================> Restoring data to Test .
> Storage Media #1: " Media created 8/2/04 08:24:56 PM "
> Backup performed on 8/3/04 at 8:12 AM
> Backup set #6: " Full Backup "
> Restore started on 8/3/04 at 10:10:35 AM.
> An error occurred on a query to database master.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> RESTORE DATABASE must be used in single user mode when trying to restore
the master database.
> ^ ^ ^ ^ ^
> Restore completed on 8/3/04 at 10:13:42 AM.
> 1 item was skipped.
>
> Processed 0 bytes in 3 minutes and 7 seconds.
> Throughput rate: 0.0 MB/min
> ---
> ======================================================================> Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
> Job completion status: Failed
> ======================================================================> ****************************************************
> 2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623
(Intel X86)
> Nov 27 1998 22:20:07
> Copyright (c) 1988-1998 Microsoft Corporation
> Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
> 2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft
Corporation.
> 2004-08-03 09:55:16.52 kernel All rights reserved.
> 2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file
'D:\MSSQL7\log\ERRORLOG'.
> 2004-08-03 09:55:16.58 kernel initconfig: Number of user connections
limited to 32767.
> 2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class
'normal'(1 CPU detected).
> 2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread
processing
> 2004-08-03 09:55:17.96 server Directory Size: 10801
> 2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks
> 2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed
Transaction Coordinator.
> 2004-08-03 09:55:18.82 spid1 Failed to obtain
TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
> 2004-08-03 09:55:18.83 spid1 Warning ******************
> 2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode.
Updates allowed to system catalogs.
> 2004-08-03 09:55:18.84 spid1 Warning ******************
> 2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
> 2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
> 2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
> 2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
> 2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort
order and character set.
> 2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database
'master' (1).
> 2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database
'master' (1).
> 2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
> 2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
> 2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
> 2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
> 2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
> 2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
> 2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
> 2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version
'7.00.00.0623'.
> 2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to
listen on '\\.\pipe\sql\query'.
> 2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to
listen on '3180'.
> 2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to
listen on 'AOATESTBOX'.
> 2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
> 2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
> 2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
> 2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
> 2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
> 2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
> 2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
> 2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
> 2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
> 2004-08-03 09:55:23.55 spid1 Recovery complete.
> 2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
> 2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
> 2004-08-03 09:55:23.57 spid1 comparison style = 196609.
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
> 2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
> 2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
> 2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to
execute extended stored procedure 'sp_MSgetversion'.
> 2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or
Ctrl-Break signal.
> *******************************************************
> Here's the Veritas log:
> ************************************************
> ************************************************
> "Keith Kratochvil" wrote:
> > This method will work. I think Hari copied and pasted the answer
directly
> > from Books Online! I would have provided exactly the same answer. I
> > probably would have also pointed you at Books Online (within your SQL
Server
> > program group). BACKUP and RESTORE information and examples can be
found
> > there. Knowing how to restore the data that you are backing up is
> > important. Cathy, you are smart to be doing your research now (instead
of
> > when the entire company is waiting for you to restore the data).
> >
> > --
> > Keith
> >
> >
> > "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> > news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > Hi,
> > >
> > > To restore the master database you have start the SQL server itself in
> > > Single user mode.
> > >
> > > 1. Stop the MSSQL server and sql agent service
> > >
> > > 2. Go to command prompt and execute below command,.
> > >
> > > sqlservr.exe -c -m
> > >
> > > 3. Login to sql server using query analyzer and retore the master
> > database.
> > >
> > > 4. After the restore .. go to old comamnd prompt and press CONTRL and
C to
> > > close the old session
> > >
> > > 5. Go to control panel and start the MSSQL server and Sql agent
service.
> > >
> > > Note:
> > >
> > > I recommend you to restore the master database first followed with
other
> > > databases.
> > >
> > > Thanks
> > > Hari
> > > MCDBA
> > >
> > >
> > >
> > > "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
> > message
> > > news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> > > > Hi:
> > > >
> > > > I've got a problem that's causing me headaches! I'm using Veritas
Backup
> > > Exec to perform my db backups. I've just
> > > > recently taken over the DBA responsibilities and one of the first
things
> > > I've wanted to do is test those backups since
> > > > we've never had occassion to use the backups. I have a test system
that
> > > I'm using and have it configured exactly as the
> > > > production system.
> > > >
> > > > After installing MS SQL Server 7 putting on SP4 and all the security
> > > patches I try to restore all the databases. I can
> > > > get all my databases restored except the master db that contains all
my
> > > security info. I keep getting the message
> > > > "must be in single user mode". I've tried to set the master db into
> > > single user mode and there's just no way to do it!!
> > > > I've tried using the EM and the sp_dboption. Without that master db
> > > restored I'm in deep doo-doo!
> > > >
> > > > Any ideas how I can handle this' Any help/suggestions is greatly
> > > appreciated.
> > > >
> > > > TIA
> > > >
> > > > Cathy
> > > >
> > > > SQL Server 7( SP4), NT4.0
> > >
> > >
> >
> >
Subscribe to:
Posts (Atom)