I had sametime working fine with the BES for months, we upgraded the sametime server to 7.5 and now the BES can't connect. RIM's support is it's usual useless self and I still can't get it working. The error from the BB_IM log is "Sametime Connection logged out; REASON [ 8000021c]: " Rim said that this has been known to happen and to try connecting from another server. I set up a test server and I get the same message. I have the ip's trusted, and ports open. I have been playing with the vps_allowed_login settings in the notes.ini as a long shot. If that line is not in the ini then it is open right for any client to connect, or does that setting need to be made in the sametime.ini ?? I need some help if anybody has any ideas, please let me know.

It's not a RIM issue it's Sametime. We had similar issue after upgrading to 7.5.1. Updating with 7.5.1 CF1 fixed a lot of issues.

I was thinking it was a sametime issue, but there are no rejection errors in the sametime logs. Does anybody know of any domino debug parameters I could use to log the failed entry in sametime. That would tell me that the bes connection command is making it thru to the sametime server. RIM's failure message is generic so maybe something from sametime would be more informative.

I think you're on the right track. The vps_allowed_login setting controls what terminal types are accepted by the Sametime server; I found it when Notes 8 beta clients were being rejected. An easy test (if you can restart the SameTime service) would be to remove it and see if your clients connect. If so, you need to figure out what their client strings are. If not, there' some other problem.

BES BBIM service calls the NotesAPI for connecting to Sametime servers, usually it will leave the error code in the BBIM log. Good that you have gathered from the BBIM log => "8000021C".

IBM has an article on the list of Sametime Community Services error codes here - IBM - Explanation of error codes associated with Sametime Community Services

<snip>
user does not have appropriate privilege level --- 0x8000021C
</snip>

Have you upgraded Sametime to 7.5.1 CF1 as suggested by x14?

I got the same problem here. I'm on BES 4.1.3 & Sametime 7.5.1CF1. Appreciate any help!

I opened a PMR with IBM and after weeks of narrowing down the issue, and recreating the stconfig.nsf (and everything else they could think of) we never did get it to work correctly. We have a work around by adding VPS_BYPASS_TRUSTED_IPS=1 to the sametime.ini, but to some companies this might be a security issue on the sametime server. IBM said it was not an issue for us as the sametime server resides in the DMZ. So for now we leave the debug parameter in place, maybe the next sametime update will help.

Have you checked the following KB article in RIM site Doc ID : KB14187

After the upgrade did you resend the service book to the blackberry users.

Install the sametime client on the blackberry server and try connecting to the sametime server using sametime client. if you can able to do that then the problem is not with the connection.

Are you connecting to the sametime server using IP address or FQHN of the sametime server.

Regards

I recall from another thread it was mentioned that there was a lot of Sametime issue with BES 4.1.3.

I've skipped 4.1.3 completely. I was running 4.1.2 and upgraded to 4.1.4 MR2.

All, having a similar issue here. I did a knife-edge from my data center in Los Angeles to the data center in Florida. All went well except for the Sametime connectivity. I updated the community servers field in the Sametime config with the new address. I discovered that it did not update the actual CommunityConfig doc in the sametime directory so I manually edited it. In the BBIM log I see the known error “Sametime Connection logged out; REASON [ 8000021c]”. I have pushed policy and service books. But I am also seeing a bunch of java errors that I suspect is the real problem. I’m lost here with the java errors. I’ll attach here in hopes someone can help me out.

Thanks-Jeff

BES 4.1.4.15/Domino 7.0.3/Win2K3sp2

Sametime 6.5.1/Domino 6.5.2/Win2000sp4

Open the stconfig.nsf and inside the communityconnectivity field, make sure that you add the ip address of the BES into the community trusted ips field.