If you have native IPv6 connectivity on your network, Windows Meeting Space will fail to run with the following error:
The stack trace is the following (on Vista 64):
0 Id: 132c.d0c Suspend: 1 Teb: 000007ff`fffdd000 Unfrozen
Child-SP RetAddr Call Site
00000000`001db188 00000000`7706ed73 ntdll!NtWaitForMultipleObjects+0xa
00000000`001db190 00000000`76f7e96d kernel32!WaitForMultipleObjectsEx+0x10b
00000000`001db2a0 000007fe`fc551ab6 USER32!RealMsgWaitForMultipleObjectsEx+0x129
00000000`001db340 000007fe`fc55371f DUser!CoreSC::Wait+0x62
00000000`001db390 000007fe`fc553696 DUser!CoreSC::WaitMessage+0x6f
00000000`001db3d0 00000000`76f6bd1a DUser!MphWaitMessageEx+0x36
00000000`001db400 00000000`771c2016 USER32!_ClientWaitMessageExMPH+0x1a
00000000`001db450 00000000`76f7df2a ntdll!KiUserCallbackDispatcherContinue
00000000`001db4b8 00000000`76f673e9 USER32!ZwUserWaitMessage+0xa
00000000`001db4c0 00000000`76f6760a USER32!DialogBox2+0x261
00000000`001db540 00000000`76f674c6 USER32!InternalDialogBox+0x134
00000000`001db5a0 00000000`76f67918 USER32!DialogBoxIndirectParamAorW+0x58
00000000`001db5e0 000007fe`fc34f262 USER32!DialogBoxIndirectParamW+0x18
00000000`001db620 000007fe`fc2930ca COMCTL32!SHFusionDialogBoxIndirectParam+0x56
00000000`001db670 00000000`ffce84ab COMCTL32!CTaskDialog::Show+0x156
00000000`001db6e0 00000000`ffce86de WinCollab!ReportMessageForLH+0x178
00000000`001db7b0 00000000`ffce87a1 WinCollab!ReportMessage+0x1dd
00000000`001ddf70 00000000`ffce887a WinCollab!ReportErrorCommon+0x9f
00000000`001ddfd0 00000000`ffcf43ba WinCollab!ReportError+0x67
00000000`001de000 00000000`ffcf125d WinCollab!CStartMeetingMain::CallCallbackOnGroupConnected+0x11c
Monday, November 5, 2007
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment