Message body is blank for the Emails moved by rules to the PST

When Outlook 2007 rules have moved HTML/RTF Emails to the personal folder, the message body strips off. In Unicode mode PST these rules do not work at all and gives error "Cannot move to the "name of the PST" personal folder"

-Create new Outlook Profile

-Check Outlook is in unicode mode now with the below steps:
Clicked on Tools ---Account Settings---Change--More Settings---Advanced tab---Mailbox Mode should be unicode
-Create new Personal Folders for unicode and then set up the rules.

Issue occured because Outlook 2007 was running in non-unicode mode and user had ANSI PSTs. In ANSI PST if HTML/RTF Emails are moved by the rules then the message body strips off. Another issue can be with the unicode mode PST running with non-unicode mode mailbox.

Instant Search is not working for Outlook

Instant Search does not retrun any results for special characters and incomplete strings. If we try to find 5-8N-13W or A&(((((& or anything with special characters, Outlook 2007 will not return any results. Also, if we try to search for incomplete string like 781 from 78483781, it will not return any results.



Outlook is considering the syntax as operators that is why it is not giving any search results. Also, it will return results only for whole string, incomplete string search will not work. It works for Outlook cache mode because cache mode Outlook uses local indexing.



Resolution: Use Outlook cache mode or use Advanced Find

Subject changes to the organizer's name for resource mailbox

Check the calendar setting with
get -mailboxCalendarsettings


mailbox name> if -deleteSubject is $True and set it to $false

Also set -AddOrganizerToSubject to $false


Command:

set-mailboxCalendarsettings -deleteSubject $false

-AddOrganizerToSubject to $false

Outlook Rules Issues and mfcmapi tool

Common Issues with Rules:

1. Rules are lost from Outlook
Resolution: Follow the mfcmapi steps to check if rules show up via mfcmapi

2. Meeting notifications are not getting updated on user’s calendar. Notification rule is set to deliver notification to a particular folder.Delete Outlook Rules table via mfcmapi

Resolution: Export all the rules, Upgrade the old rules, Reopened outlook and calendar items should start getting updated.

3. Rules causing duplication of Emails

No Resolution. Reasons can be varied.
Duplicate messages when using Organize combined with forward rule "on this machine only”

Workarounds:

Deselect all organize rules

or

remove the setting "on this machine only"

or

add to the rule

"stop processing more rule" to the rule

4. Can not create more rules because rules file size has increased
Resolution: Rules file size is 32-KB in Exchange 2003 and 64-KB in Exchange 2007. Delete old ones to create new rules.


Create a new Online Profile and select this profile when using MFCMAPI. O yes not to forget that you need to download mfcmapi tool from http://mfcmapi.codeplex.com/

 On the Session menu, click Logon and Display Store Table.


If you are prompted to select a profile, click the profile name in the Profile Name list, and then click OK.

Double-click the mailbox that contains the inbox rules that you want to delete.

Expand Root Container, and then expand Top of information Store.

Right-click Inbox, and then click Open Associated Contents Table

In the Microsoft Exchange server MAPI Editor window, locate and check for the items that have the IPM.Rule.Message

Note: Outlook should be in Online mode to use MFCMAPI. If you see IPM Subtree instead of Top of information Store, Outlook Cache mode is enabled. Disable Outlook Cache mode before you use MFCMapi.

Ref Article: http://support.microsoft.com/kb/924297

Outlook Troubleshooting:
http://outlook2007troubleshooting.blogspot.com/

Not able to open attachments in Outlook

1. Open REGEDIT.EXE and go to Edit -> Find... In the Find dialog box type "OutlookSecureTempFolder" without the quotes and locate that registry key.
2. That key will contain the actual folder location, and will look like:
C:\Documents and Settings\%USER_NAME%\Local Settings\Temporary Internet Files\OLK#\ (where # is a random letter or number)
3. Copy the location of that folder.
4. Click on Start -> Run... and paste the folder location from step #2 then click OK.
5. Windows Explorer will open that folder. Please, delete all files present.
6. Restart Microsoft Outlook and check if you are able to open the attachments

Delete freebusy via mfcmapi

Create a new Online Profile and select this profile when using MFCMAPI. O yes not to forget that you need to download mfcmapi tool from http://mfcmapi.codeplex.com/

1). Launch MFCMAPI.EXE, click "Session", click "Logon and Display Store Table" and
connect to the Outlook profile for the user.
2). Double click the "Mailbox - username".
3). Click "Root Container" to show the properties in the right-side pane.
4). Right click "PR_FREEBUSY_ENTRYIDS" and click "Delete Property" and click OK for
the dialog that pops up.
5). Expand "Root Container" and expand "Top of Information Store".
6). Click "Inbox" to show the properties in the right-side pane.
7). Right click "PR_FREEBUSY_ENTRYIDS" and click "Delete Property" and click OK for
the dialog that pops up.
8). Close all MFCMAPI windows and close Outlook.
9). Start Outlook from the Run line using the command: "Outlook /cleanfreebusy".

Also
1). Launch MFCMAPI.EXE, click "Session", click "Logon and Display Store Table" and
connect to the online profile.
2). Double click the "Mailbox - username".
3). Expand "Root Container".
4). Double click "Freebusy Data" folder.
5). Select the line which Subject is "LocalFreeBusy" and delete it.

Important: In the Deletion style select "Delete to deleted items" and click OK.

6). Close all MFCMAPI windows and close Outlook.
7). Start Outlook from the Run line using the command: "Outlook /cleanfreebusy".

Outlook freebusy information

How Outlook 2007 fetches Freebusy in Exchange 2007 environment:

Outlook 2007 runs against Availability Service Web Service and relies on the Autodiscover Service to find the Availability URL to view the Freebusy information on Exchange 2007. So in regards we can check the requests going to the CAS server. Outlook 2007 issues may be related to Autodiscover/Availability/CAS(IIS virual directories…speaking on larger scale. )
Information visible on OWA , not visible on Outlook 2007: Issue is more likely with Autodiscover.

Outlook versions earlier than Outlook 2007 uses LegacyExchangeDN attribute to view the freebusy information.
LegacyExchangeDN attribute is also used by Outlook clients’ in Exchange 2007 to delegate access to folders.
Outlook 2007 =>CAS local=>CAS Remote AG=>Ex2007
Outlook 2007=>CAS local=>Public Folder server by http://server/public/?Cmd=freebusy>

+CAS gets requests to get free/busy from remote AG user, CAS will choose home PF server as attendee’s home server. If there is no PF replica CAS will choose another PF randomly.
+If CAS can not return the information , it adds the server to badserver list and will connect to the good server for further information.

Data stored in LocalFreebusy folder:
Free/busy publishing settings
Delegate configuration
Direct booking options

Errors when Local Freebusy is Corrupt:
Unable to save free/busy information
Unable to clean your local free/busy information.
The Delegates settings were not saved correctly. Unable to activate free/busy information.
The Delegates settings were not saved correctly. Unable to activate send-on-behalf-of list. You do not have sufficient permission to perform this operation on this object.
Can't open this item. Unable to open the free/busy information (EventID: 25)
Ref KB:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;958443

What is PR_FREEBUSY_ENTRYIDS?
The PR_FREEBUSY_ENTRYIDS is a pointer to the LocalFreeBusy message stored in the Freebusy Data folder of the mailbox. During the mailbox move the pointer becomes unreadable by Outlook.

For deletion of this entry via mfcmapi tool refer to the below post:
http://outlook2007troubleshooting.blogspot.com/2011/06/delete-freebusy-via-mfcmapi.html

+Check if these users have been migrated from a different admin group or server. If so then check their LegacyExchangeDN value using ADSIEdit and surfing through the user attributes.The LegacyExchageDN value should be correct. The LegacyExchangeDN value contains the same name of the Administrative Group.