Agent started but not started?

I have a SQL 2005 server running on a win2k3 box. For some reason, no
matter what account the SQL Server Agent runs under, error messages
are logged in the security logs. Even if the login account is set to
"local service". BUT if I look at the service under "services", it
says started. It also says started in the SQL 2005 configuration
manager.
Has anyone seen this before?
Thanks
Hello,
Can you create one test job and try executing. If the job runs then SQL
Agent is working fine...also see the SQLAgent.out file in Log folder of SQL
Server
installation folder for any errors
Thanks
Hari
<costello_joe@.hotmail.com> wrote in message
news:1180399298.618353.292290@.q19g2000prn.googlegr oups.com...
> I have a SQL 2005 server running on a win2k3 box. For some reason, no
> matter what account the SQL Server Agent runs under, error messages
> are logged in the security logs. Even if the login account is set to
> "local service". BUT if I look at the service under "services", it
> says started. It also says started in the SQL 2005 configuration
> manager.
> Has anyone seen this before?
> Thanks
>

Agent started but not started?

I have a SQL 2005 server running on a win2k3 box. For some reason, no
matter what account the SQL Server Agent runs under, error messages
are logged in the security logs. Even if the login account is set to
"local service". BUT if I look at the service under "services", it
says started. It also says started in the SQL 2005 configuration
manager.
Has anyone seen this before?
ThanksHello,
Can you create one test job and try executing. If the job runs then SQL
Agent is working fine...also see the SQLAgent.out file in Log folder of SQL
Server
installation folder for any errors
Thanks
Hari
<costello_joe@.hotmail.com> wrote in message
news:1180399298.618353.292290@.q19g2000prn.googlegroups.com...
> I have a SQL 2005 server running on a win2k3 box. For some reason, no
> matter what account the SQL Server Agent runs under, error messages
> are logged in the security logs. Even if the login account is set to
> "local service". BUT if I look at the service under "services", it
> says started. It also says started in the SQL 2005 configuration
> manager.
> Has anyone seen this before?
> Thanks
>

Agent started but not started?

I have a SQL 2005 server running on a win2k3 box. For some reason, no
matter what account the SQL Server Agent runs under, error messages
are logged in the security logs. Even if the login account is set to
"local service". BUT if I look at the service under "services", it
says started. It also says started in the SQL 2005 configuration
manager.
Has anyone seen this before?
ThanksHello,
Can you create one test job and try executing. If the job runs then SQL
Agent is working fine...also see the SQLAgent.out file in Log folder of SQL
Server
installation folder for any errors
Thanks
Hari
<costello_joe@.hotmail.com> wrote in message
news:1180399298.618353.292290@.q19g2000prn.googlegroups.com...
> I have a SQL 2005 server running on a win2k3 box. For some reason, no
> matter what account the SQL Server Agent runs under, error messages
> are logged in the security logs. Even if the login account is set to
> "local service". BUT if I look at the service under "services", it
> says started. It also says started in the SQL 2005 configuration
> manager.
> Has anyone seen this before?
> Thanks
>

After Install WIN2K3 SP1 on SQL 2K SP3 Cluster Problem

My site have two HP server are install SQL 2K Cluster Server (MSCS) on
Windows 2003 Server are running smoothly but when I upgrade both Windows 2003
to SP1 the problem was appear, when I reboot Passive B cluster server it will
take over the SAN disk(the database disk) but it doesn't failover the SQL
process, I'm sure I didn't set failback to passive server.
When I manual to failover from Active A Cluster to passive B server, it can
success to failover to B, then I restart A Cluster server, it can takeover
all process and SAN disk back, I'm also sure I didn't set failback to A
Server.
So, could you mind give me some hints for me to trouble shooting, I hear
before most of the cases are cause of Windows 2003 SP1.
Make sure that you HBA's are certified to run under SP1, this is not always
the case. You may need to update the drivers after SP1. Worse case,
uninstall SP1 until the vendor supports SP1.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://msmvps.com/clustering/archive.../20/58233.aspx NYC Clustering
class
"TM" <TM@.discussions.microsoft.com> wrote in message
news:17C5D515-8B5B-4C4F-9E0F-4FFE1375D145@.microsoft.com...
> My site have two HP server are install SQL 2K Cluster Server (MSCS) on
> Windows 2003 Server are running smoothly but when I upgrade both Windows
> 2003
> to SP1 the problem was appear, when I reboot Passive B cluster server it
> will
> take over the SAN disk(the database disk) but it doesn't failover the SQL
> process, I'm sure I didn't set failback to passive server.
> When I manual to failover from Active A Cluster to passive B server, it
> can
> success to failover to B, then I restart A Cluster server, it can takeover
> all process and SAN disk back, I'm also sure I didn't set failback to A
> Server.
> So, could you mind give me some hints for me to trouble shooting, I hear
> before most of the cases are cause of Windows 2003 SP1.