There are plenty of occasions when you will find that Microsoft Office 2016 applications may crash or cannot start. You hook up to the net to find a solution and there are many articles around such issues from Microsoft or others. However, every case is very different and there is no one rule to solve them. The same happened to us and we thought a discussion of such a particular case could be helpful to others since we did not find any ready reference for a quick remedy for the issue we faced.

When an application on your PC crashes, one of the possible codes you will see in the Event Viewer log is the Event ID 1000 application error. When this shows up, the program you’re using will unexpectedly close. Moreover, you won’t be able to launch it properly. If you start to notice that this error code has been occurring more frequently on your computer, then it is high time you addressed the problem.

In this article, we are going to tell you how to resolve the error code 1000 application crashes for OUTLOOK.EXE.

ISSUE

Recently a Microsoft security update caused an issue in Outlook 2016. Outlook crashes on opening after July Security Updates are pushed by Microsoft.

After update to Windows 10 Pro (64-bit) build number 19041.388, Outlook has been refusing to start up. All the other Office applications work without error. Only Outlook closes automatically every time it is started.

Users will notice an error message of ‘Event ID 1000’ in their Event Viewer log. This entry basically means that a specific application crashed due to unknown events. Along with the error code, you will also be given the file path of the application which crashed.

In this case, Outlook 2016 crashes almost immediately with the following message in Event Viewer:

Event ID 1000, Application Error

Faulting application name: OUTLOOK.EXE, version: 16.0.13001.20384, time stamp: 0x5f05e3bb

Faulting module name: OUTLOOK.EXE, version: 16.0.13001.20384, time stamp: 0x5f05e3bb

Exception code: 0xc0000005

Fault offset: 0x000000000015c52a

Faulting process id: 0xc2c

Faulting application start time: 0x01d65ad2b9b2e67a

Faulting application path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE

Faulting module path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE

Report Id: 55dc3cb1-8aed-446d-862f-4f19ef361174

Faulting package full name:

Faulting package-relative application ID:

SOLUTION

We tried following first with a hope to resolve the issue.

• Running Microsoft Support and Recovery Assistant tool yielded no result
• Tried office repair tool both offline, and then the online, without any result. Both reported that the problem had been fixed. But Outlook still refuses to open.

Finally we had to perform a rollback to fix it – who would think !

You may also like: Learn how to proactively identify and protect your sensitive information

OFFICE UPDATE ROLL BACK

Follow through the steps below to perform a roll back.

• Open cmd, run as administrator
• cd “\Program Files\Common Files\microsoft shared\ClickToRun”
• Run officec2rclient.exe /update user updatetoversion=16.0.6366.2062

• After checking the version of office, the screen appears as – 

• Outlook started working even if the office version didn’t downgrade.

You will of course go frantic if you suddenly find your Outlook is not working after you have done a legitimate update. And chances are you will be looking through the maze of different references available before you hit upon the one that works for you. Our bid is to help the users under the said circumstances and get back to feet quickly.

Connect with me in case you need help on such matters.

Download the Datasheet to learn more about Netwoven’s Information Protection and Compliance service.

Download the Solution Brief to learn how Netwoven’s solution proactively identifies and protects your sensitive data.

The post [Solved] Outlook 2016 crashes and returns event ID 1000 crash signatures after update to Windows 10 Pro appeared first on Netwoven.

This article describes the decommissioning of last exchange server and removing hybrid setup where most of the areas that needs to be considered are covered.

Step 1. Removing the hybrid configuration

Run “Remove-HybridConfiguration” PowerShell command in on-premise exchange server.

Using the PowerShell command is not actually the only process to remove all the object which created at the time of hybrid setup. Subsequently, some manual interventions are needed to clean up all associated objects.

Step 2. Manually remove the hybrid connectors

Before you go ahead to remove the connectors, double check that no other domains are used to relay mail between O365 and on-premises. Importantly your MX record must have already been cutover to Exchange online. If we are there are no dependencies, then remove these connectors as shown in  “Figure 1″

Figure 1: Removing inbound and outbound connectors created in hybrid setup.

Step 3. Manually remove organizational sharing

Now we should remove the organizational sharing rules for free/busy and calendar sharing between on-premises and O365. Since, this is an optional task but to make the tenant clean we should remove the all the settings which are no longer used as shown in “Figure 2”.

Figure 2: Removing organizational sharing.

You may also like: Build a Superior Enterprise Cloud with Microsoft

Step 4. Clean-up Mailbox database

Next, we must check, how many databases are mounted and are working or holding the mailboxes like system, Arbitration or Discovery mailboxes. Before removing the databases, we must clean and remove all the mailboxes residing in these databases or else we will not be able to remove it later.

Get-Mailboxdatabase : fl ebdfilepath (To check the location of databases)

An attempt to remove all mailbox databases without removing the residential mailboxes would lead to an error shown in “Figure 3”. This error is a failure notification stating that database contains the mailboxes which needs to be deleted before database removal.

Figure 3: The error during the removal of database containing mailboxes.

Once you have removed all mailboxes from the database, run the following power shell commands:

Get-Mailboxdatabase | Remove-mailboxdatabase

But, the default mailbox database won’t be deleted Since, the database has some system and arbitration mailboxes. Hence you must disable the arbitration mailbox before attempting to delete them.

Step 5. Disable Arbitration Mailbox

To check how many arbitration mailboxes are residing in the default database.

Get-Mailbox -Arbitration -Database <Database Name>

To disable all the arbitration mailboxes, execute the following command.

Get-Mailbox -Arbitration -Database <Database Name> | Disable-Mailbox -Arbitration -DisableLastArbitrationMailboxAllowed

Figure 4: Disabling all the arbitration mailboxes.

Step 6. Delete the default mailbox database.

Now the default mailbox database can be deleted using the following command:

Get-MailboxDatabase | Remove-MailboxDatabase

Figure 5: Removing database

A warning may appear because of replication failure in active directory topology though the process would complete flawlessly.

Step 7. Removing messages from queue.

It looks that we are almost done but not yet. We are just a step away from performing the last ritual of uninstalling the Exchange product from the server. The last piece is to remove all messages that may by lying in the queue. Run the following script to remove the:

Get-Message : Remove-Message

Figure 6: Removing the messages from queue.

Step 8. Uninstall Exchange Product

You can now start the product uninstallation from  “Add remove program” options in control panel.

Figure 7: Uninstalling exchange binary

Once it’s done then a reboot is required to complete the uninstallation process.

Hope you have enjoying reading through my post. Feel free to post question and any further clarity required.

The post Decommission Exchange Server 2013 appeared first on Netwoven.