I have a batch file that runs a mkdir command (DOS command for creating a new directory). I execute that batch file with an execute process task in a package. Right now that is the only thing in this package. I deployed the package to the server and I see it when I log into the management studio. I right click on the package and run it. Everything works as expected and the folder gets created. Now the problem. I run that same package in a SQL Server Agent job. I run the job and nothing happens and the the job stays running and never finishes or errors. Any idea what may be happening? The directory I am creating in the mkdir command references a drive letter that exists on the server. Besides, if I were to have specified a location that is not accessible from the server, I would get an error, but I don't. The job just keeps running and nothing happens.

why not using the File System Task for creating a folder? Or is there a good reason for the batch file. Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com | Twitter

Maybe to do with the privileges for the SQL Server Agent account? Check if the account under which the SQL Server agent is running has permissions to run an exe. The account should have administrator access to run an exe.Karthik

This is just an example to boil down the problem of calling a batch file. In reality I need to run a BCP out, but didn't want to complicate the discussion. It turns out, some windows security thing was waiting for the user to say "OK" to a prompt that asked if it is ok to run the batch file.