SQL Server Agent

vinod_pawar1 · July 2nd, 2004, 04:48 AM

hi,

I am using MSDE as backend for my software, I want to schedule the backup, but it requires SQL Server Agent has to be running.

But I don't know why my SQL Server Agent process does not start even if I am starting it explicitly.

This problem persisting even after re-installation of MSDE.

Can anybody tell me the reason why this is happening and how to get rid of it.

Vinod Pawar
Software Developer
Videocon International Ltd.
India

alyeng2000 · July 2nd, 2004, 04:06 PM

make sure that you check the service to start with window start up

Ahmed Ali
Software Developer

vinod_pawar1 · July 2nd, 2004, 10:51 PM

ya, other services are starting with windows startup except Sql server agent even after specifying "Auto-Start service when os starts". When I had installed MSDE that time it was working fine, but after some days I don't know what happened, this problem occurred and still persisting even after re-installing all.

Vinod Pawar
Software Developer
India

happygv · July 3rd, 2004, 07:01 AM

Hi Vinod,

It should be logging something on its status when you attempt to start that. Check your event logs to see what error it generates there. It would be better you post the error that you could see when you attempt to start SQL server Agent, as there are many reasons for it to not start.

Cheers!

_________________________
- Vijay G
Strive for Perfection

happygv · July 14th, 2004, 06:32 AM

Based on your log entries, it looks like SA itself has failed to login. Anything recently done to that system Like changing password or so?

I suspect there was a change in SA password done recently that is the cause for it. By any chance did you forget to mention about change in SA password in your post or did someone else changed that without your knowledge?

Check this page for work around.

SQL Server Agent Fails to Start on Windows 9x When You Change the sa Password

_________________________
- Vijay G
Strive for Perfection

vinod_pawar1 · July 14th, 2004, 07:04 AM

thanx Vijay,

I think this will solve my problem.

If you can please do suggest something for other problem also
http://p2p.wrox.com/topic.asp?TOPIC_ID=16000

thanx again.

Vinod Pawar
Software Developer
India

happygv · July 14th, 2004, 07:15 AM

Just curious to know, if the SA password was changed after which you are facing this problem. Did that happen?

_________________________
- Vijay G
Strive for Perfection

vinod_pawar1 · July 14th, 2004, 10:52 PM

hello vijay,

you are right, that was happening just because of change of password.
but, isn't it strange thing, if you change password of 'sa' user, that has also to be changed in SqlServerAgent. It's non microsoft kind thing.

thanx

Vinod Pawar
Software Developer
India

happygv · July 15th, 2004, 04:50 AM

This is the case with Win9x, not with other higher versions of Windows. You can go through the content under CAUSE heading in the micrisoft support link, that reads ...

The information needed for SQL Server Agent to start is obtained from the registry; however, the information does not exist in the registry until after the sa password is changed by the SQL Server Enterprise Manager (SEM). This method is used on Microsoft Windows 9x computers, because they do not support trusted-connections, which is the default for Microsoft SQL Server 7.0 on both Microsoft Windows NT 4.0-based computers and Microsoft Windows 2000-based computers.

Hope that explains.
Cheers!

_________________________
- Vijay G
Strive for Perfection

vinod_pawar1 · July 15th, 2004, 10:52 PM

thank you very much Vijay

Vinod Pawar
Software Developer
India