BE server service fails to start (hangs) after installation of hotfix

After LiveUpdate installed a hotfix on the BAckup Exec server, the system was rebooted. After reboot the BE Server service fails to start.
The application log contains the following entry:
Faulting application beserver.exe, version 11.0.7170.27, faulting module mscoree.dll, version 2.0.50727.832, fault address 0x000302da.

and the system log:

Application popup: Microsoft Visual C++ Runtime Library : Runtime Error!

Program: C:\Program Files\Symantec\Backup Exec\beserver.exe

Any ideas?

To circumvent the problem I installed BE on another server and tried to move the BE database etc from the old server using This did not work. Also on the new server BE server will not start. After uninstalling BE and installing it again on the new server but without using the old BE database everything is OK, but now I miss my cataloges, media sett information,  tape library configuration, etc.

Anyone able to help me getting BE to work again, or to move the catalogues and other information to the new server in a different way?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kogelerAuthor Commented:
pls close
no one even viewed the question.
I got the solution elsewhere

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
What was the solution? I've got a similiar issue...

I also would like to know how this problem was resolved. What was your solution?
kogelerAuthor Commented:
I posted the solution at: Later I had a similar problem (same symptoms), after a update of .Net.  After .Net was removed and reinstalled, it worked again.
I had the same problem and was able to resolve it using this link:  In summary set Outlook as the default mail client.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.