How to: Setup Import Export role in Office 365

I went to upload the PST files on a tenant to use the Office 365 Import service by uploading the PST files using the AzCopy.exe. After I was done, I started the import and after 60 minutes I get a failed error. I made some research and then restarted the import, but now I noticed a message saying “Please add Mailbox Import Export role for use running import and check back in 60 minutes“.

To do this,

– Login in Office 365 portal
– Click on Exchange
– Click on Permissions
– Click on Admin Roles
– Add a new role with Mailbox Import Export Role
– Add the user you are using to import as part of the group

Screenshot below

office365_importexportrole

(427)

Fix: AzCopy.exe Could not finish the operation within specified timeout

When uploading files or PST files to Office 365 using AzCopy.exe, during the upload using Microsoft’s PST Import service you might have the frustrating error saying “The client could not finish the operation within specified timeout“. On the command prompt it will be seen as stuck on saying 0 files uploaded with a transfer speed of 0 KB/s. I literally spent hours trying to find out why my PST files do not upload to Office 365.

This can be fixed by lowering the concurrent operations with the import services. After looking at the option which is /NC option to either 2 or 1 depending on the internet connection upload speed. To be safe, in my case I have setup the NC as 1.

Here’s an example of how the command prompt will look like.

AzCopy.exe /source:\\My-Server\PST /dest:https://12345ab67cd89e0fg123h45.blob.core.windows.net/ingestiondata/Company/PST /destkey:jhdfasdfnasdnflasjkdfnjklsdanflasdfn/nfasdjkfnasdjklfnsjkladnfasjkldfnsdjklf== /S /V:d:\PST_Upload\upload.log /NC:1

(278)

Fix: Azure RemoteApp GPO login scripts not working

When setting up your template and publishing your apps, if you setup a Group Policy Object (GPO) for your users, this does not work. After some research and testing I found out that to solve the issue, you must do the following:

Add the Explorer application to the Published apps

Start by publishing the command line interface (cmd.exe). In the Publishingtab, select cmd, and then click Publish > Publish program using path.

Enter the name of the app and the path. For our purpose, use “File Explorer” as the name and “%SYSTEMDRIVE%\windows\explorer.exe” as the path.

In my case this worked, hope it does for you.

(42)

Fix: Azure AD Connect unexpected error on sign in

You setup the domain, verified and you are in the process of configuring the Azure AD Connect Tool, you will be asked to enter the username and password for the tool to connect to the Azure AD.

The connector immediately stops with an error at the first step under the Express/Custom settings page titled “Connect to Azure AD” with the below error.

Unable to validate credentials. An unexpected error has occurred

unexpectederror1

This error most probably will show because you are using a user which ends with @outlook.com and the connect tool will not work with an service-bound Outlook username. To fix this issue and work successfully simply create a new ‘Global Admin’ user on the AD which ends @yourdomain.

In my case this worked like a charm.

 

(258)

Fix: Windows Server Backup The process cannot access the file

When running Windows Server Backup to another location and you get the error “The process cannot access the file because it is being used by another process”.

Capture

To fix this you would need to look on the backup logs from the location %windir%\logs\windowsserverbackup.

In the error log file you will find

Error in deletion of [C:\System Volume Information\001.dat] while pruning the target VHD: Error [0x80070020] The process cannot access the file because it is being used by another process.

In my case, what I have done is that I deleted all the files in the target folder of the backup, re-run the backup and it worked.

(211)

Fix: Exchange error 0x800ccc6c – Verify that the mailbox exists and that the Exchange receive connectors are configured properly

When having especially SBS 2008 with the POP3 Connector to retrieve mail from an outside mailbox to your internal Exchange server, you may encounter the below error in the Event Viewer.

An error occurred while delivering mail to ‘mailbox@mydomain.com’ on the SMTP server ‘localhost’. The error code was 0x800ccc6c. Verify that the mailbox exists and that the Exchange receive connectors are configured properly.

Thou the error message is misleading, this problem can happen if the POP3 Protocol Errors meet the tolerance of the Exchange SMTP Receive connectors. Exchange will close an SMTP connection after a certain number of protocol errors. The default is 5.

To solve the issue, in my case I had to in increase the value of “MaxProtocolErrors” for the Exchange SMTP Receive connectors from Exchange Management Shell by using the below command.

Set-ReceiveConnector -identify “Name of Connector” -MaxProtocolErrors 999

After this, I have restarted the POP3 Connector retrieval of messages and it worked.

(243)

Fix: Office 365 This user’s on-premises mailbox has not been migrated to Exchange Online when using dirsync

“This user’s on-premises mailbox has not been migrated to Exchange Online. The Exchange Online mailbox will be available once migration is completed”

This only happens for users that have been synced using DirSync as they are mail enabled with on premises exchange. I do not however want to migrate mailboxes and would like to start a fresh.

To fix this, one should exclude the attribute ‘msExchMailboxGuid‘ on the Azure Active Directory Connect Tool (DirSync).

-Disable Synchronization from the Office 365 Portal
-Delete all synched users (marked as cloud now)
-Remove these mailboxes from the Office 365 Recycle Bin
-Edit the MIIS so the MSExchangeMailboxGUID does not sync
-Enable Sync again

(296)

Fix Error 0x80041820 when searching through OWA

When searching through OWA you might end up with an error saying “The action couldn’t be completed. Try again later“, while users using Microsoft Outlook don’t have any issue.

You might also see the below errors in the event viewer

Log Name: Application
Source: MSExchangeIS Mailbox Store
Event ID: 9842
Task Category: Content Indexing
Level: Error
Description:
Function CISearch::EcGetRowsetAndAccessor detected that content indexing was disabled for database ‘‘ because of error ‘0x80041820’ from MSSearch.

Log Name: Application
Source: MSExchangeIS Mailbox Store
Event ID: 9877
Task Category: Content Indexing
Level: Error
Description:
Content Indexing function ‘CISearch::EcGetRowsetAndAccessor’ received an unusual and unexpected error code from MSSearch. Mailbox Database: Error Code: 0x80043629

This can be solved by doing the following steps

– Check the version of Exchange 2010 installed by running Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion (So, version 14.2 is SP2, 15.00 is SP3. If you are still using SP1 I strongly recommend to upgrade to at least SP2).
– Download the correct Service Pack and extract it.
– Run Setup /PrepareAD and Setup /PrepareSchema.
– After this is done restart the services Microsoft Exchange Search Indexer and Microsoft Exchange Information Store.

If this doesn’t work, use the following steps

– Download the script Repair-ExchangeSearchSymlinks.ps1 from the Script Center and copy it to C:\Program Files\Microsoft\Exchange Server\v14\Scripts
– Open Exchange Management Shell and browse to the above folder.
– Run the script with ./Repair-ExchangeSearchSymlinks.ps1
– After this is done restart the services Microsoft Exchange Search Indexer and Microsoft Exchange Information Store.

One last step if this doesn’t work is to reset the indexer and start indexing of the database by doing

– .\ResetSearchIndex.ps1 [-force] []…
– You will receive an Event ID 109 when the rebuilding of the index starts for each database and an Event ID 110 for each database when the index rebuild has completed.
– After receiving Event ID 110 for each database, test to make sure search functions correctly with both OWA and Outlook operating in Online Mode.

(212)

Fix: The backup set holds a backup of a database other than the existing

When restoring a database from an SQL backup .bak, one usually creates a database and then selects the restore function. As soon as you try to restore the database you get the error saying “The backup set holds a backup of a database other than the existing“. This is because it fails to read the files from the restore and matching them to the newly created files.

The error says:

Restore failed for Server ‘SQLSRV01’. (Microsoft.SqlServer.SmoExtended)
Additional Information
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The backup set hold a backup of a database other an the existing ‘test_restore’ database.
RESTORE DATABASE is terminating abnormally. (Microsoft SQL Server, Error: 3154)

To solve this one should do the following:

– Don’t create an empty database and restore the .bak file on to it.
– Use ‘Restore Database’ option accessible by right clicking the “Databases” branch of the SQL Server Management Studio and provide the database name while providing the source to restore.

This should allow you to restore the database with no error and fix the error 3154.

(490)

Fix: Hyper-V backup General access denied error (0x80070005)

When taking a backup using Windows Server Backup and during the backup you get an error as below

Writer Failures
Writer Id: {1072AE1C-E5A7-4EA1-9E4A-6F7964656570}
Instance Id: {017311EA-59CE-4B2E-830C-558BE6CEB39A}
Writer Name: Cluster Shared Volume
VSS Writer Writer State: 5
Failure Result: 80042336
Application Result: 80004005
Application Message: (null)
Component: BE389042-38BD-483E-9FD9-7E0F4CA466E466841cd4-6ded-4f4b-8f17-fd23f8ddc3de:c336e204-fbe8-46a4-a80d-faed6edafd94:SRVDCHVS02
Logical Path: (null)
Component Result: 800423F4 Component Message: Could not create backup checkpoint for virtual machine 'HYPDCORA01': General access denied error (0x80070005). (Virtual machine ID BE389042-38BD-483E-9FD9-7E0F4CA466E4) File Spec: C:\ClusterStorage\Volume1\virtual_machines\HYPDCORA01\Virtual Machines\\BE389042-38BD-483E-9FD9-7E0F4CA466E4.xml Recursive: 0 File Spec: C:\ClusterStorage\Volume1\virtual_machines\HYPDCORA01\Virtual Hard Disks\\HYPDCORA01.vhdx Recursive: 0 File Spec: C:\ClusterStorage\Volume2\\Oracle_Data.vhdx Recursive: 0 File Spec: C:\ClusterStorage\Volume1\virtual_machines\HYPDCORA01\Snapshots\\BE389042-38BD-483E-9FD9-7E0F4CA466E4-BackupSnapshot.xml Recursive: 0 File Spec: C:\ClusterStorage\Volume1\virtual_machines\HYPDCORA01\Virtual Hard Disks\\HYPDCORA01-ChildVhd.avhdx Recursive: 0 File Spec: C:\ClusterStorage\Volume2\\Oracle_Data-ChildVhd.avhdx Recursive: 0

After some research I found that it can be easily fixed. The issue occurs because most probably you have created a Shared volume and the VHDX file or Virtual Drive is in the root of the volume. To fix this, create a new folder called ‘Virtual Drives’ or whatever you wish and move the Virtual Drives onto that folder.

Restart the backup process and the issue will not occur

(456)