Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® Enterprise Service 10

Reply
New Contributor
jon_rp
Posts: 4
Registered: ‎08-03-2009
My Device: Not Specified

Office communications server and BES 5.0.1 MR1

I upgraded my BES to 5.0.1 MR1 last night and now I'm not able to log into OCS (Office Communications Server) on my Blackberry Tour. The error is "cannot contact server". On the BES server, I am able to access the ocs client web access that my server is configured to hit, so I'm not sure what might be missing. We are running OCS R2 and I am aware of the lack of support for R2 but we still have an OCS 2007 R1 CWA server in place that it is connecting to, so that shouldn't be a problem.

 

Any help would be greatly appreciated. Thanks.

Please use plain text.
New Contributor
jon_rp
Posts: 4
Registered: ‎08-03-2009
My Device: Not Specified

Re: Office communications server and BES 5.0.1 MR1

I resolved this on my own. I had to regenerate the peer to peer encryption key from the BAS.

Please use plain text.
Guru III
knottyrope
Posts: 30,117
Registered: ‎06-25-2008
My Device:

I'm rockin the BlackBerry Z30, Z10, Q10, BlackBerry Mini Stereo Speaker, 64 gig PlayBook, BlackBerry Wireless Headset HS-700

My Carrier: I am on AT&T. Please edit your Personal Profile with your DEVICE TYPE, DEVICE OS and Carrier

Re: Office communications server and BES 5.0.1 MR1

Thanks for sharing the solution with us.

 




Click here to Backup the data on your BlackBerry Device! It's important, and FREE!


Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals

BESAdmin's, please make a signature with your BES environment info.


SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope


Want to thank me? Buy my KnottyRope App here


BES 5.0.4 and BES 10.2.2 with Exchange 2010 and SQL 2008


Please use plain text.