Problem exporting multi-line contact street addresses in Outlook

Monday, November 17, 2008

When you export Microsoft Outlook Contacts in either a comma or tab separated values format, any street addresses that contain more than one line are exported with carriage returns separating the multiple lines. This may result in a skewed output file containing multiple records for those contacts containing multi-line street addresses. In a comma or tab delimited file, carriage returns are interpreted as record delimiters. For troubleshoot this problems get Outlook support and follow the below given steps:

You can trouubleshoot using two method

Use CSV Format
Export the file in comma separated values (CSV) format; then open the file in Microsoft Excel. The file will import correctly with one record per contact and the multi-line street address in one cell. You may need to change the row height in order to see the second line of the address.

Manipulate the file in Microsoft Word
Export the file in either a comma separated values or tab separated values format, and then open the output file in Word. Then, manipulate the data as follows:
1. On the Edit menu, click Replace. If the Special button does not appear, click More to expand the dialog box.
2. In the Find What box, type a double quotation mark ("). Then click Special and click Paragraph Mark.
3. In the Replace With box, type any special character not found in your data, such as a pound sign (#).
4. Click Replace All.
5. In the Find What box, click Special and click Paragraph Mark.
6. In the Replace With box, type whatever character you would like to use to separate the multiple street address lines, such as a percent sign (%).
7. Click Replace All.
8. In the Find What box, type the special character used in step 3.
9. In the Replace With box, click Special and click Paragraph Mark.
10. Click Replace All.
After completing this procedure, your file will have one record for each contact. The multi-line street address will be in one field, surrounded by quotation marks. Each street address line will be separated with the character chosen in step 6.

Rule For Forwarding To Internet Address Does Not Work

Monday, November 10, 2008

The Inbox Assistant or Rules Wizard rule for forwarding messages to Internet addresses does not work after upgrading to Microsoft Exchange Server 5.5. The Exchange Server 5.5 "Automatic Replies to the Internet" option may be disabled by default in the Internet Mail Service.
Tips for Solution:

Enable the "Automatic Replies to the Internet" option by performing the following steps:

1. Open the Internet Mail Service object in the Exchange Administrator program.
2. Go to Internet Mail tab.
3. Click the Advanced options button.
4. Clear the checkbox for "Disable Automatic Replies to the Internet."
5. Stop and restart the Internet Mail Service in Control Panel Services.

his Steps Succsess to troubleshoot this problems, so i think it provides best outlook Support for troubleshooting Outlook Problems.

How to Verify That the Client Can Contact Backend Ports

Wednesday, November 5, 2008

By default, the RPC Proxy server does not publish the EPM port location. Therefore, you cannot ping the EPM from outside your intranet or use the UUID of the service.

However, you can specify the backend port that you want to test. By default, the store is on port 6001 and DsProxy is on port 6004. If these locations have been changed, the ports can be verified by using the RpcDump utility. The RpcDump utility is available from the Microsoft Windows Server 2003 Resource Kit package. Additionally, Microsoft does not recommend publishing the global catalog Directory Service or the Exchange referral service.

The following RPC Ping Utility examples are typed in at the command prompt. To access the command prompt, click Start, point to All Programs, point to Accessories, and then click Command Prompt.
How to Use Basic Authentication and SSL to Connect to the Store’s Port
Syntax:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 1 –F 3 –a connect –u 10 –v 3 –e 6001
How to Use Basic Authentication, SSL, and Mutual Authentication to Connect to the Store’s Port
Syntax:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 1 –F 3 –a connect –u 10 –v 3 –e 6001 –B msstd:server_certificate_subject
How to use NTLM Authentication and Non-SSL to Connect to DsProxy Service
Syntax :
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 2 –F 2 –a connect –u 10 –v 3 –e 6004

Duplicate junk e-mail messages appear in the Junk E-mail folder in Outlook 2003

Monday, November 3, 2008

This problem occurs because Outlook 2003 has the junk e-mail protection level set to Safe Lists Only.

When you create a junk e-mail rule in Outlook 2003 with the junk e-mail protection level set to Safe Lists Only, the restriction structure (SRestriction) causes an Exchange Server that is running without junk e-mail filtering to decide if an e-mail message is junk e-mail or if it is not junk e-mail. Outlook 2003 then processes all the junk e-mail messages on the client side. If there is more than one instance of Outlook 2003 running, multiple copies of the same junk e-mail message can be moved from the Inbox to the Junk Mail folder while duplicates of the junk e-mail messages are created in the Junk E-mail folder.


You receive duplicate e-mail messages in your Junk E-mail folder in Microsoft Office Outlook 2003 when all the following conditions are true:
• You have more than one instance of Outlook 2003 running on different computers, and all the instances are configured with the same Microsoft Exchange Server e-mail account.
• The junk e-mail protection level for your e-mail account is set to Safe Lists Only in Outlook 2003.
• Your Exchange Server does not filter incoming e-mail messages.
• All instances of Outlook 2003 use an Exchange Server e-mail account in Cached Exchange Mode.
• The sender of the e-mail message is not in your Safe Senders list in Outlook 2003.
• The sender of the e-mail message is not in your Contacts in Outlook 2003.
• The sender of the e-mail message is not in your Blocked Senders list in Outlook 2003.
• None of the recipients of the e-mail message are in your Trusted Recipients list in Outlook 2003.


RESOLUTION

This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest Microsoft Office 2003 service pack, you do not have to install the hotfix.