[AnalyticLunatic]

I have created a console application that is run as a Job Agent Step in SQL Server by running the console's .exe. The .exe gathers information from a database view, updates a file with the information, and then ftp's the file to a web server for processing.

In my VS2010 Solution and in my published application, all works well, but the in SQL Server I continue to get:

Executed as user: XXX\XXXXX. The step did not generate any output. Process Exit Code -2146232576. The step failed.

Anyone have any ideas what I am doing wrong? Any help would be greatly appreciated as this is outside my normal skill-set...

[thava]

i am not sure, what kind of permission do you give to run a exe in server, seems your process is some where getting disturbed, or even not respond

just read this link i think this will help you

[AnalyticLunatic]

Thanks for the response thava. According to my Superior I do not have permissions to run the job as (Run->Start at Step#), but by scheduling the job to run at a certain time, the Server Account has permission. The odd thing is this console application is a direct mock-up of another FTP Console Application which is run in the exact same Job as Step #1 (successfully), run with the exact same command, from the same shared folder on the Server.

I'm at a total loss as to why it is not executing.

Job Step Details
Step Description: FTP DateFile
Step Type: Operating system (CmdExec)
Step Run as: ProxySSISFileTranser

Command: X:\Folder\Application.exe

Log Message/Details
Message: "Executed as user: XXX\XXXXX. The step did not generate any output. Process Exit Code -2146232576. The step failed."
Duration: 00:00:00
Sql Severity: 0
Sql Message ID: 0

[thava]

is the drive x: exist in the server or is it a share folder

[AnalyticLunatic]

Thanks for all the help thava. I found out the issue was due to the new application being compiled in .NET Framework 4 while the server only had Framework 3.5 Installed.

[thava]

well that was a close one any way nice work buddy