I'm having a very bad Monday. For some reason, almost every time I start Dashboard, it immediately traps. Occasionally it will start successfully but then it will not successfully perform a Start Application session. When it traps it is always on the Phone Commands tab (which I wouldn't normally utilize) Not sure what is happening today since all of our configuration is exactly the same as on Friday. The Avaya IP Phone is able to logon to the switch as can our application. It seems to be something with Dashboard. I've rebooted the IPCoDE simulator but that didn't help.

Any suggestions on how to proceed with this problem would be greatly appreciated.

Paul

Paul:

It sounds like it might be a Windows resource problem.

Try rebooting your PC.

Dave

did microsoft give you a new and improved version of .NET over the weekend?

Does the issue appear on a different PC (that microsoft may have kept their sticky fingers off of)?

Hmmmm, this is really strange. I did upgrade my laptop to use a larger disk drive this past weekend by cloning the smaller one. Everything is working just fine with the larger drive (except this problem with Dashboard). I didn't think it was possible that it could be related to the drive. I installed another download of Dashboard, but the same problems kept occurring. So I finally decided to shutdown the laptop and put back the original hard drive and sure enough - Dashboard started working again. I swapped the larger drive back in again, and Dashboard traps. I can't imagine what could be causing this unless somehow the Avaya software is cognizant of drives?? I've heard of new motherboards causing similar problems but never a hard drive. I'm at a loss to understand this. Any ideas?

The Dashboard does not look at hard drives.

Perhaps you have a faulty drive and the sector where the dashboard or the serviceProvider.dll resides is on it.

Try copying the Dashboard and the ServiceProvider.dll to another folder.

You might also try reinstalling the .NET framework.

Dave

The 5.2 dashboard trapped on me on a machine that did not have .NET installed without so much as a complaint about .NET not being installed... just a boom. I forgot to mention it to Dave. Try installing .NET again on the new disk. Me thinks the clone did not pull forward .NET correctly.

Dave, John,

OK, I'll try reinstalling .NET. Does Dashboard use .NET 3.5 or does it call for an earlier version?

Paul

3.5 should work. I think the officially supported version is 2.0.50727

Go to http://msdn.microsoft.com/en-us/kb/kb00318785.aspx to see an article which tells you how to determine which version is currently installed on your computer.

Dave

Dave, John,

I tried doing a repair on .NET 3.5 but Dashboard is still trapping. Will also try doing a full uninstall and then a reinstall.

However, I also just looked at the Event Log in Control Panel and found the following entry for Dashboard, which appears to be related to .NET 2.0 (as you stated). I'm wondering if I need to reinstall .NET 2.0 or if I can just remove it entirely. Will Dashboard use .NET 3.5 then? Or do I need to find the .NET 2.0 installable?

Event Type:   Error
Event Source:   .NET Runtime 2.0 Error Reporting
Event Category:   None
Event ID:   1000
Date:      12/15/2009
Time:      11:45:48 AM
User:      N/A
Computer:   PAULR-D630
Description:
Faulting application dashboard.exe, version 4.2.2.58, stamp 498cadbe, faulting module mscorwks.dll, version 2.0.50727.3603, stamp 4a7cd88e, debug? 0, fault address 0x0000f290.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 64 00 61 00 73 00 .d.a.s.
0030: 68 00 62 00 6f 00 61 00 h.b.o.a.
0038: 72 00 64 00 2e 00 65 00 r.d...e.
0040: 78 00 65 00 20 00 34 00 x.e. .4.
0048: 2e 00 32 00 2e 00 32 00 ..2...2.
0050: 2e 00 35 00 38 00 20 00 ..5.8. .
0058: 34 00 39 00 38 00 63 00 4.9.8.c.
0060: 61 00 64 00 62 00 65 00 a.d.b.e.
0068: 20 00 69 00 6e 00 20 00 .i.n. .
0070: 6d 00 73 00 63 00 6f 00 m.s.c.o.
0078: 72 00 77 00 6b 00 73 00 r.w.k.s.
0080: 2e 00 64 00 6c 00 6c 00 ..d.l.l.
0088: 20 00 32 00 2e 00 30 00 .2...0.
0090: 2e 00 35 00 30 00 37 00 ..5.0.7.
0098: 32 00 37 00 2e 00 33 00 2.7...3.
00a0: 36 00 30 00 33 00 20 00 6.0.3. .
00a8: 34 00 61 00 37 00 63 00 4.a.7.c.
00b0: 64 00 38 00 38 00 65 00 d.8.8.e.
00b8: 20 00 66 00 44 00 65 00 .f.D.e.
00c0: 62 00 75 00 67 00 20 00 b.u.g. .
00c8: 30 00 20 00 61 00 74 00 0. .a.t.
00d0: 20 00 6f 00 66 00 66 00 .o.f.f.
00d8: 73 00 65 00 74 00 20 00 s.e.t. .
00e0: 30 00 30 00 30 00 30 00 0.0.0.0.
00e8: 66 00 32 00 39 00 30 00 f.2.9.0.
00f0: 0d 00 0a 00 ....

personally I would do a complete un-install of .NET and install 2.0.50727 if you can find it and try to put this problem behind me. Once I had it working I would consider installing 3.5, but only if I needed the changes made to .NET.

I'm with you 100%, John. Unfortunately, this is turning into a Pandora's Box because Windows will not allow me to uninstall .NET 2.0 because it states other installed applications have a dependency on it. Repair doesn't seem to work either. Our application is based on .NET 3.5 which might explain why we are not having any issues with talking to DMCC. I may try uninstalling .NET 3.5 and then try to uninstall 2.0 but I'm not hopeful. If I'm unsuccessful resolving this, I may need to resorting to going back to my old (full) drive and trying the clone operation again (egads, I hope not).

Success!! I had to first uninstall .NET 3.5, then .NET 3.0 and then .NET 2.0. I then reinstalled in reverse and now the Dashboard is running. Thank heavens (and the Avaya support team)!

Sure hope nothing else got "mis-cloned" but I guess time will tell.

Thanks, again, John and Dave.

Paul

yea!... if you kept having problems I was considering telling you to take old Bessy out back and put a half ounce slug right behind her ear.