Showing results for 
Search instead for 
Did you mean: 

Unknown user name or bad password

Level 3

We are seeing a lot of log entries on our workgroup servers that look like the following. The BE server is a memeber of a domain, and the BE services run under domain admin credentials. The login id's that fail are the ones used by the BackupExec services on the BE server and the guest account. The BackupExec services on the system being backed up and the BackupExec jobs are configured to use local admin accounts to access these systems. Why does it try to connect using accountnames other than the ones configured in the job?


Host : <servername>

Application : Security

Time  Generated : Wed Jul 04 22:04:22 2007


Criticality : Failure

EventID : 529

Occurance : 1

Message : Logon Failure:

     Reason:           Unknown user name or bad password 

     User Name:  <username> 

     Domain:           <MyDomain>

     Logon Type: 3

     Logon Process:    NtLmSsp

     Authentication Package: NTLM

     Workstation Name: <BackupExec Server>

     Source Network Address: (BE server IP)

    Source Port:      0


Level 4
We are having a similar problem were we have to retype the password in each BE service every time the server restarts or even if we restart just the BE services. You can try that until you get an answer...

Level 3
Thanks for the info, but our backups are completing successfully. The only issue is that we are creating entries in our security logs that I would like to avoid

Level 2
Did you ever find a solution to the Event ID: 529 error?
I have the same issue with Veritas 10D sp3, The Jobs still complete sucessfully but the logs are filling up on the backup server.
I had Veritas 10 with out error and when i upgraded to 10D  the errors started and it looks like i would have this problem if i went to 11D.

Level 3
No resolution to this yet, still looking

Level 2
I was able to fix the problem by removing the  backup server from the domain and the adding it back.
I wish the techsupport people could have answered this question many weeks ago.

Level 2

I'm having this same issue.  The backup job for server-A contains the correct credentials and completes normally.  But ever day the Backup Exec Server tries to logon to server-A using the wrong credentials and is logged in the Security Event Log.  It seems like Backup Exec is checking every day to see if it still can communicate with server-A but uses the wrong credentials.

Employee Accredited Certified


As this thread was originally created against Backup Exec 11D back in 2007 I assume that you might be running a more recent version of BE.


The newer versions of BE have an option that is enabled by default to "Discover Data to Backup Up" which might be trying to connect to servers across your nwetwork and then working fine aganst the servers that are members of the domain, but perhaps causing these entries if you have workgrouped systems with different credentials. If this is the cause then the security warning shoud always be at the same time of day and the time will be close to that is configured against the "Discover Data to Backup" settings. All affected servers wil also show the times as being close to each other AND the times won't be close to significant steps against any running Backup Jobs (Job Start, Media Mount, changing between resources being backed up, Job End etc)


Thank you. I checked and the Backup Exec 2012 was set to discover data to back up every day. I turned this off and will monitor the Security Event log to see if that fixes it. Thanks again. Doc