Welcome to the Official BlackBerry® Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
All New Topics | All New Posts
inside custom component

BlackBerry® Enterprise Server Version 5.0

Reply
Topic Options
rsenio
Contributor
rsenio
Posts: 11
Registered: 06-12-2009

Oh no!!

Options

11-03-2009 01:10 PM

OK, I'm not sure what has happened. Or if someone was playing where they should not have been but...

 

We are running BES 5.0 Mr3. SQL is on another box (Windows 2008, SQL 2005 sp3). There are other DB's up and running fine on that machine. When the BES services are started things go to hell. Basically SQL stops responding, and I can't even connect to it using SQL Management Studio. Kill all the BES services, and restart SQL on the other server....everything is fine...until BES is started again. I dont see much in the SQL logs as well 

 

I'm not much of a DB guy, but someone please help!

Report Inappropriate Content
Message 1 of 6 (3,356 Views)
Reply
0 Likes
Please use plain text.
 
Guru II
Guru II
knottyrope
Posts: 22,215
Registered: 06-25-2008
My Carrier:

I am on AT&T. Please edit your Personal Profile with your DEVICE TYPE, DEVICE OS and Carrier

Re: Oh no!!

Options

11-03-2009 01:31 PM

Start with checking permissions first.

 

KB02276 - Assigning permissions for a BlackBerry Enterprise Server service account

 

 

Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info. BlackBerry Unlocking FAQ
Report Inappropriate Content
Message 2 of 6 (3,301 Views)
Reply
0 Likes
Please use plain text.
 
rsenio
Contributor
rsenio
Posts: 11
Registered: 06-12-2009

Re: Oh no!!

Options

11-03-2009 02:53 PM

OK, confirmed the permissions as required. When I begin to launch the BES Services I see on the SQL box the following in the event viewer

 

 

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the MSSQLSERVER service.

 

Thats when things begin to go south on the SQL server.

 

Thats when I start the policy service, the event log error on the BES is

NotifyDatabase: COM Error 0x80040E31 - IDispatch error #3121 - Source: Microsoft SQL Native Client - Description Query timeout expired - Command "sp_ServiceConfig

Report Inappropriate Content
Message 3 of 6 (3,290 Views)
Reply
0 Likes
Please use plain text.
 
BlackBerry Technical Advisor
BlackBerry Technical Advisor
CerealBypass
Posts: 616
Registered: 03-25-2009
My Carrier: Bell

Re: Oh no!!

Options

11-03-2009 03:54 PM

IDispatch error #3121 basically tells us that there's a SQL connectivity issue, which would make sense given that SQL becomes unresponsive.

 

Are you able to start the Dispatcher at all?

 

If we just start the Router, Dispatcher and Controller, does the SQL server start to fail? Does it seem to help up until you start the Mailstore, Policy and Synchronization services?

______________________________________________
The only stupid question is the one you don't ask before you reboot the BES.
Report Inappropriate Content
Message 4 of 6 (3,273 Views)
Reply
0 Likes
Please use plain text.
 
rsenio
Contributor
rsenio
Posts: 11
Registered: 06-12-2009

Re: Oh no!!

Options

11-03-2009 05:35 PM

Fired up the router no problem. Tried to start the dispatcher and SQL started to fail on the SQL box

Report Inappropriate Content
Message 5 of 6 (3,263 Views)
Reply
0 Likes
Please use plain text.
 
rsenio
Contributor
rsenio
Posts: 11
Registered: 06-12-2009

Re: Oh no!!

Options

11-04-2009 05:34 PM

I really dont want to believe that this fixed my problem but I applied the setting as described in

support.microsoft.com/kb/918483

 

restarted my SQL services and have yet to have an issue. We'll see

Report Inappropriate Content
Message 6 of 6 (3,205 Views)
Reply
0 Likes
Please use plain text.