could not send; a connection error occurred

Just a suggestion, have you tried turning off any firewalls?

Same here, but only occasionally. No firewalls, just the NAT from my ISP. I have to say that it happened on the official MSN® Messenger© client for Windows™ too from time to time (that was back when I had a PC eheh).

I'm having the same problem. And I don't have any firewalls or anything set up at the moment. This is the first time I've seen it come up so regularly.

Same problem, but it works sometimes. It works with older versions or other chat clients. Wierd.

I got this too just now. Started Adium, and suddenly I couldn't send. No firewalls, although a NAT. Updated to .88 as soon as it was released, didn't run into a problem (although I was NATless then) until just now. Suddenly, about a minute later, it worked again.

Same problem!

OS X 10.4.4, AdiumX 0.88 (replaced the adiumx.app package, as an upgrade, was using 0.87).

I see the same thing. Proteus works fine, as did Adium 0.87. Delete prefs, that didn't help. I am on OSX 10.3.9 with all patches applied.

Same problem here. I'm on Tiger, fully updated, with Adium 0.88, on a G4. The connection error doesn't happen every time, but if it does, it happens for every msn conversation (ie, you have to restart adium to try to remedy it - but even that doesn't often work, stopping and restarting doesn't necessarily sort it). I had no problems with 0.87

i saw the same issues with the current 1.0svn version, but actually the messages arrive (even if the error is shown)

I'm getting the same thing, and it's driving me crazy. Anyone have a workaround for this yet?

Same problem here.

I wonder would .87 be available anywhere else as I would like to downgrade again.

Yeah, me too. The right msn picture bug that was fixed in this release is really nice, but I'd rather be able to talk as soon as I log on.

Ps. Give us damn webcam support! haha

I get the same error on my Adium (I thought I was the only one!). Something that should be noted is that I can successfully message someone if *they* message me first.

Please use Adium X 0.88b6, the last Beta version of 0.88, which includes a debug window under the Adium menu; post the activity in the debug window as you connect to MSN and message a contact, receiving in response the error.

Here is mine. I started up, opened the debug window and messaged one contact:

(Libgaim: msg) Error: Unable to call the user eafritz77@hotmail.com (Libgaim: msn) destroy httpconn (0x46dfac0) (Libgaim: msn) S: NS 000: 800 28 (Libgaim: msg) Error: Unable to call the user snowangel_969@hotmail.com (Libgaim: msn) destroy httpconn (0x4b677d0) (Libgaim: proxy) Connected. (Libgaim: oscar) email: connected (Libgaim: proxy) Connected. (Libgaim: oscar) chatnav: connected (Libgaim: oscar) removing chatnav input watcher (Libgaim: msn) S: NS 000: RNG 16822703 207.46.0.148:1863 CKI 1138559041.14908 danny_desousa@hotmail.com NCC (Libgaim: msn) new httpconn (0x4b599a0) (Libgaim: msn) S: NS 000: RNG 556265950 65.54.228.29:1863 CKI 4311449.168198244 panic42@hotmail.com Evan (Libgaim: msn) new httpconn (0x4b3daf0) (Libgaim: proxy) Connecting to 207.46.0.148:1863 with no proxy (Libgaim: proxy) Connect would have blocked. (Libgaim: proxy) Connecting to 65.54.228.29:1863 with no proxy (Libgaim: proxy) Connect would have blocked. (Libgaim: proxy) Connected. (Libgaim: msn) C: SB 017: ANS 1 erin@thedalzells.org 1138559041.14908 16822703 (Libgaim: proxy) Connected. (Libgaim: msn) C: SB 018: ANS 1 erin@thedalzells.org 4311449.168198244 556265950 (Libgaim: msn) S: SB 017: IRO 1 1 1 danny_desousa@hotmail.com NCC (Libgaim: msn) S: SB 017: ANS 1 OK (Libgaim: msn) S: SB 018: IRO 1 1 1 panic42@hotmail.com Evan (Libgaim: msn) S: SB 018: ANS 1 OK (Libgaim: msn) S: SB 017: MSG danny_desousa@hotmail.com NCC 814 (Libgaim: msn) C: SB 017: MSG 2 D 150 (Libgaim: msn) C: SB 017: MSG 3 D 486 (Libgaim: msn) C: SB 017: MSG 4 D 154 (Libgaim: msn) C: SB 017: MSG 5 D 1352 (Libgaim: msn) S: SB 017: MSG danny_desousa@hotmail.com NCC 96 (Libgaim: msn) S: SB 018: MSG panic42@hotmail.com Evan 812 (Libgaim: msn) C: SB 018: MSG 2 D 144 (Libgaim: msn) C: SB 018: MSG 3 D 478 (Libgaim: msn) C: SB 018: MSG 4 D 148 (Libgaim: msn) C: SB 018: MSG 5 D 1346 (Libgaim: msn) S: SB 018: MSG panic42@hotmail.com Evan 96 (Libgaim: msn) S: SB 017: ACK 2 (Libgaim: msn) S: SB 018: ACK 2 (Libgaim: proxy) Connecting to 205.188.1.128:5190 with no proxy (Libgaim: proxy) Connect would have blocked. (Libgaim: proxy) Connecting to 64.12.31.128:5190 with no proxy (Libgaim: proxy) Connect would have blocked. (Libgaim: oscar) chat info: Chat Rights: (Libgaim: oscar) chat info: Max Concurrent Rooms: 3 (Libgaim: oscar) chat info: Exchange List: (16 total) (Libgaim: oscar) chat info: 20 (Libgaim: oscar) chat info: 16 (Libgaim: oscar) chat info: 15 (Libgaim: oscar) chat info: 14 (Libgaim: oscar) chat info: 13 (Libgaim: oscar) chat info: 12 (Libgaim: oscar) chat info: 11 (Libgaim: oscar) chat info: 10 (Libgaim: oscar) chat info: 9 (Libgaim: oscar) chat info: 8 (Libgaim: oscar) chat info: 7 (Libgaim: oscar) chat info: 6 (Libgaim: oscar) chat info: 5 (Libgaim: oscar) chat info: 4 (Libgaim: oscar) chat info: 2 (Libgaim: oscar) chat info: 1 (Libgaim: msn) S: SB 017: ACK 3 (Libgaim: msn) S: SB 017: ACK 4 (Libgaim: msn) S: SB 017: ACK 5 (Libgaim: msn) C: SB 017: MSG 6 D 1352 (Libgaim: msn) S: SB 018: ACK 3 (Libgaim: msn) S: SB 018: ACK 4 (Libgaim: msn) S: SB 018: ACK 5 (Libgaim: msn) C: SB 018: MSG 6 D 1346 (Libgaim: msn) S: SB 017: MSG danny_desousa@hotmail.com NCC 145 (Libgaim: msn) S: SB 017: MSG danny_desousa@hotmail.com NCC 145 (Libgaim: msn) S: SB 017: ACK 6 (Libgaim: msn) C: SB 017: MSG 7 D 1352 (Libgaim: proxy) Connected. (Libgaim: oscar) icon: connected (Libgaim: proxy) Connected. (Libgaim: oscar) icon: connected (Libgaim: msn) S: SB 018: ACK 6 (Libgaim: msn) C: SB 018: MSG 7 D 1346 (Libgaim: msn) S: SB 018: MSG panic42@hotmail.com Evan 145 (Libgaim: msn) S: SB 017: ACK 7 (Libgaim: msn) C: SB 017: MSG 8 D 193 (Libgaim: msn) S: SB 018: ACK 7 (Libgaim: msn) C: SB 018: MSG 8 D 187 (Libgaim: msn) S: SB 017: ACK 8 (Libgaim: msn) S: SB 018: MSG panic42@hotmail.com Evan 145 (Libgaim: msn) S: SB 018: ACK 8 (Libgaim: msn) S: SB 017: MSG danny_desousa@hotmail.com NCC 145 (Libgaim: msn) S: SB 017: BYE danny_desousa@hotmail.com (Libgaim: msn) C: SB 017: OUT (Libgaim: msn) destroy httpconn (0x4b599a0) (Libgaim: msn) S: SB 018: MSG panic42@hotmail.com Evan 145 (Libgaim: msn) S: SB 018: BYE panic42@hotmail.com (Libgaim: msn) C: SB 018: OUT (Libgaim: msn) destroy httpconn (0x4b3daf0) (Libgaim: oscar) no more icons to request (Libgaim: oscar) no more icons to request 64: Update status for <AIListContact: 0x4b008a0>:ICQ.1128613 to type 1 ((null)); message (null) 64: Update status for <AIListContact: 0x469af30>:ICQ.209235 to type 1 ((null)); message (null) (Libgaim: msn) S: NS 000: CHL 0 97962103724023260733 (Libgaim: msn) C: NS 000: QRY 29 PROD0038W!61ZTF9 32 (Libgaim: msn) S: NS 000: QRY 29 [AIChat: 4bd32c0 initForAccount] chatWithContact: Added <<<AIChat: 0x4bd32c0>:MSN.herring@telus.net>> [<NSCFSet: 0x463fd0> (<AIChat: 0x4bd32c0>:MSN.herring@telus.net)] gaim openChat:<AIChat: 0x4bd32c0>:MSN.herring@telus.net for MSN.herring@telus.net adiumGaimConvWindowAddConv adiumGaimConvWindowShow Sending testing 1 2 3 from <ESGaimMSNAccount: 0x4615310>:1:erin@thedalzells.org to <AIChat: 0x4bd32c0>:MSN.herring@telus.net Should update fingerprints list objectsBeingReceived: (empty) (Libgaim: msn) new httpconn (0x5134c80) (Libgaim: msn) C: NS 000: XFR 30 SB (Libgaim: msn) Appending message to queue. (Libgaim: msn) S: NS 000: 800 30 (Libgaim: msg) Error: Unable to call the user herring@telus.net (Libgaim: msn) Switchboard with unassigned conversation *** Conversation error type 6 (herring@telus.net): Message could not be sent because an error with the switchboard occurred: (Libgaim: msn) Switchboard with unassigned conversation (Libgaim: msn) destroy httpconn (0x5134c80) objectsBeingReceived: (empty) (Libgaim: msn) S: NS 000: FLN herring@telus.net objectsBeingReceived: (empty) (Libgaim: jabber) Recv (ssl)(198): <iq to="erin.dalzell@gmail.com/Adium8B96AD5D" id="0E2FFA72" type="set"><query xmlns="jabber:iq:roster"><item jid="evan.wise@gmail.com" subscription="both"><group>Personal</group></item></query></iq>

please preformat console or debug window output. see WikiFormatting.

erin@thedalzells.org, your log begins with an error; please include the debug log from when you connected to when you received the error. Opening the debug window as you connect is probably necessary to get the full thing. Please attach logs to the ticket as text files rather than posting them directly (and as boredzo said, use WikiFormatting when posting directly) to allow discussion within the ticket to continue.

Sorry about that guys...first time I have used this trac thingy. How do I attach a file to a bug report?

OK, I have now set up my Adium to not log into any when I start it up, so what I will do, is start Adium, then open the debug window, then connect to MSN, and then message someone.

Is that correct?

Whoops...just saw the attach file button...log incoming...

Adium log of error

Please try Adium 0.88-msn-test1, lather, rinse, and repeat :) It may fix the issue, and if it doesn't it should give slightly more verbose debug output.

Didn't fix the issue. Log attached.

Alright, let's try another direction based on that output... please give Adium 0.88-msng-test2 a shot. This version may make user icons not update as well; if it doens't fix it, let me know, and if it does, please pay attention to whether contacts' icons change appropriately (perhaps ask a contact or two to change their picture temporarily). Thanks :)

Great news...that seems to work! None of mt friends ar the icon changing type, so I can't really help you there, sorry.

Crap, the issue came back...the second time I opened a window to someone I get the same error...log attached shortly

Oh, and the icon didn't change.

errors at the bottom

Erin, did 0.87 do this for you? I ask because the -test2 build shouldn't differ from 0.87...

No, I didn't see it do it. Let me try 0.87 then and we can see if that exhibits the same behaviour.

Cool, let me know. (Adium 0.87 if you need the link.

Actually, please check with both Adium 0.87 and with AdiumX_0.88-msn-test3. test3 has added continued to add debug output, so if you have a failure with it please post your full debug log as before.

Adium .87 link doesn't work.

Oops. Adium 0.87.

Debug -- w/ Adiumx 0.88 MSN Test 3 (Error Persists)

Error persists for me (I posted my log) w/ Adium 0.88 MSN test 3. Reverted to 0.87 (problem goes away).

MSN test3 log

msn 3 doesn't work. 0.87 does. Posted log.

Please try both:

• AdiumX_0.88msn-test-4 basically reverts the buddy icon fix which was in 0.88, but with some extra debug code and with some of the changes intact... trying to focus in.
• AdiumX_0.88-msn-test5-0.87msn.dmg uses the exact msn protocol files used in 0.87... so if this still fails, there's something really sneaky going on, which would almost be encouraging considering how confusing this bug is...

Please be sure to open the debug window before you connect so your output contains everything from start to error, if you get one. :)

OK, both test4 and test5 worked perfectly, in terms of messaging! Hopefully that tells you something. I have attached both logs just in case.

test4 - success

test5 - success

Okay, so we can fix it, but at the expense of the buddy-icon-updating fix. Let's try to find something that works both ways :) AdiumX_0.88-msn-test6.

Oh, and Erin, are you signing online as Invisible? Just trying to reconcile an oddity I'm seeing in the logs.

I have no idea if I am signing on as Invisible. Where would I check that?

You'd know -- you'd have selected an Invisible status via the Status menu. Don't worry about it, totally peripheral question :)

I don't think I have done that Evan, but I will check when I get home. Unfortunately, I am forced to use Windows at work, so I can't test your stuff until I get home and put the baby to bed.

test6 - no worky

sorry man, test6 no worky. Log attached.

Thanks for your continued help :)

After a number of stabs in the dark, here's a candidate that hopefully addresses the bug at its heart... AdiumX_0.88-msn-test7.dmg.

:=(

:=(

Sad log attached.

Humph. Back to the drawing board.

Same here. But, the problem disappears after cbeing connected for like 60 seconds.

Maybe with the buddy icon fix, you're making too many calls to the server too fast. Try slowing the requests down a bit, so it doesn't give you a temporary ban.

Hm, an interesting theory.. let's try it. AdiumX_0.88-msn-test8.dmg.

Well that one crashed when I logged in to MSN...emailed the crash log to you. Tried twice, same result each time.

*embarassed* Uploaded the wrong copy. Sorry about that :) I'll have the new one uploaded in just a few minutes.

AdiumX_0.88-msn-test9.dmg this is everything test8 was supposed to be. Hopefully that means it works. Increased debug logging and implements Josh's idea about delaying between each request (delay is currently 1 second after each set of requests).

good and bad news. This one works if you wait a couple of seconds before chatting. If you try to chat immediately after connecting, you get the same error. Error log uploaded. If you want the good log, let me know.

The time delay brings up the fact that the error is happening every time you message while the maximum 5 buddy icon requests are going at once... I wonder if that's an incorrect maximum. We'll try requesting no more than 2 at once (I hestitate to change it to 1, 'cause if one buddy were to not respond the update process would halt for a long time). AdiumX_0.88-msn-test10-window2.dmg.

This time the very first chat worked, all others failed. Even if I waited 5 seconds. Log to follow.

BTW, it would be nice if I could upload the log at the same time as writing this note.

The error thrown is, according to the new debug logs which show such things, error 800, which this MSN Messenger Protocol Error Reference list claims is "Changing too rapidly"... so I think we are indeed getting close. I've improved the request-queuing code for buddy icons this time... maybe it'll be enough. AdiumX_0.88-msn-test11.dmg

And yes, I agree about the uploading; unfortunately, it's a current limitation of the Trac system.

This time I could talk to two people and it failed on the 3rd. Log to follow.

The test11 seemed to work for two people, and fail on the third, same as erin's.

We're still getting told by the server that things are happening too fast; I suspect that with the failing builds if you waited 5 to 10 minutes they'd begin to work. Queuing further robustified and slowed down... it's not like a couple extra seconds to retrieve someone's buddy icon when you first connect is going to hurt anything :)

AdiumX_0.88-msn-test12.dmg

OK, this one was a little more interesting. This time I could do 4 people before it failed on the 5th and 6th. Then I waited about a minute and then the 5th and 6th began to work. Log to follow.

Requesting icons worked a lot better when we, um, didn't do it. :P

Next up: AdiumX_0.88-msn-test13.dmg

FYI...I won't able to test this today. Can probably get to it tomorrow. Big poker game tonight!!

Good luck! I won't be able to post new builds until Monday, anyways :)

Good news, that seemed to work ok. Like I mentioned before, I can't test the icon thing as I don't normally use that. I am attaching the log anyway, just in case you need it.

But it looks like we might have a winner!

For all this help, do I win a free copy of Adium? ;=)

You get a whole site license! :D

Fantastic. Judging from your debug log, buddy icons are still coming in (just not at the breakneck pace they wanted to originally), so I think we're good in that department, too. Thanks for all your help -- couldn't have gotten this resolved with you.

Glad I could help. I was a developer in my past life, so I empathize with the plight of trying to fix bugs without being able to reproduce them.

You may have even enticed me to start helping out the Adium bug fixing work. But I have never done Objective C before and my last Mac programming was Metroworks/C/C++/Classic work, so it may take me some time to ramp up. I will take a look at the code and XCode and see if I can help out.

Meh, you require Tiger for development and I am on a lowly Summer 2001 iMac running 10.3.9. New iMac coming in June/July, so may take a look then.

Test 13 worked for me. Thank you!

James H: Awesome :)

erin: Yeah, unfortunately Apple made new versions of Xcode both require Tiger and not be backwards compatible with old 10.3.x versions. I look forward to hearing from you this summer, compiler in hand.

Test 13 working properly over here, will this replace the "old" 0.88 with the nasty bug in it?

(In [15136]) Fixed MSN rate limiting, fixes #2834. Fixed a Google Talk crash when the connection drops hopefully.

I get this same error, I just downloaded the new version (0.89.1) and this issue persists. It is when connecting to MSN and when trying to initiate conversation with some contacts. I am using 10.4.5 behind an authenticated HTTP proxy. Thanks

Is anyone else seeing this?

Works for me. Just signed on with MSN and it's fine.

I just downloaded 0.89.1 after stupid MSN Messenger forced me to download its latest version which now refuses to log in.

After heaps of trouble just logging into MSN through Adium, I now can see my entire contact list but can't chat with a single one of them due to a "connection error".

What can I do?

Try using the HTTP connect method (preferences->accounts->msn account->options).

When pasting a link or typing a url path into an msn conversation I am getting this same message.

I'm running 1.0b5

I notice the "Could not send; a connection error occurred." only happens to me when I send the message, and then close the window right after, as in it doesn't cache the text msg and send it properly (connection is killed by closing the window). Can't wait until this is fixed, because I always find myself closing the window RIGHT after I send a message.

I'm having the same problem as the last comment, but I was using gaim beta3 on linux before I bought my mac and it did the same thing, maybe its a bug on libgaim

The core problem for this ticket has been solved (wherein the error pops up every time a new conversation is begun. For issues with this same error occuring when closing a window right after sending a message, please see #5454