BE12 crash running console and resolution

[NEDC]

I thought I'd sharer this problem and resolution if anyone else ever sees this problem.  Below is a copy of my event log for anytime I tried to run the BE12 console from my desktop PC to connect to our media server.  I opened a ticket with Symantec on 5/3 and we uninstalled and reinstalled everything several times with no success.  Finally after sending 6 or so crash dumps to Symantec the Symantec engineer I was working with said it was a Microsoft.Net 2.0 problem and I needed to open a ticket with them.  Luckily I'm a Technet Plus subscriber so I opened a support case with them.  I then spoke to an engineer in the C++/C# team at MS who after analyzing the same crash dump Symantec was working with noticed that there was mention that the Verdana font was missing.  So I checked this, sure enough it was missing (I have no idea why) copied it from my laptop and the thing works fine now.  So the problem was resolved on 6/4.

The Symantec engineer said they will be creating a technote for that and possibly update the code to substitute a font in case Verdana is missing.  I guess in 11d that was the way it worked.  I can't believe a missing font could crash the console.  Oh well, I'm glad it's working again.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date:  6/4/2008
Time:  2:10:35 PM
User:  N/A
Computer: LEGERE99
Description:
EventType clr20r3, P1 bkupexec.exe, P2 12.0.1364.107, P3 48061bf1, P4 mscorlib, P5 2.0.0.0, P6 471ebc5b, P7 f48, P8 0, P9 n3ctrye2kn3c34sgl4zqyrbfte4m13nb, P10 NIL.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00   c.l.r.2.
0008: 30 00 72 00 33 00 2c 00   0.r.3.,.
0010: 20 00 62 00 6b 00 75 00    .b.k.u.
0018: 70 00 65 00 78 00 65 00   p.e.x.e.
0020: 63 00 2e 00 65 00 78 00   c...e.x.
0028: 65 00 2c 00 20 00 31 00   e.,. .1.
0030: 32 00 2e 00 30 00 2e 00   2...0...
0038: 31 00 33 00 36 00 34 00   1.3.6.4.
0040: 2e 00 31 00 30 00 37 00   ..1.0.7.
0048: 2c 00 20 00 34 00 38 00   ,. .4.8.
0050: 30 00 36 00 31 00 62 00   0.6.1.b.
0058: 66 00 31 00 2c 00 20 00   f.1.,. .
0060: 6d 00 73 00 63 00 6f 00   m.s.c.o.
0068: 72 00 6c 00 69 00 62 00   r.l.i.b.
0070: 2c 00 20 00 32 00 2e 00   ,. .2...
0078: 30 00 2e 00 30 00 2e 00   0...0...
0080: 30 00 2c 00 20 00 34 00   0.,. .4.
0088: 37 00 31 00 65 00 62 00   7.1.e.b.
0090: 63 00 35 00 62 00 2c 00   c.5.b.,.
0098: 20 00 66 00 34 00 38 00    .f.4.8.
00a0: 2c 00 20 00 30 00 2c 00   ,. .0.,.
00a8: 20 00 6e 00 33 00 63 00    .n.3.c.
00b0: 74 00 72 00 79 00 65 00   t.r.y.e.
00b8: 32 00 6b 00 6e 00 33 00   2.k.n.3.
00c0: 63 00 33 00 34 00 73 00   c.3.4.s.
00c8: 67 00 6c 00 34 00 7a 00   g.l.4.z.
00d0: 71 00 79 00 72 00 62 00   q.y.r.b.
00d8: 66 00 74 00 65 00 34 00   f.t.e.4.
00e0: 6d 00 31 00 33 00 6e 00   m.1.3.n.
00e8: 62 00 20 00 4e 00 49 00   b. .N.I.
00f0: 4c 00 0d 00 0a 00         L..... 

[Daniel_Mitchell]

We currently have this problem.  I've checked to see if we have the verdana font both in the registry and in the windows/font directory.  It is present in both places and the problem still occurs.  Is there any place else I need to check for that font?  Will installing .NET 3 resolve this issue.  Any help will be appreciated.

[NEDC]

OK the first thing Symantec wanted done was to remove all versions of .Net and restart.  There is a tool available to do that:

http://astebner.sts.winisp.net/Tools/dotnetfx_cleanup_tool.zip

After restarting install .net 3.0 SP1.  This also installs 2.0 DLLs needed for BE 12.

The Verdana font I have is verdana.ttf dated 8-4-2004 and 168kB

I assume this is a Windows XP workstation and not the actual media server.

[Daniel_Mitchell]

Thanks for the quick reply Ned.  I've done this all before except installing .NET 3 SP1.  This was done based on Symantec's tech support.  And BE 12 is installed on our media server with the required SQL and Exchange remote agents.  The verdana font is on our media server too.  I'll run the cleanup again and install .NET 3 SP1 and let you know the results.  Thanks again for your help.

[NEDC]

I never had a problem running the console direct from the media server, only on my PC.  As a workaround I installed MS Virtual PC 2007, set up a Windows XP virtual machine and installed the BE 12 admin console to that virtual PC.  I also could and did install the console to a different physical machine and used it there temporarily as a test.