[betabob]

For the past several weeks I have been unable to use the built-in IM app on my T-Mobile 8700. When I try logging into either AOL or MSN, both get hung up in the "receiving buddies" phase, but eventually they both time out. Interestingly if I am logged onto IM on my PC at the time I do automatically get logged off, so I know that the 8700 is doing something. Any ideas here?

[zymurgyboy]

That's interesting. Wish I had an answer for you. But I will pile on, since I'm having a similar problem with the OZ messenger app on my T-Mob 8100. I was logged into AIM on my Mac when I attempted to log into it on my Pearl and it hasn't worked since. I did get notified that I was logged on elsewhere and dutifully followed the prompts to kill the remote session on my Mac, but logging in through OZ eventually failed and hasn't worked since.

Now if I try to use OZ it hangs at 20% through the sign on process at which point I'll get an SMS from #4760 with a bunch of gibberish that does make it clear I've successfully authenticated with aol's Oscar server, but eventually I get an error in OZ stating that there was a communication error and it closes out.

I just upgraded the handheld OS to get my new 2GB microSD card working, hoping it might cure the OZ problem at the same time, but no luck.

[tprime]

I encountered this problem last year when i first brought my bb 7100t. I have since deleted that Oz IMsgr off my BB7100t and immediately when I got my 8700g. If you use AIM try Ramble. Yahoo and Google talk you can Download from BBhelp website. For msn I recently installed Verichat. That Oz program seem to be a bust for most people.

[betabob]

Yeah, I would definitely agree that the OZ software is unstable. Even prior to this problem it would go through periods of flakiness. I tried to access the website where you can d/l the software, thinking that a reinstall might fix the problem, but I can't even connect to the URL anymore. I was also wondering if this could be some type of service book issue, and perhaps deleting/re-downloading the appropriate service books could also fix the problem.