Problem solved.

The cause is that my integration development studio is on edition RTM while the sql server instance on SP3.

After patching the integration service with SP3, the "parameter mapping" tabs...

Hello everyone who replied to this post, I can't say I found the definitive solution, but at least it is one of the ways you can try out, which is...

Wow, this is priceless, I've just reset the agent error log in two of our servers on which the sql server agent services misteriously refused to start. And now both...

Thanks for providing this idea, but unfortunately it doesn't work.

Brandie Tarvin (10/21/2010)

---

But do you see other errors before that which might be connected to the restart fail?

John makes a good point about the log file. Find out what service...

Brandie Tarvin (10/21/2010)

---

Check the Application and System logs in Event Viewer. That might help you track down the source of the issue.

Is this a standalone server or a clustered node?

Is...

Brandie Tarvin (10/21/2010)

---

People are going to lynch me for this first question, but...

When was the last time you rebooted the box?

Has SQL Server Agent run before on this box...

Also an interesting error message:

The SQL Server Agent (MSSQLSERVER) service on local computer started and then stopped. Some services stop automatically if they have no work to do, for example,...

Apologies, it is actually a 2008 version with no service pack yet.

2008Enterprise EditionRTM

Can anybody shed some more lights on this?

Thanks again!

I am still facing this issue till now on one of my servers.

Can any of the "ten centuries" shed some lights on this topic?

Thanks very much again!

I am using 2005 epress edition and this sp_msforeachdb actually exists at master.sys.sp_msforeachdb, strangely, when I run just 'sp_msforeachdb' the system doesn't recognize. But when I use 'master.sys.msforeachdb', this is...

I am experiencing this trouble as well.

For database file migration project, the start-up parameters for master database has to be reset through configuration manager, but the MSSQLSERVER service is simply...

Or another question, is it possible to use another configuration manager to connet to this server?

BTW, the Windows Management Instrumentation service is also running fine in the services mmc.