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.

Continue reading Troubleshooting Error Code 80042109

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: 0×800c0131

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.

Continue reading Troubleshooting Error Code 800c0131

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.

Continue reading Troubleshooting Error Code 0×800ccc0e

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. Continue reading Troubleshooting Error Code 926196

 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.

Continue reading Troubleshooting Outlook Error 938816

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.

Continue reading Troubleshooting Error Code 0×80004005

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.

Continue reading Troubleshooting Error Code 0×80040113

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.

Continue reading Troubleshooting Error Code 0×80040005

There are several reasons why you may have received the 0×8004011C 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 0×8004011C error code.

Continue reading Troubleshooting Error Code 0×8004011C

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.

Continue reading Troubleshooting Error Code 0×80040111