[Azmere]

Hi All,

I'm really hoping that someone else has come across this. Recently I upgraded from 5.0.1 to SP2 on my stager servers. All appeared to go well. However I noticed I was getting extremly slow response times 1 week after installing. I decided to reboot the servers.

As this is a stager platform the SQL 2005 resides on the same server as the primary BES server. A HA server is also configured and both share a BAS pool name of the FQDN of the 1st server.

Upon reboot the BAS wont load. I've come across this before and worked through the numerous KB articles as it was was usually related to the Keystore passwords etc.
However in this case, even though the service was running no log files were showing. They just had stopped after the reboot (for the BAS).

I located this error in the BAS-AS_err.log

"SSL handshake failed: The TDS protocol stream is not valid."

I located KB19310

Now my SQL database is local to the server and I dont have SSL enabled. I'm not all that familiar with SQL server so I'm not sure where the certificates are found that the article refer's to. I have checked the local java cacerts file and the certificates directory on the SQL managment studio software and there is nothing obvious there.

Has anyone else come across this an resolved it? Does anyone know where I can find the offending cert?

Really need some help on this one.

[Azmere]

Just thought I'd post an update to this one in case anyone was following it.

Currently I have a open docket in with RIM. They advise that this currently under investigation. They can only provide workarounds as listed in KB19310. However I have found that even having the SQL server local to the BAS does not work etc. The only one that worked was the removal of the Enterprise issues certificates. Not a great option.

The JDBC driver can't be updated to version 3.0 due to the BAS not supporting it.

I'll post again if I find any other solutions.

[raindownsugar]

We added another cert in the chain (for another db on the instance) that pushed us over 4kb and now I can't see BAS either. It's a mess.

[wistowg]

Had a similar issue after upgrade to 5.0.2 (3 BESs in the pool). After server reboot or restart of services check in Task Manager to see how much memory the BAS-AS service is using. If it's less than 300MB then the BAS console will not load. On my servers it stuck at between 33 & 80MB. I tried all sorts of fixes but in the end a re-install of 5.0.2 resolved - no changes, just re-ran setup.exe and didn't change any settings.

[raindownsugar]

I'm fairly certain that our deal is the >4KB cert chain issue. We added the new cert to the chain just over a week ago and BAS has been busted since then. This is a new Exchange BES with no production users so at this point it hasn't been much of an issue. This weekend we will roll off the new cert and move that db to another instance. I imagine we'll be good at that point. I wonder when RIM will go green with JDBC 2.0?