METAmessage for Wireless
 
     
Home
About
Solutions
Products
Downloads
Support
Sales
Contact
Support - METAmessage
Problems with User Lists

Creating a User List Source from BES 4.0 Using METAmessage Version 4.2.0.25 SP

General User List Troubleshooting

 

Creating a User List Source from BES 4.0 Using METAmessage Version 4.2.0.25 SP

Note: If you have not yet upgraded to version 4.2.0.25 SP, please contact Onset support.

1) On the METAmessage server computer in Start/Programs/Administrative Tools/Local Security Policy/Local Policies/User Rights Assignment/Log on as a batch job and /Act as part of the Operating System, add the Interactive user (logged-on user) and the METAmessage domain user account.

2) If the BES is in a different domain than the METAmessage server, add the METAmessage domain user account to the Local Administrators group on the BES computer.

3) If the BES database is MSDE, run Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNETCN.exe and add the TCP/IP and NamedPipes protocols to the database.

4) If using NT Authentication with the BES database: In the METAmessage User List Source BES 4.0 Import dialog, the domain name must precede the user name (for example, onsetinc\metamessage).

5) Create a new user list source.

6) Test the user list source and delete old user list sources as needed.

In METAmessage user lists, note that the First Name field now displays both the first and last name. This maintains consistency with BES methodology.

General User List Troubleshooting

To receive a METAmessage service, all users must be configured in a user list for that service. If a user complains that they are not receiving service, check the following:

  • Has the user been added to the user list for the particular service?
  • If you manually added the user to a list, did you enter their correct e-mail address? The exact e-mail address used with every request can be found by opening the log file on the Control tab.
  • If a user list is unexpectedly empty, does the user list source still exist in the same location?

If you are migrating to Exchange 2000, in Active Directory you'll now have Read/Print/Lookup users with corresponding mailboxes. In Active Directory, grant Full Mailbox Access to the MCS domain user account for each user/mailbox by doing the following:

  1. In the Active Directory View menu, enable Advanced Features.
  2. Open the Properties dialog for a user.
  3. On the Exchange Advanced tab, click Mailbox Rights/ Add/Full Mailbox Access and add the MCS service user to the list.
  4. Click OK and repeat for each user/mailbox.

If you have trouble importing a user list from a Blackberry Enterprise Server (BES) for Microsoft Exchange source, check the following:

  • The MCS domain user account must have access to the BlackBerry Administrator mailbox.
  • The BlackBerry Administrator mailbox must not be hidden from the Global Address List.
  • The BlackBerry Administrator mailbox alias must be unique in the Global Address List. Check this by opening a new email message, entering the BES alias (typically "besadmin") in the To: field, and doing a Check Name. If the Check Names dialog pops up asking to specify from a list of matches, the alias is not unique and the user list import will not work.

Back