Hello, I installed yesterday from 11d to 12, but it was a nightware.
The installation success, but I've got the same problem with the .NET 2.0
Have anyone an idea, the solution with
-uninstalling .Net 2.0
-reboot
-installing .Net 2.0
-repair of BE 12
-reboot

does'nt help me, I think I reinstalled it 5-6 times and it won't work.
Somebody else any solution ???

Having the same problem tried recommended steps to remove, reinstalled  and repair see error.

EventType clr20r3, P1 bkupexec.exe, P2 12.0.1364.107, P3 48061bf1, P4 backupexec.uiframework, P5 12.0.1364.107, P6 48061bcd, P7 161, P8 2d, P9 system.typeinitialization, P10 NIL.

Windows SBS 2003 Backup Exec 12 small business version evrything new.

I have the same problem with my win2003 standard server.

Does anyone have a solution that works? This is my error message in event viewer:

EventType clr20r3, P1 bkupexec.exe, P2 12.0.1364.132, P3 48ac830d, P4 backupexec.ui.data, P5 12.0.1364.132, P6 48ac82fb, P7 278, P8 0, P9 system.typeinitialization, P10 NIL.

I have automatic updates turned on.  It asked me to reboot the other day.  my backup was good last night now when I try to get in I receive this error

.NET Runtime 2.0 Error   Event ID:1000

Faulting application bkupexec.exe, version 12.0.1364.132, stamp 48ac830d, faulting module kernel32.dll, version 5.2.3790.4062, stamp 46264680, debug? 0, fault address 0x0000bee7.

I also have the DLO installed 

I have been on hold 34 minutes now so we will see if I get a tech sometime today :-)

 I have not been able to find this exact error in the knowledgebase yet.  Any help would be appricated!

Ah, at least I am not alone. Recieving similar error messages when trying to run backup exec. The logs indicate that the backups are running OK but i tried to run the console application and get the following:

Faulting application bkupexec.exe, version 12.0.1364.125, stamp 4873c3d2, faulting module kernel32.dll, version 5.2.3790.4062, stamp 46264680, debug? 0, fault address 0x0000bee7.

The only recent change has been installing symantec endpoint protection on the domain. Perhaps there is a conflict? 

I have done nothing and im all out of options! (this is a production server so i cant reboot or do much of anything, except at night) Was hoping for a definitive fix before i start poking at it.

Anyone find a fix yet?

What a pain - I've got this problem also.  I finally upgraded from 10d to 12 and went from a stable product to an unstable product.  It is Murphy's Law at it's best.

Our BE 12 is running on Windows 2003 Server Std R2 SP2.  Also on that box is Symantec AV Corp Ed ver 10.1.5.5010.  The way I use BE is by using Remote Desktop to get to the BE server.  I don't use the console installed on some other machine, just simple RD to BE server. 

When I RD to the BE server and attempt to launch BE 12, I have to double click the icon 3-6 times before it launches.  I notice in the task manager that BkupExec.exe is showing as many times as I have attempted to launch it.

In order to attempt to resolve the problem I have followed the steps above:

-Removed .NET using the .NET cleanup prog; rebooted.

-Installed .NET 3.5 SP1 (which apparently installed earlier versions of .NET also); rebooted.

-Performed repair of BE; rebooted.

Still the problem exists.

Now I am doing a Live Update and it seems to be installing something eventhough I was all up to date this morning since I had previously checked Live Update and there was nothing new to install. 

Does anyone have any updates on this issue?

I have reinstalled my BE and during install I didn't do any updates, just skipped them. After installation I turned off automatic updates from symantec and everything is running just fine. In fact i'm running a stable BE for a couple of months now without installing updates.

I know it isn't that safe to turn automatic updates off but for me it was the only way to get BE running. I'm also running symantec endpoint protection and there I have the updates turned on. If symantec can guarantee me that it is safe to turn on automatic updates for BE and it will still work, than I will consider doing so. For now I'm going to leave it as it is.

Backup is running just fine, just have to get rid of the few exceptions but that's finetuning. Hopefully it can be a solution for someone

Well when the tech finally answered they walked me through add and remove programs and doing a repair on backup exec, and then it worked again. The above error was gone.   I also ran updates and checked the Alerts to see when to reboot after the updates.

Well then not to long after that we had a power outage and it took the server down hard when the battery ran out.  Seems that our backup Exec database went with it.  Luckly that was all.  So the tech had me do a repair form add and remove programs and that didnt' work and we tried to reindex and do all the repair to the database, but no luck.  We had to do a clean reinstall. 

So if you are having any issues I would try to do a Add/Remove Programs and Choose Repair.  The tech acted like this is what they do most every time as first attempt to solve any issues.

Hope this helps someone!!   :smileyhappy:

Oh and one other thing I just thought of too... I also had Endpoint installed on that server. I only had Antivirus installed, but it will run live update and update both Backup Exec and Endpoint if they are both installed on the same machine.

So when ever you have your updates scheduled is when it will run updates for backup exec. You may need to check the alerts every so often to see if the server needs rebooted if you do not normally log onto Backup Exec.

HI Guys,

I have the same problem too. Tried repair and then restart but it didn't help. Hope dsh180 has something to share.

Thanks!

I am trying a 3rd repair for Backup Exec, since the .NET repair didn't work.

The beserver Service gets stuck in a "Starting" status, and it messes up the installation/repair... I have to end the process directly from Task Manager.

Did anyone else noticed this, or could I be having a different kind of trouble?

http://support.veritas.com/docs/303843

about situation when console doesnt start: i've just removed profile (c:\Docu-s&settings\user) for "user" who cannot load BE console and then logged in again.
it helps.

I had this issue several months ago.  I tried every suggestion in this thread and nothing worked.   A day or two later, the problem went away on its own.  It came back again today.  I reviewed this thread and dreaded going through all of those steps again only to have no solution.

Then, inspiration struck: why does the problem come and go?  What could cause that?  Wait...McAfee McShield causes all kinds of wacky, inexplicable problems on all my desktops and servers alike!  I wonder...

So, I stopped the McShield service and, voila!  Problem solved.  Just one more reason I hate McAfee.

I resolved a similar problem using a repair on BE