{"id":2070,"date":"2018-06-14T11:20:08","date_gmt":"2018-06-14T09:20:08","guid":{"rendered":"https:\/\/msb365.abstergo.ch\/?p=2070"},"modified":"2018-08-15T23:09:00","modified_gmt":"2018-08-15T21:09:00","slug":"error-by-installing-exchange-cu-event-1002","status":"publish","type":"post","link":"https:\/\/www.msb365.blog\/?p=2070","title":{"rendered":"Error by installing Exchange CU (Event 1002)"},"content":{"rendered":"<p>Today I had to install new Exchange 2016 CU on a customer\u2019s exchange environment. Normally that is an easy going thing and I wouldn\u2019t write an article about that.<\/p>\n<p>However, by this customer I came across an installation problem during the update.<\/p>\n<p>&nbsp;<\/p>\n<p>I was running like always my pre setup steps for suspending the cluster:<\/p>\n<pre class=\"\">Suspend-ClusterNode \u2013Name EX2016SRV1<\/pre>\n<p>&nbsp;<\/p>\n<p>After that, I disabled the database copy activation using this cmdlet:<\/p>\n<pre class=\"\">Set-MailboxServer EX2016SRV1 \u2013DatabaseCopyActivationDisabledAndMoveNow $true<\/pre>\n<p>&nbsp;<\/p>\n<p>Then I blocked the activation Policy using the following command:<\/p>\n<pre class=\"\">Set-MailboxServer EX2016SRV1 \u2013DatabaseCopyAutoActivationPolicy Blocked<\/pre>\n<p>&nbsp;<\/p>\n<p>And last but not least I needed to set the Exchange server in Maintrance mode:<\/p>\n<pre class=\"\">Set-ServerComponentState EX2016SRV1 \u2013Component ServerWideOffline \u2013State InActive \u2013Requester Maintenance<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>Note:<\/strong> Don\u2019t forget to disable temporary the Anti Virus scanner and reboot the server before starting the setup.<\/p>\n<p>&nbsp;<\/p>\n<p>After these pre-setup tasks, I was ready to mount the ISO file and start the update using:<\/p>\n<pre class=\"\">setup \/m:upgrade \/IAcceptExchangeServerLicenseTerms<\/pre>\n<p>&nbsp;<\/p>\n<p>Good so far\u2026 Till here everything went fine and as expected. During the update Microsoft started working on the Mailbox roles. The Transport service and Client Access service had no problem and completed successfully. The same with the Language Files and Restoring Services.<\/p>\n<p>However, next task was about Unified Messaging service. Here I got after 90% the error below:<\/p>\n<p><img fetchpriority=\"high\" decoding=\"async\" class=\"alignnone size-full wp-image-2073\" src=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/1.png\" alt=\"\" width=\"1183\" height=\"611\" srcset=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/1.png 1183w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/1-300x155.png 300w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/1-768x397.png 768w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/1-1024x529.png 1024w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/1-600x310.png 600w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/1-780x403.png 780w\" sizes=\"(max-width: 1183px) 100vw, 1183px\" \/><\/p>\n<p>To understand the error, I opened the Event Viewer, for me personally it is a more easy way to read the error and to find the solution of the issue.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-2074\" src=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/2.png\" alt=\"\" width=\"1156\" height=\"808\" srcset=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/2.png 1156w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/2-300x210.png 300w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/2-768x537.png 768w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/2-1024x716.png 1024w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/2-600x419.png 600w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/2-780x545.png 780w\" sizes=\"(max-width: 1156px) 100vw, 1156px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Checking the error message I found an issue, which could be the reason for the unsuccessful setup. By taking a closer look, I found this:<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-2075\" src=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/2-1.png\" alt=\"\" width=\"464\" height=\"37\" srcset=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/2-1.png 464w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/2-1-300x24.png 300w\" sizes=\"(max-width: 464px) 100vw, 464px\" \/><\/p>\n<p>In my case that means, that by the installation of Exchange server 2016 the ISO file was mounted to the Drive Letter D:\\. After installing Exchange, the ISO was dismounted and the D:\\ Letter was used for the Mailbox databases.<\/p>\n<p>Now by installing the newest CU, the mounted ISO got the letter E:\\ and the uninstall of the old MSI was not possible, because the path of it doesn\u2019t exists anymore.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2076\" src=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/3.png\" alt=\"\" width=\"598\" height=\"343\" srcset=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/3.png 598w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/3-300x172.png 300w\" sizes=\"(max-width: 598px) 100vw, 598px\" \/><\/p>\n<p>After knowing this history, the solution in my case was easy. I have created on the D:\\ Partition a Folder called \u201cen\u201d (Note: the name can be different, it depended about your language settings) and copied the UMLanguagePack.en-US.msi from the ISO to the new folder.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2077\" src=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/4.png\" alt=\"\" width=\"381\" height=\"132\" srcset=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/4.png 381w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/4-300x104.png 300w\" sizes=\"(max-width: 381px) 100vw, 381px\" \/><\/p>\n<p>Now I restarted the setup and it went as expected without further errors to the end.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2078\" src=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/5.png\" alt=\"\" width=\"1247\" height=\"460\" srcset=\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/5.png 1247w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/5-300x111.png 300w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/5-768x283.png 768w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/5-1024x378.png 1024w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/5-600x221.png 600w, https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2018\/06\/5-780x288.png 780w\" sizes=\"(max-width: 1247px) 100vw, 1247px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>To finish the whole setup, there are now tree things left to do:<\/p>\n<ol>\n<li>Reactivate the Antivirus Software<\/li>\n<li>Reboot the Exchange server<\/li>\n<li>Disable the Maintenance:<\/li>\n<\/ol>\n<pre class=\"\">Set-ServerComponentState EX2016SRV1 \u2013Component ServerWideOffline \u2013State Active \u2013Requester Maintenance<\/pre>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Today I had to install new Exchange 2016 CU on a customer\u2019s exchange environment. Normally that is an easy going thing and I wouldn\u2019t write an article about that. However, by this customer I came across an installation problem during the update. &nbsp; I was running like always my pre setup steps for suspending the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2071,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[2,3],"tags":[],"class_list":["post-2070","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-exchange","category-powershell"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/2070","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2070"}],"version-history":[{"count":6,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/2070\/revisions"}],"predecessor-version":[{"id":2325,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/2070\/revisions\/2325"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/media\/2071"}],"wp:attachment":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2070"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2070"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2070"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}