Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Symantec Backup Exec 12 user interface stops responding

Posted on 2009-03-29
11
Medium Priority
?
625 Views
Last Modified: 2013-12-13
We have been using Symantec Backup Exec 12 for some time on our servers, and about two weeks ago the user interface would stop responding whenever you tried to open it.
I have absolutely no idea where to even start troubleshooting this, so any advice would be handy.

The system is running Windows 2003 Server

If you need more info please specify what you would like to know and i can find it.
0
Comment
Question by:ictdoulos
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
11 Comments
 
LVL 11

Accepted Solution

by:
Quetzal earned 1500 total points
ID: 24012256
Make certain that all of the Backup Exec services are running (services.msc).  If they are not, try starting each manually.  You may notice a "logon failure" for some service(s).  Edit the service and re-enter the logon credentials if needed.

If this fails, simply uninstall and re-install BE.  If you are on maintence, then upgrade to 12.5 when/if you do this.
0
 

Author Comment

by:ictdoulos
ID: 24015288
the services are all running fine, an restarting them has no effect,

will my current backup jobs be lost if i uninstall and reinstall?
0
 
LVL 11

Expert Comment

by:Quetzal
ID: 24017969
If you have a relatively small number of jobs and the selection lists are not complex, it's probably just as easy to recreate the jobs.

Save a copy of %windir%\besernum.xml to keep a copy of all your BE serial numbers.  Save copies of the Catalog and Data folders under Program Files\Symantec\Backup  Exec.  Reinstall BE, get the tape drivers installed, serials reentered etc.  Exit BE.  Stop all BE services.  Rename the new Catalog and Data folders (blah old) and copy back the previous copies.  Start all BE services.  Start BE.

0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:ictdoulos
ID: 24019068
the reason i ask is that we do have a fairly elaborate collection of jobs running, and this is an inherited system, so i have no idea of the intricacies
0
 
LVL 11

Expert Comment

by:Quetzal
ID: 24020638
If BE is under maintenance, tech support will walk you through the process.
0
 

Author Comment

by:ictdoulos
ID: 24035952
Further information which may add some clues: consistently when the server is restarted then the Backup Exec client will work without problems.  The last time I rebooted it only worked for the first day and then stopped working. Having just rebooted the server I will monitor it a bit more closely.  Any ideas of what I should look out for, or which logs I should monitor?
0
 
LVL 11

Expert Comment

by:Quetzal
ID: 24071351
With server restart, BE UI works for some period of time, then stops.  When UI is then not working, all BEservices are still running and restarting them has no effect.  In essence, the current workaround is to reboot the server.

I think the BE reinstall is the next step.
0
 

Author Comment

by:ictdoulos
ID: 24071448
Backup Exec was upgraded to 12.5 over the top of 12.1.  The same problem is still occurring.  The next step I see is to uninstall and then install afresh.
0
 
LVL 11

Expert Comment

by:Quetzal
ID: 24071520
I agree.  Symantec tech support can walk you through steps to preserve the BE catalogs and database so that you do not need to recreate your jobs.  But a clean uninstall and re-install does seem to be in order.
0
 

Author Comment

by:ictdoulos
ID: 24076008
The solution ended up being a reinstall of Backup exec, along with an upgrade to 12.5
It all went without a hitch, and the backups are up and running again

Thanks for your help
0
 

Author Comment

by:ictdoulos
ID: 24371265
Uninstalling and reinstalling solved the problem, however it was not simply a matter of using the Symantec uninstaller.  We uninstalled it, we dropped the SQL database, we deleted all registry entries and removed any trace we could find of it.  Then finally it worked again.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Nothing in an HTTP request can be trusted, including HTTP headers and form data.  A form token is a tool that can be used to guard against request forgeries (CSRF).  This article shows an improved approach to form tokens, making it more difficult to…
Microsoft will be releasing the Windows 10 Creators Update in just a matter of weeks. Are you prepared? Follow these steps to ensure everything goes smoothly and you don't lose valuable data on your PC.
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…

610 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