The Exchange Mail test mimics the mail client activity by using the MAPI (Messaging Application Programming Interface) for sending and receiving mails. If this test does not report measures, then it could indicate that the test is unable to send mails using the test parameters that have been configured. To verify this, run the following command from the command prompt of the Microsoft Outlook 2003 client on which the mailbox that has been configured for this test, exists:

cscript <Path_to_dir_containing_XChgMailTest.vbs>\XChgMailTest.vbs "<The profile name that has been configured for this test>" <Exchange mail box that has been used by this test> <SMTP Server IP configured for this test> <SMTP Port used by this test>

For example, assume that the Exchange Mail test takes the following parameters:

  1. xchgmailboxname:
  2. profilename: Outlook
  3. smtpserver:
  4. smtpport: 25

Also, assume that the XChgMailTest.vbs is available in the C:\eGurkha\lib directory.

In such a case, the command to execute the test will be as follows:

  • cscript c:\eGurkha\lib\XChgMailTest.vbs "Outlook" 25

    If, upon execution, the command returns the measures of the XChgMailTest, it indicates that the test is functioning properly.

    If the test does not execute properly, then either of the following may occur:

  • You might receive the following error message:

    [C:\eGurkha\lib\XChgMailTest.vbs(66, 1) Collaboration Data Objects: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. [Microsoft Exchange Server Information Store - [MAPI_E_FAILONEPROVIDER(8004011D)]], ]]

  • The message box depicted by Figure 8 may appear:


Figure 8 : Message box indicating a problem in sending mails

If the message (a) or any other message bearing references to Collaboration Data Objects (CDO) appears, then it indicates that the Collaboration Data Objects option was not enabled while installing the Microsoft Outlook 2003 client on the box. The Collaboration Data Objects (CDO) library allows you to access the Global Address List and other server objects, in addition to the contents of mailboxes and public folders. As the XChgMailTest actively uses this library, the absence of CDO results in the failure of the test. In such a case, follow the procedure given below to modify your installation, so that CDO is enabled:

  1. Insert the Microsoft Office CD in your CD drive, and run its Setup.exe on the system hosting the Microsoft Outlook Client that has been configured for the XChgMailTest. 
  2. Figure 9 appears requesting your confirmation to reinstall/uninstall/add or remove features to your existing Microsoft Outlook installation.
  3. Choose the Add/Remove Features option and click the Next button to proceed.


    Figure 9 : Selecting the 'Add/Remove Features' option

  4. Then, select the Outlook option from Figure 10, and also click the Choose advanced customization of applications check box. Click the Next button to move on. 


    Figure 10 : Choosing to customize the Outlook installation

  5. In Figure 11 that appears next, expand the Microsoft Office Outlook tree to view the applications/tools within. By default, the Collaboration Data Objects option in the tree will be prefixed by an X mark, indicating that the option is disabled (see Figure 12). To enable the option, click on the X mark, and select the Run from My Computer option from the shortcut menu that appears (see Figure 12).


    Figure 11 : Viewing the currently installed applications


    Figure 12 : electing the Collaboration Data Objects option

  6. Click on the Next button in Figure 12 to proceed.
  7. Finally, when setup completes, click the Finish button to exit.

On the other hand, if manual command execution returned the message box depicted by Figure 8, it indicates that a security patch named O2kSp3.exe is installed on the Outlook client. To ensure that this patch does not affect the functioning of the XchgMail test, do the following:

  1. Download Orktools.exe and admpack.exe from the following URL: to the Outlook client.
  2. Begin installing Orktools.exe on the Outlook client by double-clicking on it. Figure 13 will appear first.


    Figure 13 : The End-use license agreement

  3. Accept the license agreement displayed in Figure 13 by selecting the I accept the terms in the License Agreement option and clicking the Next >> button.
  4. Figure 14 will then appear, from where an installation location will have to be selected. Then, click the Next >> button.


    Figure 14 : Selecting the install directory

  5. Finally, click on the Install Now button in Figure 15 to begin installing the Orktools.exe.


    Figure 15 : Installing Orktools.exe

  6. Next, proceed to install admpack.exe on the Outlook client by double-clicking on it. Select Yes from Figure 16 that appears.


    Figure 16 : Accepting the license agreement for admpack.exe

  7. Next, specify the location to which the files of admpack.exe need to be extracted, and then click the OK button (see Figure 17).


    Figure 17 : Specifying the location of the admpack files

  8. Once installation completes, Figure 18 will appear. Click on the OK button to exit the setup.


    Figure 18 : Completion of admpack installation

  9. Then, go to the Microsoft Exchange Server and open its System Manager using the menu sequence depicted by Figure 19.


    Figure 19 : Opening the System Manager of the Microsoft Exchange Server 2000

  10. Expand the Folders node in the tree-structure in the left pane of the System Manager, right-click on the Public Folders sub-node within, select the New sub-menu from the shortcut menu that appears, and then choose the Public Folder option, to create a new public folder on the Exchange server (see Figure 20).


    Figure 20 : Creating a new Public Folder

  11. Name the new public folder as Outlook Security Settings (see Figure 21), and then click the Apply and ok buttons therein to register the changes.


    Figure 21 : Naming the new public folder

  12. Then, switch back to the Outlook client, and open the directory to which the files of admpack.exe have been extracted. Double-click on the OutlookSecurity.oft within to open the template file (see Figure 22).


    Figure 22 : Opening the OutlookSecurity.oft template file

  13. The Select Folder dialog box will then appear (see Figure 23). Expand the Public Folders node within, followed by the All Public Folder sub-node, and then select the Outlook Security Settings folder that was created in the Microsoft Exchange server. Next, click the ok button in Figure 23.


    Figure 23 : Selecting the Outlook Security Settings folder

  14. The Default Security Settings form (see Figure 24) will open. Now, follow the menu sequence Tools -> Forms -> Publish Form (see Figure 24) to publish the form in the chosen Outlook Security Settings folder.


    Figure 24 : Publishing the form

  15. Provide the name Outlook Security Form to the form being published (see Figure 25), and click the Publish button to publish it.


    Figure 25 : Specifying a name for the form

  16. Close the form you opened from the .oft file.
  17. Open Microsoft Outlook, select the Outlook Security Settings public folder, right-click on it, and choose Properties from its shortcut menu. In the General tab of the Properties dialog box that opens (see Figure 26), ensure that Outlook Security Form option is chosen from the When posting to this folder, use list box. 


    Figure 26 : Choosing the Outlook Security Form option

  18. Then, click on the Permissions tab in Figure 26, and set the Reviewer role for the Default user (see Figure 27). Give the Editor role only to people who administer Outlook security settings.


    Figure 27 : Selecting the Reviewer role

  19. Finally, click the Apply button and then the OK button to save the changes.