Solved

Backup Exec upgrade from 10d to 11d resulted in Windows Server Remote Agent connection error

Posted on 2008-06-17
3
1,777 Views
Last Modified: 2013-12-01
We just upgraded our Central Admin server (A) from Backup Exec 10d to 11d.  At the same time we upgraded the managed media server (B) to 11d.  After the upgrade, we did a push install to the remote servers being backed up to upgrade the Windows Server Remote Agent.  Everything upgraded without any errors.

Now, when jobs are pushed from the Central Admin Server (A) to the managed server (B) we get the following error message:

"Error category    : Resource ErrorsError             : e000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.
Make sure that the correct version of the Remote Agent is installed and running on the target computer."

I have reinstalled the Agent, verified credentials, verified that the service is running (as well as restarted the service numerous times), reinstalled using the command line utility, and created a job from scratch.  All result in the same error message above.

any help in figuring out the issue here would be appreciated.

0
Comment
Question by:brett_apfc
  • 2
3 Comments
 
LVL 24

Assisted Solution

by:ryansoto
ryansoto earned 100 total points
ID: 21805774
I had the same issue.  I had to call Symantec support.  I ran through all the same steps as you but to no avail.
They had to work some registry hacks to make it work.
0
 

Author Comment

by:brett_apfc
ID: 21816038
Update:

If I configure a test backup from the managed media server (B) then run the test job from that server, the job will complete without any errors.  The Cenral Admin Server (A) still fails when any job is run from it using server B as  the media server.
0
 

Accepted Solution

by:
brett_apfc earned 0 total points
ID: 21824277
resolution (sort of):

After spending about 4 hours on the phone with Backup Exec tech support, we final got our backup jobs working.

Numerous things were attempted to solve the problem including manual installs of the client, verification of the beremote.exe file versions (same on CASO, MMS, and client server), live updates, etc.

the technician had me change the name of all "msgq000000000.dat" files located in the C:\Program Files\Symantec\Backup Exec\Data directory on the CASO server.  After that we verified that on both the CASO and the MMS server the option to "enable selection of user shares" (Tools -- options -- network and security) was either enabled on both servers, or disabled on both servers (can't have 1 on and 1 off).

After these changes, all backups begain to work.  After further testing, we could not get the jobs to fail, even when changing the previous options to the way there were prior to changing them.  

I am pretty stumped as to the cause, or the actuall remedy other than just changing a setting and applying it making some kind of difference after the upgrade.  Regardless, the issue is no longer happening.

ryansoto -- Symantec support was part of the correct answer, so I'll award partial points to you.  Thanks for the comment.
0

Featured Post

How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

Join & Write a Comment

Suggested Solutions

A quick step-by-step overview of installing and configuring Carbonite Server Backup.
This article is an update and follow-up of my previous article:   Storage 101: common concepts in the IT enterprise storage This time, I expand on more frequently used storage concepts.
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now