Cannot start Microsoft Office Outlook. MAPI32.DLL is corrupt or the wrong version. This could have been caused by installing other messaging software.

Whaddya know what to do when you receive this error "Cannot start Microsoft Office Outlook. MAPI32.DLL is corrupt or the wrong version. This could have been caused by installing other messaging software. Please install Outlook." after uninstalling Office 2007 and install Office 2003?

Just a review, the correct Mapi32.dll file should be in c:\windows\system32\Mapi32.dll directory.

If you search your computer and you see another Mapi32.dll file, simply rename it and reinstall your MS Office 2003 and it should correct this issue.

Alternative solution:

• Go to C:\Program Files\Common Files\System\MSMAPI\1033 directory, rename the Mapi32.dll to Mapi32.old.dll file.
• Open command prompt
• Go to C:\windows\system32 directory.
• Run fixmapi.exe

When you open Outlook for the first time, it will try to reinstall the missing file(s) and correct any issues from previous install. This should fix your Outlook issue.

Please share your thought.

Whaddya know? Exchange ActiveSync On Your iPhone 2.0

To start you can read this PDF file basic overview of e-mail flow provided by Apple on how to prepare your Exchange to support iPhone 2.0.

For Exchange 2003 documentation:
http://technet.microsoft.com/en-us/library/bb123755(EXCHG.65).aspx

For Exchange 2007 documentation:
technet.microsoft.com/en-us/library/bb124234(EXCHG.80).aspx

iPhone in the Enterprise:
http://support.apple.com/manuals/en_US/Enterprise_Deployment_Guide.pdf

Share your knowledge.

Whaddya know? Configuring Exchange Server using IMAP SSL

The iPhone has arrived and the corporate world is now starting to configure their existing messaging infrastructure allowing employees to sync up their iPhone’s.I want to stress that IMAP4 should not be enabled without using SSL! Sending information in clear text is not recommended. I will be referencing the IMAP4 port 993 later in this article. I will step through the different actions taken for a non-clustered Exchange 2003 system. Enabling IMAP:

I don't know what I'm doing wrong not able to work my iPhone to our Exchange Server 2003. I've used the server for Pocket PDA and it working ok. I was able to successfully authenticate when I configured my iPhone for Exchange Server 2003 but no message and can't send e-mail. Though I test the same approach for Exchange Server 2007, it work just fine.

I guess there is something wrong with my Exchange Server 2003 so I have to wait to upgrade this to Exchange Server 2007. For the mean time, I need to use my iPhone to read and send email using my Exchange Server 2003 account. So I configured my iPhone using secured IMAP protocol, fast and secured as well.

This is the most comprehensive documents I've found in the Internet. Configuring Exchange Server using IMAP SSL http://www.azaleos.com/blog/index.php?q=node/43

Share your experience configuring iPhone with us.

Sincerely,
KING.NET

Warning message when you start Outlook 2007 and then connect to a mailbox that is hosted on an Exchange 2007: Security certificate is invalid.

I've search the Internet to find the solution with my user running Outlook 2007 connecting to Exchange Server 2007 and no success, untill this article. Here's the summary of my tasks.

SYMPTOMS
When you start Microsoft Office Outlook 2007 and then connect to a mailbox that is hosted on a mailbox server that is running Microsoft Exchange Server 2007, you receive the following security warning message:

The name of the security certificate is invalid or does not match the name of the site.

CAUSE
You replace the default self-signed Exchange 2007 certificate with a different certificate.

By default, the URL that is stored in these objects references the NetBIOS name of the server. For example, a URL that resembles the following URL is stored:

https://NetBIOS_name.contoso.com/autodiscover/autodiscover.xml

This may differ from the host name that is used in the FQDN of the replacement certificate. For example, the replacement certificate may have an FQDN that resembles the following FQDN:

mail.contoso.com

This issue causes a name mismatch error to occur. Therefore, you receive the security warning message when you try to connect Outlook 2007 to the mailbox.

RESOLUTION
To resolve this issue, modify the URLs for the appropriate Exchange 2007 components. To do this, follow these steps:
1. Start the Exchange Management Shell.
2. Modify the Autodiscover URL in the Service Connection Point. The Service Connection Point is stored in the Active Directory directory service. To modify this URL, type the following command, and then press ENTER:

Set-ClientAccessServer -Identity CAS_Server_Name -AutodiscoverServiceInternalUri https://mail.contoso.com/autodiscover/autodiscover.xml

3. Modify the InternalUrl attribute of the EWS. To do this, type the following command, and then press ENTER:

Set-WebServicesVirtualDirectory -Identity "CAS_Server_Name\EWS (Default Web Site)" -InternalUrl https://mail.contoso.com/ews/exchange.asmx

4. Modify the InternalUrl attribute for Web-based Offline Address Book distribution. To do this, type the following command, and then press ENTER:

Set-OABVirtualDirectory -Identity "CAS_Server_name\oab (Default Web Site)" -InternalUrl https://mail.contoso.com/oab

5. Modify the InternalUrl attribute of the UM Web service. To do this, type the following command, and then press ENTER:

Set-UMVirtualDirectory -Identity "CAS_Server_Name\unifiedmessaging (Default Web Site)" -InternalUrl https://mail.contoso.com/unifiedmessaging/service.asmx

6. Open IIS Manager.
7. Expand the local computer, and then expand Application Pools.
8. Right-click MSExchangeAutodiscoverAppPool, and then click Recycle.

Source: http://support.microsoft.com/kb/940726

HOWTO: Transfer outlook cache "to" field to new computer?

How to transfer outlook cache to a new computer?

I always forget this information so I blog it here and share to the world.

You just need to copy one file e.g. outlook.nk2 to your new computer and you will have your outlook cache file again.

Where to find the outlook.nk2 file?
The default location should be in your profile Outlook folder, here's the example path.
c:\Documents and Settings\loginname\Application Data\Microsoft\Outlook

where; the loginname is your user information when you login to your workstation.

How to transfer outlook.nk2 file to your new workstation?
You can use the following information on how to transfer file(s).

• The easiest approach, use USB drive to copy and tranfer file from one computer to another.
• Send the outlook.nk2 file as attachment using your email. Read this email to your new workstation and save the file to the outlook folder.
• Shared folder to copy file
• Call your local computer geek to help you.
• Send me e-mail. I normally reply within 2-8 hours.

And to delete the e-mail address in your outlook cache, follow this procedure:

1. Start by creating a "new mail message"
2. Type the e-mail address, use the Down arrow key to select, then use Delete key to remove the e-mail address.
3. Repeat the process to remove other e-mail address that you want out of your cache.

That's for now, post your comments.

Cheers.

How to Export and Import mailboxes to PST files in Exchange 2007 SP1

I'm searching a tool replacement of exmerge for Exchange Server 2007 SP1 and I stumbled to this article. I thought it would be useful to spread out this article. Post back if you have any question. Enjoy.

There might be times when an Exchange Administrator will need to export the contents of individual mailboxes to offline files in order to present specific users with a format that is easily portable and ready to consume using Outlook clients. To fulfill this need Exchange 2007 SP1 will have a new set of features to export and import mailboxes to and from PST files. As I know you will ask - yes, those PST files can be bigger than 2 GB, which was a limitation of Exmerge tool used for this purpose in previous versions of Exchange.

Export/Import to PST Requirements
In order to export or import mailboxes to PST files the following requirements must be met:

• Export/Import to PST must be run from a 32 bit client machine with Exchange Management Tools installed (Version Exchange 2007 SP1 or later). The 32bit requirement comes from a dependency with the Outlook client.


• Either Outlook 2003 or Outlook 2007 must be installed on the client machine.
  The user running the task must be an Exchange Organization Admin or an Exchange Server Admin on the server where the mailbox to export/import lives.

Exporting mailboxes to PST files

The most basic cmdlet to export a mailbox to a PST file is as follows:
Export-Mailbox –Identity -PSTFolderPath

PSTFolderPath must be a full path pointing either to a directory or to a (.pst) file. If a directory is specified a PST file named after the mailbox alias will be used as the target of the export. Note that if the PST file already exists the contents of the mailbox will be merged into it.

Source : MSExchangeTeam

Exchange System Attendant

Managing Exchange Server 2007 is easy but sometimes you still encounter new problem. I've got one today so I'm sharing this to everyone.

Creating a new mailbox in Exchange 2007. I got this error: "An Exchange 2007 server on which an address list service is active cannot be found"

Resolution:
Go to Control Panel, Services.
Check your Exchange Server System Attendant service.
Check the status, this should be Started. If not, just double click then start the service.

This should fix this issue.

MXToolBox.com nice tool to have.

I have one customers that stop sending email (delivery) to their intended recipients, but not all. For example, they can successfully send email to @gmail.com, @msn.com, and other company email addresses, but not to dsa.mil, cisa.mil and other companies that use public spam databases e.g. abuse.net, http://www.spamhaus.org/, messagelabs.com (e-mail service), etc.

My first impression is their email server public IP address is listed in one of these public spam database. So I head out to visit http://www.mxtoolbox.com/ website and use their Blacklists tool. This is a army swiss box tool for any IT Consultant out there, all you have to do is check your client e-mail server public IP address and wait for the result.

If you're in their website, try the Email Header Analyzer tool as well. You will be surprise how easy to troubleshoot an email flow.

I thought this is a useful tool for everyone in information technology.