[dpeters11]

This isn't a big deal, but how do I refresh the status section of the Handheld Configuration Tool? It looks like it hasn't updated since I got my 7520. It doesn't matter if I click refresh on the main screen, it just never updates.

[Snakeblood]

hi, I could really use some help with this.

I'm in the middle of setting up my Blackberry system, with the Exchange 2k set up on one machine, BES installed with SQL service manager on another machine, in a small domain. They each have individually assigned i.p. addresses, and appear to be running fine. When I try to open the Blackberry handheld configuration tool, I get an error: 'Database connection pool failed to initialise'.

I'm running Blackberry 4.0, and will be forever grateful for any help.

[Masud]

Hi Snakeblood,

Did you ever find any solution for this problem? Please let me know! Thanks.

Cheers,

Masud

[g3tb3nt]

I am getting this issue as well.........

Has anyone else experienced this opening the handheld configuration tool on a BES 4.0 server?

[jibi]

@g3tb3nt, http://www.blackberryforums.com/show...onnection+pool

@dpeters11 (not that its probably needed 6 months later), reactivate your handheld via EA (wired or wireless). you may have to remove your Desktop [] service books prior to doing this (wired would be preferrable after the removal of the service books).

[g3tb3nt]

"Hi all,

The issue has been solved, thanks to forum member Snakeblood...for general public knowledge purposes, I am posting the solution here:

This seems to be a known issue when using a local MSDE and is caused by the absence of two protocols. To enable these two protocols, go to the MS SQL Server folder in "Program Files\Microsoft SQL Server\80\Tools\Binn\" and run the application: "SVRNETCN.exe". Here enable 'Named Pipes' and 'TCP/IP' protocols.

Then restart MSSQLSERVER service and restart the BES

Many thanks to Snakeblood for filling me in!

Cheers,

Masud"


Verified that these are both enabled on our SQL server........

Still no luck :(

[i_m_insanity]

RIM has released hotfix 3 for BES 4.0 SP1. I was informed by RIM tech support that this hotfix is supposed to resolve this issue. I have yet to schedule an outage to apply it for our BES.