Here is a picture of the list:

Hi Hadu

 

This sounds like a permissions issue or possibly a very corrupted installation.

 

Check the Backup Exec Service Account (BESA)

 

HOW TO FIND WHICH ACCOUNT IS THE BESA
=====  =====  =====  =====  =====  =====  =====  =====  =====

1. Go to Windows Services
2. You will see a group of services starting with Backup Exec
3. They should all be using the same account except one
  a). Backup Exec Remote Agent will be different
  b). The remote agent service always uses Local System Account
4. That account is the BESA
5. Within Backup Exec™, go to Network> Logon Accounts
6. Make sure the BESA (3 & 4 above) is marked YES for Default and is a Common account

    Make sure BESA is not a member of these 2 groups (especially)

         The Domain Power Users group

         The Remote Operators group

 

Next

- From within Backup Exec go to the NETWORK menu
- Select LOGON ACCUNTS...
- The "Logon Account Management" window will appear
- There are 5 columns in the main window
   Account Name - Description used by the Backup Jobs
   User Name    - Actual logon account we are concerned about
   Default      - Will be either YES or <blank>
   Type         - Will be either RESTRICTED or COMMON
   Owner        - Name of account that was logged on when this account was created
- From here you can either add, edit, or delete accounts
- NOTE: Having more accounts here than needed may cause authentication issues

 

Make sure BESA is set as the Default account and is a common account.

Insure BESA does not have the "Deny log on locally" policy setting.

 

Finally check the following (steps are for a non-DC server)

1 Start> Programs> Administrative Tools> Local Security Policy (or ...Settings)
2 Security Settings> Local Policies> User Right Assignments

3 Add BESA specifically to the following rights:

 -Act as part of the operating system
 -Backup files and directories
 -Create a Token Object
 -Logon as a service
 -Manage auditing and security log
 -Restore files and directories

 

If all these are set properly, then you need to look at the installation.

 

Hello,

if the problem is a corruptet installation then this happend 5 times. Even the operating system is a new, clean installation.

 

The Backup exec service account is domain admin. I removed the accuont from the domain users.

Following rights were missing in the local security setting:

- act as part of the operation system

- create a token object

 

I added the rights and rebooted the server, but there is still an empty selection list.

 

What could be wrong with the installation?

The server environment check only asks for a AntiVirus check and not to install with mapped drives with terminal services. All other checks are passed.

In the feature list are

- Tape Device Drivers

- Online Documentation

- Enable Robotic Library Support

selected. The rest of the installation is without any error messages. All updates are installed with "LiveUpdate".

I repeated the installation several times.

Even the installation wth Symantec Backup Exec 10d has the problem with the empty selection list.

Then I installed the Windows Server new. Even then there is an empty selection list.

 

Thanks,

 

Harald

 

 

Have you found a resolution to this issue?  I have a 2003 SBS with BE 11d, and started to get this error on Tuesday the 31st.

Hello,

I made everything new - onley the serive account was the old one. Although the account was a domain admin it didn't work.

Now I created a new service account and it works.

 

Cheers,

Harald

 

 

I created a new service account, restarted the services, and even the server.  I am still getting the same error.  What do you mean by "you created everything new"?  After changing the service account, I've tried to create a new job and still see that the selection list is giving me the same error.

everything new means that I deleted everythig, installed Windows and then BE

Did you check the settings from Lou Buffetta?

Check the Backup Exec Service Account (BESA)

 

HOW TO FIND WHICH ACCOUNT IS THE BESA
=====  =====  =====  =====  =====  =====  =====  =====  =====

1. Go to Windows Services
2. You will see a group of services starting with Backup Exec
3. They should all be using the same account except one
  a). Backup Exec Remote Agent will be different
  b). The remote agent service always uses Local System Account
4. That account is the BESA
5. Within Backup Exec™, go to Network> Logon Accounts
6. Make sure the BESA (3 & 4 above) is marked YES for Default and is a Common account

    Make sure BESA is not a member of these 2 groups (especially)

         The Domain Power Users group

         The Remote Operators group

 

Next

- From within Backup Exec go to the NETWORK menu
- Select LOGON ACCUNTS...
- The "Logon Account Management" window will appear
- There are 5 columns in the main window
   Account Name - Description used by the Backup Jobs
   User Name    - Actual logon account we are concerned about
   Default      - Will be either YES or <blank>
   Type         - Will be either RESTRICTED or COMMON
   Owner        - Name of account that was logged on when this account was created
- From here you can either add, edit, or delete accounts
- NOTE: Having more accounts here than needed may cause authentication issues

 

Make sure BESA is set as the Default account and is a common account.

Insure BESA does not have the "Deny log on locally" policy setting.

 

Finally check the following (steps are for a non-DC server)

1 Start> Programs> Administrative Tools> Local Security Policy (or ...Settings)
2 Security Settings> Local Policies> User Right Assignments

3 Add BESA specifically to the following rights:

 -Act as part of the operating system
 -Backup files and directories
 -Create a Token Object
 -Logon as a service
 -Manage auditing and security log
 -Restore files and directories