Showing results for 
Search instead for 
Do you mean 

Crashing while syncing with Outlook 2016 may be related to an update that Microsoft recently pushed out.

Copper Elite Contributor
Posts: 434
Country: USA

Crashing while syncing with Outlook 2016 may be related to an update that Microsoft recently pushed out.

Microsoft's Click-to-Run technology provides a way to add significant features to Office without installing a new release. Their development team can now push out product enhancements as if they were mere quality updates. In an Agile development world, this is an approach often used in centrally managed web sites  but usually not available to large, locally installed applications. There are advantages to this approach.


The downside is that you are no longer in control of the software you depend on. Major changes will be pushed out to you and your customers unless you completely disable updates. The old adage, "If it ain't broke, don't fix it", applies here. Business critical software requires a stable environment. But with features distributed with security patches, how are you to control what gets installed?


We've recently had reports about Outlook Sync crashing in 18.2 and the types of error messages we're seeing lead us to this Microsoft KB:

iCloud crashes when synchronizing data with Outlook 2016


As it turns out, iCloud is not the only application affected.  The faulting module appears to be: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso30win32client.dll


There may be others as we have explored their workaround, of falling back to prior versions and disabling update, but found other Office16 modules failed. 


Our guidance here is that you watch for KB announcements for Office 2016 and regularly backup your system.  Windows 10 users should examine their Advanced Update settings and enable "Defer Updates".  This will continue to deliver security updates but will defer application updates for a month or two - giving Microsoft some time to resolve update issues that other users have encountered when they are first released.





We have attached two zip files that, when unpacked, contain .BAT files that will roll back your version of Office 2016 to one of two versions you might try. These tools work for both 32-bit and 64-bit Office 2016. 


Microsoft recommends a course of action when this issue disrupts your workflow. 


  1. Disable automatic updates for Microsoft Office until Microsoft resolves this issue.
    You may still check for updates and choose the security updates individually and apply them. If the problem reappears, make note of the updates you applied and revert your version once more. 
  2. Determine if your version of Office is affected:
    Control Panel > Uninstall.
    Find your version of Microsoft Office 2016 listed in the applications.
    Examine the value in the Version column.  Format will be 16.0.XXXX.YYYY.
    If "XXXX" is greater than 6900, your version of Office is likely affected.
  3. If you choose to revert your version of Office:
    Backup your databases,
    Backup your system, excluding your Act7 SQL instance. 
    Choose the tool for one of the versions we've provided.
  4. Zip and read the instructions text file. 


Now, we know our software is not without its own issues. The team is working on a remarkable number of fixes to Office Integration for 19.0, as well as defects throughout the entire Windows and Web Client. We wanted to make you aware of this issue so you can take preventative measures. 






Bob Breeding
New Member
Posts: 1
Country: USA

Re: Crashing while syncing with Outlook 2016 may be related to an update that Microsoft recently pushed out.

I'm getting this error as well, but we're not using Office 2016. not using click-to-run version either.

Running Office 2010 Professional on Windows 10 Pro Version 1607.


Office 2010 updated on 1/16/2017.

Act! Premium version Update 3.


Act! Integration works, but crashes very often. Error Event Viewer, windows logs, Application says ".NET Runtime", Event ID 1026

Also get event id 1001, see bottom:


Please advise.


Event ID 1026:

Application: ACT!.Integration.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageA(MSG ByRef)
   at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
   at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
   at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
   at Act.Outlook.Sync.SystemTray.OnSynchronizationCompleted(System.Object, Act.Shared.Sync.SynchronizationCompleteEventArgs)
   at Act.Outlook.Sync.Common.Scheduler.SynchronizeAll()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr, System.Object[], System.Object, System.Object[] ByRef)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessageSink)
   at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(System.Object)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Event ID 1001

Fault bucket 108683147509, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: ACT!.Integration.exe
P3: 584ee058
P4: olmapi32.dll
P5: 14.0.7172.5000
P6: 5785a84d
P7: c0000005
P8: 0007cd36

Attached files:
C:\Users\Joel Burnstine\AppData\Local\Temp\WERE5B7.tmp.WERInternalMetadata.xml

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: bff7d043-bf99-43f4-ac64-9e3e2660080b
Report Status: 0
Hashed bucket: 0aa9e4b25c4f0b152ce629afb5ad95d1

Copper Elite Contributor
Posts: 434
Country: USA

Re: Crashing while syncing with Outlook 2016 may be related to an update that Microsoft recently pushed out.

Thanks, Adam. I'll get this over to development. 



Bob Breeding
New Member
Posts: 24
Country: USA

Re: Crashing while syncing with Outlook 2016 may be related to an update that Microsoft recently pushed out.

I have been having the same "Act Integration has Stopped Working" type crash.

If I use the 4229 build it stops and says the sync was successful.

The bad part is it only updates the address book.It does not populate the Contact or People or the Calendar.

How can i get the Contacts/people and Calendar to be populated.


I've read another article which suggests a fix of setting the channel to current.


However even the the article says it will set to build 4229 it does not and sets the build to 8067 which brings back the crashing issue.



New Member
Posts: 1
Country: Canada

Re: Crashing while syncing with Outlook 2016 may be related to an update that Microsoft recently pushed out.

We have been getting the same issue of Act.Integration has stopped working.


-Act would connect to Outlook OK.

- Green progress bar all the way to the end of Getting Contacts from ACT.

- after the full progress bar, we get the error.


We are using Act! Premium Version, Update 2


Windows 10 Home - with Creators Update


Outlook 2016 (Office 365 ) Version 1704 (8076.2115 Click to Run) - Current Channel


This is occurring on two laptops - same config - both were working earlier this month.



Posts: 4,041
Country: United_Kingdom

Re: Crashing while syncing with Outlook 2016 may be related to an update that Microsoft recently pushed out.

Hi all,

The most current information we have on the this Microsoft issue is recorded (and continually updated) in the following Knowledgebase article:

For anyone experiencing the issue described in the original post, please read the article carefully and follow the steps exactly.