The Backup Exec Remote Agent is suspended when it is started on a remote server. The System Event Log On the remote server lists event ID: 7022, which is described: the Backup Exec Remote Agent for Windows Servers service hung on starting. (Backup Exec Remote Agent for Windows Servers service is suspended at startup .)
This document is translated from English. The original English document may have been modified and updated after the release of this translation. Symantec does not guarantee the accuracy of this translation document.
Situation
The Backup Exec Remote Agent is suspended when it is started on a remote server. The System Event Log On the remote server lists event ID: 7022, which is described: the Backup Exec Remote Agent for Windows Servers service hung on starting. (Backup Exec Remote Agent for Windows Servers service is suspended at startup .) Exact error message the Backup Exec Remote Agent for Windows Servers service hung on starting. remote Computer System Event Logs include the following errors: Event Type: Error Event Source: Service Control Manager event category: None event ID: 7022 Description: Backup Exec (TM) the Remote Agent for Windows Servers service is suspended at startup.
Explanation
Set Microsoft Outlook as the default mail client.
- Open Internet Explorer
- Go to tools | Internet Options | Programs tab
- Click the drop-down box next to "email" and select Microsoft Outlook (figure 2)
If you have set outlook as the default mail client, configure the outlook configuration file. Then try to start the remote Agent service.
If you are using version 12.0 or 12.5, the remote Agent for Windows Server is suspended at startup, but there is no event log with the event ID 7022 In the event viewer, to verify whether the problem is the same, run the following command:
On the Media Server:
X: \> "X: \ Program Files \ symantec \ Backup Exec \ beremote.exe"-Console
On a remote server:
X: \> "X: \ Program Files \ symantec \ Backup Exec \ raws \ beremote.exe"-Console
X is the drive to install Backup Exec.
After running the command, some information will appear, and an error will pop up:
Either there is no default mail client or the current mail client cannot full fill the messaging request. please run the Microsoft Outlook and set it as default mail client. (No Default mail client or the current mail client cannot complete the mail request. Run Microsoft Outlook and set it to the default mail client .)
Http://support.microsoft.com/kb/813745
According to the Microsoft article above, this is caused by a corrupted outlook registry key.
Try the solution provided in this document or set Outlook Express as the default client. If this error persists, configure the configuration file of Outlook Express.
247931: the error message: "either there is no default mail client or the current mail client cannot fulfill the messaging request. please run Microsoft Outlook and set it as the default mail client "is supported ed during Backup Exec Service Startup or system reboot. (When the Backup Exec Service is started or the system restarts, the following error message is received: either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client (no default mail client or the current mail client cannot complete the mail request. Run Microsoft Outlook and set it to the default mail client .))
Http://support.veritas.com/docs/247931
269216: Backup Exec cannot connect to the local media server and the system event log lists event ID: 7022 with the description: "The Backup Exec Server service hung on starting. "(Backup Exec cannot connect to the local media server. The system event log lists the event ID: 7022, which is described as: the Backup Exec Server service hung on starting. (The Backup Exec Server service is suspended at startup .))
Http://support.veritas.com/docs/269216
Document No.: 20090903165242968
Last Updated:
Date created: 2009-09-03
Product: Backup Exec for Windows Servers