Re: User keeps losing logon as service right after a power outage

From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 10/31/05

  • Next message: Steven L Umbach: "Re: Default owner of Files & Folders for an Administrator Account"
    Date: Sun, 30 Oct 2005 20:59:31 -0600
    
    

    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

    "Karim Mardhani" <KarimMardhani@discussions.microsoft.com> wrote in message
    news:F4AE15B4-9ECE-4362-AE9E-304A94F7EE95@microsoft.com...
    > 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


  • Next message: Steven L Umbach: "Re: Default owner of Files & Folders for an Administrator Account"

    Relevant Pages

    • Re: sql server installation hung/slow
      ... >> Server. ... >> Try to Install SQL Server and let us know if there is any difference. ... >> This posting is provided AS IS with no warranties, and confers no rights. ...
      (microsoft.public.sqlserver.server)
    • Re: Help with Exchange 5.5 IS
      ... deals with performance issues of the server, ... Please do not send email directly to this alias. ... This posting is provided "AS IS" with no warranties, and confers no rights. ... >> that you'll want to install. ...
      (microsoft.public.exchange.applications)
    • Re: Setting up MS Virtual Server 2005
      ... This posting is provided "AS IS" with no warranties, and confers no rights. ... "Meinolf Weber" wrote: ... You have to install a server OS the same you as would install it on ...
      (microsoft.public.windows.server.general)
    • Re: Windows 2003 Users vs Software
      ... The users do not have rights to install programs. ... >>running off the server. ... While you are right about admin rights on the local server, ...
      (microsoft.public.security)
    • Windows 2003 - User Logins vs Software
      ... We have recently installed a Windows 2003 domain server. ... Some of the software will not work unless the user has administrative rights ... I have tried several ways to install in the software. ... Install software under his/her username with the Administrator permissions ...
      (microsoft.public.windowsxp.security_admin)