When starting the Blackberry Policy Service it stops automatically.

iliaselm · #1 (**permalink**) 06-30-2010, 09:14 AM

Hello ,

When starting the Blackberry Policy Service it stops automatically.

I paste the errors from the eventviewer and bes Polc log here.

Register:
Event Type: Error
Event Source: BlackBerry Policy Service
Event Category: None
Event ID: 10000
Date: 30-6-2010
Time: 12:32:00
User: N/A
Computer: SERVERNAME
Description:
DefaultHandler - exception caught thread Id=0x27E0

Polc log:
[40304] (06/30 13:59:24.750):{0x2C58} WorkerThreadPool:: ThreadProc(): Thread released with empty queue
[45050] (06/30 13:59:24.765):{0x2FEC} DBNS: DbObject=500
[10000] (06/30 13:59:25.515):{0x2774} DefaultHandler - exception caught thread Id=0x2774
[10000] (06/30 13:59:25.515):{0x2774} DefaultHandler - Killing program
[30000] (06/30 13:59:25.515):{0x2774} Exception code: C0000005 ACCESS_VIOLATION
[30000] (06/30 13:59:25.515):{0x2774} Fault address: 00657D31
[30000] (06/30 13:59:25.515):{0x2774} Registers: EAX=0311E424 EBX=00000000 ECX=00000000 EDX=FFFFFFFF
[30000] (06/30 13:59:25.515):{0x2774} ESI=00878370 EDI=00000000 EBP=0311E424 ESP=0311E3A0 EIP=00657D31 FLG=00010202
[30000] (06/30 13:59:25.515):{0x2774} CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

Can somebody help me?

Best regards,
Ilias

Cheese Sammich · #2 (**permalink**) 06-30-2010, 10:34 AM

See here for a workaround:
KB18825 - BlackBerry Router constantly restarts and the SRP shows disconnected

This issue was also resolved with BES 5.0 SP1.

iliaselm · #3 (**permalink**) 06-30-2010, 12:53 PM

Thanks for your help. But as I see, it's another issue.

KB18825

Code:

[30000] (07/10 11:15:19.727):{0x3A0C} Registers: EAX=00000000 EBX=77E616A8 ECX=00541E64 EDX=00000000
[30000] (07/10 11:15:19.727):{0x3A0C} ESI=00541E64 EDI=00541E64 EBP=01CBFBC0 ESP=01CBFBAC EIP=00427F5D FLG=00010216
[30000] (07/10 11:15:19.727):{0x3A0C} CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

Regards,

Ilias

hdawg · #4 (**permalink**) 07-01-2010, 08:50 PM

looking at that log ... I'd try disabling DBNS.

You could also try using the Microsoft Debugger to try to process any / all dump file created by the crash to identify exactly what file is throwing the fault.

I'd also recommend contacting RIM for support on this as it looks like its an unexpected failure and isn't terminating properly ... so its probably a bug.

iliaselm · #5 (**permalink**) 07-05-2010, 05:32 AM

Solved by patient..... .... ..... .....

Remove the last configuration you added to the software configuration and update the .xml's.

KB13589 - How to update the device.xml and vendor.xml files

Follow Us On

Forum Sponsors

Google Advertisements