BES is 4.1.4 with MR5 installed.
mapi32.dll/cdo.dlll are matching versions as i've verified these repeatedly in my attempts to fix this (i apologize but it's late and i don't feel like logging on to get the exact version numbers).
"other issues" simply means my eventvwr on the BES is spammed repeatedly with event id's:
(these numbers are now drilled into my brain).
None of them make much sense because if you read them, and believe them, then this BES does not work at all and no user can get anything from this BES with their handhelds. This is obviously not true as my 15 daily users (heavy-hitting attorneys with tons of items, and their paralegals with said same) would be lighting my ass on fire right now. I'm simply trying to make sense of it all before something really hairy happens here. All I need to do is add a new user with a new BB handheld. FIN.
As per my previous post, the RIM call i was on at that moment was 'mysteriously' disconnected and i've heard nothing back from them yet and have not tried to call in again.
the MAGT log I have not yet truly scoured as it simply reflects what eventvwr says; ServerDN not established, User not started - may restart after ScanGAL, etc etc.
Q: is there any place any where to look up those 'iDispatch' error codes???
I "assumed" the E2k7 was 'trumping' E2k3 as Mailbox Agent 2 because before this environment had an E2k7 box, Mailbox Agent 2 never existed/populated/entered itself into the picture.
FYI ~ Both the E2k3 and E2k7 boxes are on VMWare servers.
I've sexto-checked the Services account rights and all is good there.
I've verified my mailbox (which is the 'new' user I am trying to add here) is/was/always has been only a member of the E2k3 Server (which is what the BES connection relies on).
Thanks for the reply; I'm willing to try anything at this point.