Showing posts with label viewer. Show all posts
Showing posts with label viewer. Show all posts

Tuesday, March 27, 2012

can't start sql2000, Database 'model' cannot be opened. It is in the middle of a restor

I can't start Sql server 2000, in the event viewer is the folowing message.
Database 'model' cannot be opened. It is in the middle of a restore.
Anyone can help me ?
Pedro MetelloYou can possibly use traceflags 3607, 3608 or 3609 to start model without recovery. However, you
need to search the net for articles describing this. Seems like MS removed these from KB... :-(
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"FRISSUL" <frissul@.frissul.pt> wrote in message news:uw6AaiTnDHA.3504@.TK2MSFTNGP11.phx.gbl...
> I can't start Sql server 2000, in the event viewer is the folowing message.
> Database 'model' cannot be opened. It is in the middle of a restore.
>
> Anyone can help me ?
>
> Pedro Metello
>|||thanks, but when I start with
SQLSERVR -T3609
it says:
"BYPASSING RECOVERY FOR DATABASE 'MODEL' BECAUSE IT IS MARKED IN LOAD"
and then
"Database 'model' cannot be opened. It is in the middle of a restore."
Pedro Metello
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:uQ7fBuTnDHA.3504@.TK2MSFTNGP11.phx.gbl...
> You can possibly use traceflags 3607, 3608 or 3609 to start model without
recovery. However, you
> need to search the net for articles describing this. Seems like MS removed
these from KB... :-(
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "FRISSUL" <frissul@.frissul.pt> wrote in message
news:uw6AaiTnDHA.3504@.TK2MSFTNGP11.phx.gbl...
> > I can't start Sql server 2000, in the event viewer is the folowing
message.
> >
> > Database 'model' cannot be opened. It is in the middle of a restore.
> >
> >
> >
> > Anyone can help me ?
> >
> >
> >
> > Pedro Metello
> >
> >
>|||Too bad. There goes that option. I'm out of ideas. I assume you have searched KB and the archives.
So unless someone else comes up with any ideas, it might be worth opening a case with MS support.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"FRISSUL" <frissul@.frissul.pt> wrote in message news:eZHqd5UnDHA.1740@.TK2MSFTNGP12.phx.gbl...
> thanks, but when I start with
> SQLSERVR -T3609
> it says:
> "BYPASSING RECOVERY FOR DATABASE 'MODEL' BECAUSE IT IS MARKED IN LOAD"
> and then
> "Database 'model' cannot be opened. It is in the middle of a restore."
> Pedro Metello
>
> "Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:uQ7fBuTnDHA.3504@.TK2MSFTNGP11.phx.gbl...
> > You can possibly use traceflags 3607, 3608 or 3609 to start model without
> recovery. However, you
> > need to search the net for articles describing this. Seems like MS removed
> these from KB... :-(
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at:
> http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> > "FRISSUL" <frissul@.frissul.pt> wrote in message
> news:uw6AaiTnDHA.3504@.TK2MSFTNGP11.phx.gbl...
> > > I can't start Sql server 2000, in the event viewer is the folowing
> message.
> > >
> > > Database 'model' cannot be opened. It is in the middle of a restore.
> > >
> > >
> > >
> > > Anyone can help me ?
> > >
> > >
> > >
> > > Pedro Metello
> > >
> > >
> >
> >
>

can't start sql server agent

Using SS2000 SP4. We rebooted our box this morning and the sql server agent
wouldn't start. I found this error in the event viewer in the system errorlog
- " The SQLSERVERAGENT service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid
for the account name specified. "
The agent is using the same login and password as the SQL Server service and
the SQL Server service started fine. I trying putting in the password again
from the services app but the hourglass kept going and going until we finally
killed it. I tried changing the startup account to the local system from
within EM but I got this message - "The new service startup account name you
have supplied is invalid or does not exist." I tried using my domain account
and got the same message. I tried going back to the original login and
password and got the same message.
Our sysadmin said he had some problems with our domain controller over the
weekend. Since it can't seem to verify the accounts I thought that might be
related but if so, why does the SQL Server account work ok with the same
login and password?
Any ideas?
Thanks,
--
Dan D.Did you try log in on Windows on the same box? Sometimes it is a profile
problem.
--
Regards,
Robson Siqueira
Enterprise Architect
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> Using SS2000 SP4. We rebooted our box this morning and the sql server
> agent
> wouldn't start. I found this error in the event viewer in the system
> errorlog
> - " The SQLSERVERAGENT service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is invalid
> for the account name specified. "
> The agent is using the same login and password as the SQL Server service
> and
> the SQL Server service started fine. I trying putting in the password
> again
> from the services app but the hourglass kept going and going until we
> finally
> killed it. I tried changing the startup account to the local system from
> within EM but I got this message - "The new service startup account name
> you
> have supplied is invalid or does not exist." I tried using my domain
> account
> and got the same message. I tried going back to the original login and
> password and got the same message.
> Our sysadmin said he had some problems with our domain controller over the
> weekend. Since it can't seem to verify the accounts I thought that might
> be
> related but if so, why does the SQL Server account work ok with the same
> login and password?
> Any ideas?
> Thanks,
> --
> Dan D.|||They were changing the monitor in the computer room and this server hasn't
been hooked up yet.
I came in this morning and the agent service had started overnight. So,
we're okay for now. Thanks,
--
Dan D.
"Robson Siqueira" wrote:
> Did you try log in on Windows on the same box? Sometimes it is a profile
> problem.
> --
> Regards,
> Robson Siqueira
> Enterprise Architect
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> > Using SS2000 SP4. We rebooted our box this morning and the sql server
> > agent
> > wouldn't start. I found this error in the event viewer in the system
> > errorlog
> > - " The SQLSERVERAGENT service failed to start due to the following error:
> > The account name is invalid or does not exist, or the password is invalid
> > for the account name specified. "
> >
> > The agent is using the same login and password as the SQL Server service
> > and
> > the SQL Server service started fine. I trying putting in the password
> > again
> > from the services app but the hourglass kept going and going until we
> > finally
> > killed it. I tried changing the startup account to the local system from
> > within EM but I got this message - "The new service startup account name
> > you
> > have supplied is invalid or does not exist." I tried using my domain
> > account
> > and got the same message. I tried going back to the original login and
> > password and got the same message.
> >
> > Our sysadmin said he had some problems with our domain controller over the
> > weekend. Since it can't seem to verify the accounts I thought that might
> > be
> > related but if so, why does the SQL Server account work ok with the same
> > login and password?
> >
> > Any ideas?
> >
> > Thanks,
> > --
> > Dan D.
>
>

can't start sql server agent

Using SS2000 SP4. We rebooted our box this morning and the sql server agent
wouldn't start. I found this error in the event viewer in the system errorlog
- " The SQLSERVERAGENT service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid
for the account name specified. "
The agent is using the same login and password as the SQL Server service and
the SQL Server service started fine. I trying putting in the password again
from the services app but the hourglass kept going and going until we finally
killed it. I tried changing the startup account to the local system from
within EM but I got this message - "The new service startup account name you
have supplied is invalid or does not exist." I tried using my domain account
and got the same message. I tried going back to the original login and
password and got the same message.
Our sysadmin said he had some problems with our domain controller over the
weekend. Since it can't seem to verify the accounts I thought that might be
related but if so, why does the SQL Server account work ok with the same
login and password?
Any ideas?
Thanks,
Dan D.
Did you try log in on Windows on the same box? Sometimes it is a profile
problem.
Regards,
Robson Siqueira
Enterprise Architect
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> Using SS2000 SP4. We rebooted our box this morning and the sql server
> agent
> wouldn't start. I found this error in the event viewer in the system
> errorlog
> - " The SQLSERVERAGENT service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is invalid
> for the account name specified. "
> The agent is using the same login and password as the SQL Server service
> and
> the SQL Server service started fine. I trying putting in the password
> again
> from the services app but the hourglass kept going and going until we
> finally
> killed it. I tried changing the startup account to the local system from
> within EM but I got this message - "The new service startup account name
> you
> have supplied is invalid or does not exist." I tried using my domain
> account
> and got the same message. I tried going back to the original login and
> password and got the same message.
> Our sysadmin said he had some problems with our domain controller over the
> weekend. Since it can't seem to verify the accounts I thought that might
> be
> related but if so, why does the SQL Server account work ok with the same
> login and password?
> Any ideas?
> Thanks,
> --
> Dan D.
|||They were changing the monitor in the computer room and this server hasn't
been hooked up yet.
I came in this morning and the agent service had started overnight. So,
we're okay for now. Thanks,
Dan D.
"Robson Siqueira" wrote:

> Did you try log in on Windows on the same box? Sometimes it is a profile
> problem.
> --
> Regards,
> Robson Siqueira
> Enterprise Architect
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
>
>

can't start sql server agent

Using SS2000 SP4. We rebooted our box this morning and the sql server agent
wouldn't start. I found this error in the event viewer in the system errorlo
g
- " The SQLSERVERAGENT service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid
for the account name specified. "
The agent is using the same login and password as the SQL Server service and
the SQL Server service started fine. I trying putting in the password again
from the services app but the hourglass kept going and going until we finall
y
killed it. I tried changing the startup account to the local system from
within EM but I got this message - "The new service startup account name you
have supplied is invalid or does not exist." I tried using my domain account
and got the same message. I tried going back to the original login and
password and got the same message.
Our sysadmin said he had some problems with our domain controller over the
weekend. Since it can't seem to verify the accounts I thought that might be
related but if so, why does the SQL Server account work ok with the same
login and password?
Any ideas?
Thanks,
--
Dan D.Did you try log in on Windows on the same box? Sometimes it is a profile
problem.
Regards,
Robson Siqueira
Enterprise Architect
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> Using SS2000 SP4. We rebooted our box this morning and the sql server
> agent
> wouldn't start. I found this error in the event viewer in the system
> errorlog
> - " The SQLSERVERAGENT service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is invalid
> for the account name specified. "
> The agent is using the same login and password as the SQL Server service
> and
> the SQL Server service started fine. I trying putting in the password
> again
> from the services app but the hourglass kept going and going until we
> finally
> killed it. I tried changing the startup account to the local system from
> within EM but I got this message - "The new service startup account name
> you
> have supplied is invalid or does not exist." I tried using my domain
> account
> and got the same message. I tried going back to the original login and
> password and got the same message.
> Our sysadmin said he had some problems with our domain controller over the
> weekend. Since it can't seem to verify the accounts I thought that might
> be
> related but if so, why does the SQL Server account work ok with the same
> login and password?
> Any ideas?
> Thanks,
> --
> Dan D.|||They were changing the monitor in the computer room and this server hasn't
been hooked up yet.
I came in this morning and the agent service had started overnight. So,
we're okay for now. Thanks,
--
Dan D.
"Robson Siqueira" wrote:

> Did you try log in on Windows on the same box? Sometimes it is a profile
> problem.
> --
> Regards,
> Robson Siqueira
> Enterprise Architect
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
>
>