Argument list being passed to system service on start up is garbled
I am trying to start a service on a Windows Server 2003 R2 system which requires an argument list (string array) be provided in order for it to start correctly. The process of doing it this way has been vetted and normally works fine. This is a new system that has not been fully configured. If it helps, the sofware that is being executed is using the System.ServiceProcess functionality within the 1.1 .NET framework. (I am not sure what underlying transport capability this uses.)My problem is this, when I attempt to start the service it tries to start, but the incoming argument list is completely meaningless, filled with strange characters. The size of the array is correct.Does anyone know, or have any experience with what could be causing this?? What service handles these requests? I'm thinking either character encoding, security, group policy setting, or maybe incorrect permission setting.Any ideas or solution would be greatly appreciated.Dave
January 7th, 2010 2:10am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics