User keeps losing logon as service right after a power outage

[Guest]

Hi All:

I have developed a .NET windows application which uses a third party
database server. The db server can be installed as a service but the user
which starts this service must be very restricted due to security reasons.
So in the installation of my application I first create a user and then I
install the db server and then I install my application. I use following
script to create the user:

net user /add /y dbuser password /EXPIRES:NEVER /COMMENT:"DB Service
Account" /FULLNAME:"DB Service Account"

ntrights -u dbuser +r SeServiceLogonRight
ntrights -u dbuser +r SeNetworkLogonRight
ntrights -u dbuser +r SeInteractiveLogonRight


This works fine initially till the clients have power outage. Once they
start PC back up after power has come back, for some reason this user can't
start the db service. The error we get is "1069 logon failure". Basically
to fix this problem I have to go into "users and password" and set the
password for this user again to the same password as original during install
time and then every thing starts working.

I am not sure why after a power outage this user would lose its password?

Maybe the way the user is created or given the rights is not correct?

Any help in this regard would greatly be appreciated.

Thanks

Karim

 

[Steven L Umbach]

If a password reset fixes the problem then it is not a problem with user
rights but apparently a problem with the password expiring. You can use the
command net user username to see details about a user account after it has
been configured to see if it is what you expect. Also check to see if there
are Group Policy startup scripts that may be executing on startup causing a
problem and look at their user account properties to make sure that "user
must change password at next logon" is not checked which I suspect may be
the problem. Use lusrmgr.msc and go to users to check the user account
properties for the particular user. --- Steve