RE: ServiceBase denies access to service name
- From: nickdu <nicknospamdu@xxxxxxxxxxxxxxxx>
- Date: Thu, 15 Jan 2009 07:00:01 -0800
As I indicated in a reply to Stephen, my original statement appears to be
correct. The service name for a win32 own service is specified as the first
argument on the command line. The .NET implementation should not skip over
this argument but instead use it to set the service name.
--
Thanks,
Nick
nicknospamdu@xxxxxxxxxxxxxxxx
remove "nospam" change community. to msn.com
""Hongye Sun [MSFT]"" wrote:
Thanks for your reply and feedback, Nick. Stephen has posted a great answer.
to your question regarding ServiceMainCallback. This seems to be limitation
issue. I will forward your message to proper channel and product team.
For the WMI method, I suggest you to have a try of it, since this is a very
simple usage in this case and we have run the service in our lab for many
times without any error.
Have a nice day.
Regards,
Hongye Sun (hongyes@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
This posting is provided "AS IS" with no warranties, and confers no rights.
- Follow-Ups:
- RE: ServiceBase denies access to service name
- From: "Hongye Sun [MSFT]"
- RE: ServiceBase denies access to service name
- Prev by Date: Logging Application Block - How to modify settings in code?
- Next by Date: WPF M-V-VM List View
- Previous by thread: Re: ServiceBase denies access to service name
- Next by thread: RE: ServiceBase denies access to service name
- Index(es):
Relevant Pages
|
Loading