Service install problem

[John]

Hi

I have a vb.net service app which I have set to run as user. When I try to
install the service via InstallUtil, I provide user/pass for the
administrator but the service fails to install. I have received the
following two messages on two separate occasions;

An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: No mapping between account names and
security IDs was done

and

An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: The account name is invalid or does
not exist, or the password is invalid for the account name specified

What is the problem and how can I solve it? The reason I am trying to
install the service as administrator is that the service can not open an
access db from a shared network drive if the service runs as LocalSystem.

Thanks

Regards

 

[Guest]

Hi,

This is the same as my requirement and I am also facing the same problem. Can anyone please give some idea how to solve this?

Thanks & Regards,
Joydeep

Hi

I have a vb.net service app which I have set to run as user. When I try to
install the service via InstallUtil, I provide user/pass for the
administrator but the service fails to install. I have received the
following two messages on two separate occasions;

An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: No mapping between account names and
security IDs was done

and

An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: The account name is invalid or does
not exist, or the password is invalid for the account name specified

What is the problem and how can I solve it? The reason I am trying to
install the service as administrator is that the service can not open an
access db from a shared network drive if the service runs as LocalSystem.

Thanks

Regards

User submitted from AEWNET (http://www.aewnet.com/)

 

[Cecil Martin]

I would suggest that you write your service to call another application that
actually does the work: a "Worker Process" if you will. Then set your
service to run as local system account. All the service will be doing is
starting an instance of the worker process, and the worker process will be
accessing your database across the network.