BlackBerry Monitoring Service - Polling Engine - failed start

[Jeldos]

Hello,
I have a problem with BlackBerry Monitoring Service after upgrade from BES 5.0.1 to 5.0.2.


Server with BES and monitoring is W2003x64 EN sp2 and all updates.
Update was BES sucesfully

I used:

1. besx_upgrader_5.0.2.exe
2. besx502mr4
3. interim bes_as_fix_1038261_5.0.2

and everything works fine, but after restart BlackBerry Monitoring Service - Polling Engine service doesn't start.


The instance's SvcRun() method failed

File "win32serviceutil.pyo", line 785, in SvcRun

File "enginesvc.pyo", line 69, in SvcDoRun

File "engine.pyo", line 223, in main

File "tools\db_convert_console.pyo", line 157, in timestamp_convert

File "tools\db_convert_console.pyo", line 85, in set_complete_status

File "tools\timestamp_utc_convert.pyo", line 206, in set_convert_status

File "common\db\db.pyo", line 114, in execute

File "common\db\db.pyo", line 90, in _run

File "common\db\db_connection_manager.pyo", line 368, in run

File "C:\DOCUME~1\besadmin\LOCALS~1\Temp\gen_py\2.5\2A7 5196C-D9EB-4129-B803-931327F72D5Cx0x2x8.py", line 1997, in Execute

File "win32com\client\__init__.pyo", line 448, in _ApplyTypes_

<class 'pywintypes.com_error'>: (-2147352567, 'Exception occurred.', (0, 'Microsoft SQL Native Client', 'The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.', None, 0, -2147217913), None)

I tried set date and time on server to another format, but it doesn't work.

Is here anybody who have any idea how to solve this problem?

Thanks..

[scottj3]

Did you ever find a resolution to this? We are suddenly seeing these exact same symptoms in our lab environment, possibly as a result of the BES 5.0.2 MR4 install, but not sure if the timing was exact on that. Monitoring had been working fine for months in that environment but now has stopped with the errors you mentioned.

We have tried regenerting the web keystore file as some have suggested and no luck there. Have also completely removed and re-install the BES Monitoring services and still are experiencing problems. This is a veru frustrating issue.

[scottj3]

For us the "broken" Monitoring Services turned out to be caused by Windows Server 2008 R2 Service Pack 1. Doing an extensive review of logs showed that Monitoring broke after the SP1 reboot. We removed SP1 and Monitoring immediately started working again. Then just to verify applied SP1 again as this was a lab server anyway, and Monitoring Services broke again.

Don't know if this is a known bug or something unique to our environment. Have not seen it referenced in any KB's or forum posts.