cocoaforge

Hi...

I really need some help/advice.

I've used Adium for several months now, so far being very happy. I updated to 1.3.2 recently when it all started to go wrong. I sign on using 2 MSN accounts at once, but they will no longer connect.

I removed this version and went back to 1.3.1 , but still no luck. I've even gone back to 1.3.0- but will still not connect.

On the PREFERENCES>>ACCOUNTS page, whilst they try to connect, the status remains stuck on 'Handshaking-12%' with no movement.

Other programs such as aMSN, Mercury allow me to sign in with these accounts, so it is definitely Adium which is the problem.

Any advice guys?

Have you tried 1.3.3rc1 @ http://beta.adiumx.com/? If it doesn't work then post a debug log, see http://trac.adiumx.com/wiki/CurrentAdiumDebug.

i have the same issue - using 1.3.3. rc1 -- in the previous version (non beta) it would take me cancelling connect and re-connecting 3 or 4 times to get it to connect.. today it wasnt connecting at all so i upgraded... now i have no connect..

"Connection error from Notification server:
Unable to connect"): Automatically reconnecting in 600.000000 seconds (14 attempts performed)

I also have the same thing, I try to log in (I used multiple accounts, so it wasn't a 1 account specific thing) and it hangs at 75% "controleren" ("checking" in English). I have tried the 3.1 version the 3.2 and the 3.3rc1 version, all of them the same thing.
It started about Christmas, it happened some times and since Newyear I've been using Microsoft messenger as I can't log in anymore.

Dimmuxx wrote:Have you tried 1.3.3rc1 @ http://beta.adiumx.com/? If it doesn't work then post a debug log, see http://trac.adiumx.com/wiki/CurrentAdiumDebug.

There are some logs in http://trac.adiumx.com/ticket/11684.

Robby wrote:

Dimmuxx wrote:Have you tried 1.3.3rc1 @ http://beta.adiumx.com/? If it doesn't work then post a debug log, see http://trac.adiumx.com/wiki/CurrentAdiumDebug.

There are some logs in http://trac.adiumx.com/ticket/11684.

Not from rossy09 though and #11684 might not be the same problem.