Microsoft Outlook, at times, is known to give an error saying — The action cannot be completed. The connection to Microsoft Exchange is unavailable, Outlook must be online or connected to complete this action. In this post, we will show how you can fix this problem and get back it to working as usual.
The connection to Microsoft Exchange is unavailable, Outlook must be online or connected to complete this action
There are two ways to fix tjis issue. First, create a new default profile. Second, Delete the default profile. Not many have multiple Outlook profiles is not always an option. So use the second method as follows:
- Delete Default Profile
- Create a New Outlook Profile
- Update or create your Outlook profile with RPC encryption
- Disable the encryption requirement on all CAS servers
- Deploy a Group Policy setting to update existing Outlook profiles with RPC encryption
The first, three can be configured by the end-user, while the last two are only for Servers.
1] Delete Default Profile
- Launch Outlook, and then click on Info > Account settings dropdown > Manage Profile
- It will open the Mail Setup window. Click on Show Profiles button.
- Delete the default profile by clicking on the Remove button.
- Restart Outlook.
When you remove the profile, all offline cached content for its account will be removed. However, you can backup the OST profile to reuse it.
When you relaunch Outlook, you will have to create a new profile, and then go through the setup process again.
2] Create a New Outlook Profile
If you do not want to delete, you can create a new default profile. At the Mail Setup > Profiles section, you can click on the Add button, and then give a name to the profile. Next, you need to add the email accounts you want to add. Make sure to properly configure the email account, so the error doesn’t reappear. Also, make sure to set that as the default profile.
3] Update or create your Outlook profile with RPC encryption
Most of the users have all email accounts under one single profile. One of the email accounts may be having trouble with that is running Microsoft Exchange Server 2010, Microsoft Exchange Server 2013, or Microsoft Exchange Server 2016. These are usually corporate accounts that haven’t been configured properly.
- Launch Outlook, and then click on Info > Account settings dropdown > Manage Profile
- Click on E-mail Accounts > select the email which is configured with Exchange Server, and then click on Change > More Settings
- In the Microsoft Exchange window, switch to Security tab
- Select Encrypt data between Microsoft Office Outlook and Microsoft Exchange.
- Click Ok and exit
It should fix the issue if it were because of RPC encryption error.
4] Disable the encryption requirement on all CAS servers
This part is specifically for IT admins who can disable encryption requirements. Microsoft warns that it should be only used where you cannot immediately deploy the necessary RPC encryption settings on your Outlook clients. Run the following command in the Exchange Management Shell:
Set-RpcClientAccess –Server <Exchange server name> –EncryptionRequired:$False
You must run this cmdlet for all Client Access servers that are running Exchange Server 2010 or later version. Rerun this command for each Exchange server that has the Client Access Server role. Also, make sure to disable RPC encryption, which we talked about in the above step.
However, make sure to enable it back again after deployment with changes to the RPC requirement on the Outlook.
5] Deploy a Group Policy setting to update existing Outlook profiles with RPC encryption
You can also change RPC settings on the server-side by using Group Policy. Navigate to User Configuration > Administrative Templates > Microsoft Office “Version number” > Account Settings > Exchange. Locate policy Enable RPC encryption and disable it.
We hope these methods helped you to resolve Outlook connected issues with Microsoft Exchange.
What do you want to read next?
Are you looking for an open source EDB to PST Converter tool? Want to download it for free? Did not find perfect match till now? No need to worry. Here, we have come up with a proper solution for the same.
Microsoft Exchange Server is really popular among the users and storecomplete mailbox data like emails, contacts, calendars, etc., in EDBfile format. But there are some situations in which it becomes littledifficult for the users to access Exchange database EDB file. It canbe due to any reason like corruption in database, Exchange Server isunder maintenance, moving to some other platform, etc.
In these scenarios, users are start searching for some solution tohave permanent and easy access to Exchange mailbox data. Therefore,one of the reliable way of overcoming this is convert EDB to PSTformat. Now, as it stores crucial information in it so, conversionprocess needs to carried without any loss of data. After this, thevery first question that strikes in user’s mind is how to do thesame. This is the reason user’s want open source EDB to PSTConverter. Considering this requirement, we have discussed a free EDBto PST Converter that you can easily download and use directly.
What Makes User’s Look for Free EDB to PST Converter Tool?
Before converting Exchange database file to some other file format,it is important to understand when it will be beneficial. To knowabout the same, continue reading the section below:
- It might be possible that MS Exchange Server is under Maintenance and will take long to get completed. In this situation, even Exchange will be unable to perform any task.
- Your organization is moving from Exchange Server to some other platform.
- You simply want to backup / move / transfer Exchange data on local machine or to another place.
Apart from this, there is one more major reason behind it i.e.,corruption in Exchange database file. In order to recover EDB file,you need to convert it to PST format. Here, some of the possiblereasons behind damaged Exchange database file:
- Whenever there is some technical fault in internet connectivity or there is a sudden power shutdown, Exchange shutdown abnormally resulting corruption in database.
- Whenever there is Exchange Server downtime, there is possibility some unwanted errors. For example, virus attack or hardware failure, breakdown of Exchange information store, JET engine error, and many more.
An Open Source EDB to PST Converter Tool : Try It Before Buying It!
SysTools EDB to PST open sourceis one of the popular application that can let you all export Exchange mailbox data. A user can convert emails, contacts, calendars, notes, etc., from EDB to PST format in a few simple clicks. The software is designed in a manner that it supports EDB file of all version of Exchange Server. In addition, if a user wants, he or she can export selective data items from Exchange data to PST format via date-based and category filter.
Features of EDB to PST Converter Open Tool
- Export offline EDB mailbox to Outlook PST format
- Capable to convert public folders and private mailboxes to PST format
- Provide preview of EDB file data like emails, contacts, calendars, etc.
- Allows to export even corrupted or damaged EDB files to PST data format
- Remove SMIME / OpenPGP encryption from emails in EDB file
- Compatible with all Exchange Server, Outlook & Windows versions
Try the demo of Free version of EDB to PST Converter. The software will export only first 25 items per folder. When you get satisfied with the working of the tool, you can activate the software with licensed version and have to complete access to it.
While trying to connect your Outlook account with Exchange by using ActiveSync protocol the users may get the Outlook does not support connections to exchange by using ActiveSync error. This error is commonly caused if the Outlook does not support connection to a server that is running Exchange server. A similar discussion can also be read on the Microsoft Community forum.
On the same Windows 8 Pro machine, on the same user account – Windows Mail app is connected successfully to my corporate e-mail account (‘Outlook‘ account type, use SSL connection, domain and user name specified).
In Outlook 2013 the same account can’t be connected (selecting ‘ActiveSync’ account type, specifying server name and user name, however there are no options to specify SSL and domain) – getting error message ‘Log onto Exchange ActiveSync mail server (EAS): The server cannot be found.’
Follow the steps listed in the article below to fix Outlook server issue with ActiveSync and Exchange.
Is the Exchange Activesync supported by Outlook?
1. Connect to Exchange using Standard Exchange Connection
- Launch the Outlook desktop app.
- Click on File and then click on Add Account button.
- Enter your email address and click Connect.
- Now you will be asked to enter your password again. Enter the password, and click OK.
- Click Finish to connect to exchange using standard exchange connection.
- Trying to set up your email account manually can create issues like the one mentioned earlier. Try to set up the email account normally and check if the error is resolved.
2. Configure Outlook 2013 / 2016 Manually
- If you want to configure Outlook for Exchange by using ActiveSync do the following.
- Launch the Outlook desktop client.
- Choose “New Email Account“.
- Select “Manual setup or additional server types“.
- Select “Exchange ActiveSync“.
- Now you need to fill in the server setting. The username can be in Domainusername format.
- Now press and hold the Enter key on the Keyboard until all the boxes go away.
- Once the connection goes through. Launch the Outlook client and check if the error is resolved.
For Outlook 2016 / Office 365
- Launch the Outlook client in your Windows system.
- Click on File and select Add Account.
- Now enter the email address for the account and click the Advanced Options.
- Select “Let me set up my account manually” option.
- Click the Connect button.
- Select “Exchange” option.
- Enter the password for your ID and check if the connection is established without any error.
The EAS protocol provides access to data in exchange mailboxes thus keeping all of your connected devices in sync. Since EAS connection does not provide all the features of an Exchange account, Outlook does not support this method resulting in the error.
RELATED STORIES YOU MAY LIKE:
- Windows 10 Calendar not syncing with Gmail/Outlook [FIXED]
- You don’t have permission to create an entry in this folder in Outlook [FIX]
- Outlook won’t print in color [PERMANENT SOLUTION]
Checking on above
1) Any particular tips/tric to implement it? Will it distrupt any email flow?
2) Since the add-on create a folder at Outlook, would it ‘eat’ or own up temporary space from Exchange server?
Should customer make any new overall dis space sizing?
|Article Number: 499650||Article Version: 3||Article Type: Break Fix|
Avamar Plug-in for Exchange VSS
We observe that Exchange DAG backup change-ratio presents a huge change ratio if we perform a failover of a database in a DAG environment “moving one DB from one exchange node to another”
We see the % value spiking up from the usual daily value of ~0.5% going up to ~20%/~30% and depending on which DB is being failed-over we even see ~60% of change ratio.
The DB is exactly the same before and after the failover, the only difference is that after the failover it is being backed up from a different node of the DAG cluster.
This behavior gives the impression that the backup data is being sent twice to the avamar storage, the expectation is that it should only send the usual ~0.5 of data which reflects average the daily change ratio for all the DBs under this DAG cluster environment.
The result of this inconsistency is that the avamar capacity is being unnecessarily over-utilized.
This is an expected behavior.
The logical structure of the Exchange database is the same but Avamar uses the *physical* layout of the database when performing the de-duplication.
In DAG environments, Exchange performs log shipping from the active copy of the database to the passive copy and replays the transactions against this passive copy.
Each Exchange server is responsible for applying the transaction logs against its copy of the database and there is no guarantee that it will use the same physical database layout as the other servers in the DAG.
Here is an example to better explain this concept:
- Imagine we have two copies of the same picture and we cut each one into a puzzle using a different pattern.
- While the picture looks the same once assembled, the physical layout of the puzzle is completely different.
Since Avamar only looks at the shape of the pieces, it has no way to know that the data is the same logical data, therefore the data is being sent to the server again however.
The DB failover was performed in the DAG cluster.
As per above explanation we learned that this is the normal behavior of the product.
I’ve been spending a few hours reading docs and trying to get Exchange backups going without success.
From the Exchange server, I correctly configured a NMM Exchange Admin, I can validate an existing admin successfully.
Also when I run nsrnmmsv -P, I get successful message (no errors) -> Successfully listed supported save sets.
From the NetWorker console, I configured a client with Microsoft Exchange Server application enabled, I left most settings default.
From the Objects window, I selected all available:
APPLICATIONS:Microsoft Exchange 2010
APPLICATIONS:Microsoft Exchange 2010Database-Name1
Backup Objects: APPLICATIONS:Microsoft Exchange 2010
backup command: nsrnmmsv
Backup Type: Microsoft Exchange Server
Snapshot Management: false
Block based backup: true
Client direct: true
Parallel save streams: false
Data Domain interface: IP
Actually I can do a Filesystem backup successfully..
But when I try an Application: Exchange backup (to backup the Exchange database), I get the errors you see below.
I believe it has to do with my storage pool, I currently use local, adv_file media type..
After reading some posts on this forum, I can confirm that save -b POOL_NAME -a DIRECT_ACCESS=yes C:” is working well from the client computer.
Is it related to the fact that I didn’t configure a Remote user in the Device properties? If so, I don’t understand how to do it, please help.
107092:nsrnmmsv: Version information for C:Program FilesEMC NetWorkernsrbinnsrnmmsv.exe: Original file name: nsrnmmsv.exe Version: 9.1.0 (ntx64) Comments: Supporting Microsoft Volume Shadow Copy Service
127159:nsrnmmsv: Created temp path C:Program FilesEMC NetWorkernsrtmpnmm2018-08-16_15-00-12_5564-6044.
nsrnmmsv: multithreaded save set parallelism==6
145369:nsrnmmsv: Initialization success — Exchange shell successfully initialized. Required for Exchange.
133296 1534446013 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 26 Starting backup operation. 0
145369 1534446014 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 89 Initialization success — Exchange shell successfully initialized. Required for Exchange. 0
132558 1534446016 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 75 Initialization process successful. Required for getting required log range. 0
115938 1534446016 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 71 The maximum number of Consistency Check process threads is set to ‘%d’. 1 1 1 4
129273 1534446016 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 41 Consistency Check Throttling is disabled. 0
114457 1534446017 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 89 ‘%s’: adding to the file list with the minimum range as = %d and the maximum range as %d. 3 0 52 APPLICATIONS:Microsoft Exchange 2010Database-Name1 1 3 109 1 3 110
98519 1534446018 2 5 0 6116 5564 0 Exchange-Server.domain.local nsrnmmsv NSR warning 47 Unable to setup direct save with server %s: %s. 2 12 33 Backup-Server.domain.local 49 294 86929 125 %s:%s: Unable to perform backup for save-set ID ‘%s’ with %s=%s, check device and pool configuration to enable Client direct. 5 12 33 Exchange-Server.domain.local 51 66 APPLICATIONS:Microsoft Exchange 2010Database-Name1DatabaseFiles 0 10 4269132226 11 13 DIRECT_ACCESS 0 3 Yes
90018 1534446018 5 5 0 6116 5564 0 Exchange-Server.domain.local nsrnmmsv NSR critical 55 Cannot open a %s session with NetWorker server ‘%s’: %s 3 20 8 nsrnmmsv 12 33 Backup-Server.domain.local 49 294 86929 125 %s:%s: Unable to perform backup for save-set ID ‘%s’ with %s=%s, check device and pool configuration to enable Client direct. 5 12 33 Exchange-Server.domain.local 51 66 APPLICATIONS:Microsoft Exchange 2010Database-Name1DatabaseFiles 0 10 4269132226 11 13 DIRECT_ACCESS 0 3 Yes
0 1534446018 1 5 0 6116 5564 0 Exchange-Server.domain.local nsrnmmsv NSR notice 50 %s%s%s: %-*s%s%s%s %*s %2.2ld:%2.2ld:%2.2ld %6s %s 15 0 0 0 0 20 8 nsrnmmsv 1 1 0 23 66 APPLICATIONS:Microsoft Exchange 2010Database-Name1DatabaseFiles 0 7 level= 0 4 full 0 1 , 1 1 0 0 4 0 KB 30 1 0 30 1 0 30 1 0 36 1 0 0 5 files
110812 1534446018 5 0 0 6116 5564 0 Exchange-Server.domain.local nsrnmmsv NSR critical 44 Backup of Saveset ‘%s’ failed with error %s. 2 51 66 APPLICATIONS:Microsoft Exchange 2010Database-Name1DatabaseFiles 24 240 Exchange-Server.domain.local:APPLICATIONS:Microsoft Exchange 2010Database-Name1DatabaseFiles: Unable to perform backup for save-set ID ‘4269132226’ with DIRECT_ACCESS=Yes, check device and pool configuration to enable Client direct.
98519 1534446018 2 5 0 5828 5564 0 Exchange-Server.domain.local nsrnmmsv NSR warning 47 Unable to setup direct save with server %s: %s. 2 12 33 Backup-Server.domain.local 49 289 86929 125 %s:%s: Unable to perform backup for save-set ID ‘%s’ with %s=%s, check device and pool configuration to enable Client direct. 5 12 33 Exchange-Server.domain.local 51 61 APPLICATIONS:Microsoft Exchange 2010Database-Name1LogFiles 0 10 4252355010 11 13 DIRECT_ACCESS 0 3 Yes
90018 1534446018 5 5 0 5828 5564 0 Exchange-Server.domain.local nsrnmmsv NSR critical 55 Cannot open a %s session with NetWorker server ‘%s’: %s 3 20 8 nsrnmmsv 12 33 Backup-Server.domain.local 49 289 86929 125 %s:%s: Unable to perform backup for save-set ID ‘%s’ with %s=%s, check device and pool configuration to enable Client direct. 5 12 33 Exchange-Server.domain.local 51 61 APPLICATIONS:Microsoft Exchange 2010Database-Name1LogFiles 0 10 4252355010 11 13 DIRECT_ACCESS 0 3 Yes
0 1534446018 1 5 0 5828 5564 0 Exchange-Server.domain.local nsrnmmsv NSR notice 50 %s%s%s: %-*s%s%s%s %*s %2.2ld:%2.2ld:%2.2ld %6s %s 15 0 0 0 0 20 8 nsrnmmsv 1 1 0 23 61 APPLICATIONS:Microsoft Exchange 2010Database-Name1LogFiles 0 7 level= 0 4 full 0 1 , 1 1 0 0 4 0 KB 30 1 0 30 1 0 30 1 0 36 1 0 0 5 files
110812 1534446018 5 0 0 5828 5564 0 Exchange-Server.domain.local nsrnmmsv NSR critical 44 Backup of Saveset ‘%s’ failed with error %s. 2 51 61 APPLICATIONS:Microsoft Exchange 2010Database-Name1LogFiles 24 235 Exchange-Server.domain.local:APPLICATIONS:Microsoft Exchange 2010Database-Name1LogFiles: Unable to perform backup for save-set ID ‘4252355010’ with DIRECT_ACCESS=Yes, check device and pool configuration to enable Client direct.
140124 1534446020 0 0 0 6076 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 89 Performing the cleanup of ‘%s’ to avoid inconsistency in the indexes for child save sets. 1 51 52 APPLICATIONS:Microsoft Exchange 2010Database-Name1
139527 1534446027 3 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR error 51 The backup operation did not complete successfully. 0
102333 1534446027 3 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR error 21 Exiting with failure. 0
2018-08-16 3:00:27 PM Removing files under temp path C:Program FilesEMC NetWorkernsrtmpnmm2018-08-16_15-00-12_5564-6044.
This is an environment with 20,000+ mailboxes and OWA is used to access the mailboxes (Outlook is almost not used). Now, this environment consists on 8 Exchange 2016 servers with mailbox and CAS roles ach of them and of course SourceOne extensions for OWA version 7.24.4058 are installed. on all Exchange servers and had been working good, or… That´s what it seems.
Issue: Exchange servers are experiencing high user processor at peak hours because the OWA App pool takes 90+% of processor, when this happens in one server, the issue replicates to other Exchange servers as well and the only workaround is restarting the affected Exchange servers.
Microsoft has been working on this for two weeks and now they wonder if ES1 extensions may be impacting, since ES1 and Exchange App pools are related (I ask myself if ES1 may be impacting too).
I know this intensive OWA usage is unusual but, Has anyone experienced this before? Has anybody idea of what to check from the SourceOne perspective on the Exchange server when this happens?
I´d really appreciate any tips or feedback.
Thanks in advance