Problem with operating system.
-
I have windows service which starts a process using System.diagonist.Process.Start(process name); I have the service interact with desktop and it works fine when tested on windows xp 2002(service pack 2). i.e the service invokes the process. But when I install the same service on windows server 2003 the process doest starts. I am very confused why this is happening can u plz help me.
-
I have windows service which starts a process using System.diagonist.Process.Start(process name); I have the service interact with desktop and it works fine when tested on windows xp 2002(service pack 2). i.e the service invokes the process. But when I install the same service on windows server 2003 the process doest starts. I am very confused why this is happening can u plz help me.
justintimberlake wrote:
I have the service interact with desktop
This is probably why. Interacting with the desktop requires a user to be logged on. With XP this is not a problem as xp also requires a user for most operations, whereas windows server 2003 do not. Hope this helps you a bit.
-
justintimberlake wrote:
I have the service interact with desktop
This is probably why. Interacting with the desktop requires a user to be logged on. With XP this is not a problem as xp also requires a user for most operations, whereas windows server 2003 do not. Hope this helps you a bit.
thanx very much for your response. but still is there any solution. or is it impossible
-
thanx very much for your response. but still is there any solution. or is it impossible
I think you can have the process run under a specific user account; this requires your code to provide username and password to the appropriate ProcessStartInfo members in Process.StartInfo (if you are willing to provide those in your code, it looks like a security risk...) Also, you should log the complete Exception.ToString() that must occur right now when it fails to run on Windows Server; it probably tells you exactly what is failing. :)
Luc Pattyn [My Articles] [Forum Guidelines]
-
I think you can have the process run under a specific user account; this requires your code to provide username and password to the appropriate ProcessStartInfo members in Process.StartInfo (if you are willing to provide those in your code, it looks like a security risk...) Also, you should log the complete Exception.ToString() that must occur right now when it fails to run on Windows Server; it probably tells you exactly what is failing. :)
Luc Pattyn [My Articles] [Forum Guidelines]
well i did that but still no help !!!
-
well i did that but still no help !!!
Either Process.Start fails and produces an Exception, or the process starts and maybe exits due to some error condition. Which is it, and what exception/error occurs ? :)
Luc Pattyn [My Articles] [Forum Guidelines]
-
Either Process.Start fails and produces an Exception, or the process starts and maybe exits due to some error condition. Which is it, and what exception/error occurs ? :)
Luc Pattyn [My Articles] [Forum Guidelines]
i get process starts only in the back ground
-
i get process starts only in the back ground
in xp 2002 it starts in forground as well