A few months ago I wrote this article about troubleshooting Outlook when it throws an Error 10. Having run into it again, and realizing that my previous article didn’t go into the details when there really is a mismatch between the name(s) on the certificate and how your client is configured, I thought this would be a great topic to cover in this week’s post.

In this situation, you configure Outlook to connect using RPC over HTTPS and at launch, you get an error that states:

There is a problem with the proxy server’s security certificate. The name on the security certificate is invalid or does not match the name of the target site.

Outlook is unable to connect to the proxy server. (Error Code 10)

If you launch your browser and go to visit your OWA site, you may also get a certificate warning that the name does not match. If you used the steps cover in this post on the Exchange Certificate Wizard, you may still run into this error if two conditions exist:

1. Your CA (especially if you are running your own internally) does not support Subject Alternate Names
2. The first SAN in your certificate does not match the CN of your certificate.

If you are running your own CA, make sure that it supports the SAN attribute for certificates. It can process requests that include SANs, and issue certificates, but without the SAN attributes. To check and to fix this, open an administrative command prompt on your CA and run this command.

certutil -getreg policy\EditFlags

Look at the output and confirm that it lists EDITF_ATTRIBUTESUBJECTALTNAME2. If it does not, run this command, and then restart Certificate Services.

certutil -setreg policy\EditFlags
+EDITF_ATTRIBUTESUBJECTALTNAME2

Now you can request a certificate with the complete list of SANs you require. When you create your request, you want to have the CN match the FQDN that you will use when configuring clients. You want that same FQDN to appear first in the list of all SANs that you may configure on this certificate. Using an FQDN in the CN and listing it first in the SAN list not only eliminates the error 10 issue on Outlook clients, but it also makes sure that you can use this certificate for POP and IMAP over SSL, both of which require a FQDN (not a hostname.)

If you want to create your CSR by hand instead of running the Exchange Certificate Wizard:

1. create a csr.inf file with the following contents.

[NewRequest]
Subject="CN=host.example.com,OU=something,O=somethingelse,
L=YourCity,S=YourStateorProvince,C=yourCountry2lettercode"
Exportable=TRUE
KeyLength=2048
MachineKeySet=TRUE
FriendlyName="Exchange cert"
KeySpec=1

[EnhancedKeyUsageExtension]
OID=1.3.6.1.5.5.7.3.1

[RequestAttributes]
CertificateTemplate=WebServer
SAN="dns=host.example.com&dns=host&dns=alternate
FQDN&dns=alternate2FQDN"

Make sure you replace all the obvious values above, and also make sure if you copy/paste, all your double quotes are straight double quotes and not smart quotes.

2. Now run the command

certreq -new csr.inf cert.req [enter]

3. Use the cert.req file to submit the request to your CA and issue the certificate. Save it as cert.cer.

4. Copy the issued certificate back to your Exchange server.

5. Run the command

certreq –accept cert.cer [enter]

6. Launch the Exhange Management Console, browse down to Server Configuration, and you will see the certificates on your server.

7. Right-click the new certificate and assign the services you want to use to it.

8. I usually reboot the server at this point, but you can just restart the Exchange Transport Service and run an iisreset if you prefer.

Now test your Outlook client again and all should be well. If you still get the error, first, make certain that Outlook closes before relaunching. Then go ahead and reboot the Exchange server to be sure. There’s a reason I usually reboot the server after all.

Error Code 10 Redux

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

Usually Exchange’s error messages are, while concise, informative and tend to point you in the right direction towards resolution, but sometimes an error occurs and the error message generated has little to nothing to do with the actual problem. One such case is with the proxy error 10.

This post will talk about what proxy error 10 usually means and how to fix that, but it will also go over another situation that occurs frequently, causes Outlook to throw the same error, but has little to do with the message.

Let’s talk first about this error message and what it indicates to the user. The text of the error can read as one of the following messages, where %s is a hex string;

Error message 1

There is a problem with the proxy server’s security certificate, %s. Outlook is unable to connect to this server. (%s)

Error message 2

There is a problem with the proxy server’s security certificate, %s. The name on the security certificate is invalid or does not match the name of the site. Outlook is unable to connect to this server. (%s)

Error message 3

There is a problem with the proxy server’s security certificate, %s. The security certificate is not from a trusted certifying authority. Outlook is unable to connect to this server. (%s)”

Error message 4

There is a problem with the proxy server’s security certificate. The name on the security certificate is invalid or does not match the name of the target site %FQDN.

These error messages are usually caused by an issue with the certificate, including a name mismatch, an invalid or revoked certificate, or a certificate issued by an untrusted CA. It can also be caused by a mismatch between the FQDN in the account settings on the client, and what is on the certificate. For errors 1 and 2, the %s is a bitmask representing what is wrong with the certificate.

FLAG_CERT_REV_FAILED 0×00000001

FLAG_INVALID_CERT 0×00000002

FLAG_CERT_REVOKED 0×00000004

FLAG_INVALID_CA 0×00000008

FLAG_CERT_CN_INVALID 0×00000010

FLAG_CERT_DATE_INVALID 0×00000020

FLAG_CERT_WRONG_USAGE 0×00000040

FLAG_SECURITY_CHANNEL_ERROR 0×80000000

One way to examine the certificate from the client’s side is to view the certificate being presented by browsing to https://servername/rpc and then using the browser to check the certificate. You should be able to tell whether there is a name mismatch (don’t forget that the FQDN might be listed in the Subject Alternate Name (SAN) property,) and whether or not you trust the chain up to the root CA.

Error 4 is a unique one, where the wording in the message might send you on a wild goose chase. Before spending too much time tearing out your hair trying to figure out what is wrong with a perfectly valid certificate, check your Client Access Server to make sure that the Microsoft Exchange Address Book (MSExchangeAB) service is running. If that service has stopped (or is unreachable) then your Outlook 2010 clients will throw the fourth example of Proxy Error 10. Determine and resolve why the service failed or is unreachable, start the service, and have your clients re-launch Outlook.

How to Fix Error Code 10

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

Occasionally when a user sends email they may receive a Non Delivery Report (NDR) with error code 5.1.1 from the destination email server such as Microsoft Exchange 2000 and 2003 Server. This is an error message that is indicating that the recipient does not exist on the destination email server. And to add more confusion to the situation it is possible that the intended recipient of the first unsuccessful email is able to send email to the original sender and that original sender can successfully reply back to what was the original recipient.

If there are problems with delivering email to a recipient then a Non Delivery Report will be sent back to the sender. The NDR message is a subclass of a larger group of delivery status notifications. The delivery status notifications define three types of status:

1. Success (2.X.X numeric codes)
2. Persistent transient failure (4.X.X numeric codes)
3. Permanent failures (5.X.X numeric codes)

Most NDRs are sent because of failures so those error codes will be of the form 4.X.X or 5.X.X. This implies that the server is able to identify the reason for the failure and so is able to assign an error code which identifies the failure. The NDR which is sent back to the sender of the original email will contain the assigned error code.

Here is an example of what an Outlook client might see when they receive the 5.1.1 error message:

Your message did not reach some or all of the intended recipients.

Subject: Original Message
Sent: 3/24/2002 11:40 AM

The following recipient(s) could not be reached:
user@domain.com on 3/24/2002 11:40 AM
The e-mail account does not exist at the organization this message was sent to.
Check the e-mail address, or contact the recipient directly to find out the
correct address.
<server.domain.com #5.1.1>

In this example, the server that is reporting the 5.1.1 error code is listed as “server.domain.com”. It is important to note that sometimes the server that is reporting the problem is not the same as the server that is experiencing the problem.

Another example of the error code is a basic message such as: “511 – recipient address has invalid format”.

Here is a list of reasons why the 5.1.1 error may be produced:

1. There is no email account on the destination email server’s site for the recipient’s email address. This may happen if the email account was moved from one administrative group to another administrative group. If the recipient email user then replies to an old email during the transition then an old administrative group style LegDN will be used and the NDR will be sent back to the sender. The same result would also happen if the moved user did not recreate their Outlook profile.
2. Note that if an administrator tries to take a short cut by simply renaming an account in active directory then it will most likely result in NDR messages being created. A workaround would be to put the old legDN in as an x.500 address. This will prevent NDRs from being generated when email is replied to or sent to the old legdn. Note that it is not a Microsoft recommended practice to change the legdn’s.
3. The email message was sent to obsolete personal address book entries. The email account may once have existed there but has since been removed. The account may no longer exist if the end user has left the company and their account has been deactivated or deleted. It is also possible that the email address used is incorrect.
4. The categorizer rejected delivery because you configured your SMTP contact with characters that do not meet the requirements of RFC0821.

To correct this problem an administrator should verify that the recipient’s email address is formatted correctly and then resend the message. Confirm that the receiver’s email server is able to resolve the recipient’s email address.

If the email was sent to a user internal to the organization within the same domain, then it usually means that the recipient’s email address, as shown in either of the “To”, “Cc”, or “Bcc” fields, does not exist in your organization’s email system. If the email was sent to a user email address external to your company then the recipient’s email address should be verified by contacting administrators responsible for the destination email server site.

Troubleshooting Exchange Error 5.1.1

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

Occasionally sending and receiving emails can pose problems for end users. One of the more serious problems is when users are unable to receive their email messages.

A sample error message related to being unable to receive emails is the following:

“Outlook is unable to connect to your outgoing (SMTP) email server”

This error message can occur if Outlook is trying to retrieve email messages from a Post Office Protocol (POP3) email server. It can also be produced if Outlook is trying to retrieve email messages from a Simple Mail Transfer Protocol (SMTP) email servers.

It is also possible that you may receive the error code 0×80042109 along with the above error message. This can happen if an end user is attempting to send a message via an email server and they are then asked to provide their login credentials. However, if the OK button is clicked again it will only result in another login prompt being displayed. And, instead of selecting the OK button, if the user hits the Cancel button then the following error message is displayed:

Task ‘<SMTP server name> – Sending and Receiving’ reported error (0×80042109): ‘Outlook is unable to connect to your outgoing (SMTP) email server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).’

A workaround for this problem is to create a new profile for the user account. The current email server is not responding to the existing user’s profile. A new profile will correct this problem.

It is also possible for the client to use either port 587 or port 465 (with Secure Socket Layer – SSL). Some email servers are configured to work with those ports instead of using the standard email port (25). Some service providers will require authentication on port 587.

Follow the steps below to change your port from 25 to 587 for the Outgoing server:

1. From the Tools menu go to “email accounts”.
2. Select View or Change existing email accounts.
3. Double-click on (your email server)
4. Select “More settings”
5. Go to the Advanced tab
6. Change the Outgoing server (SMTP port) from 25 to 587
7. Click OK or hit enter
8. Select Next
9. Finish or Done.

Additionally, an administrator may also have to change the outgoing server name within Outlook to a different server as determined by their service provider. The POP3 incoming email server does not need to be changed.

On the Outgoing Server tab an administrator should ensure that the checkbox is checked for “My Outgoing Server (SMTP) requires authentication.” Then enter the appropriate email address and password combination. After the username and password has been entered the administrator should then click on “Remember Password” and select “Log on using Secure Password Authentication (SPA)”.  At this point either press the OK button or hit the enter key. Some administrators have reported that they have used this workaround and have not had to change the Port numbers. Their incoming port was port 110 and their outgoing port, 587, was left unchanged.

Some users have reported that in addition to the 0×80042109 error they also received the following message:

”Your server does not support the connection encryption type you have specified. Try changing the encryption method.”

If this happens then an administrator can make the following changes:

1. Open the account settings for the user account.
2. Select the Advanced tab.
3. Verify that the “This server requires SSL” checkbox is checked.
4. Verify that the “Use the following encryption type” has Secure Socket Layer (SSL) selected.

As you can see there are a variety of problems and solutions related to the 0×80042109 error code. Sometimes the solution can be as simple as creating a new password. This can be needed if a password has become corrupted. What happens is that Outlook will continue to ask the end user for their password and the user will re-type their password two or three times before realizing that there is a problem either with what they thought was their password or with the password itself. Changing the password on the server and then within Outlook can sometimes be the simple solution to what appears to be an otherwise complex problem.

Troubleshooting Error Code 80042109

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

In my last couple posts I addressed the issue of running out of memory and how it affects Outlook and Outlook Express. As an email administrator you will often have various resource issues as you have probably already experienced. Besides finding out that your system is running out of memory the other issues you will probably run into from time to time is that of running out of disk space.

If you’ve received any of the following errors then you have already dealt with these issues. But if not then here are some low disk space scenarios and potential solutions.

One indication that you may have a low disk space problem that adversely affects Outlook Express execution is if you receive the following error:

OLEXP: Error Message If the Folders.dbx File Is Missing or Damaged

Other errors you may receive, after you start Outlook Express or try to send any email messages can include any of the following error messages:

MSIMN caused an invalid page fault in module Msoe.dll
MSIMN caused an invalid page fault in module “unknown”
MSIMN caused an invalid page fault in module Directdb.dll
Msimn caused an exception C0000006h in module Directdb.dll
Outlook Express: The message could not be sent. There is not enough Disk space.
Unknown error has occurred. Protocol: SMTP Port: 0 Secure: No [SSL] Error: 0x800c0131

If you get any of these error messages then it is most likely because your Folders.dbx file has become corrupted or cannot be found for some reason. It is also possible that the read-only attribute has been set for the Folders.dbx file.

At this point it is probably a good place to review how all data related to Outlook Express is stored on the hard drives. Your Outlook Express is your end users conduit to all of their email folders and messages. It contains information about the local IMAP folders and messages and any newsgroups that are subscribed to by your end users. All of this information gets stored in one folder called the store root folder. Some administrators refer to it as the store root. It is also know as the store folder. The bottom line is that this one folder holds everything and sits in the Store root directory located at:

C:\Windows\Application Data\Outlook Express\<Group Unique ID>
or
C:\Documents and Settings\<User>\Local Settings\Application Data\Identities\<Group Unique ID>\Microsoft\Outlook Express

If this were a UNIX system the GUID would refer to a Group User ID.

And of course, you, or a previous email administrator or other system administrator, may have relocated the file or directory to another location more aptly named for your environment. If you inherited this system and need to lookup the current location of your Store folder then you can select Tools, Options, Maintenance, and then Store folder to find its location.

The Folders.dbx file must exist in order for Outlook Express to run correctly. It contains your mail folder and all sub folders, newsgroups and options for synchronization of all subscribed newsgroups and other email folders.

When Outlook Express starts up, it scans for the existence of this file. If it cannot find it then Outlook Express will create a new Folders.dbx. If for whatever reason you wished to start over you could always backup your current Folders.dbx file, and any of your default email folders such as your <dot>dbx files known as Inbox.dbx, Drafts.dbx, Sent Items.dbx and Deleted Items.dbx, rename them, and then restart Outlook Express. That will give you a fresh start. You could always go back and restore those files using an email archiving tool.

You may need to do this if Outlook Express was having trouble starting up or if it begins to run slow. You can fix this by using the above steps. But remember that all of your nested trees, lists of newsgroups and any options such as synchronization will be lost. You may also need to re-edit your email message rules.

Once you restart Outlook Express and after having deleted Folders.dbx, then all of your default email folders previously mentioned that cannot also be found will be created automatically for you.

You can rename the Folders.dbx file by performing the following steps:

1. Click Start, select Find, and then click on Files or Folders.
2. In the Named box, type in folders.dbx.
3. In the Look In box, select your primary hard disk (usually the C drive), and then click Find Now.
4. Right-click the Folders.dbx file, and then click Rename.
5. Type folders.old or follow your own renaming scheme, and then click OK.
6. Start Outlook Express.

This process will create a new Folders.dbx file for you automatically when Outlook Express starts up.

Troubleshooting Error Code 800c0131

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

Sending and receiving emails over the network involves the transmission of data to and from common application services such as network services and mail services. At the lower levels in the technology stack, email is sent to services identified by their well known port numbers. Between email clients and email servers the port number used is port 25 for sending emails over TCP/IP networks.

On most email servers, a background process, or daemon, will listen to port 25 for any incoming email. This is the port that clients make socket connections in order to be able to send their emails. Sometimes the port is blocked or unavailable on the email server.

When retrieving email from the server there is another port that can also be blocked and thus prevent emails from being receive. If port 110 is blocked then the client cannot pull down their messages.

Sometimes administrators will block port 25 to stop the flow of spam and/or viruses from their servers. The problem is that you’re effectively throwing the baby out with the bathwater. To be able to send emails and also prevent spam or viruses you need to be able to write some kind of filtering code.

This can get sticky if you’ve outsourced your email servers. Your control is obviously limited in this scenario.

However if you have some control over the email server you can configure your settings such that the ports used for sending and receiving are different than the standard ports of 25 and 110. Spam will still be directed – thru email – to ports that essentially become bit buckets. You decrease your exposure to risk while still maintaining your normal business operations which include communication by email.

How will you know if your ports are blocked?

If you’re using Exchange server clients to send or receive messages you’ll know by the type of error messages you get when you try to send a message to your Simple Mail Transfer Protocol (SMTP) server. One of the error messages you might receive will look like the following:

“The connection to the server has failed. Account: ‘your_account’,
Server:’your_SMTP_server’, Protocol:SMTP, Port: 25, Secure(SSL): NO,
Socket error: 10061, Error Number: 0x800ccc0e”

Note that the specific port number 25 is listed in the error message.

And if you are trying to receive emails from your Post Office Protocol version 3 (POP3) email server, then the error message you might receive will look like this:

“The connection to the server has failed. Account: ‘your_account’,
Server:’your_POP3_server’, Protocol:POP3, Port: 110, Secure(SSL): NO,
Socket error: 10061, Error Number: 0x800ccc0e”

Here you see port 110 listed in the error message.

Both of these messages indicate that ports 25 and 110 are unavailable. While these can prevent email attacks from occurring and prevent viruses from spreading they as already mentioned negatively impact the sending and receiving of emails. Thus, as an administrator you need to know who to investigate the status of these ports and how to turn back on these ports (listeners).

The most common utility to use for investigation is the “netstat” command.

The “netstat” command is often used for displaying the contents of the routing table but can also be used to verify if those services are running on ports 25 and 110. Normally these ports are “up” and running whenever the services for the Exchange Server are started. Port 110 for the Post Office Protocol version 3 (POP3) is automatically started on the Exchange server as soon as the Information Store service is started. And when the Internet mail service is started then port 25 is also started. To verify that they are up and running you can perform the following steps.

• Go down to the Start button and click on it to bring up the menu.
• Pull right on All Programs and then again pull right on Accessories.
• Select Command Prompt to bring up a command prompt window.
• You might want to increase the screen buffer size to make viewing of the command output easier to read. You can do so by right clicking in the upper left corner of the command prompt window. Click Properties and the click on the Layout tab. Increase the screen buffer size to something like 600 or 700 – whatever is your preference. Save the change for the current window or modify the shortcut which started the window if you are comfortable with the change.

Now you’re ready to run the netstat  command. Type in “netstat –an”, hit enter and then watch all that output of services go scrolling by. Because of the change you made above you’ll be able to scroll backward and look for the lines that indicate that your listeners (ports) are up and running.

Proto  Local Address     Foreign Address        State
TCP    0.0.0.0:25             0.0.0.0:0              LISTENING
TCP    0.0.0.0:110           0.0.0.0:0              LISTENING
     
If you cannot find these entries then this means that those services are obviously not running and you will need to troubleshoot further.

Troubleshooting Error Code 0x800ccc0e

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

I’m sure your users have encountered many times not being able to start their email programs. It can be very frustrating especially when you, as an administrator, are not in full control of software that gets installed onto end users computers.

Sometimes, after starting Microsoft Office Outlook, they get an error message that tells them that their MAPI32.DLL file is corrupt. The error message will also indicate that the DLL file is possible the wrong version. How can this happen?

Usually this happens after other message software has been installed. The error message will go on to suggest that Outlook itself be removed. This is when having well-known company policies in place can prevent such unwanted installs from occurring. Also setting up user accounts with limited privileges can stop end users from installing additional, unapproved software – such as beta software – onto company computers.

Now that you have a problem lets talk about how to fix it.

Let’s assume that the Beta 2 version of Outlook has been installed. If the end user tried it for a while and then uninstalled it they would probably run into problems so they called you, the administrator. The technical cause of the problem is that the MSMAPI32.DLL file was not removed from the folder:
C:\Program Files\Common Files\System\Msmapi\LocaleID

The LocaleID refers to the language of the locality. If using English – such as in the United States – then LocaleID is equal to 1033. Lookup the following website for more information about LocaleID’s: http://msdn2.microsoft.com/en-us/library/0h88fahh.aspx

Anyway, assuming LocaleID is 1033, you should open up the folder
C:\Program Files\Common Files\System\Msmapi\1033 and then right click on the MSMAPI32.DLL file and select rename. Next, you can type in MSMAPI32.OLD or MSMAPI32.something and then press ENTER. This procedure will rename the file. After that just restart Outlook and the program will be repaired.

In a related problem there’s a situation which can occur that can cause an incorrect version of Outlook to start up. This can happen if your end user decides that they want to run another version of Office on a computer with an existing version of Office installed. The end user selects an option to keep the earlier version of Office. What they end up with is that Outlook 2007 gets installed even though they wanted to keep the current version of Office suite installed. They won’t realize they have a problem until they fire up Outlook. That’s when they realize that their previous version of Outlook is no longer available to them – in fact, it’s been removed. So they call you, the administrator, to go back and help them get their previous version of Outlook up and running.
The reason why this happened is because you can’t have two versions of Outlook on the same computer. To fix this problem you’ve got a couple different options. One is you can keep the earlier version of Outlook. But you’re going to have to check with the end user if they did not installed the original non-trial release version of 2007 Office suite. If they didn’t do this then when they startup Office suite you can click on the Customize option and then on the Upgrade tab select the “Keep all previous versions.” Next click the Installation Options tab and then click the Microsoft Office Outlook icon. Select Not Available and then click Continue.
 
On the Upgrade tab of the Setup program your end user should have gotten a message warning them that “Before you install Microsoft Office Outlook 2007, you must remove any earlier version of Outlook. Two versions of Outlook cannot coexist on the same computer. If you want to keep an earlier version of Outlook, you must explicitly choose on the Installation Options tab to not install Microsoft Office Outlook 2007” when they tried to upgrade their Office suite version.

This may have been misleading to the end user because they didn’t have to remove the earlier version of Outlook before they installed Outlook 2007. Outlook is removed automatically when Outlook 2007 is installed.

If the end user wanted to keep the earlier version of Outlook after they installed the non-trial release version of a 2007 Office suite then there are some additional steps to follow which I will cover in a subsequent article.

Your end user might also have installed and then uninstalled Outlook 2007 onto a system that already had Outlook 2003 installed. If they did that then they probably received an error message when they tried to start Outlook 2003 that said their MAPI32.DLL file was either corrupt or the wrong version. They (you) will be asked to reinstall Outlook.

You can find out more information about this error message and how to resolve this problem by going to the article, 926196, in the Microsoft Knowledge Base.

Additionally, to find more information about what happens when a trial version of a 2007 Office suite is installed when another version of Office already exists check out the article, 930559, in the Microsoft Knowledge Base.

Troubleshooting Error Code 926196

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

 It is possible to receive the error, 938816, when one of two conditions exist:

1. You are attempting to create a new MAPI form or you’ve tried to open some custom forms in Outlook 2003.
2. You notice changes in how your application runs after you’ve installed post-Office 2003 Service Pack 3 updates.

The unwanted behaviors that you will see in Microsoft Office Outlook 2003 can include any of the following effects:

• You are receiving messages asking you to contact the administrator after you’ve created a new MAPI form in Outlook 2003.
• Or you are getting a message that informs you that a form could not be displayed and that you should again contact your administrator. This can occur if you are for instance attempting to open a custom form.
• Or, after receiving a custom form as an email item you try to open it and get a message stating that the form cannot be opened or displayed. You are again asked to contact your administrator.

To fix these error conditions you should go to the Microsoft Support web site and search for the file:  EnableMAPIFormsInOutlook.msi. Select the file and then click Run in the File Download dialog box. The Fix it wizard will walk you through the steps to correct this error.

I’d also recommend that you save the fix file to your local hard drive or some other media such as a writeable CDROM so that you have a local copy. You can also save the file if you are not on the computer that is having the problem.

There is another way for you to fix the problem yourself without using the wizard. However, these steps involve touching the registry and any time you touch (modify) the registry you can inadvertently cause serious damage to your system. So I strongly advise that you backup your registry before performing this task. If you have any problems after modifying the registry then you will have a backup copy that your can restore to get your system back into a known working state. Please review article number 322756 in the Microsoft Knowledge Base for instructions on how to backup and restore the registry.

Now, if you still want to fix these issues manually then you need to enable MAPI forms. Here are step-by-step instructions on how you can enable MAPI forms by performing the following steps.

• First go down to the lower left corner of your screen and click the Start button.
• Then to your right on the pop-up screen click Run and then type “regedit” without the quotes.
• Next click OK or just hit the Enter button on your keyboard. This will bring up your Registry Editor.
• At this point you want to locate and then click the following registry subkey:
  HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Forms\
• Next, double-click the EnableMapiForms registry entry and type 1 in the Value data text box.
• Hit Enter or just click OK.

The registry path might not exist. That’s okay. What you can do is to create a new dWord-Value registry entry and name it EnableMapiForms. Give it the value of 1.

I mentioned earlier that you can also experience changes in how your application runs after you’ve installed post-Office 2003 Service Pack 3 updates. Some of these updates include installing an update to the Mso.dll file.

You will notice that you now have the ability to configure Office 2003 such that you can enable or to deny specific COM components. You can find more information about this change in article number 938815 in the Microsoft Knowledge Base.

Another change you might notice is that some COM components are not functioning as expected. This may be the case if they have unusual characteristics.

For instance you might experience reduced functionality of an add-in or an ActiveX control. Or the COM component is seemingly blocked. These limitations will be noticeable after you install Office 2003 Service Pack 3. You can find more information about these changes in article number 938814 in the Microsoft Knowledge Base.

You might have issues or problems when you run the Microsoft Office Document Imaging program after you install Office 2003 Service Pack 3. There were changes made to the behavior of Microsoft Office Document Imaging. You can find out more information about the changes by reviewing article number 938813 in the Microsoft Knowledge Base.

Other problems you might notice is that you have lost versioning capabilities on some documents such as Office files that are saved in certain formats. You can get more information about which files don’t have versioning by reviewing article number 938807 in the Microsoft Knowledge Base.

Troubleshooting Outlook Error 938816

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

There are several situations where you may encounter error code 0×80004005.

You can receive the error code 0×80004005 if you use Distributed Authoring and Versioning (DAV) to query for message properties on the information store in Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003. A 0×80004005 (ecCallFailed) error is returned if the urn:schemas:mailheader:to property is requested. Additionally, an error is returned if there are messages in the result set that have recipients where the value of PR_EMAIL_ADDRESS is an empty string (“”).

You may also receive the error when you use xp_sendmail extended stored procedure to send e-mail from SQL Mail with SQL Server 2000. The error message you receive will look like: xp_sendmail:failedwithmailerror 0×80004005.

Another circumstance when you receive error code 0×80004005 is when you query for a specific MAPI interface by using a pointer that you obtained from an Outlook object’s MAPIOBJECT property. The error message is short: 0×80004005 (E_FAIL).

When this happens it is because The MAPIOBJECT property is available only for compatibility with Microsoft Collaboration Data Objects (CDO) 1.21. It is a hidden property of Outlook Object Model objects, and is not meant to be used from the Outlook object. The MAPIOBJECT property is meant to be used from the corresponding CDO object. To use the MAPIOBJECT property, use CDO to obtain it from the corresponding CDO object.

Additionally, a SQL Server Database Maintenance Plan includes an option to send a maintenance report (that is, a file that contains results for the execution of the maintenance plan) by e-mail to a predefined operator on the server. E-mailing the maintenance report file to the operator may fail with the following error message, which can be found in the maintenance report for the Database Maintenance Plan:

Error 18025: [Microsoft][ODBC SQL Server Driver][SQL Server]xp_sendmail: failed with mail error 0×80004005. 

Note that this error does not affect the reporting of the job status. The job is still shown as successful.

The xp_sendmail extended stored procedure fails with the 0×80004005 error when attempting to send an open file as an e-mail attachment. Sqlmaint.exe executes the Maintenance Plan and writes output to the report file. The final step in the Maintenance Plan, which is to send an e-mail, is also recorded in the report. Because the report file is still open when xp_sendmail tries to send it as an attachment, the attempt fails.

You can resolve this problem by obtaining the latest service pack for SQL Server 2000.

Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.

To work around this problem, you can include the script below as an additional job step in the last job created by a particular Maintenance Plan. This script below sends the last report file for a specific Maintenance Plan to a specified e-mail address.

To use this workaround, follow these steps:

1. Identify the last job for the Maintenance Plan.
2. Right-click the job, click Properties, click Steps, select the step, and then click Edit.
3. On the Edit Job Step dialog box, click the Advanced tab.
4. Set On Success Action to Go To Next Step.
5. Click OK on the Edit Job Step dialog box.
6. Click New to add a new step, and then give the step a name. Type should be Transact-SQL Script (TSQL) and Database should be master.
7. Paste the following script in the command window:
   declare @planname varchar(100)
   declare @dir varchar(200)
   declare @operator varchar(50)
   declare @cmd varchar (200)
   declare @mailfilename varchar(200)
   declare @filenamelen int

Values set here can actually be provided as parameters to a stored procedure.

If provided as parameters to a stored procedure, rem the following select statements.
@plananme is the plan whose maintenance report is sent.
@dir is the log directory for SQL Server. It is the directory to which the maintenance report files are written.
@operator is the email address of the person to whom the report file should be mailed.

select @planname = ‘Database Maintenance Plan 1′
select @dir =’c:\Program Files\Microsoft SQL Server\MSSQL$SQL2K1\LOG’
select @operator =’email@domain.com’

You can automatically set the above by reading various values from SQL Server.

SET NOCOUNT ON
IF RIGHT (@dir, 1) <> ‘\’
begin
select @dir =@dir +’\’
end
SELECT @dir = ‘dir /s /b ‘+’”‘+@dir + @planname+’*.txt’+'”‘ +’ >c:\dir.txt’

create table #TMP_MAINT_FILENAMES (NAME1 varchar(8000))
exec xp_cmdshell @dir
BULK INSERT #TMP_MAINT_FILENAMES
   FROM ‘c:\dir.txt’
   WITH
      (
         ROWTERMINATOR = ‘\n’
      )

select @mailfilename=MAX(name1) from #TMP_MAINT_FILENAMES
print ‘The following file is being sent as an attachment’
print @mailfilename

Set the various parameters for xp_sendmail.
declare @tmpmessage varchar(300)
declare @tmpsubject varchar(300)
select @tmpmessage = ‘This is the last maintenance report on the server for the maintenance plan ‘+@planname
select @tmpsubject = ‘SQL Server Maintenance Report for ‘+@planname

Now send the last file for the maintenance plan.
exec master..xp_sendmail @recipients= @operator, @subject =@tmpsubject, @message=@tmpmessage,
@attachments= @mailfilename

Perform cleanup.
drop table #TMP_MAINT_FILENAMES
exec master..xp_cmdshell “del c:\dir.txt”
SET NOCOUNT OFF

8. Make sure that the @planname, @dir, and @operator values are set in the script.
9. Save the job step.

These programming examples are provided for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. Make sure that you are familiar with the programming language that is shown and with the tools that are used to create and to debug procedures.

Troubleshooting Error Code 0×80004005

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

Getting the error code 0×80040113 can sometimes take one down a road of various fixes that lead off in different directions, some of which can come as a surprise that they can fix your problem. Most of the time you have an idea of what might be causing your problem but you might only have limited bits of information to work with.

Such is the case with Error code 0×80040113. Surprisingly it can occur not only when using Outlook Mobile Manager but also when issuing a command to MSGraph that uses OLE automation. Sometimes the error occurs when using Personal Folders and you get a “Sending and Receiving reported error…” message.

Here are some related 0×80040113 error messages and some ways you can handle this error.

In the past, if you were using Microsoft Outlook Mobile Manager you may have received an error message such as “MAPI Error Occurred. (Error code 0×80040113)”. This issue could occur if your network connectivity was disconnected. Having your network connection get disconnected would prevent communication with the Exchange 2000 or Exchange Server computer. This might happen if the server became unavailable, or if you were having a cable, network adapter, or some other network problem.

The effect was that when you attempted to send a daily summary or a test message in Outlook Mobile Manager, the connection wizard might have taken an unexpectedly long time to attempt to send the message (as if the system had stopped responding), and then you would most likely have received the following error message: Mobile Manager could not save your changes. Please exit and restart.

If you clicked Help, and then clicked Troubleshooting; the following error message was logged: A MAPI error occurred. (Error Code: 0×80040113)

The description for that error lists error code 1217, which indicates:
The connection to the Exchange server has been lost. There is a network problem or the Exchange server is offline and that you should contact your network administrator.

At this point, you should have exited Outlook Mobile Manager, closed the system tray icon, and then restarted Outlook Mobile Manager. Next you would have tried to reconnect to your Microsoft Exchange 2000 Server or Microsoft Exchange Server computer.

If the problem continued then you could also have tried to resolve it by checking your network connectivity and ensuring that you could still connect to your Exchange 2000 or Exchange Server computer and other network shares. The most basic of network diagnostic tasks is to try a simple “ping” command to check for network connectivity between the client and the server.

Beyond the network diagnostics you could also try restarting Outlook Mobile Manager.

Be forewarned that Microsoft Outlook Mobile Manager has been discontinued and is no longer available for download. If you have already installed Outlook Mobile Manager, you can continue to check the Microsoft Knowledge Base for any documented issues. More information about Microsoft Mobile Information Server can be obtained from the following Microsoft Web site: http://www.microsoft.com/exchange/default.mspx.

I also noted earlier that issuing a command to MSGraph that uses OLE automation could cause the error message: OLE error code 0×80040113 Invalid class string.

As an example you might have tried:  Append General myGeneralFieldName Class “MSGraph

The reason you received an error code was because Microsoft Graph had not been installed or registered to the operating system.

Microsoft Access ships with many smart components including forms and reports, text and combo and list boxes, options groups and the ability to add Active X and OLE components. The most complicated of the standard objects is Microsoft Graph. As MS Graph is part of the standard install process with Access, you will generally find that the object is available on most computers that Access is installed on.

When trying to diagnose the cause of error 0×80040113 you can also turn on diagnostic logging. For more information about how to turn on diagnostic logging you can review the following URL:  http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479

Note that IMAP and Hotmail accounts generate one log for each Send/Receive action that you perform on these accounts (the log files are named Hotmail0.LOG, Hotmail1.LOG, etc.). If you have multiple Hotmail accounts configured, the folders where the logs are placed are named Hotmail, Hotmail 1, Hotmail 2, etc. You may have to close Outlook for the logs to be written to the log files.

Troubleshooting Error Code 0×80040113

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

There are more than a couple of situations when you may receive the error code, 0×80040005. Here are some of those situations:

1. when you cannot move, synchronize, or autoarchive messages
2. if active mail session with Exchange server was broken
3. when emailing a report using the tree email from within FRx Report Designer
4. when you use Distributed Authoring and Versioning (DAV) to query for message properties on the information store in Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003

If you are in a situation where you (1) cannot move, synchronize or autoarchive messages then you may receive the error code 0×80040005. When you try to AutoArchive messages, move messages, or synchronize items while Microsoft Outlook is connected to a Microsoft Exchange Server mailbox, you may receive the following error message:

Error while archiving folder <folder name – Inbox> in store “Archive Folders”. The source and destination folders for this operation cannot be the same.

It is possible that you receive the following message in the synchronization log:
12:51:31 Error synchronizing folder   
12:51:31 [80004005-501-0-550]   
12:51:31 The client operation failed.   
12:51:31 Microsoft Exchange Server Information Store
     
You might also receive the following error message when you attempt to copy/move:
“Can’t move the items. The item could not be moved. It was either already moved or deleted or access was denied.”

To resolve this behavior, verify that all items with attachments are either opened or deleted when you receive them.

You can use the Preview pane in Outlook to view the messages. This opens the messages and allows the scan to take place. There may be minor delays in the process while the scans occur.

In the case where (2) active mail session with Exchange server becomes broken - this may happen if xp_sendmail fails with the mail error code 0×80004005.

When you use xp_sendmail extended stored procedure to send e-mail from SQL Mail with SQL Server 2000, you might receive the following error message:
 
Server: Msg 18025, Level 16, State 1, Line 0
xp_sendmail:failedwithmailerror 0×80040005
 
You receive the same error message if you use SQL Server Agent to send email messages. However, when you use the Microsoft Outlook client on a computer that is running SQL Server (and Outlook is configured with the same MAPI profile as SQL Mail), the delivery of messages is not affected and you can successfully send e-mail.

You can experience problems described in the “Symptoms” section of this article if connection to the Microsoft Exchange server was broken during active SQL Mail session. The connection could be broken due to a sudden loss of network connectivity with an Exchange server or because of other network problems. As a result, an invalid SQL Mail session is left on an SQL Server, and SQL Server attempts to utilize it for xp_sendmail calls. Since the mail session is invalid, an error is returned.

To fix the problem without restarting the SQL Server service, you may manually stop the invalid mail session. To do so, connect to the SQL server with Microsoft SQL Server Query Analyzer or similar utility using an account with sysadmin privileges, and run the following command:
 
exec master.dbo.xp_stopmail
 
This will force the broken mail session to quit and allow new sessions to be successfully created during xp_sendmail calls.

Another situation can occur where you receive the 0×80040005 error message, “Send Message Error: -2147467259 – (Collaboration Data Objects) – e_fail (80004005)”

This error occurs when (3) emailing a report using the tree email from within FRx Report Designer.

One of the following should resolve the error:

1. Confirm that the pathing for the Output path in the Company – Information screen and pathing that has been entered in the Catalog – Output tab Filename field is a valid path.
2. When sending an attachment and using the email in the tree, a Mailbox file size limit may be reached. Remove some users from the tree or increase the size limit of the Microsoft Outlook mailbox.

Another possible circumstance when you might receive the error code 0×80040005 is (4) when you use Distributed Authoring and Versioning (DAV) to query for message properties on the information store in Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003. Then the DAV query of the information store for message properties returns the 0×80004005 error code.

A 0×80004005 (ecCallFailed) error is returned if the urn:schemas:mailheader:to property is requested. Additionally, an error is returned if there are messages in the result set that have recipients where the value of PR_EMAIL_ADDRESS is an empty string (“”).

To resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information you can review article number, 836993, in the Microsoft Knowledge Base to learn more about how to the latest service packs for Exchange Server 2003.

In addition, a supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem concerning when the DAV query of the information store for message properties returns the 0×80004005 error code.

Troubleshooting Error Code 0×80040005

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

There are several reasons why you may have received the 0x8004011C error code. Sometimes an Extended MAPI function will return a numeric result codes that is the equivalent of the MAPI_E_UNCONFIGURED error code.

Other times you will receive this error in conjunction with using the MAPI component of ASP. The Mail Application Programming Interface (MAPI) is a component used in Active Server Page (ASP) code. It was formerly called Active Messaging, but is now called Collaboration Data Objects (CDO). To allow for greater functionality from the object library than was available in Active Messaging 1.1, the objects were replaced by CDOs. CDOs are objects that support capabilities beyond simple messaging into the areas of calendaring, collaboration, and workflow.

ASP technology is used very widely in Exchange 2000 conferencing and as a result, you may encounter a variety of MAPI warnings and error messages one of which will be the 0x8004011C error code.

The optimal return value for any call to MAPI is zero, which signifies that the call is successful and is producing the expected results. However, MAPI may return a warning value (CdoW) or an error value (CdoE) to the CDO libraries. A warning signifies a partial success with possible unexpected results or side effects. An error indicates the call was not successful. All warning and error return codes are nonzero.

Such is the case of a returned error code of 0x8004011C (decimal value 1284) -  CdoE_UNCONFIGURED

Sometimes your error received will look something like this:

Event Type: Error
Event Source: MSExchangeAdmin
Event Category: Move Mailbox
Event ID: 1008
Date:  (Date)
Time:  (Time)
User: N/A
Computer: xxxxxxxxxx
Description:
Unable to move mailbox ‘<xxxx>’.
Error: The information store could not be opened.
An unexpected, unknown error has occurred.
MAPI 1.0
ID no: 8004011c-0289-00000000

Another condition for you to receive the error code 0x8004011C is if you receive the message “Your profile is not configured” when you access Client Permissions. This can happen if you are in Exchange System Manager, when you right-click a public folder, click Properties, click the Permissions tab, and then click Client permissions to view the permissions on the public folder. You may receive the following error message:

Your profile is not configured.
An unexpected, unknown error has occurred.
Microsoft Exchange Server Information Store
ID no: 8004011c-0521-00000000

ID no: c1050000
Exchange System Manager

This issue can occur if the mailbox store where the System Attendant mailbox is located is not mounted. To resolve this issue, mount the mailbox store where the System Attendant mailbox is located. If you do not want the System Attendant mailbox to be located on the current mailbox store, you can move it to another mailbox store on the same server.

Another situation when you might receive the error code 0x8004011C is when mailbox logon scripts fail; Exchange 2000 Management Pack components for Microsoft Operations Manager (MOM) 2005 cannot monitor a server that is running Microsoft Exchange 2000 Server. An event that is similar to the following appears in the MOM 2005 Operator Console:

Description:
Cannot verify availability of the following test account:
Exchange Server: “Server Name”
MDB:” Store Name”
Mailbox: “Mailbox Name”
due to the following error
Error ID: 0×80040704(-2147219708)
Error text: Your profile is not configured.
[Microsoft Exchange Server Information Store - [MAPI_E_UNCONFIGURED(8004011C)]]
Computer: Computer Name
Time: Time
Type: Error
Provider Name: Script-generated Data
Event Number: 9983
Provider Type: Generic Provider
Source: Exchange MOM
Category:
Raises Alert: True
Consolidated:
From:
To:
Event Id: EventId

For this situation, a supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described above. Apply this hotfix only to systems that are experiencing this specific problem. There is a “Hotfix download available” section at the Microsoft Knowledge Base.

The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Because of file dependencies, this hotfix requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For more information, please review the following Microsoft article number, 301378, in the Microsoft Knowledge Base.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date          Time    Version      Size      File name
   ——————————————————-
   03-Aug-2004   19:12   6.0.6615.0   716,800   Cdo.dll         
   03-Aug-2004   19:10   6.0.6615.0   745,472   Mapi32.dll  

Microsoft has confirmed that this is a problem in Exchange 2000 Server.

Troubleshooting Error Code 0x8004011C

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

I am sure that at some point your users have come to you and complained that they can’t send email. You can take a look at the logs and also at a particular user’s setting to see if there if anything different about their profile.

Sometimes they will try to send an email but get back a message similar to the following: This message could not be sent. Try sending the message again later, or contact your network administrator. The Microsoft Exchange server is currently busy. If this message is still displayed in 30 minutes, contact your Exchange server administrator. Error is
[0x80040111-0x80040111-0x000520].

There are other situations when you may get the error code 0×80040111 such as:

• PRB: Error “ClassFactory Cannot Supply Requested Class” (80040111 …  (279129).
• Attempting to install Microsoft Windows Live OneCare.
• If you have two instances of Microsoft SQL Server 2000 on the same computer, and SQL Mail is configured with separate mail profiles on each instance.
• Move Mailbox operation is unsuccessful.
• Logons to the Microsoft Exchange server computer fail and you get “The information store could not be opened” error message.
• If the MSSQLServer Service startup account is set to the local system account and xp_startmail fails.
• Exchange 2000 Management Pack MAPI Logon Check Reports Logon Failures.

Sometimes you receive fatal error messages when you use the MsExchange Event Services (Events.exe) in Exchange Server 5.5 or in Exchange 2000 Server to process messages. This can happen when a client action spawns activation of a script and they get the following error message:

A fatal error (0×80040111) occurred in an IExchangeEventSink while processing message [Subject = "xxx"]

This is a MAPI error which translates to the MAPI_E_LOGON_FAILED error value.

This issue may occur if any one of the following conditions are true:

• At least one script was last modified by someone who shares the same alias, the same surname, or the same display name as someone else in the global address list.
• For an Exchange 2000 Server-based computer, the Exchange Event Service logs on as the local computer account instead of a service account.
• If you join an Exchange 2000 Server-based computer to the site, and then perform either of the following actions:
  o Move the mailbox that created the event scripts that are bound to a folder.
  o Move an existing Exchange Server 5.5 script to an Exchange 2000 Server-based computer.

You should first determine if there is a duplicate mailbox alias (Mixed or Pure Exchange environments). You can do this by following the steps listed below. (Remember to always backup your Registry.)

1. Determine which mailbox has a duplicate alias by clicking on the EventConfig_servername folder for the server that is receiving the errors, then see who has Owner permissions. Do this because only the owners can modify the scripts.
2. Look for duplicate names by sending a new message to the alias, and then perform a check name procedure. If more than one mailbox is returned, check the surnames to see if there are duplicates.
3. To check for ambiguity for each of those aliases:
   o Type their alias in the To line of the client and perform a Check Name.
   -Or-
   o Type =alias on the To line, then press ALT+K.
   -Or-
   o Perform a directory export of the global address list and sort on the Alias column to see if any of the owners of the EventConfig_servername folder shows multiple listings.
4. Set diagnostic logging to Maximum (5) for the Event Service. This can only be done in the registry at:
   HKEY_Local_Machine/System/CurrentControlSet/Services/MSExchangeES/Parameters

If no duplicate mailbox aliases were discovered then you should resolve known issues with permissions (Mixed or Pure Exchange environments).

If duplicate mailbox aliases were discovered then you have to decide whether you want to choose a different (unique) mailbox to edit the scripts or remove the other mailboxes from the global address list.

If the scripts are installed in mailbox folders, the next part is even more detailed if you do not have a list of which mailboxes have scripts associated with them or there are many that do. This is because even with Event Service logging turned up to Maximum (5) in the registry, the Event ID 16385 (which occurs just before the Event ID 11) says that the folder being processed is Inbox. Every mailbox has an Inbox folder. So you cannot know which mailbox has been altered by the “rogue” EventConfig owner.

1. Post or send a message to the above mailboxes in a segmented fashion to determine when the Event ID 11 occurs. Twenty percent intervals during a quiet time in the environment are suggested.
2. When you find the mailbox, simply go into the script and save it while you are logged on as a unique mailbox alias.
3. If the scripts are installed in public folders:

• Set Event Service logging to Maximum (5) in the registry.
• Post or send messages to the public folders in the same fashion as described with mailboxes above, and monitor the application log.
• Event ID 16385 tells you which folder it is processing and, in case there are multiple agents in the folder, Event ID 32773 tells you the agent that it’s calling.
• Log on to a unique mailbox that has Owner permissions on the EventConfig_servername and the public folder, then open the script, and save it.

Troubleshooting Error Code 0×80040111

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

Many people have reported problems when they try to sync their cell phones with their Exchange servers.

When they try to sync with MS Exchange Server 2003 using Windows Mobile 5.0 they might get the following error code: 0x80072f17. Some users have also reported problems when trying to sync with MS Exchange Server 2007.

This problem is usually associated with using Secure Socket Layer (SSL) certificates.

Remember that you use SSL for Internet protocols such as Network News Transfer Protocol (NNTP), Simple Mail Transfer Protocol (SMTP), Post Office Protocol version 3 (POP3), and Internet Message Access Protocol (IMAP).

The SSL authentication method uses public/private key technology to ensure privacy. The SSL protocol resides at the Open Systems Interconnection (OSI) presentation layer and moves data from the application layer to the TCP transport layer. It is responsible for authentication, encryption, and verification of data integrity.
The authentication function assures that the data is being sent to the correct server and that the server is secure. Encryption ensures that data cannot be read by anyone other than the target server. Data integrity ensures that the data has not been corrupted or altered in transit.

If your user removes the SSL authentication then they’ll probably be able to synchronize their phones with the server. But that’s probably not how you want them to operate. Even if you directly install the certificate you may still have problems. Checking or un-checking the proxy settings related box does not have an effect on the problem.

One solution to this problem is to reissue the SSL certificate through Internet Information Services (IIS). This can happen if you were using the original certificate the Exchange Server installed and the certificate was replaced.

Another possible cause for the 0x80072f17 error is if an unsupported certificate has been installed. If you installed a certificate that supported wildcards from a certifying digital certificate provider, then this certificate will probably install but using the certificate was most likely not supported. To fix this problem you can replace the certificate with one that does not use wildcards and is listed in the root certificate store on the device.

Another situation when the problem can occur is when Microsoft Exchange does not connect but generates another error code: 0x80072EE7. Selecting another system to synchronize with will result in a related synchronization error message such as when the Microsoft Exchange server shows “Synchronization could not be completed. Try again later”. The support code generated by the system is: 0x80072F17.

You might need to add a new certificate to your device. Such as when your SSL certificate issuer on the Exchange Server is new to the business or has made some changes.

Here’s how you can enable and disable Outlook Web Access for internal clients:

If you are using Microsoft Exchange Server 2003 Service Pack 1 (SP1), the following steps do not apply. The Web DAV address check is not present in Microsoft Exchange 2003 Service Pack 1.

To restrict access to Outlook Web Access if you are using Exchange Server 2003 SP1 or later, follow these steps:

1. In the Active Directory Users and Computers snap-in, right-click the user account that you want to restrict from using OWA, and then click Properties.
2. Click the Exchange Features tab, click Outlook Web Access, and then click Disable.

By default, user accounts that are mailbox-enabled are also enabled for Outlook Web Access in Exchange Server 2003.

You can enable users in your corporate network to access Outlook Web Access. At the same time, you can deny access to external clients. The key to this approach is a combination of a recipient policy and a special Hypertext Transfer Protocol (HTTP) virtual server.

To use this approach, follow these steps:

1. Create a recipient policy with a Simple Mail Transfer Protocol (SMTP) domain name. Users who connect to an HTTP virtual server must have an e-mail address with the same SMTP domain as the virtual server. Creating a recipient policy is an efficient way to apply the same SMTP domain to multiple users. (Note Outlook Web Access users do not have to know the name of the SMTP domain.)
2. Apply the recipient policy to the user accounts that you want to enable access for.
3. On the front-end server, create a new HTTP virtual server that specifies the domain that is used in the recipient policy.

After you have completed these steps, users whose e-mail addresses do not have the same SMTP domain as the HTTP virtual server cannot log on and access Outlook Web Access. Also, as long as you do not use the SMTP domain as the default domain, external users cannot determine what the SMTP domain is because the domain does not appear in the From field when users send e-mail messages outside the organization.

For more information, review the following article number in the Microsoft Knowledge Base:  293386  HTTP 401 or 404 error messages when you access OWA implicitly or explicitly.

Besides enabling Outlook Web Access for users in your corporate network, you can also prevent specific internal users from accessing Outlook Web Access. You do this by disabling the HTTP and Network News Transfer Protocol (NNTP) protocols for those users.

To prevent an internal user from accessing Outlook Web Access, follow these steps:

1. In the Active Directory Users and Computers snap-in, open the user’s Properties dialog box.
2. On the Exchange Features tab, click Outlook Web Access, and then click Disable.
3. Restart the IIS Admin Service.

Troubleshooting Error Code 0x80072f17

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

There are more than a couple of situations under which you will see the error code 0x8004011b.

Some of these situations include:
- when Outlook performs send/receive operation
- when a user performs send/receive operation
- when there is a MAPI_E_CORRUPT_DATA message from the Exchange Calendar Update Tool

Here are some ways to resolve these problems.

In the first situation, The error message:  “Task ‘Microsoft Exchange Server’ reported error (0x8004011B) : ‘Unknown error 0x8004011B” can appear when outlook does a send/receive operation.

There are several causes for this problem:

1. Antivirus software blocks a connection from Outlook to the Exchange server.
2. Firewall blocks a connection from Outlook to the Exchange server.
3. Outlook 2003 has been installed on Exchange 2003 Server/domain controller.
4. Outlook profile has been corrupted.
5. Exchange database has been corrupted (usually this will occur if some third party software – like antivirus – scans Exchange database directly).

To resolve this error you can do the following:

1. Disable any antivirus on the client side and server side.
2. Verify that you use antivirus software that is compatible with Exchange 2003 and Outlook 2003.
3. If the outlook and Exchange server are insulated from each other by using a firewall, you may need to configure static port mapping: http://support.microsoft.com/default.aspx?scid=kb;en-us;q270836
4. Check Exchange database by using Eseutil Utility and Isinteg Utility.
5. Delete old outlook profile and create a new profile.
6. If Outlook 2003 has been installed on Exchange server/domain controller, you need to change the security settings of “log on network security” to “Kerberos Password Authentication”  (“Kerberos/NTLM Password Authentication” – the default settings – may fail to use the correct authentication model).

In addition to receiving the 0x8004011b error you may also see one or both of the following events recorded in the Application log.

Event ID 9360
Event ID: 9360
Category: OAL Generator
Source: MSExchangeSA
Type: Error
Machine: SERVER_NAME
Message: OALGen encountered an error while generating the changes.oab file for version 2 and 3 differential downloads of address list “\Global Address List”. The offline address list has not been updated so clients will not be able to download the current set of changes. Check other logged events to find the cause of this error. If the cause of the problem was intentional or cannot be resolved OALGen can be forced to post a full offline address list by creating the DWORD registry key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters\OAL post full if diff fails” and setting it to 1 on this server. When OALGen next generates the offline address list clients will perform a full OAB download. After that time the registry key should be removed to prevent further full downloads.

Event ID 9331
Event ID: 9331
Category: OAL Generator
Source: MSExchangeSA
Type: Error
Machine: SERVER_NAME
Message: OALGen encountered error 8004011b (internal ID 5020114) accessing the public folder store while generating the offline address list for address list ‘\Global Address List’. – Default Offline Address List

These events only get logged if diagnostic logging for the OAL Generator category in the MSExchangeSA service is set to the maximum logging level in the Exchange System Manager.

This issue may occur if an error occurs when Exchange Server 2003 generates changes to the .oab file. If this error happens, Outlook may not download the Offline Address Book.

To resolve this issue, follow these steps on the server that is running Exchange Server 2003:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then right-click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters
3. Point to New, and then click DWORD Value.
4. Type OAL post full if diff fails to name the new value.
5. Right-click OAL post full if diff fails, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor.
8. Dismount and then mount the Public Folder Store again. To dismount and then mount the public folder store, follow these steps:
   a. Start Exchange System Manager.
   b. Expand Servers, expand the server that you want, expand Storage_Group_Name, and then right-click Public Folder Store.

Note If administrative groups are defined, follow these steps: 
- Expand Administrative Groups. 
- Expand Administrative_Group_Name. 
- Expand Servers.
- Expand the server that you want.
- Expand Storage_Group_Name.
- Right-click Public Folder Store.
c. Click Dismount Store, and then click Yes to continue.
d. Right-click Public Folder Store, click Mount Store, and then click OK.

Make sure that you follow these steps carefully. Always backup the registry before you modify it. If a problem occurs after modifying the registry then you will be able to restore the registry to a known working state.

Troubleshooting Error Code 0x8004011b

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

Trying to view Public Folders in the Exchange System Manager can sometimes cause the error message “The SSL certificate name is incorrect – ID Number  c103b404” to occur. This happens when a SSL certificate on the default web server contains a different Fully Qualified Domain name (FQDN) than the internal server’s FQDN – externally the server had a different FQDN than what is used internally. If the Exchange System Manager thinks that the folder name is incorrect then it will not allow you to view the public folders.

One solution is to remove the SSL requirement from both the public virtual directory and the Exadmin in IIS. You should also read and review Microsoft Article ID : 324345. http://support.microsoft.com/kb/324345/en-us

Another solution is to use the ADSIEdit utility to manually stop the Exchange System Manager from using SSL. You can do so by doing the following:

1. Install the ADSIEdit Utility (a Windows Server Support tool) from your SBS CD using suptools.msi
2. Run a Microsoft Management console (Start->Run->MMC)
3. Open the ADSIedit.msc (browse to the Support Tools folder)
4. Drill down to: Configuration > Services >  Microsoft Exchange > Domain Name > Administrative Groups >     First Administrative Group > Servers > Servername > Protocols > HTTP > 1 > Exadmin
5. Right click msExchSecureBindings, and click Properties
6. Highlight :443: and click Remove
7. Click OK
8. Restart the Exchange System Attendant and the IIS Admin service

Another solution is to delete the certificate from the Default Web site properties and then re-running CEICW and re-apply the same certificate details. Then restart the IIS Admin Service and reopen the System Manager. You should now be able to access the Public Folders.

Alternatively you can check if you have the FQDN of the server on the certificate. You can also try adding the FQDN of the server and its IP address to the host file. Uncheck SSL in “ExAdmin” Virtual Directory based on KB, and restart ESM. If the issue still persists, uninstall the certificate temporarily from the default website folder and monitor the issue again, then reassign the certificate.

Still another way to resolve this issue is to remove the SSL on the Exadmin virtual directory. Follow the steps outlined below:

1. Click Start, point to Programs, click Administrative Tools, and then
   click Internet Services Manager.
2. Click your server, and then expand the Web site that contains the
   Exadmin virtual root (the default Web site is “Default Web Site”).
3. Right-click Exadmin, and then click Properties.
4. Click the Directory Security tab.
5. Under Secure Communications, click Edit.
6. Click to clear the Require secure channel (SSL) check box. If Require
   128-bit encryption is shaded, click to select Require secure channel (SSL), click to clear Require 128-bit encryption, and then click to clear the Require secure channel (SSL) check box again.
7. Click OK, OK.
8. Restart Exchange System Attendant Service (Services.msc) and then restart Exchange System Manager

If the issue persists then you can collect the IIS metabase on Exchange Server and send it to Microsoft support for further review.

1. On Exchange Server, install .NET Framework Version 1.1:
   http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&DisplayLang=en
2. Install MBExplorer by installing IIS 6 Resource Kit Tools:
   http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-B628-ADE629C89499&displaylang=en
3. After installation is complete, access it from Start, Programs, IIS Resources, Metabase Explorer.
4. In the left pane, right click ”LM” to choose ”Export to file”, and then save it as IIS.mbk.
5. Compress the mbk file and send it to Microsoft for review.

Many times you will receive additional error messages along with the c103b404 error code. You might see something like the following when you use Exchange System Manager to view public folders in Exchange:
 
The SSL certificate server name is incorrect.
ID no: c103b404
Exchange System Manager

The connection was aborted. Ensure that the settings on your default Web site are correct and refresh the Public Folder Tree
ID no: c103b402
Exchange System Manager

The token supplied to the function is invalid.
ID no: 80090308
Exchange System Manager

I’ve already mentioned that the error can occur if you do not have the Fully Qualified Domain Name (FQDN) of the server on the Secure Sockets Layer (SSL) certificate. You can also get the error if an SSL certificate is incorrectly published to the Exadmin virtual root in Internet Information Services (IIS).

You can correct the issue by publishing a new SSL certificate that has the FQDN of the Exchange server to the IIS server.

You can also remove SSL from the Exadmin virtual root in IIS by following the steps mentioned previously.

Troubleshooting Error Code c103b404

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators

Troubleshooting error codes in Microsoft Windows can be an arduous task. Oftentimes the error code can occur under different conditions and will take multiple diagnostic paths until you discover the reason for the error. Sometimes the error can seem random and other times the error is consistent and can be reproduced.

For instance, error code 0×80040119 is most often produced to indicate synchronization problems. Sometimes the error will occur after you’ve performed an Exchange upgrade. But diagnosing what code or application produced the error will take some time.  If you’re like most system administrators your highest priority is to keep the systems up and running. And this implies that you need to keep your end users up and running. So with that pretext in mind I will focus this blog post on how to correct your problem so that you can keep your users online and as productive as possible.

Sometimes you will have a small number of email users, out of hundreds of users, who are the only ones receiving email error messages. Everyone else will be receiving emails with no problems.  The email error messages will reference error code 0×80040119 and say something about client operation failures or synchronization errors. One such system administrator running Microsoft Outlook had the situation where only a couple email users out of many were receiving emails indicating synchronization issues. Here’s a sample of those email error messages:

Synchronizer Version 11.0.6352
Synchronizing Mailbox ‘John, Doe’
Synchronizing Hierarchy
Error synchronizing folder
       [80040119-501-0-5C0]
       The client operation failed.
       Microsoft Exchange Server Information Store
       For more information on this failure, click the URL below:
       http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80040119-501-0-5c0
Done
Microsoft Exchange offline address book
Download successful

A possible solution is to recreate the outlook profile for each user who is having the error messages. This has been known to fix the problem in the past.

Open Control Panel and double click the mail icon.  Then select Show Profiles and Add a new profile.  Proceed through all the necessary steps to create the account until you are finished.  When all ‘add profile’ steps have been completed and you have confirmed that all your profile settings are correct then you can delete the old profile.  Your users should not receive any more synchronization error messages.

You can also try:
Go into TOOLS – ACCOUNT SETTINGS
Select your exchange account
Click on CHANGE
Click the MORE SETTINGS button
Click on the ADVACED TAB
Uncheck “Download public Folders Favorites”
OK – NEXT – CLOSE

This is a good solution for two or three users who are having this problem but what do you do when a couple of hundred users are receiving the same error messages? Or maybe all your users are receiving the same error messages?

This is the reason why backups and replicas are important. It’s a lot easier to restore information for a couple of hundred users than it is to have to spend hours and hours manually rebuilding user profile information.

I mentioned earlier that your diagnostic path for resolving error code 80040119 can be varied given the different circumstances that the error will manifest itself.

Sometimes, the error message will report:

Failed to locate correct profile. Please close Outlook, open Outlook, and synchronize again. ERROR: 80040119 Communication Failure (80040119,4011).

If you get the error for all four Outlook conduits, then you should do the following:

If you are using Windows Vista:

1. Go to Start/Search
2. Click on the drop down for Advanced Search in the upper right corner
3. Click on the drop down for location and select Local Disk (C:)
4. Enter mapi32.dll in the Name field
5. Check the box for “Include non-indexed, hidden, and system files (might be slow)
6. Hit Search
7. Once the file is located (should be in C:windows/sysem32) right mouse click on it and select rename
8. Change the .dll to .old
9. Open Outlook and wait 30 second to 2 minutes. See if you get a message that a recently installed program may cause Outlook to function improperly. Answer yes that you want Outlook to repair the problem. Wait another minute, close and reopen Outlook.
10. Sync again

If you are using Windows XP:

1. Ensure that Outlook is shut down (including any open e-mails or other Outlook applications).
2. Click on “Start/Find/Files and Folders”, and type MAPI32.DLL in the “Named” field.
3. Look for the Mapi32.dll file that is located in C:\Windows\system or C:\winnt\system32 depending on which version of Windows you have. Then right mouse click on that file, and click on “Rename” from the pop up menu and rename it to Mapi32.old
4. Open Outlook. You will get a message that a “Recently installed program” may be causing Outlook to function improperly. Choose to have Outlook fix the error. Wait approximately 30 seconds (you won’t see anything happen.)
5. Sync again

Troubleshooting Error Code 0×80040119

Free ebook download: Top 10 Most Popular Troubleshooting Posts for Email Administrators