ASP.NET Process Start PowerShell Script IIS 7.5

Question

All works fine on my dev machine but if deployed to IIS the process doesn't get started. I am starting a powershell script by

    private void RunScript()
    {
        Process process = null;
        try
        {
            int timeout = 1800000;
            var startInfo = new ProcessStartInfo
            {
                FileName = @"powershell.exe",    
                Arguments = string.Format("{0} {1}", "\path\toscript", "myParam"),
                UseShellExecute = false,
                CreateNoWindow = true
            };                   

            process = Process.Start(startInfo);
            process.WaitForExit(timeout);
        }
        finally
        {
            if (!process.HasExited)
            {
                if (process.Responding)
                    process.CloseMainWindow();
                else
                    process.Kill();
            }
            if (process != null)
            {
                process.Close();
                process.Dispose();
            }
        }  
    }

Here's what's configured for the app pool this is running under.

Process Model
->Identity = domain user who is a Domain Admin.
->Load User Profile = True

Web App
Authentication is Windows

What else do I need to configure to so that I can run the Process?

dmuun · Accepted Answer · 2011-10-24 21:14:05Z

As Start-Automating suggested I eventually ended up doing this:

            using (Runspace runSpace = RunspaceFactory.CreateRunspace())
        {
            try
            {
                runSpace.Open();
                RunspaceInvoke scriptInvoker = new RunspaceInvoke(runSpace);
                scriptInvoker.Invoke("Set-ExecutionPolicy Unrestricted"); 
                using (Pipeline pipeLine = runSpace.CreatePipeline())
                {                        
                    var myCommand = new Command(scriptPath);                           
                    var myParam1 = new CommandParameter("-paramName", "someValue"); 
                    myCommand.Parameters.Add(myParam1);
                    pipeLine.Commands.Add(myCommand);       
                    pipeLine.Commands.Add("Out-String");
                    Collection<PSObject> returnObjects = pipeLine.Invoke();
                    runSpace.Close();

                    return returnObjects;                                              
                }
            }
            finally 
            {
                runSpace.Close();
            }
        }

On the IIS server I executed the following powershell command "Set-ExecutionPolicy RemoteSigned"

LosManos · Accepted Answer · 2019-02-24 20:40:14Z

1

It's much better to embed the PowerShell APIs the call the .exe

Here's an old link that will get you a PowerShell runspace embedded in ASP.NET per user:

http://powershellpipeworks.com/

edited Feb 24, 2019 at 20:40

LosManos

7,7826 gold badges61 silver badges120 bronze badges

answered Oct 22, 2011 at 18:49

Start-Automating

8,4372 gold badges33 silver badges50 bronze badges

Comments

rick schott · Accepted Answer · 2011-10-21 20:45:51Z

0

Check the permissions of the file system where powershell.exe lives.

Also, check the Security Log in the Event Viewer for authentication errors and access violations.

answered Oct 21, 2011 at 20:45

rick schott

21.1k5 gold badges54 silver badges81 bronze badges

1 Comment

dmuun Over a year ago

The app pool domain account being used is also member of the Administrators group on the machine. So on C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe the Administrators group has Read, Read & Execute permissions. Is that sufficient rights?

Collectives™ on Stack Overflow

ASP.NET Process Start PowerShell Script IIS 7.5

3 Answers 3

Comments

Comments

1 Comment

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

1 Comment

Related