SQL Server Agent started and then stopped?

    Date: 09/12/08 (SQL Server)    Keywords: sql

    Okay, this is new...

    SQL Server Express Edition 2008. Brand-new install. For some reason SQL Server Agent was listed as Disabled in the agents listing, so I set it to automatic and started it. It worked. I restarted the computer (for an unrelated reason) and started having problems connecting from C#, so I checked the agent again. It was again listed as disabled. I switched it once again to Automatic and hit Start, at which point I received the following message:

    "The SQL Server Agent (SKINGAWEE) service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."

    SkingaWee (the instance name) is currently running, I have it open in Management Studio. Thus, it would seem Agent would have something to do. Anyone know why this might be occurring and, more importantly, how I can fix it?

    Source: http://community.livejournal.com/sqlserver/67400.html

« Разработчик/ар... || Crystal Reports Question »


antivirus | apache | asp | blogging | browser | bugtracking | cms | crm | css | database | ebay | ecommerce | google | hosting | html | java | jsp | linux | microsoft | mysql | offshore | offshoring | oscommerce | php | postgresql | programming | rss | security | seo | shopping | software | spam | spyware | sql | technology | templates | tracker | virus | web | xml | yahoo | home