question

@paws27284 Is it possible that the path is incorrect? What is **d**? If it is a drive name then should it be **d$** (admin share)? Please check that pasting the path (without the file name) into windows explorer window address bar actually opens the folder containing the file. If it does then please ask the user to do the same. It looks like the problem might be related to either the spelling of the file path or else to the lack of permissions for that user to the share where the file is located. <\!-- **Begin Edit** You can try using the C# code below, it should help to figure out the source of the problem. Generally speaking, when you use sqlcmd to execute the script from the file, and the script executes the procedure to start a job then the following must take place: The Active directory user (the one who is invoking the batch file from her computer) does not need any permissions to the SQL Server, but does need to have at least READ permission to read the contents of the .SQL file. If logging is desired then she also must have the permissions to write to the log file The user specified with user ID and password (SQL Authentication) must: - Exist as a valid login on the SQL Server instance - Exist as a user in msdb database (mapped to that login) - Have a role membership to SQLAgentUserRole and SQLAgentOperatorRole msdb database roles. For example, suppose that the login info specified in the sqlcmd file is valid, which means that it already exists as a valid login to that SQL Server instance. Running the script below will create a user in msdb database and add the user to the database roles, which is necessary to have enough permissions to execute the procedure to start the job. use msdb; go -- create user in msdb database create user [some_user] for login [some_user]; go use msdb; go -- make the user a member of 2 database roles: exec sp_addrolemember N'SQLAgentUserRole', N'some_user'; go exec sp_addrolemember N'SQLAgentOperatorRole', N'some_user'; go Below is the C# code you can use. If you have a Visual Studio then create a Console application named MonthlyExtractExecutor and then add a reference to System.Configuration. Paste the code below into it: using System; using System.Configuration; using System.Data; using System.Data.SqlClient; using System.IO; namespace MonthlyExtractExecutor { class Program { static void Main(string[] args) { string filePath = ConfigurationManager.AppSettings["filePath"]; string connection = ConfigurationManager.ConnectionStrings["main"].ConnectionString; try { // First step is to access the file located in the shared folder on network // The Active Dirtectory user running this program must have access to it Console.WriteLine("Trying to access the file, please wait..."); using (StreamReader reader = new StreamReader(filePath)) { // read the first line from the file, it should contain the call to execute sp_start_job proc Console.WriteLine("Reading the first line in the file, please wait..."); string sql = reader.ReadLine(); // try to open connection and then execute the job. For this to succeed, the following must happen: // The user (the one specified with user id and password in the config file) has to // be a valid user in msdb database // be granted the SQLAgentUserRole and SQLAgentOperatorRole database roles in msdb database using (SqlConnection cn = new SqlConnection(connection)) { Console.WriteLine("Trying to open connection, please wait..."); cn.Open(); using (SqlCommand cm = new SqlCommand()) { cm.Connection = cn; // generally speaking, it would be better to specify the command type as StoredProcedure, // provide the name of the procedure and pass parameters, but the code below is used just // to create a scenario from the original question cm.CommandType = CommandType.Text; cm.CommandText = sql; Console.WriteLine("Trying to execute the procedure to start the job, please wait..."); cm.ExecuteNonQuery(); } // command object instance is disposed cn.Close(); } // connection instance is disposed :) reader.Close(); } // reader is disposed } catch (Exception ex) { Console.WriteLine("Error Message: " + ex.Message); Console.WriteLine("\r\n\r\nStack Trace: " + ex.StackTrace); } Console.WriteLine("All done, please press any key to end."); Console.ReadLine(); } } } Before running the application, please add the connection string details and path to the sql file to the app.config file. If the solution explorer in Visual Studio does not show that the app.config file is already there then add new item -> application configuration file from the right-click menu of the project: If you compile and run the application, it will do what sqlcmd was meant to do, but it will let you kinda debug it by spelling out what it is doing step by step and bailing out if any error occurs. Because it is a .NET app, it does not really need any installation package. You can just have the user to login to her computer, copy the contents of the bin\\Debug folder to it and then have her to double-click on the executable file to run the job. This will complete if all is well and write out the error information if something is wrong. For example, if the SQL user does not have membership roles in msdb database then you will get the error stating the job named Monthly extract does not exist. If the user or password or server info is incorrect then it will tell you that the connection to the server could not be established or login failed. If the Active Directory User who is running the app does not have permissions to the file then you will see this error information. Please let me know if this helps. Oleg **End Edit** --\>