Process.Start in a windows service

[Daniel Reber]

I am trying to start a process from a windows service but when the process
starts the command window that the process runs in never shows. Is this
because I am calling it from a windows service? Is there something else
that I need to do?

Here is my code:

System.Diagnostics.ProcessStartInfo info = new
System.Diagnostics.ProcessStartInfo();

info.FileName = "DTSRun";
info.Arguments = server.ExeSyntax; //Arguments for dtsrun
info.WindowStyle = System.Diagnostics.ProcessWindowStyle.Maximized;
System.Diagnostics.Process.Start(info);
Thanks

Dan Reber

[Willy Denoyette [MVP]]

"Daniel Reber" <no****@nospam.com> wrote in message
news:uY**************@TK2MSFTNGP11.phx.gbl...

I am trying to start a process from a windows service but when the process
starts the command window that the process runs in never shows. Is this
because I am calling it from a windows service? Is there something else
that I need to do?

This because the Service runs in the context of a non interactive desktop,
if you start another process froms this parent process, the child will run
in the same non visible desktop.

What you could do (but I hate the idea because it opens a security hole as
big as the Ozon hole), is to set the service to interact with the desktop.

Willy.

[Daniel Reber]

That worked, thanks. What kind of holes? Is there any other way for a
windows service to start an executable that has UI?

Thanks for your help.

Dan.

"Willy Denoyette [MVP]" <wi*************@pandora.be> wrote in message
news:Ow**************@TK2MSFTNGP09.phx.gbl...

"Daniel Reber" <no****@nospam.com> wrote in message
news:uY**************@TK2MSFTNGP11.phx.gbl...

I am trying to start a process from a windows service but when the process starts the command window that the process runs in never shows. Is this
because I am calling it from a windows service? Is there something else
that I need to do?

This because the Service runs in the context of a non interactive desktop,
if you start another process froms this parent process, the child will run
in the same non visible desktop.

What you could do (but I hate the idea because it opens a security hole as
big as the Ozon hole), is to set the service to interact with the desktop.

Willy.

[Willy Denoyette [MVP]]

"Daniel Reber" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

That worked, thanks. What kind of holes? Is there any other way for a
windows service to start an executable that has UI?

A lot of info can be found on MSDN about security and elevating security
privileges when running services in the interactive winstation ( start with
KB Q327618).

Willy.

[Daniel Reber]

I will look into it.

Thanks for your help.

Dan
"Willy Denoyette [MVP]" <wi*************@pandora.be> wrote in message
news:Oy**************@TK2MSFTNGP10.phx.gbl...

"Daniel Reber" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

That worked, thanks. What kind of holes? Is there any other way for a
windows service to start an executable that has UI?
A lot of info can be found on MSDN about security and elevating security
privileges when running services in the interactive winstation ( start

with KB Q327618).

Willy.