[penguin3107]

The OCS 2007 client is available for download on blackberry.com

BlackBerry - BlackBerry Enterprise Instant Messaging

EDIT/UPDATE #4: Looks like RIM has gotten their act together. Link above is updated to reflect the changes on RIM's site. Previous updates removed to avoid confusion.

[Sith_Apprentice]

Wirelessly posted (BlackBerry 9000 4.6.0.67)

I was getting ready to post this from the BES-Admin list but you beat me to it. (Y)

[kjarrodc]

Thanks for posting the links. I know what I'll be doing today...

[penguin3107]

So far no luck logging in with the new client.
Anyone want to take a stab at troubleshooting based on this error log below?
I can log in just fine through CWA on my PC, so I'm pretty sure CWA is configured properly.

<2008-07-24 10:40:27.269 EDT>:[65]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, EVENT = ReceivedFromDevice, SRPID = S45454545, DEVICEPIN = pinpinpi, USERID = u3, TAG = ADA450EF, SIZE = 372>
<2008-07-24 10:40:27.269 EDT>:[66]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = SCM, EVENT = StartJob, name = IMLoginJobPool-Thread-1, queueDelay(ms) = 0, JobPool = IMLoginJobPool, queueLength = 0, availableThreads = 4>
<2008-07-24 10:40:27.269 EDT>:[67]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, DEVICEPIN = pinpinpi, USERID = u3, THREAD = IMLoginJobPool-Thread-1, TAG = -1381740305, EVENT = INCOMING, TYPE = 1, METHOD = onLoginRequest, SERVICEID = 4, SIZE = 372>
<2008-07-24 10:40:27.550 EDT>:[68]:<BBIM_BES04_BBIM_2>:<INFO >:<LAYER = BBIM, The version of CWA supporting this service is 2007>
<2008-07-24 10:40:28.300 EDT>:[69]:<BBIM_BES04_BBIM_2>:<INFO >:<LAYER = BBIM, DEVICEPIN = pinpinpi, USERID = u3, IM server information = OCS2007/Office Communicator, ocs.my.domain.net:8443>
<2008-07-24 10:40:28.300 EDT>:[70]:<BBIM_BES04_BBIM_2>:<INFO >:<LAYER = BBIM, DEVICEPIN = pinpinpi, USERID = u3, CWA Command Channel = https://ocs.my.domain.net:8443/cwa/MainCommandHandler.ashx>
<2008-07-24 10:40:28.316 EDT>:[71]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, LAYER = BBIM, EVENT = AddSession: u3>
<2008-07-24 10:40:28.316 EDT>:[72]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, LAYER = BBIM, EVENT = AddSession: u3>
<2008-07-24 10:40:28.316 EDT>:[73]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, LAYER = BBIM, EVENT = ActiveSessions: 1>
<2008-07-24 10:40:28.316 EDT>:[74]:<BBIM_BES04_BBIM_2>:<INFO >:<LAYER = BBIM, DEVICEPIN = pinpinpi, USERID = u3, SIP URI = >
<2008-07-24 10:40:28.316 EDT>:[75]:<BBIM_BES04_BBIM_2>:<INFO >:<LAYER = BBIM, DEVICEPIN = pinpinpi, USERID = u3, Account = >
<2008-07-24 10:40:28.394 EDT>:[76]:<BBIM_BES04_BBIM_2>:<WARNG>:<LAYER = BBIM, DEVICEPIN = pinpinpi, USERID = u3, CWA Server -> IM Proxy failure response = CwaRequestFailedResponseType, rid = null>
<2008-07-24 10:40:28.394 EDT>:[77]:<BBIM_BES04_BBIM_2>:<WARNG>:<LAYER = BBIM, DEVICEPIN = pinpinpi, USERID = u3, CWA signon exception for https://ocs.my.domain.net:8443/iwa/logon.html = CWA server did not return a cwaTicket in signon response>
<2008-07-24 10:40:28.394 EDT>:[78]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, DEVICEPIN = pinpinpi, USERID = u3, TAG = 464519169, EVENT = OUTGOING, TYPE = 2, METHOD = writeLoginResponse, RESULT = 304, SIZE = 10>
<2008-07-24 10:40:28.394 EDT>:[79]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, EVENT = CreatedQueue, DEVICEPIN = u3>
<2008-07-24 10:40:28.394 EDT>:[80]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, EVENT = Sending, SRPID = S45454545, DEVICEPIN = pinpinpi, USERID = u3, TAG = 1BB00001, SIZE = 28>
<2008-07-24 10:40:28.394 EDT>:[81]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, LAYER = BBIM, EVENT = RemoveSession: u3>
<2008-07-24 10:40:28.394 EDT>:[82]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, LAYER = BBIM, EVENT = ActiveSessions: 0>
<2008-07-24 10:40:28.394 EDT>:[83]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = SCM, EVENT = FinishJob, name = IMLoginJobPool-Thread-1, timeSpent(ms) = 1125, JobPool = IMLoginJobPool, queueLength = 0, availableThreads = 4>
<2008-07-24 10:40:28.394 EDT>:[84]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = SRP, SRPID = S45454545, EVENT = Sending, VERSION = 1, COMMAND = SEND, TAG = 464519169, SIZE = 154>
<2008-07-24 10:40:35.926 EDT>:[85]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = SRP, SRPID = S45454545, EVENT = Receiving, VERSION = 1, COMMAND = STATUS, TAG = 464519169, SIZE = 10, STATE = DELIVERED>
<2008-07-24 10:40:35.926 EDT>:[86]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, EVENT = RemovedSendingQueue, DEVICEPIN = u3, QueueSize = 0>
<2008-07-24 10:40:35.926 EDT>:[87]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = BBIM, EVENT = Notification, TAG = 1BB00001, STATE = DELIVERED>
<2008-07-24 10:40:36.191 EDT>:[88]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = SRP, SRPID = S45454545, EVENT = Receiving, VERSION = 1, COMMAND = RECEIVE, TAG = 24010187, SIZE = 506>
<2008-07-24 10:40:36.191 EDT>:[89]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = SRP, SRPID = S45454545, EVENT = Sending, VERSION = 1, COMMAND = RECEIVE, TAG = 24010187, SIZE = 10>
<2008-07-24 10:40:36.191 EDT>:[90]:<BBIM_BES04_BBIM_2>:<DEBUG>:<LAYER = SCM, EVENT = ScheduleJob, JobPool = IMLoginJobPool, queueLength = 0, availableThreads = 5>

[kjarrodc]

Just got ours up and running. What's different on this version is that I had to use our full domain name in the user field. So, the username looks like: sub.domain.gov\username.

Does anyone know if configuring the krb5.conf file will have any affect on this? I'd rather my users type in just their username here.

If I had any guesses on your problem, it might be the port settings. If you browse to __https://ocs.my.domain.net:8443/iwa/logon.html from a web browser, does it work?

I had to configure mine to use port 443.

[penguin3107]

Originally Posted by kjarrodc

Just got ours up and running. What's different on this version is that I had to use our full domain name in the user field. So, the username looks like: sub.domain.gov\username.

Does anyone know if configuring the krb5.conf file will have any affect on this? I'd rather my users type in just their username here.

If I had any guesses on your problem, it might be the port settings. If you browse to __https://ocs.my.domain.net:8443/iwa/logon.html from a web browser, does it work?

I had to configure mine to use port 443.

I tried both ports actually.
Right now, it's set to use 443.
If I browse to https://ocs.my.domain.net:443/iwa/logon.html ... It doesn't do much. I get an error message that looks like this:
- <cwaResponses>
<requestFailed eid="16" />
</cwaResponses>

If I switch the port to 8443, it behaves the same way.

[JavaJunkee]

Has this been removed? I only see the two 2005 versions listed in the drop down.

[penguin3107]

Originally Posted by JavaJunkee

Has this been removed? I only see the two 2005 versions listed in the drop down.

Yep... it's gone. Unbelievable.

I just got off the phone with RIM Level 2 support. They couldn't figure out my problem and have escalated the issue. I should have a callback in 24 hours. Not too sure how this is going to play out.

[kjarrodc]

Hrm - Maybe it's just me, but 4.1.6 and ocs 2007 seems to have been rushed.

Had another thought for your penguin3017. "IM Proxy failure response" makes me think maybe it has to do with how your proxy settings are configured for MDS. It's a long shot, but maybe it'd be worth removing all your proxy settings for MDS, restarting all the services, and then try logging in. The idea is that if your request is somehow getting routed outside your network, removing the MDS proxy settings will keep the request within your intranet. ... ( long shot - I know ... )

[JavaJunkee]

Originally Posted by penguin3107

Yep... it's gone. Unbelievable.

Why am I not surprised!

[penguin3107]

Originally Posted by kjarrodc

Hrm - Maybe it's just me, but 4.1.6 and ocs 2007 seems to have been rushed.

Had another thought for your penguin3017. "IM Proxy failure response" makes me think maybe it has to do with how your proxy settings are configured for MDS. It's a long shot, but maybe it'd be worth removing all your proxy settings for MDS, restarting all the services, and then try logging in. The idea is that if your request is somehow getting routed outside your network, removing the MDS proxy settings will keep the request within your intranet. ... ( long shot - I know ... )

It was a good thought... but still no go.
We don't have any proxy servers in our environment at all. All proxy fields in MDS and Collaboration Services properties are empty.

I agree with you. In my opinion, 4.1.6 and OCS 2007 were definitely released too soon.
RIM already admitted (unofficially) that 4.1.6 was mistakenly released prior to its planned release date.

[kjarrodc]

Scratch that last idea. Looking at my logs again, it appears that I get the same "IM Proxy failure response" message if I use incorrect credentials.

Another thought - is your enhanced presence turned on in OCS2007? I just tested another user and he was unable to log into the new OC client until we had his turned on.

[penguin3107]

Originally Posted by kjarrodc

Scratch that last idea. Looking at my logs again, it appears that I get the same "IM Proxy failure response" message if I use incorrect credentials.

Another thought - is your enhanced presence turned on in OCS2007? I just tested another user and he was unable to log into the new OC client until we had his turned on.

Enhanced Presence is turned on for all users. (Just verified.)

Speaking of incorrect credentials... perhaps that's part of my issue.
Maybe I'm just logging in wrong?

For the Sign-In field, and the User Name field, we're using the email address for the user.
Are you using something different?

I wanted to try using the Domain\Username in the sign-in field, but I can't seem to type a backslash in that field.

[kjarrodc]

When I use incorrect credentials, the logs also report:

"Integrated Authentication fails due to invalid username/password or incorrect config/krb5.conf." --- This is what prompted my question on the krb5.conf earlier.

To log in, we're using the following:

Sign-in name:
User name: sub.domain.gov\username
Password: ********

[penguin3107]

Originally Posted by kjarrodc

When I use incorrect credentials, the logs also report:

"Integrated Authentication fails due to invalid username/password or incorrect config/krb5.conf." --- This is what prompted my question on the krb5.conf earlier.

To log in, we're using the following:

Sign-in name:
User name: sub.domain.gov\username
Password: ********

Just out of curiosity...

If you go to log into CWA from a browser on a Windows PC, there's only two fields to enter for the credentials. Sign-In and Password. (At least that's how it is for us.)

We are unable to log in using the email address as the Sign-In. We must use domain\username in that field.

Is this normal, and does yours behave the same way?

[kjarrodc]

Hum - Our CWA does have just the two fields - sign in and password. Here, we have to use domain\username. I believe the credential fields for the BlackBerry OC client and the CWA client are different. Have you tried logging in using the credentials for the BlackBerry OC client like we are?

[penguin3107]

Originally Posted by kjarrodc

Have you tried logging in using the credentials for the BlackBerry OC client like we are?

Yep. No good.
I appreciate all the help so far!

[kjarrodc]

How do you have the collaboration services configured on the BES? I understand that the OC client's communicate through what ever you have specified in the 'office communicator web access server settings' portion of the collaboration service tab.

We have our host name settings simply put "im.domain.gov" (no quotes ... ) with HTTPS selected using port 443.

[kjarrodc]

Also - are you restarting the collaboration services after changing these settings?

[penguin3107]

Originally Posted by kjarrodc

How do you have the collaboration services configured on the BES? I understand that the OC client's communicate through what ever you have specified in the 'office communicator web access server settings' portion of the collaboration service tab.

We have our host name settings simply put "im.domain.gov" (no quotes ... ) with HTTPS selected using port 443.

That's exactly how I have mine set up too.
Host .... ocs.my.domain.net
Port .... 443
Transport Protocol ... HTTPS