Hi,
Missing dylib on startup (Mac OS X 10.13.6 - High Sierra). EXCCORPSENOTIFY Termination Reason: DYLD, 0x1 Library missing Application Specific Information: dyld. At once, we would like to suggest you please try to rebuild Outlook for Mac profile and see if the Outlook for Mac is opening or not. Quit all open Office programs on Mac (Outlook, Word, Excel, etc).
I am currently using 10.13 and Office 365 latest version. I am unable to launch outlook.
Apr 10, 2018 1 Responsible: Microsoft Outlook 2077 User ID: 501 Date/Time: 2018-04-08 16:03:39.930 +0100 OS Version: Mac OS X 10.13.4 (17E199) Report Version: 12 Anonymous UUID: CC771526-C309-CEC5-3B34-EB908FCC2C71 Time Awake Since Boot: 750 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXCCRASH (SIGABRT) Exception.
Process: Microsoft Outlook [610]
Path: /Applications/Microsoft Outlook.app/Contents/MacOS/Microsoft Outlook
Identifier: com.microsoft.Outlook
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Microsoft Outlook [610]
User ID: 903949055
Date/Time: 2017-10-11 14:28:00.982 +0530
OS Version: Mac OS X 10.13 (17A405)
Report Version: 12
Anonymous UUID: 7A104D50-7F16-A4A2-A105-5F468FF9F94E
Time Awake Since Boot: 110 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1
kernel messages:
VM Regions Near 0 (cr2):
-->
__TEXT 0000000108340000-000000010914c000 [ 14.0M] r-x/rwx SM=COW d []
Thread 0 Crashed:
0 0x000000010e07a19c _dyld_start + 0
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffee78bfc08
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x000000010e07a19c rfl: 0x0000000000000200 cr2: 0x0000000000000000
Logical CPU: 0
Error Code: 0x00000000
Trap Number: 0
Binary Images:
0x108340000 - 0x10914bfc7 + (0) <16FD3B0D-38ED-33DC-98E5-0CB414392CCE>
0x10e079000 - 0x10e0c398f + (519.2.1) <002B0442-3D59-3159-BA10-1C0A77859C6A>
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 954
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=18.9M resident=0K(0%) swapped_out_or_unallocated=18.9M(100%)
Writable regions: Total=8500K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8500K(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
STACK GUARD 56.0M 2
Stack 8192K 2
__DATA 3048K 5
__LINKEDIT 4872K 4
__TEXT 14.3M 3
shared memory 8K 3
TOTAL 86.1M 13
Model: MacBookPro11,1, BootROM MBP111.0142.B00, 2 processors, Intel Core i5, 2.6 GHz, 8 GB, SMC 2.16f68
Graphics: Intel Iris, Intel Iris, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x112), Broadcom BCM43xx 1.0 (7.77.37.0.1a1)
Bluetooth: Version 6.0.0f7, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0512F, 500.28 GB
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.2
Can someone let me know what can be done?
I have installed all updates for OS & Application already.
Thanks,
Sajesh
MacBook Pro (13-inch Mid 2012), macOS High Sierra (10.13)
Posted on Oct 11, 2017 2:16 AM
“Outlook stuck on verifying data” might be one of the unusual errors that you might encounter on your Outlook application. You might experience this either while closing the Outlook application or while launching based on the cause of the error. Since the error is due to various reasons there is no specific method to fix this error. However, you can fix it based on the scenario you have encountered. With minute detailing this article will guide you to fix when Outlook stuck on verifying data integrity, by helping you figure out the scenario.
Why is Outlook Stuck in Verifying Data Integrity?
Comparatively, “verifying data integrity” error is familiar to Outlook 2010 version and not so common on other versions. Frankly, there are various reasons for this error, the following are the most common reasons.
- Oversized OST file
- Abrupt Outlook termination
- Malfunctioning of Add-ins
- Corrupted Outlook data file
Since this error is mainly associated with an OST file it is suggested to set a backup of the OST file even before trying to fix the error. This backup of your Outlook data can be used when you tend to damage the OST file while trying to fix the errors. The best possible method for you to set backup of the OST file is through Remo Outlook Backup and Migrate. A holistic tool that is developed to Backup, Migrate and Restore Outlook data files. Download and install the Remo Outlook Backup and Migrate to launch the application. Select a smart scan and follow the instructions which will be mentioned clearly to set a backup. it is also completely free to set the backup so click on the download button right now..!
Once you have set a backup now let’s figure out how to fix the error by disabling the verifying data integrity on Outlook. First let’s focus if you have come across the error while closing the Outlook application or while using the Outlook.
Fix Stuck in Verifying Data Integrity Outlook 2010, 2013, 2016
If your Outlook is stuck at verifying data while using or quitting the application, it is most probably due to damaged or malfunctioning add-ins. If add-ins are not the cause then it could be the result of an unstable internet connection.
In either case, the easy way out is to force quit the Outlook application using the task manager. It is recommended that you do not try abrupt Outlook termination by any other means as it directly affects the integrity of the Outlook data file OST. Outlook termination using task manager might act as an instant fix but not a permanent one, here are the steps:
Note: If you don’t have any add-ins installed or if your Outlook is stuck at verifying data while launching the Outlook application, you can completely skip this process.
- Press Ctrl+Alt+Del or right click on the taskbar and select Task Manager
- From the listed applications, select Outlook and click on End Task to force quit Outlook application.
Now open the Outlook application and see whether the error is fixed or not. You might also experience the error before closing due to malfunctioning Outlook Add-ins.
How to Fix Outlook Stuck in Verifying Data Integrity due to Faulty Add-ins.
If Outlook is stuck on verifying data integrity due to malfunctioning Add-ins, you will observe that Outlook does not close until all the Outlook related processes are terminated. To do that you need to force quit all the running Outlook related processes. The following are the steps to force quit running Outlook processes.
Microsoft Outlook Termination Reason: Dyld 0x1 Library Missing Free
- Launch Task Manager, click on more details to reveal all the background running processes
- Scroll through the listed running programs, manually identify the running Outlook processes, select them, and click on the end task.
Relaunch the Outlook application in safe mode. In safe mode, Outlook runs only on basic essential firmware and blocks all the third party related add-ins. If Outlook application runs seamlessly in safe mode, it indicates that the third-party add-ins or plug-ins are responsible. Although painstaking you can disable each of the add-ins one by one in normal mode. Repeat this process until you find the add-in causing the error.
Forced quitting Outlook as mentioned above can also take a wrong turn and damage your Outlook data file. Safeguard your data by taking a backup of the OST file before any sort of troubleshooting. In just a few clicks, Remo automates finding the OST file, extracting all data stored on the OST file, and lastly creating a backup PST file.
Outlook Stuck in Verifying Data Integrity due to Large OST file
Microsoft Outlook Termination Reason: Dyld 0x1 Library Missing Page
If you are not aware, OST file functions on the principle of synchronization. the file gives your Outlook some time to sync and wait until the process is completed.
In most cases, it should not take you more than 30 minutes to sync with respect to the size of the OST file. After synchronizing completely, your Outlook application must work normally. If a large OST file is causing the error, you better shrink the large OST file. If your Outlook is still stuck in verifying data integrity, it must be due to damages in the OST file or incorrectly terminated Outlook application.
Generally, problems associated with abrupt termination can be fixed by opening Outlook in safe mode. The following are the steps to open Outlook in safe mode.
- Tap crtl+r to open the run dialogue box. In the run dialogue box type, “outlook /safe” and press enter.
If you have never unethically terminated your Outlook application, then the error is due to a damaged OST file.
How to Fix Outlook Stuck in Verifying Data Integrity due to Damaged OST File
The best possible solution for you in case of a damaged OST file is to convert it to PST file. Post converting to create a PST backup, uninstall and reinstall the Outlook application. Now import the PST backup file on to the reinstalled Outlook application. There are two possible ways to create a backup file.
- Set a PST file backup using export and import wizard (manual and complex)
- Convert OST file to PST using Remo OST to PST converter (Streamlined and secure)
Microsoft Outlook Termination Reason: Dyld 0x1 Library Missing File
However, manually recovering OST to PST is complex and time-consuming. Additionally, the file structure will not be the same if you manually export the OST data. so the most efficient way to backup the OST data is by using Remo OST to PST converter.
Ensure Data Integrity by converting Outlook OST to PST
Since Remo streamlines the entire conversion process it is simple to use. following are the steps to convert OST to PST using Remo OST to PST converter
- If you know the exact location of an OST file click on the Open OST file and select the file. If you are certain about the location click on Find OST file and leave it to the tool to search.
- From the next screen click on find to locate the OST file and wait for the tool to locate the OST file. after locating the OST file, select the OST file and click on next.
- Select the browse option and set a destination folder to save the PST file and click on Convert. It’s that simple, no need to select attributes manually; additionally, the tool is going to retain the exact folder structure which might not be possible if you manually export the PST file.
Microsoft Outlook Termination Reason: Dyld 0x1 Library Missing Word
Steps to Fix the Outlook stuck in verifying Data integrity due to Damaged OST file
In the case of Damaged OST file then Outlook might refuse to sync the OST file with the online server resulting in the error. To fix the error you need to create a backup of the OST file by converting the OST file to PST. Using Remo will evade the errors in the OST file and create an error-free PST file. You can follow the steps mentioned in the previous section to convert OST to PST using Remo.
Microsoft Outlook Termination Reason: Dyld 0x1 Library Missing Email
Once you have converted and taken the backup of the OST file now you can uninstall the Outlook application and reinstall it. Export the Outlook attributes from the error-free PST file and sync it with the Online server. Since it is a newly created backup file and Outlook is reinstalled there should not be any scope for verifying data integrity error in Outlook.