In Windows Messenger 5.1, you receive an access violation error message when you click a user display name to start a conversation

Article ID: 937107 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

In Microsoft Windows Messenger 5.1, you receive an access violation error message when you click a user display name to start a conversation.
Back to the top | Give Feedback

CAUSE

This issue occurs because the Msimnetc.dll module incorrectly processes some characters.
Back to the top | Give Feedback

WORKAROUND

To work around this issue, only use ASCII characters for the user display names.
Back to the top | Give Feedback

RESOLUTION

The resolve this issue, install the hotfix that is provided on the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=A8D9EB73-5F8C-4B9A-940F-9157A3B3D774&displaylang=en
(http://www.microsoft.com/downloads/details.aspx?FamilyId=A8D9EB73-5F8C-4B9A-940F-9157A3B3D774&displaylang=en)

This hotfix is included in Windows Messenger 5.1 version 5.1.0000.0706.

For more information about the latest version of Windows Messenger 5.1, click the following article number to view the article in the Microsoft Knowledge Base:
899283
(http://support.microsoft.com/kb/899283/ )
How to obtain the latest version of Windows Messenger 5.1
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

MORE INFORMATION

When this issue occurs, the following debugging log is generated:
(42c.520): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000001 ebx=00000001 ecx=00000002 edx=0006ea00 esi=0006ecce edi=0006ead4
eip=04ec21fd esp=0006e978 ebp=0006e984 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00210202
msimnetc!CXMLUnparsePCData::Process+0x3f:
04ec21fd 8a10            mov     dl,byte ptr [eax]          ds:0023:00000001=??

0:000> kv
ChildEBP RetAddr  Args to Child
0006e984 04ec25b9 0006ead4 0006ecd6 00000012 msimnetc!CXMLUnparsePCData::Process+0x3f 
0006e9d4 04ec2888 0006ead4 0006ec7c 0006ebbc msimnetc!CXMLUnparseValue::Process+0x179 
0006e9f4 04ec2ae6 0006ead4 0006ec74 00000001 msimnetc!CXMLUnparseContacts::Process+0x58 
0006ea18 04eaf6a2 00000001 0006ebbc 00000008 msimnetc!CXMLUnparseNotify::Process+0x95 
0006eae8 04eb2e17 00000000 051905d8 00000000 msimnetc!CIMNotifyMessageCallback
0006eafc 04ebaa7c 05246fd8 00000000 02af8d40 msimnetc!CIMRequestCallback
0006eb2c 04ebb296 00772834 04ca4ed0 04cbef90 msimnetc!CIMNotifyMessageCallback
0006eb5c 02ae994a 04cbefe8 04cd1fe0 00000001 msimnetc!CIMNodeManager
0006ec00 02adf736 04cd1fe0 00000001 05246fd8 msimmsgr!CMsgrIMService::NotifyMessage+0x10c 
0006ec50 02ae3e1e 051bbf88 00000002 0988dfac msimmsgr!CMsgrIMUser::SendTextEx+0xf5 
0006f8e4 02ae45ec 05242f68 0988dfa0 00772818 msimmsgr!CMsgrIMSession::InviteUser+0x276 
0006f914 02aed39e 00772818 05242f68 00000001 msimmsgr!CMsgrIMSession::Enable+0x93 
0006f9f8 02aed81b 00000000 0006fa3c 00000000 msimmsgr!CMsgrIMService::GetSession+0x290 
0006fc60 01035817 00772844 05242f84 051e4b20 msimmsgr!CMsgrIMService::CreateIMSession+0xe2 
0006fc84 01036aec 00742f84 01060009 051e1ff0 Msmsgs!CBLObject::CreateIMSession+0x6c 
0006fcac 010a4a3f 00740fac 01060009 051e1ff0 Msmsgs!CBLInstance::CreateIMSession+0x23 
0006fcec 0104aec7 05242f84 05242f84 04cdf18c Msmsgs!CIMesg::CreateSessionConnection+0x4a 
0006fd4c 01081b47 05242f84 00000001 00000000 Msmsgs!CUIManager::MakeIMWindow+0x1e9 
0006fd78 010843e3 05242f84 0006fec4 00000000 Msmsgs!CMSBLListView::OnPopupSendMsg+0x1f 
0006fddc 01084530 00000464 00009c66 00000000 Msmsgs!CMSBLListView::OnMessage+0xd9
Back to the top | Give Feedback

Properties

Article ID: 937107 - Last Review: June 15, 2007 - Revision: 1.0
APPLIES TO
  • Microsoft Windows Messenger 5.1
Keywords: 
kbexpertiseinter kbhotfixserver kbqfe KB937107
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top