Blackberry - Activation Problem

When you try to activate blackberry and it stucks at saying

encryption verified...
................
..............
"waiting for the services"

Then it can be services issue. ensure that following services are started on BES.

Blackberry Policy Service
Blackberry Synchronization Service

To activate new BB, this services must be started.

Setting the location of the BES server log files.

1. Open BlackBerry Server Configuration.

2. Click the Logging tab.

3. Press the Browse button [...] and choose the desired location of the log files.

4. Apply settings and press OK button close window.

Outlook - Meeting appointment Problem

When you send meeting appointment to someone and you receive following error message :
The following recipient(s) could not be reached:
/O=XYZ/OU=FIRST ADMINISTRATIVE
GROUP/CN=RECIPIENTS/CN=rparmar on 2008/02/20 17:54
The e-mail account does not exist at the organization this
message was sent to. Check the e-mail address, or contact the recipient
directly to find out the correct address.The MTS-ID of the original
message is:c=us;a= ;p=xyz;l=XYZPERSER1-080220085403Z-1384



Then it s delegation issue. Check outlook of the meeting appointment recepient.
Go to Tool -> Options -> delegates and remove delegates to users(in this case rparmar) who no longer exists in active directory.

This will reslove the issue.

how to restore exchange database using RSG and Data Protector

1.Create Recovery Storage Group on the server.
2.Add database to RSG.
Make sure you select different location for database file and streaming file(different location from Original files) and ensure that “This database can be overwritten by a restore” checkbox is checked.
3.Now on data protector select database to be restored. Select the correct version and make sure that tapes are in drive.
NOTE : if tape is expired and you get error in restoration . Do “import Catalog ” for that tape.
On options tab, specify the directory for temporary files
4.Once database is restored then use eseutil to check whether database is in clean shutdown state or Dirty shutdown state. Use following command to check it

Eseutil /mh "Full path of restored .edb file"

5.if the database is in “Dirty shutdown ” state use following command to fix the database file.

Eseutil /p /i "Full path of restored .edb file"

It takes quite long time to fix database file and it depends on the size of database.

6.Once the above process finish , use command in step 5 to make sure that database is in clean shutdown state.
7.once database is in clean shutdown state then Go back to Exchange manager and do “Mount store” on RSG.
8.Once database is mounted, use Exmerge to restore mailbox to PST file.

Steps to restore Exchagne 2003

Steps to restore exchange server 2003
1. Replace any damaged hardware. If possible, ensure that all replacement hardware in the server you are rebuilding is identical to the hardware that existed in the server that experienced the disaster.
2. Install windows 2003 on the server that you are rebuilding.
3. Restore the windows backup set that was performed on the damaged server to the
server you are rebuilding. Restoring the windows backup set restores the windows 2003
system files, including the registry database and internet information services metabase files. This process also provides the server that you are rebuilding with its original NetBIOS name and returns it to the correct domain. If you do not perform this step, you cannot properly run setup in disaster recovery mode.
4. Install any windows 2003 service packs and software updates that were running on the damaged server to the server you are rebuilding.
5. Install any application (other than exchange server 2003) that run on the server.
6. Restore any additional data backups that were performed on the damaged server.
7. Run exchange server 2003 setup in disaster recovery mode. This process installs
exchange applications and any necessary exchange files to the server you are rebuilding. This process also uses the configuration information that is stored on the exchange server object in Active directory to reclaim the configuration of the original server. The configuration information that is reclaimed includes the exchange storage group names, mailbox store names, public folder store names, and virtual server configuration settings. When you run exchange in disaster recovery mode, ensure that all the components that existed on the damaged server are selected.
8. If not already selected, select disaster recovery for each component that was installed on the damaged server.
9. Install Exchange server 2003 to the same drive and directory that it was installed to on the damaged server. At a minimum, you should ensure that all the drive letters on which databases and log files were kept are available.
10. Install any exchange server 2003 hotfixes that were running on the damaged server.
11. Install in disaster recovery mode any exchange server 2003 service packs that were running previously on the damaged server to the server. Installing exchange server 2003 service packs in disaster recovery mode prevents the exchange databases from being mounted at the end of the service pack installation process, which enables you to proceed to restoring the exchange databases from backup.
12. After exchange database restore, check the state of the database by using eseutil. If they are in dirty shutdown state, use eseutil to covert them to clean shutdown state. Once exchange databases are in clean shutdown, you can mount them.
13. Restore exchange database files and log files to the correct locations from the backup.
14. If you do not have the latest log files then you will lose changes that were made to exchange databases up to the time the disaster occurred.