...and a bit more info...created a SQL Server Agent job that runs :

xp_cmdshell 'c:\blah.exe'

This runs under the Agent ( agt ) user id that has the same priviledges as the...

I've spent a bit more time on this and I've discovered that if you log onto the box as the SQL Server user, you can run taskkill OK, no problems.

I...

Hi - SQL Server (MSSQLSERVER) in Services logs on as <<domain>>\<<server>>adm.

This is the same user that xp_cmdshell is running as.

That user is in the Admin group for the server.

thansk -...

...EXEC master.dbo.xp_cmdshell 'SET USERNAME'...

...that user is in the Admin group...

...hhhm, I was happy it was working until I realised it wasn't returning a return code!

When run as a cmdexec, the step either returns 1 or 0. As xp_cmdshell it...

...thanks for the suggestion, I'll give it a go...

S

...by a strange coincidence we're upgrading to 2005 in a few months time. Would have been nice to have resolved the issue instead of it just going away tho!

thanks -...

...occurs 9 times out of 10. As it happens, server was re-booted on Sunday. 'Failure' ( note use of quotes! ) occured Monday, Tuesday and today, but was fine Wednesday...

The...

...final attempt to get to the bottom of this one... ran trace, set sql agent to trace messages, created output file for CmdExec... result :

i) CmdExec log file empty

ii) No...

hey, I'm just glad that someone has experienced the same pain I'm going thru'! I've Googled the error code extensively and everything I've found related to DTS and SSIS...

S

...amazing how many issues dissapear when you throw hardware at them! Did the behaviour I saw in the trace file sound familiar? i.e. Commits successfully and then appears to be...

Hi - Has anyone come up with a definitive answer to this problem? Hoping so as I'm experiencing a similar issue with a scheduled job on SQL Server 2000.

It's running...