Problem on installing Windows services

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

cindy liu - 09 Jan 2004 18:42 GMT

Hi Everyone,

I created a Windows service and its setup project on one
of my machines. The setup ran without any problem.
However, when I moved the same Windows service project and
its setup project to another machine and ran the setup. I
got the error, saying "The account name is invalid or does
not exist, or the password is invalid for the account name
specified."

I did noticed that when installing on the first machine,
the default selected folder is "c:\Program
files\Invensys\LmxServiceSetup". When installing on the
second one, the folder name is "c:\Program
files\Wonderware\LmxServiceSetup".

So I recreated my two projects on the second machine. I
still got the same problem. One of dependent dll of my
Windows service had the strong name. I also recreated that
strong name for that dll. Still doesn't solve the problem.

Has anyone encountered this problem before? Please help me
out!

Thanks in advance!!!!!
Cindy

Reply to this Message

Phil Wilson - 11 Jan 2004 18:50 GMT

The values for Manufacturer are sometimes retrieved from the registry (I
forget the exact location) but you can set the values in project
properties - the default folder name includes Manufacturer, and you can
change that.

Exactly where did you see that error? A messagebox from the installation?
And was there an error number such as 1926? If this is a .NET Service with
an Installer class, what configuration have you done regarding local system
account etc?

Signature

Phil Wilson
[MVP Windows Installer]

> Hi Everyone,
>
[quoted text clipped - 22 lines]
> Thanks in advance!!!!!
> Cindy

Reply to this Message

cindy liu - 12 Jan 2004 22:09 GMT

Hi Phil,

Thanks for replying my posted question!

My project is a .NET Service with an Installer class. I
set the account property of serviceProcessInstaller1 to
LocalService and the StartType of serviceInstaller1 to
Automatic. I didn't set Username and Password of
ProjectInstaller.cs, they are all null.

I don't think this problem related to Manufacturer.
Because I somehow made one of my machine worked with
different Manufacturer name. I don't know what made it
worked on that machine. Then I tried another machine. I
got the same problem again. Do you know where is the
problem?

Thanks,
Cindy

>-----Original Message-----
>The values for Manufacturer are sometimes retrieved from the registry (I
[quoted text clipped - 34 lines]
>
>.

Reply to this Message

cindy liu - 12 Jan 2004 22:22 GMT

Hi Phil,

Sorry, I forgot to anwser your questions. I see that error
in a message box without any error number, just the
description I mentioned in my first post.

Thanks,
Cindy

>-----Original Message-----
>The values for Manufacturer are sometimes retrieved from the registry (I
[quoted text clipped - 34 lines]
>
>.

Reply to this Message

Phil Wilson - 13 Jan 2004 23:31 GMT

LocalService is not a valid account on Windows 2000, only on XP and higher - is
that the problem?

Signature

Phil Wilson [MVP Windows Installer]
----

> Hi Phil,
>
[quoted text clipped - 57 lines]
> >
> >.

Reply to this Message

cindy liu - 15 Jan 2004 03:39 GMT

I'm running Windows 2003. So LocalService account should
work. It makes sense the installer doesn't work on Windows
2000. On Windows 2000, after I changed to LocalSystem, the
problem goes away.

On Windows 2003, if I changed to LocalSystem, it also
worked. Why using LocalService on Windows 2003 doesn't
work?

I also tried to use User. That means when I install my
service, the installer pops up login dialog box to get
user name and password and runs the service as that user.
The same problem also happens on Windows 2003 box. Do you
know why?

Thanks,
Cindy

>-----Original Message-----
>LocalService is not a valid account on Windows 2000, only on XP and higher - is
[quoted text clipped - 62 lines]
>
>.

Reply to this Message

Phil Wilson - 29 Jan 2004 00:02 GMT

I think that dialog box is expected behavior when the Account property is User :
Quoting from the Account property docs:

"When the Account property is User, the Username and Password properties are
used to define an account under which the service application runs.
The Username and Password pair allows the service to run under an account other
than the system account. This can, for example, allow the service to start
automatically at reboot, when no user is logged on. If you leave either the
Username or Password empty and set Account to User, you will be prompted for a
valid user name and password at installation.
You can also specify that the service run under the local system account, or as
a local or network service."

Signature

Phil Wilson [MVP Windows Installer]
----

> I'm running Windows 2003. So LocalService account should
> work. It makes sense the installer doesn't work on Windows
[quoted text clipped - 93 lines]
> >
> >.

Reply to this Message

Problem on installing Windows services

Free Magazines