Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® Enterprise Service 10

Reply
New Contributor
Posts: 4
Registered: ‎08-10-2013
My Device: Z10
My Carrier: Vodafon
Accepted Solution

WARNING An exception occurred when opening database

[ Edited ]

Hi,

 

after some server crahses of my Traveler V9, i now get these error

 

Notes Traveler: WARNING ..........An exception occurred when opening database CN=xxxxxx/OU=server/O=xx!mail/bkaram.nsf using user shortname xxxxxxxxxx n order to retrieve changed documents. Exception information: Throw: TASK_PROFILE_OPEN_DB
*** Content Adapter Exception ***
Unknown 2 (ERR_ITEM_NOT_FOUND)
--- Debug Info ------------:
Database cannot be opened. 

 

 

The devices are offline now and are not synched.

 

Before everything worked well.

 

Please help

 

Thanks

thomas
--

Guru III
Posts: 32,114
Registered: ‎06-25-2008
My Device:

I'm rockin the BlackBerry PRIV, Passport, Z30, Z10, Q10, BlackBerry Mini Stereo Speaker, 64 gig PlayBook,BT Headset HS-700

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

Re: WARNING An exception occurred when opening database

are the NSF files still intact and present on the server?

 




Click here to Backup the data on your BlackBerry Device! It's important, and FREE!


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.


SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope


Want to thank me? Buy my KnottyRope App here


BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V


New Contributor
Posts: 4
Registered: ‎08-10-2013
My Device: Z10
My Carrier: Vodafon

Re: WARNING An exception occurred when opening database

Hi,

 

Yes they are all working and accessable.

 

But I solved the problem by a defrag on the traveler.

 

 

Thanks for all

 

thomas