05-22-2013 02:07 PM
I have installed the BCS addon for BES 10.1 and deployed the app to my Z10 running 10.1 and am having issues connecting. I can open the app and try to login, but I get this message.
"Cannot Sign In: There server is currently unavailable. Please try again later."
When I look at the BBIM logs on the server, it shows its connected to the internal sametime server.
<2013-05-22 08:40:50.501 CDT>::<BBIM_FDLIC-BES10_BBIM_1>:<INFO >:<LAYER = SCM, Starting EIMServer ... >
<2013-05-22 08:40:50.564 CDT>::<BBIM_FDLIC-BES10_BBIM_1>:<INFO >:<LAYER = BBIM, Sametime version: minor 8521; major 30>
<2013-05-22 08:40:52.648 CDT>::<BBIM_FDLIC-BES10_BBIM_1>:<DEBUG>:<LAYER = BBIM, Did not load non-secure port. Server only accessible over secured connection.>
<2013-05-22 08:40:52.788 CDT>::<BBIM_FDLIC-BES10_BBIM_1>:<INFO >:<LAYER = SCM, RetrieveAddressBookAPIPoolJobPool Pool size = 20>
<2013-05-22 08:40:52.788 CDT>::<BBIM_FDLIC-BES10_BBIM_1>:<INFO >:<LAYER = BBIM, Sametime Connection logged in succesfull: SERVERNAME>
Can anyone assist as to why I cannot connect?
05-31-2013 04:40 PM
Add a me too to this one...
Thinking maybe it doesn't like a non SSL connection to the sametime server??
No time to open ticket today...will have to wait until after conference next week.
06-03-2013 10:49 AM
have the same issue. Installed BES10.1 and BB Coll. Service in the latest version. Z10 is updated to OS 10.1. Pushed BlackBerry Enterprise IM App to company World, installed the app on the Z10 device. Checking the settings in BAS Coll. Service aera to the old BES5 server... same. ST Server is already upgraded to 8.5.2 with Domino 8.5.3. Started the app typing in my Username like the old BB Device with first and lastname with internet password. After pushing OK button, the message appears immediately the the server in not available. Did some search with wireshark and checked the firewall logs, it seems that the connection from Device --> Blackberry --> Collaboration Service ends on the BDS server. There is no traffic on our Sametime server simultaneously.
Where is the problem? Network? BCS? Bug? In front of the monitor?
Giving up for today. I am fed up with this service a.t.m.
06-14-2013 11:35 AM
So as I expected, BCS wants Sametime to be using SSL as opposed to HTTP. This kinda sucks because it's all internal and our existing BES5 Sametime functions fine as is.