Strange Exchange 2010 issues

Dear Exchange experts,
I am having a very strange Exchange issue. Here is a little background information. On Sunday We needed to restore an older database from our backups. After successful restore i opened the database with a third party Quest software. I had to installed Outlook (MAPI) for the software to run. We restore emails that we needed to.
On Monday several users complained that on Sunday they were getting prompted for password while working from home and Outlook would not accept password, but OWA did. When in the office, Outlook works fine.
On Tuesday i arrive to the office and i get an error message while launching Outlook saying that my mailbox was moved and i had an option use temporary mailbox or offline version. The only way to fix this was to delete the profile. Which i did.
Throughout the day i sent bunch of emails and never got responses to. Towards the end of the evening i confirmed with one user that my email from an hour ago didn't go through, when i resent it, it went through right away.
I get home, open my outlook and all mail in inbox is missing except Brand new bounce back emails from the entire day. I log into my OWA and all of my mail is there, but the bounce back emails are not. Below is an example of two bounce back emails.  Any suggestions how to start troubleshooting this issue?

We are using Exchange 2010, not 365.



From: Microsoft Outlook
Sent: Tuesday, March 13, 2018 9:33 AM
To: User1
Subject: Undeliverable: RE: Sick Today
 

Your message couldn't be delivered to multiple recipients.
The recipients weren't found at the destination domains.
user1      Office 365      Recipients
Action Required            Recipients
                             

Unknown To address            

Couldn't deliver to the following recipients:
user2@domain2.com, user3@domain1.com, User4@domain2.com

 
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:
•        Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
•        Contact the recipient (by phone, for example) to check that the address exists and is correct.
•        The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
•        Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365, and then send the message again. Retype the entire recipient address before selectingSend.
If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Adminssection below.


Was this helpful? Send feedback to Microsoft.

________________________________________

More Info for Email Admins
Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:

The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.

Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.

For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365.

Original Message Details
Created Date:      3/13/2018 1:33:00 PM
Sender Address:      user1@domain1.com

Recipient Address:      user2@domain2.com, user3@domain1.com, . . .

Subject:      RE: Sick Today


Error Details
Reported error:      550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipientuser2@domain2.com not found by SMTP address lookup
DSN generated by:      BLUPR17MB0020.namprd17.prod.outlook.com


 
Message Hops
HOP      TIME (UTC)      FROM      TO      WITH      RELAY TIME
1      3/13/2018
1:33:00 PM      BLUPR17MB0452.namprd17.prod.outlook.com
BLUPR17MB0452.namprd17.prod.outlook.com
mapi      *
2      3/13/2018
1:33:02 PM      BLUPR17MB0452.namprd17.prod.outlook.com
BLUPR17MB0020.namprd17.prod.outlook.com
Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256)      2 sec
Original Message Headers
Authentication-Results: domain2.com; dkim=none (message not signed)
 header.d=none;domain2.com; dmarc=none action=none
 header.from=domain1.com;
Received: from BLUPR17MB0452.namprd17.prod.outlook.com (10.164.17.30) by
 BLUPR17MB0020.namprd17.prod.outlook.com (10.160.190.142) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id
 15.20.548.13; Tue, 13 Mar 2018 13:33:02 +0000
Received: from BLUPR17MB0452.namprd17.prod.outlook.com
 ([fe80::4b8:a916:6a8d:a1c6]) by BLUPR17MB0452.namprd17.prod.outlook.com
 ([fe80::4b8:a916:6a8d:a1c6%14]) with mapi id 15.20.0588.013; Tue, 13 Mar 2018
 13:33:00 +0000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Oleg Gudym <user1@domain1.com>
To: Andy Michalski <user2@domain2.com>
CC: Marcelo Motta <User3@domain1.com>, Andrea Zeman
        <user3@domain1.com>, "Albina, Ballali" <User4@domain2.com>
Subject: RE: Sick Today
Thread-Topic: Sick Today
Thread-Index: AdO6z2ytoQGFhNKsRDWMz/7Af6Wb0gAACL0Q
Date: Tue, 13 Mar 2018 13:33:00 +0000
Message-ID: <BLUPR17MB0452F604E17852A7236E30BBBAD20@BLUPR17MB0452.namprd17.prod.outlook.com>
References: <A929E6263B1A654D8B9403EAA8EFA28BFE68CFB6@vSRV06.cac.local>
In-Reply-To: <A929E6263B1A654D8B9403EAA8EFA28BFE68CFB6@vSRV06.cac.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <BLUPR17MB0452F604E17852A7236E30BBBAD20@BLUPR17MB0452.namprd17.prod.outlook.com>
MIME-Version: 1.0
X-Originating-IP: [50.193.154.113]
X-MS-PublicTrafficType: Email
X-Microsoft-Exchange-Diagnostics: 1;BLUPR17MB0452;35:EZrcuybtZgH35qmKwTH/MH07cc2IEZKQQfWgqthnTDzTz/wAo7Pgrq9QTfnf+mexwNJtXqCO4nMpPJqVnbQGlQ==
X-MS-Exchange-Antispam-SRFA-Diagnostics: SSOS;SSOR;
X-Forefront-Antispam-Report:
        SFV:SKI;SCL:-1;SFV:SKI;SFS:;DIR:INB;SFP:;SCL:-1;SRVR:BLUPR17MB0020;H:BLUPR17MB0452.namprd17.prod.outlook.com;FPR:;SPF:None;LANG:en;
Return-Path: user1@domain1.com
X-MS-Office365-Filtering-Correlation-Id: fe361bdf-d431-4fa7-465c-08d588e6f0ed
X-Microsoft-Antispam:
 UriScan:;BCL:0;PCL:0;RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(2017052603328)(7153060)(7193020);SRVR:BLUPR17MB0020;
X-Microsoft-Exchange-Diagnostics:
 1;BLUPR17MB0020;3:9PDA1dlYxzrVzTmfItOVNjm785ch3C+F71gOke2CMXKXsymg8grAsUafIM1H4zDKz3+lNp09D7/Bg53GNOfEslMlnCqN0qawLyCCg5BiqE4QXMWNjqf0/YS/aKrlzXa7i+wodqRcMHWVGG8uzTCpSzvINtwerxJnniGm/UvxmuLGhk6AAPFPQiQNU4HCK8tyT6zLMDaoNBYj+083CIPvL8yVWO2zpukrWWMAg0ChncQoUbtvy3d+zgi+nyb9n6rL;25:uzQU2ruCIdKrRFjE8xfFiE1tDDFC7GXGYnCkDEXtVb6vgxPrXnflDLV6JJFzw4JKaWVcq3JCZgdqooNTwlZat43cG0DNGx1GhBm9tggL3hd/KurmzN2Q3jXWODjLUgZKjYchgEANhIr662bXRCJrOQErQUEoX9htXL7b0TYY1/ZKZCpk4uUH2seQnfbI17HK1aLvYEHNGU/a/h8UDZxANByAn75dKbM7s4nlFkcRkVRat+cDRkgBjMmCebI9ZDqUCRqXBNsz6diIjez1qHAooNQeKgmHi8VVVQk9UhEeE0Z4r8HNXLjXpUzsAWg9Yjf5FbPNMAplt/ZfOTvH4WlVsw==;31:eLqzvrr31MgzBTC+qUYNnJ2WYNo2dQ0eSsV6oepP4AtwgtQ4J/3bOiahonYTbMAXtjgmUAWAnt40gYMnL/TGJ8I6b4jhVY7UP9iNRaZ6nsNlDi1OS6D5Jn4Fz40ptCmLrXY10YxHchgLCD2MkbZYRmbobkolNul1smdSnJ9gTJx5Vf7rFvUgrMsM73VgZRloWOwoOK6FBfGLZh8CKNkOy1NZf1JF5435f83X7FeFOss=
X-MS-TrafficTypeDiagnostic: BLUPR17MB0020:
X-Exchange-Antispam-Report-Test: UriScan:(28532068793085)(21748063052155);
X-Exchange-Antispam-Report-CFA-Test:
 BCL:0;PCL:0;RULEID:(9101524173)(2401047)(8121501046)(3002001)(93006095)(93001095)(10201501046)(3231221)(944501244)(52105095)(201708071742011);SRVR:BLUPR17MB0020;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0020;
X-Microsoft-Exchange-Diagnostics:
 1;BLUPR17MB0020;4:ZM46gBFfXuiL4QbfLPT660FN17UA4E37NrGu2JeKm6dVI8YkkhmpKeEs3zvPlHImWnADAaffl9WNI7bW4dh85A4bdnhmDiMbCSMjvMWAyIvvCmjX7fQgo/VXCcjMQw4soTmDkftL50LNm75WqYFrJX4SDFdMHry3PXUfS0wwLheK6WJ7aKAStfpcAOXgyP4BrVOF4U7Av2LHlRBvnmuCIuclMtBd8Q2V9FvcEtOEgbhiwDsaV7JWbgmWUqsQKOsHsRQXernk1loq/cAQNncjzBo3m2FT/E2TqSi3aWRg8G7R1NDpbh41t2YHGOHKrONAMehDdo7djQ3uNIrKri8MaJmfh0slgfV85kcdba4YUOU=;23:d3YUjmKvd+6db1bF0pYJSajIgk0f1zYy5P2y4wHriV7bzMhqQJTWbSNptHu9IImI7B7DNvLlYq7OBz4ekeW7qoZ9m2/ZDstU0PfmriyXqdl0fAd+Z+wTxQn2gn8uVinK;6:IuRzLDAlPjneUztWoA43HiMA7CdJCBpp7Z6EPkc2LcZo08BzVOvg4X4zVtXSMaUuZahIBiJ1A8K6Ei05Us33AZgESZIljmiQw4O6XbbfN7tLgiIFn7rnYXjB/mKUtdNJRdMI7FX5ii83MAK1+Ru2thngTdn48jeur9z21wte4Mq93R6tT0M2qpgqpIk02gNl3ZZ9nEVZ/tjXx3MW1lO85JMDi5mGuPI+3vdQjI4FcdN0K8FzWj3OGsP2Q1NqjIQzjWfLVx8AuZqLqU7PnbLLfmRPfyqBFgITgnTTbSYNowrjNMm4fT9FsgUV5tWF/IVoBnt9g1UrSruQvMIYaRmbhRx8a4xtC2m3yzCq9S3leGPU+1tL7ppjjhnZzci+KwSJ
X-Microsoft-Antispam-Message-Info:
 cnPkLzAX6I2EmTSKHnfaojRsHHTbovSjK+UMwG/BiaJzs1VPpf6mej7t8sHlxbj/aeRAqH9VxvBK+nxTSFHJazQ4eLrzIhQvXeYfjQXDOWW4QLfDAE8thvh4LaiwQohWGZeIYBZ7nmCjAfuJcKw2Bv6WDN0dBA8f08sG084rA/ONzt1gQzy5wYDUfN/SqGmfAvM0NPvpzAdGKtKamqWFsqvH5Mf7hQqUkLPGWJHfGcKjDRsEIgu/eqRU4YkFAi/Wk9r34N6V17zeh/HeennjflhDFB443U8aIeAVY3K+PvadG9vpo04UTKbxnYt600KSjlhqy5Fj4oP6L5UPz1TQiQ==
X-Microsoft-Exchange-Diagnostics:
 1;BLUPR17MB0020;5:2ymu6BhBn+yHFjMrSxyneAhEdN/5SE+j3K2DMpqnpluI0+2w3H5izuxQVFd2jS5Ha+giHSrl1P9vWtgNbtBzmDa5MpVORGvby1P/4fFkQxktVyDAprC8FghqQftb+hPLRtTqHKk+y5XCoNBmbaTBIfog2skM1xT0c7wzBX6YMYo=;24:rM4t8CR+RDL3Oa1UGIq8xPZSyg9gfVntmOL2YsBjfSf/csPiyNuq4G/P/mjDyCFxPoT4veKM+sOtJ/yaIL35G/0Wep4JTHDZmLgvEteq2P0=;7:Z6LWNaJCZKEV9FUcmFo8SDwQdnyoX3hjp7FlXbURoTeLmMqo0vLKy3YGM0EVd4LD1UqmyITjOZji9ZVYLsRV3f00qxyxnEWokXgzkyfBBTHrN0RKjKj3+FUnUYCUMRJ4GHs+mTX9oscH0LTbcsFX7+572GVrIZwbkCcLT2AhWp63cvyp3Rcjye/7qD8O4b9LhZGM+TB+lC3I1KGJUvXELe/EbppOEJlN5BlCxVg7uxqvte9hRGLO2mo2Zj17e2yB
SpamDiagnosticOutput: 1:0
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Mar 2018 13:33:00.8418
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: ea681ba6-a990-4040-8c61-18addcbded7e
X-MS-Exchange-CrossTenant-Network-Message-Id: fe361bdf-d431-4fa7-465c-08d588e6f0ed
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0020

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
From: Microsoft Outlook
Sent: Monday, March 12, 2018 3:57 PM
To: User1
Subject: Undeliverable:
 

Your message to user2@domain2.com couldn't be delivered.

user2 wasn't found at domain2.com.

user1      Office 365      user2
Action Required            Recipient
                             

Unknown To address            

 
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:
•        Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
•        Contact the recipient (by phone, for example) to check that the address exists and is correct.
•        The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
•        Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365, and then send the message again. Retype the entire recipient address before selectingSend.
If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Adminssection below.


Was this helpful? Send feedback to Microsoft.

________________________________________

More Info for Email Admins
Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:

The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.

Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.

For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365.

Original Message Details
Created Date:      3/12/2018 7:57:01 PM
Sender Address:      user1@domain1.com

Recipient Address:      user2@domain2.com

Subject:      MirrorCast in the conference room


Error Details
Reported error:      550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipientuser2@domain2.com not found by SMTP address lookup
DSN generated by:      BLUPR17MB0434.namprd17.prod.outlook.com


 
Message Hops
HOP      TIME (UTC)      FROM      TO      WITH      RELAY TIME
1      3/12/2018
7:57:02 PM      BLUPR17MB0452.namprd17.prod.outlook.com
BLUPR17MB0452.namprd17.prod.outlook.com
mapi      1 sec
2      3/12/2018
7:57:02 PM      BLUPR17MB0452.namprd17.prod.outlook.com
BLUPR17MB0434.namprd17.prod.outlook.com
Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256)      *
Original Message Headers
Authentication-Results: domain1.com; dkim=none (message not signed)
 header.d=none;domain1.com; dmarc=none action=none
 header.from=domain1.com;
Received: from BLUPR17MB0452.namprd17.prod.outlook.com (10.164.17.30) by
 BLUPR17MB0434.namprd17.prod.outlook.com (10.164.17.24) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id
 15.20.567.14; Mon, 12 Mar 2018 19:57:02 +0000
Received: from BLUPR17MB0452.namprd17.prod.outlook.com
 ([fe80::4cc4:75f5:93d0:2564]) by BLUPR17MB0452.namprd17.prod.outlook.com
 ([fe80::4cc4:75f5:93d0:2564%14]) with mapi id 15.20.0548.021; Mon, 12 Mar
 2018 19:57:02 +0000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Oleg Gudym <user1@domain1.com>
To: Nate Carpenter <user3@domain1.com>, Adam Norris
        <user4@domain1.com>
CC: Andy Michalski <user2@domain2.com>, Marcelo Motta
        <User3@domain1.com>
Subject: MirrorCast in the conference room
Thread-Topic: MirrorCast in the conference room
Thread-Index: AdO6O18iDIiHzuv4QMWajyKvCiKw3A==
Date: Mon, 12 Mar 2018 19:57:01 +0000
Message-ID: <BLUPR17MB045228556BF4306A43F6C725BAD30@BLUPR17MB0452.namprd17.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <BLUPR17MB045228556BF4306A43F6C725BAD30@BLUPR17MB0452.namprd17.prod.outlook.com>
MIME-Version: 1.0
X-Originating-IP: [50.193.154.113]
X-MS-PublicTrafficType: Email
X-Microsoft-Exchange-Diagnostics: 1;BLUPR17MB0452;35:hhtC++IRC94zxkQS0D9XkGJ7Bdgdoyf5aGkJ2l/sBcVrDm5DpQENisDgO10ovjzCD7xYOzkkC0WjV3PVoApa8A==
X-MS-Exchange-Antispam-SRFA-Diagnostics: SSOS;SSOR;
Return-Path: user1@domain1.com
X-MS-Office365-Filtering-Correlation-Id: a1f3d243-20de-48be-bb6f-08d588536c1c
X-Microsoft-Antispam:
 UriScan:;BCL:0;PCL:0;RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(2017052603328)(7153060)(49563074)(7193020);SRVR:BLUPR17MB0434;
X-Microsoft-Exchange-Diagnostics:
 1;BLUPR17MB0434;3:nDvznln28AV6w/frORdn8TbKhEfOR4mONJkgmpGjQBkoN8v6ttRe3K+bT/DQnfjnz836sR/Ap7hJHUHNVaMCqqKA/w/2eQuhhtYtTEH9Tj0wyBSr7jyoj7nS6fPoSaYo6rRlfbVEHWs6fWbJ11Eu3w0DVCzcGMcisRDjZZyz4nnwYT9aQ9gdZD1FGMy4SiVq2RQN3BIXpjO/ppQOaRz/2wX2hdxsizI9IKDtbj1drWKc0RIVuoIUnsSAVGy6+L2X;25:cdii5McHbRxU+tBFOk4yTQ6wbfz0AfkbuMkyET0m5Xye7MhBw4kO2LQ32ih9SI9bH6st/J85UM6WYbdnO/4hfZQ87e14usXJdk76M8OyVUk7IS37gkGHczdJTB3iRUaa3JCsLoGDxAdvTtgPih3dUEKr8+c5YpsKcsdLVgcwGZodNC3FwttQXNCnsbh03WvhcpjPTuI2k1gL93KJ8mQMdLq9ryosIJq04Nms7N4paxM7GU3dq9VTDjBmQKDJPErsS143l7SHEgWq7i3yNExEOjW1uer+j8Y05pAc2tXORANBBnuyPp57BIDE0agkLuP9fWb0ynu4xzP1aDWwsESrbA==;31:ZVrVnGiILcOqsQTs7blHHLbld7poWhG0zTdNv4DzP4dBQHgw3Ilg+BNSHTtBDN/AmcdJwkQJ93akWWjjv3gKF9i5aL9r+SfbHhhnweXhu74pAAGqBt2vM0p6elDaG7CA1HrRKUKAEP7HntSzw8Zs3QbPG7JYnJ3cQ+dBiDtVeMXIPs+BaPpEcgzSAIMlP55AY074tqWnsEz6sJjm/0VYIslC1rE6b/65kRLpKAoNMq8=
X-MS-TrafficTypeDiagnostic: BLUPR17MB0434:
X-Exchange-Antispam-Report-Test:
        UriScan:(28532068793085)(209352067349851)(21748063052155)(21532816269658);
X-Exchange-Antispam-Report-CFA-Test:
 BCL:0;PCL:0;RULEID:(102415395)(9101524173)(2401047)(8121501046)(93006095)(93001095)(3002001)(3231220)(944501244)(52105095)(10201501046)(201708071742011);SRVR:BLUPR17MB0434;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0434;
X-Microsoft-Exchange-Diagnostics:
 1;BLUPR17MB0434;4:0lp4a5On/hUaqipawX3u7X/QGmJnb5VJzwApBw17wDyOqKZYzY+0eXrptREmkXGJEZ+0O7sie3I5XWOw0qmYMY5LpQCh/HqAqRQ8c5D5nN8GKfgffjdbvZnwcEGOSmsoreRb8ZhpaS5B+k98HHgf3jXFegGvhTEvAlcjwhGuGFFXNvWt7rmahc1+CRr269svbCprwNaKP+gnURqeAhHDJBzR3e5LxwfubEkdotrSPUKjZcFklTBphlmXlszKGwrJSsFU6xJCLgsUeQS8DfPHP2iaSVWyT1nwEWGb4xmL6MSXP3j4af9rzcU4IU+uSYkkfT/xet81WuxVL5nwqsFr+HUPM69gDPlJX07I8Q+q1BOx3+zQbYoKzocNudn5rM77ufZIaiCxa7NjlYdI6Y7fbSGN3gd9YnBdP/594ePMk98=;23:mZ+jUrSeoKKwbviNFvRb2QrTGS2Q3dILHwV5xAPL/xML3rN8EuB531ufPSIlZAl2khDvpblRP0lEx3o0SscO5JodzppoXt5UpLz6+7f0nTEFR9VXe591f3D7j95B3ij2
X-Forefront-Antispam-Report:
        SFV:SKI;SFS:;DIR:INB;SFP:;SCL:-1;SRVR:BLUPR17MB0434;H:BLUPR17MB0452.namprd17.prod.outlook.com;FPR:;SPF:None;LANG:en;
X-Microsoft-Antispam-Message-Info:
 cHiIEjdXoNBRXlp03lJtMC87VYSzySs6D7s9zfWB9aoWfTf2sEZXX6HwSKFGTtQ+3rc7Hx+Xy8K3u4gNxbogG2B3AIIX8Iv0zhEStQ2CtaNzGwXNIs0NE62GjwVu253N1ySTZzz+7Nsr5GpG9AlFawtuvVkE+N1h+7aJhVOfx6m3mb4Qa5QHNH8lbNCyuBCroNTGGTY1QJR3bFcXlwTE3bomydeGmHUm8JzaSSbp0vm28VkjOc5BZVUpZ4k+aZMl6wtlQtvH5eeq5UvEhmP3Fne0N1ChuQ1HpnWsGeiCOfpcxTmUUa2kqCchOpnCMtT7tzFuLF/BeRoanU6C/P6OkA==
X-Microsoft-Exchange-Diagnostics:
 1;BLUPR17MB0434;6:XodiOqYJXN5Y1Wi0rFzNii37xU9tkXyCAMp7fgM/iPfYOvLfBN92MmQ5kQT6j5ujnS4J5AGg3xdpdOcfhcKpcYYb9gOKExCQYOhv96MUTOhi1bjm40cgFihUTb0UQ+lR6bmQDZuRIYCugnDy80586tqtHRaYLHJc30CjdFkiwqWlaYDYInu8LOJ9Y9zuRTE+UUsiVpgPkSo89k24iprYdRc1sTcefh2nDlsbdvutURdfjdHg3lC2L448VSt9wdOr0k9Iqwsg6KBnlfSbDxzcHbDBUYKUYw6zFIcp0Kpo06ccVRIl9zZmRUo6tKSZ7hxWGlIB4GStcCEAb7Z8V4ScYjdaakZlVa6X3hTiMjdZaSg/ETpMdv0FjsgGH3Uru4OMV/PKTLiKECNBwBlrW12mNQ==;5:5WJpoFJI+aEGdPzEI4lbPABnLkwiNHsOPP4h3UJx0wrpWAX7caB9+EcpA7m6hMvLmoSMutBOsrdBqBuAnUkfe9LopIs/L9gWi45mj04pJ9riE2bnimR9Hn0njxr5cmtwdOu7K0eDIs/T7RukeiQnz0u35wVrVHmuFYTLsxrMtj4=;24:gljOp4BJQqH7LhUeWVOaCoMLdW13wvsvYs8EUVqS29+JwpsamAsLPLFNyr82WvcaQwktrXQXi3PndYmuwIp7buvcexb98+qpkl6lDOOIIfc=
SpamDiagnosticOutput: 1:0
X-Microsoft-Exchange-Diagnostics:
 1;BLUPR17MB0434;7:pyUVApNCBtCQDDA9J8ACgR1XixUaXcrrAU+Cu562BRfemipKVgHWkJjQFgMimFsWpQPTdLBEdHSlbEVvpTiY20H4/wrnGsOXSbDBU/TCYNHvZJtnvAqMrNLGZoVFbSp0Z3PxAPm+mSwjfXyEFV+8pExr/NVZuzEXGtQqGyWJJmeuRFBxOcYtR54m7YhTcYj+xFyUfZQEHU2yJyGqFgAuGq6zFuLtzNcJ0tNEJszfUSXMCcSmqSc7nncIaUTA1yDN
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Mar 2018 19:57:01.7622
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: ea681ba6-a990-4040-8c61-18addcbded7e
X-MS-Exchange-CrossTenant-Network-Message-Id: a1f3d243-20de-48be-bb6f-08d588536c1c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0434
O GChief Technology Officer, Co-FounderAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jose Gabriel Ortega CEE Solution Guide - CEO Faru Bonon ITCommented:
I have a question.

When you did the restore of the database, you did it in a productive environment?

if the answer is yes, what you did was to mess up the links of the users with their database (because it is duplicated reference to the same user).

if the answer is no, you can just unmount the old database and check the messages on event viewer on the server
0
O GChief Technology Officer, Co-FounderAuthor Commented:
Jose,
Yes, but the restore was not through exchange server. Restore was through a third part application to a completely different volume on the server. So basically i restored a database from 2015, opened it with a third party app and restored a single mailbox to a PST file. I did try ti create a new recovery database and point it to the restored DB, but received an error and didn't move forward. What do you think?
0
Jose Gabriel Ortega CEE Solution Guide - CEO Faru Bonon ITCommented:
My point is that it was restored to the same server.
if you just took the "EDB" file restored, it shouldn't be that one the issue.

Because the EDB file that you restored is out of the exchange server infrastructure.

My point in here, do you know if only this 3rd party software wrote the EDB, or if it wrote the EDB file and mount it to exchange server.

Review in your exchange server ECP, what is the databases that are mounted right now.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

O GChief Technology Officer, Co-FounderAuthor Commented:
It did not mount the database on the Exchange. I also know that Rapid Recovery didn't mess with Exchange because i worked at Dell on backup and recovery team and we used this software to Exchange restores. Basically what it does just opens unmounted database and you're able to drill down to a single mailbox and restore a PST.
0
AlanConsultantCommented:
Hi,

For what its worth, my experience is that almost all third-party software is a bad idea on an Exchange Server - most of it is snake-oil, and the stuff that isn't still causes problems far too often.  I strongly advise clients never to let anyone install or run anything except Microsoft apps on an Exchange Server.

However, that is too late for that now, so we need to find a way to get it working again.

My suggestion would be to backup your Exchange Server (starting with a VHD backup and / or a bit level image, as appropriate, would be good), plus separately Exchange and in particular, the EDB, then restore a backup from before you ran the third party software, then bring the EDB back up to date using the backup.

I would regard this Exchange Server as being borked right now.


Alan.
0
O GChief Technology Officer, Co-FounderAuthor Commented:
@Alen - Suggesting Exchange server is broken without more details is a bit extreme. Exchange server working fine without any issues.

What ended up happening is this client has Office 365 Business premium subscription. Office 365 Business plan comes with Online Exchange.  My AD and Office 365 password was the same.  For some reason Outlook connected to Office 365 Exchange instead of our in house Exchange server. I opened a support ticket with MS, they are still trying to figure out why this happened. Same issue happened to another user in our organization, right after his AD password expired and he changed it to whatever his Office 365 password was.  Has anyone experienced this issue before?
0
AlanConsultantCommented:
HI OG,

You made this statement in your original post:

After successful restore i opened the database with a third party Quest software

For me, having Quest installed on an Exchange Server would be sufficient for me to be wary of that server from there on, and if I experienced any issues, I would wipe it and restore from a backup prior to the third party software being run on it.

You experienced such issues, hence my suggestion.

As I said before, I strongly advise clients never to let anyone install or run anything except Microsoft apps on an Exchange Server.


However, it is completely your call of course.

Alan.
0
AlanConsultantCommented:
Options for resolving given.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
authenticaion

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.