powered by Jive Software

Aim Users Blank Roster

One of our users is reporting that their aim users do not show up on their contact list. There is the green dot, but then nothing after it. However, if you mouse over it the persons AIM name is listed. I’m not seeing any log files specific to this currently

Spark: 2.5.7

Openfire: 3.3.3

IM Gateway: 1.1.3a

Any ideas/suggestions as to whats going on?

Spark Screenshot: http://ltc.uww.edu/private/axelsena/spark.jpg

I did a fresh install of openfire 3.4. beta1 and IM gateway 1.2.0 alpha and the user still gets blank aim roster items. Now, the weird thing is that it only happens for that user so far. I have not been able to duplicate it with different accounts.

Pulled this out of the debug log:

2007.10.18 16:47:47 Received iq packet: <iq id="0ubF2-111" to="user1@aim.myserver.edu" type="get" from="username@myserver.edu/spark"><vCard xmlns="vcard-temp"></vCard>
</iq>
2007.10.18 16:47:47 Unable to handle iq request: vcard-temp
2007.10.18 16:47:47 aim: Sending packet: <iq type="error" id="0ubF2-111" from="user1@aim.myserver.edu" to="username@myserver.edu/spark"><error code="503" type="cancel"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></service-unavailable></error></iq>
2007.10.18 16:47:48 Received iq packet: <iq id="0ubF2-112" to="user2@aim.myserver.edu" type="get" from="username@myserver.edu/spark"><vCard xmlns="vcard-temp"></vCard>
</iq>
2007.10.18 16:47:48 Unable to handle iq request: vcard-temp
2007.10.18 16:47:48 aim: Sending packet: <iq type="error" id="0ubF2-112" from="user2@aim.myserver.edu" to="username@myserver.edu/spark"><error code="503" type="cancel"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></service-unavailable></error></iq>
2007.10.18 16:47:50 Received iq packet: <iq id="0ubF2-113" to="+15555555555@aim.myserver.edu" type="get" from="username@myserver.edu/spark"><vCard xmlns="vcard-temp"></vCard>
</iq>
2007.10.18 16:47:50 Unable to handle iq request: vcard-temp
2007.10.18 16:47:50 aim: Sending packet: <iq type="error" id="0ubF2-113" from="+15555555555@aim.myserver.edu" to="username@myserver.edu/spark"><error code="503" type="cancel"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></service-unavailable></error></iq>
2007.10.18 16:47:50 Received iq packet: <iq id="0ubF2-114" to="user3@aim.myserver.edu" type="get" from="username@myserver.edu/spark"><vCard xmlns="vcard-temp"></vCard>
</iq>
2007.10.18 16:47:50 Unable to handle iq request: vcard-temp
2007.10.18 16:47:50 aim: Sending packet: <iq type="error" id="0ubF2-114" from="user3@aim.myserver.edu" to="username@myserver.edu/spark"><error code="503" type="cancel"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></service-unavailable></error></iq>
2007.10.18 16:47:50 Received iq packet: <iq id="0ubF2-115" to="user4@aim.myserver.edu" type="get" from="username@myserver.edu/spark"><vCard xmlns="vcard-temp"></vCard>
</iq>
2007.10.18 16:47:50 Unable to handle iq request: vcard-temp
2007.10.18 16:47:50 aim: Sending packet: <iq type="error" id="0ubF2-115" from="user4@aim.myserver.edu" to="username@myserver.edu/spark"><error code="503" type="cancel"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></service-unavailable></error></iq>
2007.10.18 16:47:50 Received iq packet: <iq id="0ubF2-116" to="user5@aim.myserver.edu" type="get" from="username@myserver.edu/spark"><vCard xmlns="vcard-temp"></vCard>
</iq>
2007.10.18 16:47:50 Unable to handle iq request: vcard-temp
2007.10.18 16:47:50 aim: Sending packet: <iq type="error" id="0ubF2-116" from="user5@aim.myserver.edu" to="username@myserver.edu/spark"><error code="503" type="cancel"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"></service-unavailable></error></iq>

Hi Aaron! Those logs shouldn’t matter. Since vcards aren’t supported yet, a vcard request gets an error. (what you are seeing is typically because of mousing over things in spark -> auto-vcard request) Have you checked to see if the contact in question literally has an empty nickname/name? I found that was the case with some of my contacts when I first saw this. I don’t know what caused them to be busted in the first place though.

Is there a solution for this problem yet? Is that a spark issue or a server issue? We are about to deploy Openfire and during the testing one of the users had the same problem