Код ошибки 21999 outlook

In this fast growing economic world sending and receiving emails is an important mode of communication. In this domain Microsoft outlook is playing an essential role and providing services. Microsoft Outlook provides assistance for your email messages, calendar events, tasks, and other items in either an Outlook for Windows Data File (.pst) or an Outlook for Mac Data File (.olm).

We know that technology has its own limitations and what would a user do if user cannot send or receive mails by using Outlook service? This type of error in outlook regarding error in sending or receiving email is known as “outlook error code 21999”. In this article readers get the instructions for handling these type of errors. So, everyone get ready for this knowledgeable journey and learn methods for solving the issue as soon as they encounter this error in Outlook. Most of the Outlook errors are simple to resolve just by giving a restart to your system/Outlook, by checking account settings, or using scan PST, etc. But there are some issues that require categorical methods to solve them. Outlook usually use by Microsoft Office users but Mac users are also getting service of this software as desktop email program built specifically for Apple’s Mac operating system by the IT giant Microsoft. In this article we will be looking at how users can resolve this error for Mac computers and solutions to avert it in the future. When the user tries to synchronize email with MS Exchange for various reasons, many problems occur, ultimately leads to the inaccessibility of stored data. Even failure in sending and receiving emails causes all scheduled activities to fail and leads to disrupt business flow wherever the client-server application is installed.
In this article, users will be going to read causes for outlook error code 21999, and methods to resolve it. So, in the section below, we have listed some common causes that leads to the error along with the reason for their occurrence.

Outlook perform synchronization but some users complain of Outlook for Mac error ‘Microsoft Sync Services has encountered a problem and needs to close’. We are sorry for the inconvenience’. To fix this error it is advised to clear the Outlook Mac cache

Unexpected Outlook errors are difficult to handle and we are really tired of such errors. These errors difficult to understand that can bring your daily work to halt whereas some errors are self-explanatory. One such Outlook error is “21999” – it occurs during sending or receiving an email. Such errors might not be very easy to comprehend on first look.

The truth is that it is not that difficult to fix Outlook error codes and a few easy steps are all you need. This write-up is focusing on the MS Outlook error 21999 which indicates that there has been an interruption in the connection to the server.

Causes And Reason Behind 21999 Error Outlook

Causes for the error:

Unexpected errors in outlook are become difficult to handle and users are really irritated of such errors. These errors are difficult to understand and can bring your daily work to a halt whereas some errors are simple and self-explanatory. One such Outlook error is “21999” – it appears during sending or receiving an email. This error might not be very easy to understand on first look.

The fact is that it is not that difficult to resolve Outlook error codes and a few easy steps are all require by users need to follow. This write-up is focusing on the MS Outlook error 21999 which indicates that there has been an interruption in the connection to the server.

Now, Causes behind Outlook error 21999 include:

1) Terrible synchronization of software with system.

2) Antivirus applications creates hindrance in smooth functioning.

3) Big attachment in the messages in the software.

Outlook for Mac has the following limitations also:

• Users are not able to send email messages from a distribution list, a security group, or a mail-enabled Public Folder.
• Users are not able to use a distribution list, a security group, or a mail-enabled Public Folder as a delegate.

Effect Of Microsoft Outlook 21999 Error Message

Symptoms for the error:

When users are trying to send email messages from a distribution list, a security group, or a mail enabled Public Folder, Outlook for Mac 2011, Outlook 2016 for Mac, or Outlook for Mac 2019 times out, and users receive one of the following error messages:

Console Copy

Error: An unknown error has occurred in Outlook.

Details: Mail could not be sent. The message has been moved to your Drafts folder.

Error code: -19991

Error: An unknown error has occurred in Outlook.

Error code: -19992

Error: An unknown error has occurred in Outlook.

Details: Mail could not be sent.

Error code: -21999.

How To Fix MS Outlook Mail Error Waring 21999

Steps to fix error:

There are certain Troubleshooting steps which help in solving the issue:

1) Reset internet settings in the system.

2) Reinstall antivirus if it is creating a hindrance.

3) Remove unwanted mail.

If the above methods do not help users in solving the issue then users must follow the below listed steps to resolve the issue.

These steps are:

Methods to Solve ‘Outlook for Mac Sync’ problem:

Users must follow the steps mentioned below to solve Outlook 2016 Mac Sync problem:

1. Disable Sync Services Preferences
2. Give a command to start Outlook in your system (if it opens).

• 1. Then go to outlook menu and click on Preferences.
  2. Under the Other options go and select Sync Services.
  3. Uncheck all the boxes and close Outlook.
  4. Then give a command to restart Outlook and check the error is solved or not.

This will ultimately disable the sync services, if the issue is resolved it projects that the sync preferences are corrupted and needs to be reset. To reset Outlook for Mac sync issues follows the steps mentioned below:

Command for Force Quit Outlook:

• Go and click on the Apple menu
• A dialog box with all the active/ running applications will pop up

• Select all the applications but do not select Finder
• And finally click on the ‘Force Quit’ button
• But Before quitting any application, keep back up all items and Outlook identities for later use.

After performing synchronization for outlook still some users face the issue of Outlook for Mac error ‘Microsoft Sync Services has encountered a problem and needs to close’. We are sorry for the inconvenience’.

To fix this error it is advised to clear the Outlook Mac cache

• First of all disable Sync services and close all applications that are running.
• Go to the menu and click on Applications>> Utilities and then open Activity Monitor.
• Type Sync to in the box.
• Quit all the processes found in the software.
• When the users completes the task close Activity Monitor.
• Then go to Home and then click /Library/Application Support/,
• And Open Sync Services and move all the files to there.

Then gives command to restart all applications and turn on sync services

This will resolve the issue of Outlook for Mac Sync Error. Users may try any of the above discuss methods as per the system and error encountered. But there always a good habit of taking back up files before starting any process. These manual steps will remove the Microsoft Sync problem in Outlook for Mac.

If the error is still not resolve then users need to look in their firewall.  Firewalls can interfere and block incoming and outgoing traffic and this creates hindrance in the working of outlook. So users make sure that Outlook and/or the required ports for email are listed as an exception to go through it.

If users are facing the send/receive errors after updating Outlook, then probably they need to reconfigure their firewall to re-allow Outlook to pass-through again. The reason behind it is that many firewall solutions verify everything in depth so that the correct outlook.exe that is trying to pass through the firewall may pass and not any virus which named itself outlook.exe. As with most software get updates the outlook.exe is not an exception and gets updates as well, you’ll need to accept it as safe again. And to understand it more users can find more information about this in the manual of your firewall solution.

Virus scanners which integrates themselves with Outlook are become the source of causing all sorts of send receive issues. Users by disabling their virus scanner’s integration with Outlook resolves the problem and it does not leads to any compromise with their system’s safety.

After reading this article now users can resolve the issue of outlook error 21999 and enjoy the smooth functioning of the outlook.

Краткое руководство по устранению проблемы «Outlook не может подключиться к прокси-серверу»

Microsoft Outlook устанавливает соединение с Exchange Server с помощью запроса HTTPS, который подтверждается сертификатами SSL. Однако многие пользователи сталкиваются с некоторыми проблемами с этими сертификатами, из-за которых их Outlook не может подключиться к прокси-серверу.

Outlook не принимает сертификаты SSL, подписанные только организацией. Outlook требует действительный и надежный сертификат SSL для установления безопасного и успешного подключения.

Преимущества использования SSL-сертификатов для Exchange Server

1. При аутентификации SSL сообщения кодируются с помощью симметричного 256-значного шифрования и ключа подписи RSA из 2048 частей.
2. Они используются для проверки вашего работника MS Exchange и предоставления подтверждения клиенту.
3. Он дает подтверждение клиенту электронной почты, что он не ведет к мошенничеству, а является подтвержденной учетной записью Exchange.
4. Действительный сертификат SSL устраняет требования к самозаверяющим сертификатам для всех клиентов электронной почты.

Причины, по которым Microsoft Outlook не может подключиться к прокси-серверу?

Помимо неполного сертификата безопасности SSL, существует несколько причин, по которым может возникнуть эта проблема:

Программы для Windows, мобильные приложения, игры — ВСЁ БЕСПЛАТНО, в нашем закрытом телеграмм канале — Подписывайтесь:)

1. Для подключения к серверу требуется центр сертификации (ЦС).
2. Если вы не доверяли центру сертификации в корне.
3. Недействительный или отозванный сертификат.
4. Сертификат не соответствует названию сайта.
5. Неисправные надстройки сторонних производителей или надстройки браузера.

Ваш Outlook не работает с прокси? — Вот резолюция!

Это список сообщений об ошибках, которые могут возникнуть, когда Outlook пытается подключиться к серверу.

Ошибка 1: Проблема с сертификатом безопасности прокси-сервера% s. Outlook не может подключиться к этому серверу. (% s).

Ошибка 2: Проблема с сертификатом безопасности прокси-сервера% s. Имя в сертификате безопасности недействительно или не соответствует имени сайта. Outlook не может подключиться к этому серверу. (% s).

Ошибка 3: Проблема с сертификатом безопасности прокси-сервера% s. Сертификат безопасности не получен от доверенного удостоверяющего центра. Outlook не может подключиться к этому серверу. (% S) ».

Ошибка 4: Проблема с сертификатом безопасности прокси-сервера. Имя в сертификате безопасности недействительно или не соответствует имени целевого сайта outlook.office365.com. Outlook не может подключиться к прокси-серверу (код ошибки 0).

Решение для ошибки 1 или 2: проверьте сертификат

Прежде всего, вам следует проанализировать сертификат, а затем обратиться к системному администратору для решения проблемы. Для проверки сертификата выполните следующие действия:

1: В Microsoft Internet Explorer подключитесь к серверу RPC или к защищенному серверу.

Например, тип https: // www. имя_сервера.com/rpc в адресной строке веб-браузера и нажмите клавишу ВВОД.

2: Дважды щелкните значок замка, расположенный в правом нижнем углу веб-браузера.

3: Щелкните значок Подробности таб.

Обратите внимание на информацию в нижеприведенных полях:

1. Действителен до — В нем указывается дата, до которой сертификат действителен.
2. Предмет — Данные, представленные в поле «Тема», должны совпадать с названием сайта.

Решение для ошибки 3: установите доверенный корневой сертификат

Следуйте инструкциям по установке доверенного корневого сертификата:

1. Щелкните Установить сертификат, когда на экране появится диалоговое окно Сертификат.
2. Нажмите Следующий.
3. Установите флажок, выберите разместить весь сертификат в следующем магазине.
4. Нажмите Просматривать.
5. Выбирать Доверенные корневые центры сертификации> ОК.
6. Нажмите Далее >> Готово >> Нажмите ОК.

Решение для ошибки 4: отключите сторонние надстройки

Запустите Outlook в безопасном режиме, чтобы изолировать проблему. Следуйте инструкциям, чтобы сделать то же самое:

1. Нажмите Пуск >> Выполнить.
2. Тип outlook.exe / сейф, а затем щелкните Ok.

Если Outlook успешно запускается в безопасном режиме, возможно, проблема вызвана надстройкой стороннего производителя.

Проверьте наличие сторонних надстроек COM и отключите их. Для этого выполните следующие действия:

1. Перейти к файлу меню> щелкните Параметры> Надстройки.
2. В поле «Управление» щелкните Надстройки COM> Перейти.
3. Снимите флажок рядом со сторонними надстройками, которые вы хотите отключить.
4. Перезагрузите Outlook.

Иногда Outlook не может подключиться к прокси-серверу из-за повреждения файла OST. В таком случае вам необходимо восстановить поврежденный файл OST. Чтобы преобразовать поврежденный OST в работоспособное состояние, вы должны использовать Tool.

Утилита эффективно и легко восстанавливает сильно поврежденный файл без ограничения размера файла. Более того, вы можете восстановить безвозвратно удаленные данные из зашифрованного и полностью поврежденного файла. Функция быстрого и расширенного сканирования эффективно выполняет глубокий анализ данных OST.

Вывод

В этом блоге мы обсудили причины, по которым Outlook не может подключиться к прокси-серверу. Кроме того, мы перечислили все сообщения об ошибках, которые могут возникнуть при подключении Outlook к прокси-серверу.

После этого мы предоставили решение, чтобы исправить все эти сообщения об ошибках. Однако, если проблема вызвана проблемами, связанными с Outlook, такими как повреждение OST, мы предложили автоматический инструмент.

Программы для Windows, мобильные приложения, игры — ВСЁ БЕСПЛАТНО, в нашем закрытом телеграмм канале — Подписывайтесь:)

Источник

Outlook Internal Exchange Error 80000000? Try these fixes

Outlook and Exchange are the backbones of a corporate organization’s communication and things can get very ugly for the organization if these two applications stop communicating with each other. One such issue is the Outlook internal Exchange error 80000000, in which, an Outlook client cannot communicate with the Exchange server locally (although, the external connection is working fine) and throws the error 80000000. Usually, the following type of message is shown:

Outlook Internal Exchange Error 80000000

The following are found to mainly cause the Outlook internal Exchange error 80000000:

• HTTP Protocol: Due to the complexity involved with HTTP protocol (certificates, etc.), it is recommended that an Exchange server may be accessed by using the TCP/IP protocol. If the Outlook client is configured to use the HTTP protocol, then the Outlook client may show the error 80000000.
• Improper configuration of the Server’s Security Product: If the Server’s security product (like F5) is interfering with the Outlook/Exchange communication, then you may encounter the Outlook internal Exchange error 80000000.
• TLS Update: TLS is an improved version of SSL and if its latest update is not applied to the client system, then the Outlook client may become incompatible with the Exchange Server, thus causing the Exchange error 80000000 when accessed internally.

Set the Outlook Client to Use TCP/IP Protocol

As the Outlook client is having issues internally when using the HTTP protocol, setting up the client to use the TCP/IP protocol (as recommended when using the client in the internal environment) may solve the problem.

1. Launch the Outlook application and open its File menu.
2. Now, in the right pane, expand the dropdown of Account Settings and select Account Settings. Open Account Settings of Outlook
3. Then, in the Email tab of Account Settings, double-click on the account using the Exchange server, and in the resulting window, open More Settings. Open the Exchange Account Settings of Outlook
4. Now, in the Connection tab, uncheck Connect to Microsoft Exchange using HTTP and apply your changes. Uncheck Connect to Microsoft Exchange using HTTP
5. Then, relaunch the Outlook client and check if it is working fine.

Edit the System’s Registry to Delete the HTTP Value

Outlook may show the internal Exchange error 80000000 if the HTPP settings of the system are not properly configured in the system’s Registry and properly configuring the same may solve the problem.

Warning: Proceed at your own risk as editing the system’s registry may harm your data/system, if not done properly.

1. Firstly, to be on the safer side, create a backup of the system’s Registry.
2. Now click on Windows and search for Registry Editor.
3. Then, right-click on the result of Registry Editor and select Run as Administrator. Open Registry Editor as Administrator
4. Now navigate to the following path:
5. Then, in the right pane, delete the DefaultSecureProtocols value and close the Editor. Delete the DefaultSecureProtocols Value in the WinHttp Registry Key
6. Now, restart your system and upon restart, check if the Outlook Exchange error 80000000 is cleared.

If the issue is still there and you are having issues when the Exchange server is accessed from the local network, then make sure that the local DNS server properly points to the local address of the Exchange server.

Enable TLS 1.1 and TLS 1.2 Protocols on the Client Machine

TLS (Transport Layer Security) is a successor to the old SSL (Secure Sockets Layer) or in simple words, TLS is an improved version of SSL. If the client device does not have TLS 1.1 and 1.2 enabled, then it may not be compatible with the updated Exchange server and thus cause the issue. In this scenario, enabling TLS 1.1 and TLS 1.2 on the client system may solve the problem.

1. Launch a web browser and download the following Easy Fix file from the official Microsoft website.
2. Once downloaded, launch the Easy Fix as administrator.
3. Then follow the prompts on your screen to apply the fix and afterward, restart your system.
4. Upon restart, launch a web browser and download the following update from the official Microsoft Update Catalogue website. Download the TLS Update KB3140245 from the Update Catalog Website
5. Now download the update as per your OS and once downloaded, launch the downloaded update as administrator.
6. Then follow the prompts on your system to apply the update and afterward, restart your system.
7. Upon restart, check if the Outlook internal Exchange error 80000000 is cleared.

If that did not work, then check the following Microsoft URL to set up TLS as per their recommendations. If that did not work as well and your organization is using F5 security, then check if changing the encryption method of the F5 in the SSL Profile from default to DEFAULT auf ALL:!DHE-RSA-DES-CBC3-SHA solves the problem. Also, if the problematic client is using Windows 7 and the F5 security is installed on the server, then the time may have arrived to update the machine to Windows 10 as F5 creates a lot of issues (including the one under discussion) for Windows 7 machines.

Источник

question

outlook on windows 11 does not connect to the internal exchange error 80000000

Hello,
I recently(1 week) switched some of the workstations to windows 11.
But with the transition to Windows 11 I noticed that Outlook Office 365 or Outlook 2016 that I used to connect to the internal exchange server (Exchange server 2010, Windows Server 2008) through Outlook Anywhere no longer works.
The error received is: there is a problem with the proxy server’s security certificate. Outlook is unable to connect to the proxy server autodiscover. Error Code 80000000
I mention that the security certificate is a purchased one and that it is functional.
On Windows 10 and Office Outlook 365 or Outlook 2016 works without problems for many years.
I have 3 days of intense internet searches but without success. Everything I tried doesn’t work
Please advise me, I don’t want to go back to Windows 10 although I reinstalled some more important workstations with Windows 10.

Having same issue with Office 2016 Outlook on all machines with Windows 11 but works fine with Windows 10 and prior. OWA works file also.

Welcome to our forum!

As I know, Microsoft 365 is not supported for Exchange 2010. If there’re something wrong when you use Microsoft 365 and Exchange 2010, incompatibility may also have an impact on this. Please install the corresponding compatible Outlook client, such as Outlook 2013.

To further confirm whether the issue is related to Outlook client, please try logging in to OWA and check if it works normally.

Considering impact of windows upgrade, please use the same mailbox to do the same test on win10 and win11 to check if there are differences.

In addition, Exchange Server 2010 reached its end of support on October 13, 2020. For your better user experience, it is suggested that you could upgrade your Exchange server to a newer version.

Just checking in to see if above information was helpful. If you have any further updates on this issue, please feel free to post back.

I confirm that, on windows 10, all office versions (2013, 2016, office 365) are perfectly connected from outside the organization to the 2010 internal exchange server.
Any of these versions(2013, 2016, office 365) installed on windows 11, in the same scenario (outside the organization) cannot connect to the same server exchange 2010.
The problem appeared with windows 11 (either we are talking about the new installation of windows 11, or the upgrade from win 10 with absolutely all the updates up to date).

Add your Exchange server’s MX name to proxy exclusion list. For example : mail.yourorganisation.com

8 Answers

I have the same issue. Upgraded to window 11 and just got this proxy error.

Exchange 2010 with Office 365 Outlook. Works fine in windows 10.

Want to try windows 11 but can’t if won’t work with Outlook.

Had the same issue. Used VPN locally on our network and it worked. But now Outlook only works over VPN.

I have the same error message with Windows 11 + Office 365 + Exchange Server 2013
Everything was working with Windows 10
Any Solution!?

The same problem. Unable to work with Outlook with this.

Windows 11 has many bugs, obviously. Recently we were also not able to install our company software running the new Microsoft Installer. Waited about a week, restarted the computer several times, and tried again and now it works. Was also a certificate type error, being misreported I think like here with Outlook and its connection.

The problem is that in Windows 11 some Cipher Suites are disabled.
You have to change to min. TLS1.2 in Exchange 2010.

I was able to solve this issue.
PLEASE NOTE
This is not a safe work around
TLS 1.0 is retired and should be moved away from
but if you need an immediate resolution do the following
1) Turn on TLS 1.0 on the local windows 11 system by adding a registry key under
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInternet SettingsWinHttp
DWORD named DefaultSecureProtocols
with the key value of 00000080
Save and restart
Reconnect, the error should be gone and should work offsite

Other solutions are:
2) Switch Exchange 2010 to TLS 1.2 (better option)
3) Switch to newer Exchange or hosted email plaform

RohanBradley-7040, you’re the best. It helped me too.

I was using an Outlook 2013 to connect to a Windows 2008 Exchange Server but yesterday I updated my laptop to windows 11 and now I cannot access the exchange server from outside office (i did not try from inside our office network). I receive the same error message with code 80000000
I am not very good with registry and I am not sure I understand correct your solution.
After edit my registr looks like this (picture attached) but still does not work. Any ideas?

You have that correct, you just need to add it to a second location. It has to be added to the same spot under this location

One remote user got new laptop (Windows 11) Uses OWA to connect to mail — I know this is a little old but this did not work for me. I added it to the first location just fine in registry and no go (still times out.) Then I saw to add to second location. Well second location did not have WinHttp location in registry. I added it and the DWORD and no luck. New HP laptop Windows 11 Pro v. 22H2 — Not much on the web about other than changing the WinHttp settings. Anyone?

Running Ex 2010 (Win2k12 server)

Thank you so much.
I was on the verge of returning to windows 10.
This worked for Outlook 2013 with a Windows 2009 Exchange Server.

Ok, so this worked great and allows Outlook to connect to an old Exchange 2007 server. However when this registry key is present, Microsoft Edge will no longer update. In Edge if you go to «Help and Feedback, About Microsoft Edge» it will say «Checking for updates» and then eventually error out with «An error occurred while checking for updates: Unable to connect to the Internet. If you use a firewall, please allowlist MicrosoftEdgeUpdate.exe. (error code 7: 0x80072EFE — system level).» If I remove the registry key it updates poperly. Any idea on how to get around this?

Issue solved by reconfiguring servers:

Our failed configuration was: Outlook 2013 running on Windows 11 not connecting to Exchange 2010 running on Windows 2008 R2 via proxy.

Cause of failure: Windows 11 disables TLS 1.0 and TLS 1.1 by default and Exchange 2010 running on Windows 2008 R2 uses TLS 1.0. Therefore, Outlook can’t communicate with Exchange. In our case, this happened when the Windows 10 workstations were upgraded to Windows 11 and is only noticed on workstations connected outside of the subnet the server is connected to. That is all of the workstations connected to the same subnet as the server never had a problem after the Windows 11 upgrade, but all of the workstations outside of that subnet failed with proxy (Error Code 80000000).

NOTE: This is a safe work around:

Solution: Add TLS 1.2 to the servers. This works because Windows 11 supports TLS 1.2 by default at this time and Windows 2008 R2 can be made to support TLS 1.2. This is great solution because only the server needed to be touched and we did not have to touch the workstations. We followed this for guidance: https://jaapwesselius.com/2018/10/05/exchange-2010-and-tls-1-2/

Fortunately, in our case Windows and Exchange were already well patched so we only needed to add these registry keys and DWORD items on the server and reboot it.

Here are all of the registry keys and DWORD items we added:

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocols]
Added Key: TLS 1.2

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2]
Added Key: Client
Added Key: Server

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Client]
Added DWORD: DisabledByDefault = 00000000 (0)
Added DWORD: Enabled = 00000001 (1)

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Server]
Added DWORD: DisabledByDefault = 00000000 (0)
Added DWORD: Enabled = 00000001 (1)

Источник