Unable to start BES automatically, but runs manually

[devas]

Hi All,

I am new to BES. I have BES Version 4.1.4.15. I am able to start BES Service Manually. But It does not start automatically. I have SQLSERVER 2005.

I HAVE ALREADY SEEN A SAME TOPIC LIKE THIS IN THIS FORUM. BUT THAT DOESN'T SEEM TO WORK FOR ME!!!

I have following errors in my event log in the specified order

1. The description for Event ID 1111 from source TermServDevices cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

2. The BlackBerry Policy Service service terminated with service-specific error 5003 (0x138B).

3. The BlackBerry Synchronization Service service terminated with service-specific error 5201 (0x1451).

4. The BlackBerry Dispatcher service terminated with service-specific error 5608 (0x15E8).

I have searched these issues and applied the possible changes specified in Article KB03806

I have given the DependOnService in Policy Service Folder, Sync Folder, Dispatcher Folder in the following order in registry.

NtLmSsp
EventLog
LanmanWorkstation
MSSQLSERVER

I use SQLSERVER Windows Authentication. I couldn't understand what is wrong.

Anybody Please help me. This is very urgent for me to fix.

Thanks for any help.


Devas

[epsilon]

Hello devas,

can you do the following test for me? Open Blackberry Server Configuration from start menu and select "database connectivity" tab. Press "test sql server connection" and let us know of the result.

[devas]

Hello devas,

can you do the following test for me? Open Blackberry Server Configuration from start menu and select "database connectivity" tab. Press "test sql server connection" and let us know of the result.

Hi,

Thanks for the Quick reply.

It says "Test Connection to database was Successful!."

[epsilon]

So this means no problems with connectivity. you didn't specify it on the description but I've noticed on the subject that you can run manually the service after BES boots up. Have you tried restarting the server after fixing the registry?

[epsilon]

Also i suggest you take a look on KB04185 which fits your problem and environment.

[devas]

Also i suggest you take a look on KB04185 which fits your problem and environment.

Hi,

As I specified on the subject, There is no problem on starting the BES service manually.

I will look into the article and come back again...

[devas]

Hi I attached my BES Log file.If you need further info, let me know

[epsilon]

Can you also upload MAGT (might be more than one) DISP and ALRT logs?

[devas]

Can you also upload MAGT (might be more than one) DISP and ALRT logs?

Hi

find the files attached,


Thank You

[epsilon]

I found the following:

On your policy service log (POLC):
COM Error 0x80004005 in ConnectionItem::ConnectToDB() - Cannot open database "BESMgmt" requested by the login. The login failed. - Unspecified error (connection string - Provider=SQLOLEDB;Server=BBSERVER;Database=BESMgmt;Trusted_Connection=Yes)

On Messaging Agent logs (MAGT):
ExtUDPNtfThread::DeleteSubscription: COM Error 0x80004005 - Unspecified error - Source: "Microsoft OLE DB Provider for SQL Server" - Description "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied." - Command "DELETE FROM ServiceConfig WHERE id = 64 "

And on dispatcher log (DISP):
COM Error 0x46F4F0 in CheckValidConnection - [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation. - Unspecified error

It's pretty clear that you're dealing with SQL errors related to dependent services that start earlier than SQL server (thus the "sql does not exist" errors).

I would suggest to check this article (KB15017) for a workaround BUT definitely put a call to RIM's support because they might have a proper fix for your problem since DB errors are not properly documented on their support site.

[devas]

I found the following:

On your policy service log (POLC):
COM Error 0x80004005 in ConnectionItem::ConnectToDB() - Cannot open database "BESMgmt" requested by the login. The login failed. - Unspecified error (connection string - Provider=SQLOLEDB;Server=BBSERVER;Database=BESMgmt;Trusted_Connection=Yes)

On Messaging Agent logs (MAGT):
ExtUDPNtfThread::DeleteSubscription: COM Error 0x80004005 - Unspecified error - Source: "Microsoft OLE DB Provider for SQL Server" - Description "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied." - Command "DELETE FROM ServiceConfig WHERE id = 64 "

And on dispatcher log (DISP):
COM Error 0x46F4F0 in CheckValidConnection - [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation. - Unspecified error

It's pretty clear that you're dealing with SQL errors related to dependent services that start earlier than SQL server (thus the "sql does not exist" errors).

I would suggest to check this article (KB15017) for a workaround BUT definitely put a call to RIM's support because they might have a proper fix for your problem since DB errors are not properly documented on their support site.


Hi,

Thanks for your time. I will look into that article and check anything can be done and update again.

Thanks once again

[devas]

Hi,

After using the script specified in the article on startup, My BES starts automatically. Thanks for the link.

But Still, I have the same errors in the system event viewer.

What could be wrong? Please guide me asap.

Thanks for any help.

Additional Info:

In System login screen, It says a service is disabled or unable to start and check that in event viewer (THIS SAME ERROR APPEARS BEFORE USING THE SCRIPT ALSO)

In Application log, there is a warning stating "user jose not started".

I checked the user "jose" in the users list. The user has already been deleted in both Exchange and BES Manager.

In BES Manager home page, It says No. of users is 23. while there is only 22 users.

[epsilon]

1) check the permissions of the service account (besadmin) depending on the exchange version you're running (KB02276)
2) I'm seeing lots of users with names such as "pat" or "jose" you're referring above. have you changed their legacy Exchange Distinguished Name attributes? If yes you should check KB16459 and from what i read rollback the changes.

But definitely for a start check the permissions thoroughly since it seems that the installation is not completed the way it should be.