AIM client version 6.9 and higher shows the buddy list as empty when the buddy list has many entries

Article:TECH190561  |  Created: 2012-06-07  |  Updated: 2012-06-07  |  Article URL http://www.symantec.com/docs/TECH190561
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution

Product(s)

Issue



AIM client logs in through IM Manager.  The buddy is list empty.

Typically this occurs when the buddy list contains hundreds of entries.

Conditions

  • Logging in around IM Manager allows the AIM client to show the full buddy list.
  • AIM client log shows the entire buddy list not being received and then finally ignored.

See the following article for details on getting an AIM client log: How To Capture AIM Client Logging for AIM version 6.x and 7.x.

1. Client starts receiving the buddy list here:

       01:36.59 FlapStream 013DF470: rcvd FEEDBAG:REPLY; l=4862 s=30179 r=308d0005(continued)
       01:36.83 FlapStream 013DF470: rcvd FEEDBAG:REPLY; l=5530 s=30180 r=308d0005(continued)
       01:36.89 FlapStream 013DF470: rcvd FEEDBAG:REPLY; l=5659 s=30181 r=308d0005(continued)
       01:37.10 FlapStream 013DF470: rcvd FEEDBAG:REPLY; l=5009 s=30182 r=308d0005(continued)
       01:37.34 FlapStream 013DF470: rcvd FEEDBAG:REPLY; l=5019 s=30183 r=308d0005(continued)
       01:37.46 FlapStream 013DF470: rcvd FEEDBAG:REPLY; l=6551 s=30184 r=308d0005(continued)
       01:37.62 FlapStream 013DF470: rcvd FEEDBAG:REPLY; l=5682 s=30185 r=308d0005(continued)
       01:37.69 FlapStream 013DF470: rcvd FEEDBAG:REPLY; l=5613 s=30186 r=308d0005(continued)
       01:37.87 FlapStream 013DF470: rcvd FEEDBAG:REPLY; l=5380 s=30187 r=308d0005(continued)
       01:38.10 FlapStream 013DF470: rcvd FEEDBAG:REPLY; l=4823 s=30188 r=308d0005(continued)

 

2. Then the client times out waiting for the rest of the buddy list:

01:43.82 Timer 0140B840: fires
01:53.82 Timer 0140B840: fires
02:03.83 Timer 0140B840: fires
02:03.83 TRequestMapper 013D7358: timing out request 308D0005
02:03.83 Timer 0140B840: stopped
02:03.83 FeedbagManager: snac id=5 timed out
02:03.83 Error 013E0CF0 created
02:03.83 Error set, cat=Service, code=RequestTimeout, subcode=0, url=

 

3. The client then ignores the entire buddy list here: 

02:16.47 BuddyManager 013D4678: Ignoring info for non-buddy bubbles99

 

NOTE:  A normal sequence for receiving a buddy list looks like this:

       00:57.40 FlapStream 013E08D8: rcvd FEEDBAG:REPLY; l=4006 s=32745 r=50250004(continued)
       00:57.41 FlapStream 013E08D8: rcvd FEEDBAG:REPLY; l=4842 s=32746 r=50250004(continued)
       00:57.41 FlapStream 013E08D8: rcvd FEEDBAG:REPLY; l=4775 s=32747 r=50250004(continued)
       00:57.41 FlapStream 013E08D8: rcvd FEEDBAG:REPLY; l=5098 s=32748 r=50250004(continued)
       00:57.42 FlapStream 013E08D8: rcvd FEEDBAG:REPLY; l=4832 s=32749 r=50250004(continued)
       00:57.42 FlapStream 013E08D8: rcvd FEEDBAG:REPLY; l=5654 s=32750 r=50250004(continued)
       00:57.42 FlapStream 013E08D8: rcvd FEEDBAG:REPLY; l=5353 s=32751 r=50250004(continued)
       00:57.42 FlapStream 013E08D8: rcvd FEEDBAG:REPLY; l=5521 s=32752 r=50250004(continued)
       00:57.42 FlapStream 013E08D8: rcvd FEEDBAG:REPLY; l=5368 s=32753 r=50250004(continued)
       00:57.42 FlapStream 013E08D8: rcvd FEEDBAG:REPLY; l=3575 s=32754 r=50250004

 

Notice that the last entry does not say "continued".

 

 


Cause



IM Manager is only sending ten (10) network packets containing the buddy list to the client.  If AOL sends more than ten network packets with the buddy list IM Manager does not send them.  This causes the client to consider the buddy list "corrupt" and reject the entire buddy list.


Solution



Symantec is aware of this issue.  This article is updated as more information is available.  Subscribe to this article to receive updates.

Workaround

Symantec has a hotfix that addresses this issue for IM Manager 8.4.18.  Open a technical support case with Symantec to receive the hotfix.


Supplemental Materials

SourceETrack
Value2644714


Article URL http://www.symantec.com/docs/TECH190561


Terms of use for this information are found in Legal Notices