BlackBerry® Enterprise Server Version 5.0

[hemant]

Hello All,

I just now completed the installation of BES on my local server.
Details:-
BES Version 5.0.1 for MS Exchange Server 2007
Windows 2008 Server

After, installation, when I checked whether service are running/not, I found most of the services were stopped and also when I clicked on BlackBerry Administration service option, the browser shows error on SSL certificate, when I continue anyway it shows "HTTP Error 404.0 Not Found".

Also, I can see the status of Dispatcher service, it is in Starting state.
Dispatcher log shows,

[30058] (01/19 08:26:04.312):{0x1DEC} Starting Database
[30000] (01/19 08:26:04.312):{0x10A8} [DIAG] EVENT=Register_thread, THREADID=0x10A8, THREADNAME="CBESRpcServer"
[30000] (01/19 08:26:04.313):{0x1DEC} ADO ConnectionTimeout value = 30s
[30000] (01/19 08:26:04.313):{0x1DEC} ADO ConnectionTimeout for re-initalizing the pool = 45s
[25137] (01/19 08:26:34.320):{0x1DEC} {ConnectionItem::ConnectToDB} Failed to connect. Connection string is Provider=SQLNCLI.1;Server=SERVER\BLACKBERRY;Databa se=BESMgmt;Network=dbmssocn;Trusted_Connection=Yes
[25000] (01/19 08:26:34.320):{0x1DEC} ConnectionItem::ConnectToDB: COM Error 0x80004005 - Unspecified error - Source: "Microsoft SQL Native Client" - Description "SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. " - Command "ConnectionItem::ConnectToDB"
[25105] (01/19 08:26:34.320):{0x1DEC} Failed to authenticate connection - local machine time may be out of sync with domain controller time. Please restart Windows Time Service.
[25105] (01/19 08:26:34.320):{0x1DEC} Failed to authenticate connection - local machine time may be out of sync with domain controller time. Please restart Windows Time Service.
[25105] (01/19 08:26:34.320):{0x1DEC} Failed to authenticate connection - local machine time may be out of sync with domain controller time. Please restart Windows Time Service.
[35028] (01/19 08:26:34.320):{0x1DEC} {ConnectionPool::InitializePool()} Pool Initialization failed for attempt 1 of 5
[25137] (01/19 08:27:14.310):{0x1DEC} {ConnectionItem::ConnectToDB} Failed to connect. Connection string is Provider=SQLNCLI.1;Server=SERVER\BLACKBERRY;Databa se=BESMgmt;Network=dbmssocn;Trusted_Connection=Yes
[35029] (01/19 08:27:14.310):{0x1DEC} {ConnectionPool::InitializePool()} Pool Initialization failed because timeout of 60 seconds was exceeded
[20652] (01/19 08:27:14.311):{0x1DEC} OpenDB: OPEN_DB failed
[20645] (01/19 08:27:14.311):{0x1DEC} DBInit: OpenDB failed - 0

Any idea what may be going wrong here. I know, there might be many reasons for all these errors, but I need to start from somewhere now.
So, if anyone having idea about the same, then please guide me.

Thanks and appreciate your response,
Hemant

[ce4you]

I believe it is some sort of problem with your SQL database. Is it running? What type of authentication did you use during SQL install and what kind during BES install?

[hemant]

I verified the things, SQL Server is running. Even form BES configration wizard I am able to test the SQL Server connection.

Even with SQL Server manager, I can anytime connect to SQL server.

I am using Windows Auth to connect to BES.

During SQL Server installation, I selected both (SQL and indows Auth Mode).

Even I tried to restaart the Windows Time Service. But not having much success with it.

Any suggesions?

[ce4you]

More info about SQL and accounts used needed If noone else can help better, then please tell me...

1) What is your SQL version / install type / local/remote / instance?

2) What account is SQL running under?

3) What account and with what priviledges was BES installed under?

4) Did you successfully verified SRP info during BES install?

5) Since you are using windows authentication, which account did you use for the successful testing of the connection to SQL server?

Sorry to ask you but this seems like a general problem...

[hemant]

hi,

1.  SQL SERver 2008, Local

2.  BES has created SQL server account called MACHINE/BLACKBERRY, it is running under Local service account.

3.   Account BESAdmin -- Domain Users+Local Admin

4.   Yes.

5.   BESAdmin

Hope, this will answer your questions.

Thanks and appreciate your response,

Hemant

[keithk23]

Did you ever resolve this issue?  I am having the same problem!

Thank you,

Keith

[keithk23]

I was able to get my issue resolved!! 

For those that run into this issue, I had to change the SQL Server Browser from Disabled to Automatic and everything started working properly! 

[ElKabong]

Thanks for the suggestion KeithK23.  This has seemed to work for us, too.  Here's a little more detailed rundown of our situation.

What I was seeing on my 5.0 BES was a repeating series of errors, happening at least once a minute.  There were a ton of these that preceded a BES thread shutdown

First, there would be some DB-related error, as shown below, that looks like BES was trying to connect with the SQL DB.

EVENTID 25000   SOURCE: Blackberry Messaging Agent <SERVERNAME> Agent <X>

 ODBCRecord DoGetFirstValue: COM Error 0x80040E2F - IDispatch error #3119 - Source: "Microsoft SQL Native Client" - Description "Cannot insert duplicate key row in object 'dbo.SyncFolderList' with unique index 'IX_SyncFolderList_GUIDLoc'." - Command "ODBCRecord DoGetFirstValue"

Next, there’d be a ‘failed to authenticate’ error, which also referenced the domain time synch, recommending that the time service be started.  I think this was a red herring, as others who had this error said restart of the svc did nothing.  Sounds like it was bad coding on RIM’s part.  This is a BES-reported error in the app log, NOT a true Windows error reported in the system log.  Tsk Tsk RIM…

EVENTID 25105   SOURCE: Blackberry Messaging Agent <SERVERNAME> Agent <X>

Failed to authenticate connection - local machine time may be out of sync with domain controller time. Please restart Windows Time Service.

  

Finally, (after one or more of the same or similar errors shown above), the ‘cycle’ would end with the error shown below. 

 EVENTID 20000   SOURCE: Blackberry Messaging Agent <SERVERNAME> Agent <X>

ODBCRecord DoGetFirstValue SQL = "calling proc SyncFolderPrivateAdd".

What we did was to enable/start the SQL browser service on our remote SQL 2005 server (it had been disabled), and then I restarted the BES services.  Haven't seen it since <so far...>  I've seen one other person report  this as a solution to this issue, and it seemed to work for us.

Good Luck and thanks again!