Problem restarting SQL Server Agent

We're running SQL Server 2000. Apparently the servers were restarted after
maintenance over the weekend (without telling me :-) and the SQL Server Job
Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
stops unexpectedly' is NOT set (and I'm not sure I have the authority to
change this option).
There were two messages in the Agent Error Log that appear relevant and
happened at about the same time..
[240] 1 engine thread(s) failed to stop after 30 seconds of waiting
[311] Thread 'JobInvocationEngine' (ID 3812) is still running
Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
automatically during a normal server startup? Also please define
'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)Hi
"B. Chernick" wrote:
> We're running SQL Server 2000. Apparently the servers were restarted after
> maintenance over the weekend (without telling me :-) and the SQL Server Job
> Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
> stops unexpectedly' is NOT set (and I'm not sure I have the authority to
> change this option).
> There were two messages in the Agent Error Log that appear relevant and
> happened at about the same time..
> [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
> [311] Thread 'JobInvocationEngine' (ID 3812) is still running
> Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
> automatically during a normal server startup? Also please define
> 'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
These errors look like they have occurred during shutdown and not startup!
Check on the server properties in the general tab for Autostart policies
when the Operating System starts that Autostart SQL Agent is set to start.
John|||My apologies. It looks like I appended too soon. I am not a full time DBA.
The agent option was unchecked.
(Looks like the problem is administrative, not technical.)
"John Bell" wrote:
> Hi
> "B. Chernick" wrote:
> > We're running SQL Server 2000. Apparently the servers were restarted after
> > maintenance over the weekend (without telling me :-) and the SQL Server Job
> > Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
> > stops unexpectedly' is NOT set (and I'm not sure I have the authority to
> > change this option).
> >
> > There were two messages in the Agent Error Log that appear relevant and
> > happened at about the same time..
> >
> > [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
> > [311] Thread 'JobInvocationEngine' (ID 3812) is still running
> >
> > Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
> > automatically during a normal server startup? Also please define
> > 'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
> These errors look like they have occurred during shutdown and not startup!
> Check on the server properties in the general tab for Autostart policies
> when the Operating System starts that Autostart SQL Agent is set to start.
> John

Problem recovering old database

> I need to resurrect an old info database from a ms sql 7 server backup
(generated from a sql

quote:

---

> maintenance plan). I have recovered the master, model and msdb databases

---

as well as the old info

quote:

---

> database. Unfortunately the sa password has been lost and once I recover

---

the master DB, I cannot

quote:

---

> log on to the query analyser to get the info I need. I have tried both sql

---

authentication and nt windows

quote:

---

> authentication.
> can anyone point me in the right direction to reset or recover?
> Thanks
> Si

---

The error messages that I get when trying to log into querry analyser are:
Using Windows NT Authentication
Unable to connect to Server \\SQL-SERVER1:
Server: Msg 18456, Level16, State1
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'SQL-SERVER1\administrator'
----
--
Using SQL Authentication
Unable to connect to Server \\SQL-SERVER1:
Server: Msg 18456, Level16, State1
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user 'sa'
Thanks
si
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:zFzg4Zn6DHA.568@.cpmsftngxa07.phx.gbl...

quote:

---

> What error message do you get when you attempt to login using the sa
> account?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

---

Any reason you need the system databases? You can restore the the old user
database to a new system. You will need to use sp_change_users_login to
remap the usernames to logins, but the data should be just fine. You can
even restore to an SQL 2000 host system.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"John Smith" <so@.funtime.com> wrote in message
news:1075904525.255819@.smtp-1.griffin.com...

quote:

---

> (generated from a sql
databases[QUOTE]
> as well as the old info
recover[QUOTE]
> the master DB, I cannot
sql[QUOTE]
> authentication and nt windows
> The error messages that I get when trying to log into querry analyser are:
> Using Windows NT Authentication
> Unable to connect to Server \\SQL-SERVER1:
> Server: Msg 18456, Level16, State1
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
> 'SQL-SERVER1\administrator'
> ----

---

--

quote:

---

> --
> Using SQL Authentication
> Unable to connect to Server \\SQL-SERVER1:
> Server: Msg 18456, Level16, State1
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user 'sa'
> Thanks
> si
>
> "Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
> news:zFzg4Zn6DHA.568@.cpmsftngxa07.phx.gbl...
rights.[QUOTE]
>
>

---

|||I want to restore the server "as was" for a period of time. I thought I
could just follow the notes supplied by microsoft on moving databases to a
new server. They recommend that the system databases are first restored.
Thanks for the help
si
"Geoff N.Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:ugObu9y6DHA.4012@.tk2msftngp13.phx.gbl...

quote:

---

> Any reason you need the system databases? You can restore the the old

---

user

quote:

---

> database to a new system. You will need to use sp_change_users_login to
> remap the usernames to logins, but the data should be just fine. You can
> even restore to an SQL 2000 host system.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "John Smith" <so@.funtime.com> wrote in message
> news:1075904525.255819@.smtp-1.griffin.com...
> databases
> recover
> sql
are:[QUOTE]
> ----
> --
'sa'[QUOTE]
> rights.
>

---

Problem recovering old database

> I need to resurrect an old info database from a ms sql 7 server backup
(generated from a sql
> maintenance plan). I have recovered the master, model and msdb databases
as well as the old info
> database. Unfortunately the sa password has been lost and once I recover
the master DB, I cannot
> log on to the query analyser to get the info I need. I have tried both sql
authentication and nt windows
> authentication.
>
> can anyone point me in the right direction to reset or recover?
>
> Thanks
>
> Si
The error messages that I get when trying to log into querry analyser are:
Using Windows NT Authentication
Unable to connect to Server \\SQL-SERVER1:
Server: Msg 18456, Level16, State1
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'SQL-SERVER1\administrator'
----
--
Using SQL Authentication
Unable to connect to Server \\SQL-SERVER1:
Server: Msg 18456, Level16, State1
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user 'sa'
Thanks
si
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:zFzg4Zn6DHA.568@.cpmsftngxa07.phx.gbl...
> What error message do you get when you attempt to login using the sa
> account?
>
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>Any reason you need the system databases? You can restore the the old user
database to a new system. You will need to use sp_change_users_login to
remap the usernames to logins, but the data should be just fine. You can
even restore to an SQL 2000 host system.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"John Smith" <so@.funtime.com> wrote in message
news:1075904525.255819@.smtp-1.griffin.com...
> > I need to resurrect an old info database from a ms sql 7 server backup
> (generated from a sql
> > maintenance plan). I have recovered the master, model and msdb
databases
> as well as the old info
> > database. Unfortunately the sa password has been lost and once I
recover
> the master DB, I cannot
> > log on to the query analyser to get the info I need. I have tried both
sql
> authentication and nt windows
> > authentication.
> >
> > can anyone point me in the right direction to reset or recover?
> >
> > Thanks
> >
> > Si
> The error messages that I get when trying to log into querry analyser are:
> Using Windows NT Authentication
> Unable to connect to Server \\SQL-SERVER1:
> Server: Msg 18456, Level16, State1
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
> 'SQL-SERVER1\administrator'
> ----
--
> --
> Using SQL Authentication
> Unable to connect to Server \\SQL-SERVER1:
> Server: Msg 18456, Level16, State1
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user 'sa'
> Thanks
> si
>
> "Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
> news:zFzg4Zn6DHA.568@.cpmsftngxa07.phx.gbl...
> > What error message do you get when you attempt to login using the sa
> > account?
> >
> > Rand
> > This posting is provided "as is" with no warranties and confers no
rights.
> >
>
>|||I want to restore the server "as was" for a period of time. I thought I
could just follow the notes supplied by microsoft on moving databases to a
new server. They recommend that the system databases are first restored.
Thanks for the help
si
"Geoff N.Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:ugObu9y6DHA.4012@.tk2msftngp13.phx.gbl...
> Any reason you need the system databases? You can restore the the old
user
> database to a new system. You will need to use sp_change_users_login to
> remap the usernames to logins, but the data should be just fine. You can
> even restore to an SQL 2000 host system.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "John Smith" <so@.funtime.com> wrote in message
> news:1075904525.255819@.smtp-1.griffin.com...
> > > I need to resurrect an old info database from a ms sql 7 server backup
> > (generated from a sql
> > > maintenance plan). I have recovered the master, model and msdb
> databases
> > as well as the old info
> > > database. Unfortunately the sa password has been lost and once I
> recover
> > the master DB, I cannot
> > > log on to the query analyser to get the info I need. I have tried both
> sql
> > authentication and nt windows
> > > authentication.
> > >
> > > can anyone point me in the right direction to reset or recover?
> > >
> > > Thanks
> > >
> > > Si
> >
> > The error messages that I get when trying to log into querry analyser
are:
> >
> > Using Windows NT Authentication
> >
> > Unable to connect to Server \\SQL-SERVER1:
> >
> > Server: Msg 18456, Level16, State1
> > [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
> > 'SQL-SERVER1\administrator'
> >
> ----
> --
> > --
> > Using SQL Authentication
> >
> > Unable to connect to Server \\SQL-SERVER1:
> >
> > Server: Msg 18456, Level16, State1
> > [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'sa'
> >
> > Thanks
> >
> > si
> >
> >
> > "Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
> > news:zFzg4Zn6DHA.568@.cpmsftngxa07.phx.gbl...
> > > What error message do you get when you attempt to login using the sa
> > > account?
> > >
> > > Rand
> > > This posting is provided "as is" with no warranties and confers no
> rights.
> > >
> >
> >
> >
> >
>