Posts Tagged ‘error codes’
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. Continue reading Error Code 10 Redux
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.
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:
- Success (2.X.X numeric codes)
- Persistent transient failure (4.X.X numeric codes)
- 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.
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.
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.
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.
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:
- You are attempting to create a new MAPI form or you’ve tried to open some custom forms in Outlook 2003.
- 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.
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.
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.