Enterprise Activation using Dekstop Manager

Sebenarnya ada 3 Step dalam Enterprise Activation (mendaftarkan device BB ke BES Server) antara lain :

1. Via Wireless --> IT BES men-set password EA. Kemudian user menginput password tersebut ke menu di device BB. Options --> Advanced Options --> Enterprise Activation. Masukkan alamat email + password yg di set oleh IT BES

2. Via Desktop Manager --> User menginstall aplikasi Desktop Manager for BES di PC dimana user menggunakan email client-nya (Outlook atau Notes)

3. Via Server BES langsung --> Device BB dicolokkan langsung ke BES Server

Berikut panduan untuk Enterprise Activatiion (EA) via Desktop Manager

A. install aplikasi Desktop Manager (DM) for BES

B. Buka aplikasi DM tersebut, kemudian pilih Email Settings

klik menu Advanced --> Encryption Key. pilih Generate Key manually



Klik Tombol Generate.



gerak-gerakan mouse hingga handset merespon New Generate Key dari Server BES.

Error Description for BlackBerry

Berikut notifikasi Error dan penjelasan arti kode Error yg muncul saat handset BlackBerry Anda mengalami masalah (crash). Dan muncul notifikasi kode Error.

ERROR DESCRIPTION
Code Error	Description
101	Internal JVM error
102	Invalid code in file system. The .cod files in the handheld have been checked for modification and it has been determined that there is a problem with one or more .cod files.
103	The starting address for the boot .cod file cannot be found. This might mean that a boot .cod file has not been installed on the handheld, or that its format is invalid or corrupt.
104	An uncaught Java exception was thrown in the Java code and diagnosed by the JVM. Execution can be continued or the handheld can be attached to a debugger on a desktop through a serial or USB cable. The event log should contain the traceback of the thrown exception.
105	An OS file system API returned an error status for a certain operation. This can indicate a corrupt file system or an error in the JVM.
106	An error has been detected in the graphics system of the handheld.
107	Internal JVM error.
108	Internal JVM error.
109	Internal JVM error.
110	Non-idle event downtime error. A problem has been detected in the accumulation of JVM down time that represents how long the JVM has been idle. This indicates an error in either the OS code or the JVM code.
200	Application manager threw an uncaught exception. The application manager event thread threw an uncaught exception and so cannot continue running.
201	Initialization of the cryptographic system failed and the handheld cannot continue to operate.
202	An attack on the key store has been detected, and the handheld cannot continue to operate.
203	The application manager console process, usually the Home screen ribbon, has failed, like due to an uncaught exception.
501	Internal error.
502	All processes exited. The last Java process has terminated, and there is nothing left to execute.
503	Internal error.
504	Internal error.
505	Internal error.
506	An uncaught Java exception was thrown in the initial VM Java thread thus killing the only live thread in the system. The event log contains the traceback for the exception.
507	A dependency on a .cod file could not be satisfied due to a missing .cod file. Load the missing .cod file onto the handheld.
508	Invalid object. A problem has been detected with a debugger command to the VM
516	Error occurred during garbage collection, which might indicate a corrupted file system.
510	All threads are waiting on objects, which results in a deadlock. The system cannot recover from this state since no thread can release a lock.
511	A problem has occurred during debugging.
515	The reachable objects form a group that cannot be represented properly by the VM because there are too many objects or the total size of the objects is too large.
516	When committing a persistent object, the VM found that the persistent store id counter has reached its limit. The object was not committed
517	An inconsistency has been detected in the VM persistent object store.
518	Internal error.
519	Internal error.
520	Internal error.
521	Indicates that Object.wait() has been executed by a thread that holds a lock on another object; occurs only in simulator if the JvmDebugWaits application switch.
522	A thread has acquired two locks on objects in an order that doesn't match the order that previous locks for the two types were acquired, which indicates a future potential deadlock situation; reported only in the simulator when the JvmDebugLocks application switch is set.
523	A critical Java process has died and the device cannot continue to operate normally.
524	An object has been marked as recovered by the Low Memory Manager but it was not freed during a garbage collection. This is only checked in the simulator under the control of the JvmDebugLMM application switch.
525	Bad persistent object. An auto-commit operation during a garbage collection has detected a non-persistent object reachable from the persistent store root. The type of the object has been output into the event log.
526	The class definition for java.lang.Object cannot be found.
527	The class definition for java.lang.String cannot be found.
528	The file system is corrupted. Data on the handheld is unrecoverable.
529	The file system is corrupted. An attempt is going to be made to recover data, but some data might be lost.
530	Internal JVM error.
531	Flash memory has been exhausted.
532	A JVM assertion has been violated. This error can occur only in the simulator, not on an actual handheld

Sebagian case Error diatas bisa diatasi dg install ulang OS di BB dengan melakukan Wipe OS dahulu (Java_Loader). Kemudian install kembali fress OS ke BB melalui Desktop Manager.

STORM as Modem di VISTA

Berikut panduan BlackBerry Storm (9500) di set sebagai modem pada Windows Vista




Pastikan Desktop Manager dalam keadaan Aktif dan BB 9500 terkoneksi melalui kabel data.

Klik menu Start --> Control Panel. pilih menu Phone and Modem options



Klik tombol Change Settings





pilih tab menu Diagnostics, kemudian klik tombol Query Modem . Pastikan muncul hasilnya seperti gambar dibawah.



Klik tab Advanced. isikan parameter seperti gambar, klik Ok




Pada menu Windows, masuk ke pilihan Control Panel --> Network and Sharing Center
kemudian pilih menu Setup a connection or network



pilih Connect to the Internet, kemudian klik Next




Pilih Create New Connection



Pilih Connect using dial-up modem



pilih Standard Modem



buat profile modem. contoh seperti gambar dibawah

untuk user name dan password = 'kosong'. kemudian klik Connect









Untuk Speed tergantung koneksi dan kapastitas di network area tersebut.

Karena BlackBerry hanya memiliki driver Standard Modem untuk Windows maka kecepatannya secara general adalah 115,2 Kbps

JL_CMDER atau Java Loader

Berfungsi untuk me-wipe OS atau me-reset factory device handset BB

Aplikasi bisa didownload di : http://www.4shared.com/file/98795641/4d77fce2/JL_Cmder_v190.html


1. Jalankan aplikasi JL_Cmder-nya, pastikan BB dicolok dan dalam keadaan tanpa SIM Card dan memory card



2. Jika BB-nya ada password device maka pilih Yes dan ketikkan password device. Namun jika tidak, silahkan pilih No untuk lanjut.



3. Pilih menu (4) Wipe --> untuk Wipe OS atau pilih menu (5) reset of factory


4. Muncul notifikasi, pilih Yes untuk melanjutkan


5. Proses Wipe


6. Di handset akan muncul seperti dibawah ini. Artinya sekarang handset tanpa OS


Untuk meng-install OS, bisa melalui Dekstop Manager. Pilih Application Loader.

Atau coba cara berikut :

Buka Command Prompt di Windows, ketikkan directory seperti dibawah


.



Selanjutkan akan melakukan install OS ke device melalui Desktop Manager

Desktop Manager for BES user

Berikut panduan installasi Dekstop Manager untuk user BES



1. Contoh installer Desktop Manager v4.7
Bisa di download di : http://na.blackberry.com/eng/support/downloads/download_sites.jsp


2.



3.


4.



5.


6.


7.



8.


9.



10.



11.

Change Device Dg DM 4.7

Jika kita ingin melakukan penggantian handset BlackBerry, dari BlackBerry A ke BlackBerry B secara instant termasuk memindahkan data-data dan aplikasi yg terinstall. Kita bisa menggunakan fitur change Device melalui Desktop Manager. Fitur tersebut sudah bisa ditemui di versi Desktop Manager versi 4.2, namun di versi 4.7 interface-nya lebih mudah.

Berikut langkahnya :

1. Buka aplikasi Desktop Manager 4.7, pilih menu Device Switch Wizzard



2. Pastikan kedua handset BlackBerry dicolokkan di PC atau Laptop




3. Pilih menu Switch BlackBerry Devices, klik Start



4. Pilih PIN Devices yg akan dipindahkan (sebelah kiri) dan PIN Devices baru (sebelah kanan). Pastikan jangan sampai tertukar. Cek kembali dimasing-masing PIN device melalui menu Options --> Status



5. Progress Read & Backup data di BlackBerry lama



6.



Progress Restore Data







Finish, data di BB A sudah berhasil direstore di BB B

Problem BlackBerry Messenger

Sering ditemui case saat ber-Instant Messaging menggunakan Blackberry Messenger justru nama orang lain yg muncul. Bukan nama kita sendiri.

Salah satu penyebabnya adalah handset tersebut 2nd (bekas) dipakai user lain sebelumnya. Dan tidak dilakukan Wipe Handheld dahulu. sehingga masih menyisakan data contact lama didalamnya.

Untuk user BES biasanya belum ter-refresh secara system di BES Server. Misal user A mendelegate handset-nya ke user B. dan saat user B menggunakan handset user A, sebagian contact BBM [BlackBerry Messenger] masih nyangkut. Baik yg diadd dg metode Add by Email maupun Add By PIN.

Solusi :

1. Pastikan Info name (My Info) sudah sesuai dg nama user. Masuk ke aplikasi BBM --> tekan menu pilih Edit My Info ketik nama user.








2. Untuk contact yg bermasalah, bisa dilakukan re-Add lagi. Delete contact-nya, kemudian add kembali by email maupun by PIN handset.