08-25-15 05:00 AM
39 12
tools
  1. lawrencecar's Avatar
    In an effort to ward off the freak attack vulnerability, i installed on my Verizon Z10 the leaked OS 2558 and 2576 as well. Both worked fine but when i try to sign into Enterprise IM (on BES 10) i get a server unavailable error. If i role back to previous OS ver of 2267 works fine. Thoughts ?
    03-17-15 08:58 AM
  2. delboyca's Avatar
    We've also found this in my company, only devices on the latest FREAK OS level fail with Enterprise IM logon.

    No solution at the moment, but our BES team is contacting BlackBerry.



    Posted via CB10
    03-17-15 09:59 AM
  3. lawrencecar's Avatar
    We've also found this in my company, only devices on the latest FREAK OS level fail with Enterprise IM logon.

    No solution at the moment, but our BES team is contacting BlackBerry.



    Posted via CB10

    thanks for the reply. Will keep an eye out.
    03-17-15 10:37 AM
  4. Bert Vespermann's Avatar
    Hi, wie have the same trouble with Lync and the newest BB OS Update.
    Z10: 10.3.1.1779 (no more FREAK)
    Z30: 10.3.1.1767 (no more FREAK)

    Our BlackBerry-Business-Support has no information about the problem or a resolution. We dont have the newest BES10-Server-Insallation nor the newest Collaboration Service Plugin.

    BES 10.1.3
    Collaboration Service (on BES): 10.2.0.8


    There is an upgrade of the Collab. Service to 10.2.2MR3 avaible, but we cant do that without an extravagant customer engineering approval. And there ist no information or garantie, that it would help.

    What versions of "BES10 Server" and "Collaboration Service" do you have installed?
    03-18-15 06:33 AM
  5. DeviousTDI's Avatar
    I'll check in the office. It I don't think they have a new bes 10 server or collaboration service that will fix the bug. Took us a while to narrow down the os/device combination that was a problem. Our classic users - fine. Our Z30/Q10 users that had upgraded to the latest handheld os get the Error.

    T-Support is aware of the issue but as of late day yesterday no ETA to resolution. Ugh on the quality control of the build. It's causing major pains at our org and current solution is to roll back the OS (which is pretty painful operation to do to 40+ devices that have the bad build.

    Posted via CB10
    Last edited by DeviousTDI; 03-20-15 at 01:06 PM.
    03-20-15 07:40 AM
  6. lawrencecar's Avatar
    I'll check in the office. It I don't think they have a new bed 10 server or collaboration service that will fix the bug. Took us a while to narrow down the os/device combination that was a problem. Our classic users - fine. Our Z30/Q10 users that had upgraded to the latest handheld os get the Error.

    T-Support is aware of the issue but as of late day yesterday no ETA to resolution. Ugh on the quality control of the build. It's causing major pains at our org and current solution is to roll back the OS (which is pretty painful operation to do to 40+ devices that have the bad build.

    Posted via CB10
    Agree,, seems like major miss in testing as at least for us the Enterprise IM is used extensively. We have over 4000 devices but fortunately only a small amount has upgraded the new OS before we noticed the flaw.
    03-20-15 08:46 AM
  7. DeviousTDI's Avatar
    No good update yet. We had to roll back 2 users that are travelling overseas on the weekend to 2267.

    Groan.. that was fun.
    03-20-15 04:34 PM
  8. lawrencecar's Avatar
    No good update yet. We had to roll back 2 users that are travelling overseas on the weekend to 2267.

    Groan.. that was fun.
    yes did the same thing back to 2267..
    03-20-15 05:05 PM
  9. menshawy's Avatar
    03-25-15 10:14 AM
  10. Zorro4X4's Avatar
    The error although same as mentioned in the KB is not related to it. The issue is being tracked by BlackBerry under "JI 898186". BlackBerry states there is no resolution or workaround for the problem for the OS's that remediate the FREAK attack. Expecting BlackBerry to release a fix for the problem.

    Posted via BlackBerry Passport
    03-25-15 11:46 AM
  11. menshawy's Avatar
    The error although same as mentioned in the KB is not related to it. The issue is being tracked by BlackBerry under "JI 898186". BlackBerry states there is no resolution or workaround for the problem for the OS's that remediate the FREAK attack. Expecting BlackBerry to release a fix for the problem.

    Posted via BlackBerry Passport
    A fix like an update in EIM? Or how do you see it

    Posted via CB10
    03-25-15 04:20 PM
  12. Zorro4X4's Avatar
    A fix like an update in EIM? Or how do you see it

    Posted via CB10
    Something like 10.3.1.2480 that had a patch for Passport screen flickering, or maybe an updated version of EIM. I'm not sure.

    Posted via BlackBerry Passport
    menshawy likes this.
    03-26-15 07:59 AM
  13. menshawy's Avatar
    Anyone loaded the latest 10.3.2 leak and tried the EIM?
    03-26-15 09:40 AM
  14. DeviousTDI's Avatar
    I'm running 10.3.2 (not leak, but from BB) and I can confirm it does not fix EIM.

    You have to go back to 2267.

    Support claims the fix will be in an OS release either Friday or Monday but then one has to wait for carriers. I'm pulling my hair out as we have a lot of users impacted now that are very frustrated. Reloading old OS's is a real party.

    Anyone loaded the latest 10.3.2 leak and tried the EIM?
    menshawy likes this.
    03-26-15 04:22 PM
  15. lawrencecar's Avatar
    awaiting to see what happens here..
    03-26-15 04:43 PM
  16. menshawy's Avatar
    03-27-15 09:19 AM
  17. DeviousTDI's Avatar
    Thanks -- based on that it confirms what I wanted to test. I wondered if they broke something when they added EIM to BES12 with the release of 12.1. Bottom line confirms it for me... i'll probably bring up a 12.1 eval server so I can get these people online. Less painful than backing up their device and reolling them back to an older 10.3.1. release.

    I'll do that today and post results.
    03-27-15 10:26 AM
  18. DeviousTDI's Avatar
    Well. That went in a different direction. My bes guy tried to rush a bes 12.1 install and it didn't happen Friday. So I was left still having myself and other users sans EIM.

    Looks like bes updated the KB 36835 to state they have a SQL workaround. It was a slightly more major deal because my collaberation service was 10.2.0.8 and the document is clearly written with 10.2.2 in mind so step one was upgrading my collaberation service to 10.2.2 and then do a bunch of cert gobblygook, update the IMConfig table with new private key and certificate and I'm all good again.

    Pretty sure all types of devices and OS versions can EIM again. Hurrah.

    Takes calling t support. Reference the KB. Wait on hold for eons to find someone (I waited an hour) the. They have to request the script and document from another group that they finally email you.

    They told me expect it in a day or so. I told them it better cone in an hour.

    Lovely guy he was, I got a script in an hour.


    Posted via CB10
    03-29-15 01:13 AM
  19. lawrencecar's Avatar
    we are upgrading to bes 12 on 4/1. will advise on outcome. just installed 10.3.1.2708 last night. Im going to leave it on until after bes update to see what happens.
    03-29-15 08:12 AM
  20. Zorro4X4's Avatar
    The problem is prevalent in BES 10 and BES 12.

    Posted via BlackBerry Passport.
    03-29-15 01:21 PM
  21. lawrencecar's Avatar
    The problem is prevalent in BES 10 and BES 12.

    Posted via BlackBerry Passport.
    according to the kb36835, This issue is not applicable to BES5 or BES12 version 12.1.
    03-29-15 07:30 PM
  22. DeviousTDI's Avatar
    If you are running 10.2.2 of the collab service, just do the workaround. Probably takes 20 minutes.

    One weird thing that has begun happening is devices have randomly frozen when we launch IM now (this started before we did the workaround). Doesn't even get to the login screen of IM. We've had to wipe the work side and that seems to correct it (reboot does not... launching app in airplane mode does not).

    Annoying, but at least my EIM works again.
    03-30-15 09:59 AM
  23. chedardog's Avatar
    Anyone else running into issues with Step 9 of the certificate replacement instructions?

    The error we get is:
    cert - invalid argument at 0, try -h!
    Failed with error: [0xb005] invalid usage

    We only replaced the -p and -ct:TLS values as instructed, what are we doing wrong?
    03-30-15 03:48 PM
  24. DeviousTDI's Avatar
    I had no issues. Paste me what you put and I'll compare vs what I did.

    Posted via CB10
    03-30-15 11:38 PM
  25. vinay dhimar's Avatar
    I have the same 'cannot sign in' 'the server is currently unavailable. Please try again later.'

    Our BES (10.2.1.19) (collaborations service 10.2.2) supports approx. 50 users some who have updated beyond 10.3.1.2552 and some lucky ones who have not yet updated to 10.3.1 so are not getting this and able to log in fine.

    Do we know when BB intend to release an update to either the OS to fix this issue??? Our business uses Lync 2013 and Enterprise IM heavily so this is a real nightmare at the moment!!

    Cheers
    Vin
    03-31-15 04:57 AM
39 12

Similar Threads

  1. New FREE BBM Sticker!
    By radewa in forum General BBM Chat
    Replies: 27
    Last Post: 04-28-16, 05:37 AM
  2. Delete automatic OS update
    By Carmels in forum BlackBerry 10 OS
    Replies: 7
    Last Post: 03-17-15, 11:01 AM
  3. Contacts, +45 or 0045 ?
    By Warios in forum BlackBerry Q10
    Replies: 3
    Last Post: 03-17-15, 09:54 AM
  4. BBM with China Unicom not working properly.
    By xplizitremix in forum BlackBerry Passport
    Replies: 0
    Last Post: 03-17-15, 06:35 AM
LINK TO POST COPIED TO CLIPBOARD