Forum Discussion

vjsanchez's avatar
vjsanchez
Level 3
13 years ago

"Netbackup Client Service" doesn't start: windows error 1057. NB 7.0 Windows Server 2003 x86

Hi all,

I have a Windows Server 2003 SP1 x86 with a NB 7.0 client installed. Recently I have rebooted it due to Windows updates. After that "Netbackup client service" doesn't start and I receive the windows error 1057 "The Account Name is Invalid or Does Not Exist".

Before reboot this service was configured with a local windows account and it worked fine. This account have never changed nor password. I need this NB service works on local account due to several backup scripts.

I have tried all: another local account with necessary rights (Manage auditing and security log, act as part of the operating system, create a token object, member of "Backup operators" windows group, ...), re-install NB software, ..., without successfull results.

Has anyone have this issue too? Thanks.

 

7.1.x and Earlier
Backing Up
Backup and Recovery
NetBackup
Windows
  • Mark_Solutions's avatar
    Mark_Solutions
    13 years ago

    Just re-read this thread ....

    Are you saying that the client service runs fine as Local System, just not as anything else?

    The account you use must have visibility of the domain, if a domain account, and should be added to the local admins groups on the server.

    When you add an account to a service it should give it extra rights so you also need to check that these have been allowed when it was added. They are as below - as per tech note listed:

    http://www.symantec.com/docs/TECH50318

    The NetBackup Client Service was being started by an account other than the local system account.  The NetBackup Client Service must be started an account which has the following permissions:


    - Act as part of the operating system

    - Replace a process level token

    - Logon as a service

    - Create a token object


    Change the permissions for the account starting the NetBackup Client Service and restart the service.  It may be necessary to wait 10-15 minutes for replication throughout the Windows environment to occur for all changes to take affect. 

    Hope this helps
     

     

  • vjsanchez's avatar
    vjsanchez
    Level 3
    13 years ago

    Hi,

    the service has always running with this local account (not domain account) until server has to been rebooted by Windows updates.

    When I reinstalled NB client software I choose the local account again (see picture attached). I checked in "Local Security Policies" that local account has right permissions.

     

     

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    13 years ago

    Dont know if you have looked into it but do you have any Anti Virus / Firewall on this client - have you tried turning them off to see if they are affecting it.

    If McAfee you need to disable Access Protection as well if it is used and may also need to disbale the firewall driver by renaming C:\WINDOWS\system32\drivers\MFETDIK.sys and rebooting.

  • vjsanchez's avatar
    vjsanchez
    Level 3
    13 years ago

    I uninstall anti-virus software (Panda), re-install NB client and install anti-virus again. Now I running a complete anti-virus scan of the machine.

    I have tried to create a new service with "sc create" command and I obtain the same error.

    Is really necessary configure NB client service with a domain windows account instead of local windows account?