Scehudling assistant causes Outlook 2013 crash when creating meeting with external attendee

Good morning
I have a very annoying problem with Outlook 2013 that occurs when a user attempts to create a meeting, inviting and external attendee and uses the Scheduling Assistant to help them organise timings. We are running Exchange 2013 CU3 with no other versions
of Exchange in our environment.
Everything works fine until the user attempts to use the Scheduling assistant, as soon as they do, Outlook promptly crashes. Using OWA, things seem to work as expected.
This is the error logged in event viewer:
Event ID: 1000
Faulting application name: OUTLOOK.EXE, version: 15.0.4569.1503, time stamp: 0x52b0b282
Faulting module name: mso.dll, version: 15.0.4605.1000, time stamp: 0x531f9fba
Exception code: 0xc0000409
Fault offset: 0x00009408
Faulting process id: 0x1320
Faulting application start time: 0x01cf6453441df03b
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
Report Id: 62895ac5-d04a-11e3-8285-7071bc433f94
Faulting package full name:
Faulting package-relative application ID:
Has anyone experienced this before and if so can you help me fix it please? Is this a bug with Outlook or Exchange? I am going to test the same scenario on a machine running Outlook 2010 to see if the same issue still persists.

Open Outlook with /safe command (Or hold Ctrl key when open Outlook) starts Outlook without the Reading Pane or toolbar customizations. Both native and managed Component Object Model (COM) add-ins are turned off. To narrow down the cause,
you can also try /safe:1 and /safe:3 commands.
/safe:1 Starts Outlook with the Reading Pane off.
/safe:3 Both native and managed Component Object Model (COM) add-ins are turned off.
To do this, press Windows key + R to open the Run command, type outlook.exe /safe:1
and press Enter.
In addition, you can refer to the steps in this article to troubleshoot issue that Outlook does not crash when you start it in safe mode. See the "Step 6: Start Outlook in safe mode" section:
http://support.microsoft.com/kb/2934538/en-us
Please let me know the result.
Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Similar Messages

Outlook 2013 crashes when PDFMaker add-in is enabled

Outlook 2013 crashes when the Acrobat v.11.0.3 PDFMaker add-in is enabled. Outlook 2013 will automatically disable the add-in.
The Outlook 2013 version is 15.0.4517.1509, 32 bit. Windows 7 Pro 64 bit is the OS.
Below is the screenshot of the Outlook Account Info page.
Any comments or suggestions would be appreciated.

I was having to start Outlook 2013 two times every time I turned on my computer (running Windows 8.1 64-bit). The first time, Adobe Acrobad crashed Outlook, disabled PDF Maker, and closed. The second time Outlook started, told me it disabled PDF Maker, and gave me the option to re-enable. I then click to re-enable PDF Maker.
However, I tried LoriAUC's suggestion #1, to launch Outlook 2013 as Administrator. When I did that, Outlook just started up without disabling PDF Maker and without crashing. And PDF Maker remained availble to use within Outlook. That's the way it should always work.
So, I remember that Outlook ran fine with PDF Maker until this month of February 2014. I wonder what changed, Outlook or Acrobat Standard Edition so that Outlook crashes (unless running Outlook as Administrator).
In the meantime, I wonder how to make Outlook start as Administrator automatically without my having to do any extra steps. Or is there a better fix.

Outlook 2013 crashes when opening Calendar search result

I have a user who uses her Outlook 2013 calendar extensively, mainly to note for herself when she has spoken to a customer, and creating appointments for when she needs to speak to them again. (This is outside of our policy to note the contact in
MS CRM.) She can have scores of such Calendar items each day.
When seraching for these appointments in her Calendar, she gets the list of results, but Oulook crashes when she tries to open any of them. Sometimes Outlook restarts on its own, sometimes she must relaunch it herself.
Related threads reference a wwlib.dll error, but she is not getting that. It is Outlook.exe itself that is crashing. There are other threads that reference other open windows, or items containing webpages or tables, but these do not apply to her, either.
Event Data (two related entries) contain the following:
OUTLOOK.EXE
15.0.4551.1004
5253ad6f
c0000005
00025b09
19cc
01cef2a610938033
C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE
C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE
77f5e493-5e9b-11e3-9ef4-00219b4a7172
And:
3915849571
1
APPCRASH
Not available
0
OUTLOOK.EXE
15.0.4511.1004
5253ad6f
OUTLOOK.EXE
15.0.4551.1004
5253ad6f
c0000005
00025b09
C:\Users\[username]\AppData\Local\Temp\163947659.cvr C:\User\[username]\AppData\Local\Temp\CVR780F.tmp.cvr
C:\Users\[username]\AppData\Local\Temp\WERA546.tmp.WERInternalMetadata.xml
C:\Users\[username]\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_OUTLOOK.EXE_2e80497b46642ed3f64262bb26bbba2f6ecc_02d1bdd5
0
77f5e493-5e9b-11e3-9ef4-00219b4a7172
0
On answers.microsoft.com, Girish M (Support Engineer who eventally directed me here), asked me to run Scanpst.exe. I would paste the results here, but this window does not seem to allow pasting. A summary description of what it found on her .ost file (no
.pst in use) is basically this:
**Beginning NDB recovery
**Attempting to open database
**Attempting to validate header
**Attempting to validate AMap
**Attempting to validate BBT
**Attempting to validate NBT
**Attempting to validate BBT refcounts
    ??Couldint find BBT entry in the RBT (E025CC)
**Attempting to validate header NID high-water marks
**Beginning PST/OST recovery
**Attempting to recover all top-level objects
    **Store created by biuld: 15.4517
**Attempting to walk all folders
      Failed to add row to the FLT, RowID = 719
      Failed to add row to the FLT, RowID = 6CD
      Failed to add row to the FLT, RowID = 6DE
      Failed to add row to the FLT, RowID = 6D8
and so on, and so on, with a few hundred more FLT RowID errors, finally ending with:
**Attempting to locate any orphaned folders/messages
**Performing Final HMP validation
**Attempting to check top-level objects for consistency
**Updating folder hierarchy
  **Verifying message moves
My understanding of the Scanpst.exe process is that it also disables any addons which might cause crashing, but the issue is still being experienced. Running Scanpst.exe a second time (appending the previous log, although it seemed to actually prepend the
file) only returned a few lines from the top of the result above ending with "Attempting to validate BBT."
Fixes not attempted yet that I have found performing searches include running the Office Repair tool, or checking for KB2817631 (a Word update that is apparently having adverse affects on Outlook, not attempted yet because it seems to be related to the wwlib.dll
error, which is not happening here).
Any thoughts out there? Thanks!

Mavis,
Thanks for the reply. Running Outlook using /cleansharing and
/cleanroamedprefs did not have any effect when used individually or in combination with each other.
Running the Search Index Rebuild option also did not seem to do anything, as the pop-up message indicated that it may take a long time to finish, and yet seemed to finish instantaneously, not giving any indication that the indexing took place. The option
window immediately said "Indexing complete" for 23,755 items.
As to the Outlook Forum, they are the ones who directed me to this forum (you can see the thread on the Answers support page under Office - Office 2013 - Microsoft Office Outlook - Office on Windows 7, under the title "Outlook 2013 restarts when
opening Calendar Search result item" first posted on Dec 11, 2013), as Girish M felt that it might be due to Exchange, and not Outlook. (I have no reports of any of our other users on the same Exchange server having the problem with their Outlook, but
they also do not use it the way this user has been.)
I can repost the issue there, or continue the same thread, if you think the issue lies with them. Was the "Answers" site the improper place to post, perhaps? Should it go in a different thread on Technet instead?
Thanks for your assistance!
Edited to add:
Here are the KBs installed just before or on the date the problem started (12/6/2013):
12/5/2016 (Office updates, all 32-Bit):
Security Update Office 2013 KB2768005
Office 2013 KB2768016
Office 2013 KB2817640
Office 2013 KB2827228
Security Office 2013 KB2837618
Word 2013 KB2817631
InfoPath 2013 KB2752078
Office 2013 KB2817493
Office 2013 KB2760539
Office 2013 KB2827235
Office 2013 KB2827225
Security Excel 2013 KB2827238
Office 2013 KB2760242
Office 2013 KB2817626
Office 2013 KB2817314
Office 2013 KB2760610
Access 2013 KB2768008
Office 2013 KB2738038
SkyDrive Pro KB2825633
Security Office 2013 KB2817623
Office 2013 KB2760267
Visio Viewer 2013 KB2768338
Office 2013 KB2827230
OneNote 2013 KB2810016
Office 2013 KB2827228
Office 2013 KB2767845
Definition Office 2013 KB2760587
Office 2013 KB2726996
Security Office 2013 KB2810009
Office 2013 KB2817316
Word 2013 KB2817631
Lync 2013 KB2817621
Office 2013 KB2760224
Office 2013 KB2726954
Office 2013 KB2817640
Publisher 2013 KB2752097
PowerPoint 2013 KB2817625
Office 2013 KB2760257
Office 2013 KB2817309
Security Outlook 2013 KB2837618
Visio 2013 KB2752018
Office 2013 KB2817490
Word 2013 KB2827218
Office 2013 KB2760553
12/6/2013 (for Windows, all Security):
KB2900986
KB2888505
KB2876331
KB2868725
KB2868626
KB2862152
I listed all updates because there have been reported instances of a Word update causing Outlook to crash, but she is not getting the wwlib.dll error related to that KB. If you are aware of any issues with these updates, and which ones might be worth uninstalling
in an attempt to fix, please let me know.
Thanks again!

Outlook 2013 crashing when sending email Exception code 0xc0000602 MSO.dll error

Two are three times a week Outlook crashes when sending email with the following error
Log Name:      Application
Source:        Application Error
Date:          15/01/2015 10:00:58
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ********.***.local
Description:
Faulting application name: OUTLOOK.EXE, version: 15.0.4667.1000, time stamp: 0x543d3698
Faulting module name: mso.dll, version: 15.0.4675.1002, time stamp: 0x5474349b
Exception code: 0xc0000602
Fault offset: 0x011b1687
Faulting process id: 0x11dc
Faulting application start time: 0x01d030a6e4aa1ee7
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
Report Id: 66ad29a2-9c9d-11e4-b53c-082e5f1727fc
Event Xml:
<Event xmlns
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-01-15T10:00:58.000000000Z" />
    <EventRecordID>10015</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Events-HP8200.ICI.local</Computer>
    <Security />
</System>
<EventData>
    <Data>OUTLOOK.EXE</Data>
    <Data>15.0.4667.1000</Data>
    <Data>543d3698</Data>
    <Data>mso.dll</Data>
    <Data>15.0.4675.1002</Data>
    <Data>5474349b</Data>
    <Data>c0000602</Data>
    <Data>011b1687</Data>
    <Data>11dc</Data>
    <Data>01d030a6e4aa1ee7</Data>
    <Data>C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE</Data>
    <Data>C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll</Data>
    <Data>66ad29a2-9c9d-11e4-b53c-082e5f1727fc</Data>
</EventData>
</Event>
Any clues on a fix?

Hi,
Thanks for your question.
This issue might occurs due to lots of reasons. Do you have a virus scanner installed which integrates itself with Outlook? If yes, please try to disable it, and then try again. You might opt to uninstall the virus scanner temporarily to make
sure it will not interfere the testing.
Also, lots of Office crash issues are caused by third-party add-ins. You might want to have a check and see if you have any integrated with your Outlook client which might cause the issue.
Since the issue occurs randomly ("Two are three times a week"), Office
Safe Mode will not be effective here, just manually disable all third-party add-ins in Outlook FILE>Options>Ass-Ins, use outlook for a period of time, then verify result.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Outlook 2013 crashes when clicking calendar icon to get to the calendar

When clicking the calendar icon, Oulook 2013 crashes and leaves this event:
Faulting application name: OUTLOOK.EXE, version: 15.0.4551.1004, time stamp: 0x5253ab76
Faulting module name: OUTLOOK.EXE, version: 15.0.4551.1004, time stamp: 0x5253ab76
Exception code: 0xc0000005
Fault offset: 0x00025b09
Faulting process id: 0x2668
Faulting application start time: 0x01cef1ede0ad9dd8
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
Faulting module path: C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
Report Id: 25f2f8e0-5de1-11e3-aa96-b8ca3a76ef90
Faulting module is OUTLOOK.exe so I don't know what to look for. I have done the following:
Ran outlook in safe mode
Ran outlook without addons
Created a new mail profile
Repaired Office 2013, also uninstalled and reinstalled Office 2013
Cleared temp files
I am not sure why this is crashing and I don't see any hints in the event viewer logs or in the error report that was created. It just says that Oulook crashed but has no indication. What can I look for in these logs to find a culprit?
Version=1
EventType=APPCRASH
EventTime=130307499751212652
ReportType=2
Consent=1
UploadTime=130307499751836680
ReportIdentifier=47e54e86-5dee-11e3-8617-b8ca3a76ef90
IntegratorReportIdentifier=47e54e85-5dee-11e3-8617-b8ca3a76ef90
WOW64=1
Response.BucketId=3941454205
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=OUTLOOK.EXE
Sig[1].Name=Application Version
Sig[1].Value=15.0.4551.1004
Sig[2].Name=Application Timestamp
Sig[2].Value=5253ab76
Sig[3].Name=Fault Module Name
Sig[3].Value=OUTLOOK.EXE
Sig[4].Name=Fault Module Version
Sig[4].Value=15.0.4551.1004
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5253ab76
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00025b09
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
UI[3]=Microsoft Outlook has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Program Files\Microsoft Office 15\root\office15\AppVIsvSubsystems32.dll
LoadedModule[5]=C:\Program Files\Microsoft Office 15\root\office15\AppVIsvStream32.dll
LoadedModule[6]=C:\Program Files\Microsoft Office 15\root\office15\c2r32.dll
LoadedModule[7]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[9]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[10]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[11]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[12]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[13]=C:\Windows\syswow64\ole32.dll
LoadedModule[14]=C:\Windows\syswow64\GDI32.dll
LoadedModule[15]=C:\Windows\syswow64\USER32.dll
LoadedModule[16]=C:\Windows\syswow64\LPK.dll
LoadedModule[17]=C:\Windows\syswow64\USP10.dll
LoadedModule[18]=C:\Windows\system32\USERENV.dll
LoadedModule[19]=C:\Windows\system32\profapi.dll
LoadedModule[20]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[21]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[22]=C:\Program Files\Microsoft Office 15\root\office15\MSVCR100.dll
LoadedModule[23]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll
LoadedModule[24]=C:\Program Files\Microsoft Office 15\root\office15\MSVCP100.dll
LoadedModule[25]=C:\Windows\system32\IMM32.DLL
LoadedModule[26]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[27]=C:\Windows\syswow64\oleaut32.dll
LoadedModule[28]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
LoadedModule[29]=C:\Windows\system32\MSIMG32.dll
LoadedModule[30]=C:\Windows\system32\uxtheme.dll
LoadedModule[31]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\Comctl32.dll
LoadedModule[32]=C:\Windows\system32\dwmapi.dll
LoadedModule[33]=C:\Windows\system32\d2d1.dll
LoadedModule[34]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[35]=C:\Windows\system32\WINSTA.dll
LoadedModule[36]=C:\Windows\system32\dxgi.dll
LoadedModule[37]=C:\Windows\system32\VERSION.dll
LoadedModule[38]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[39]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[40]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[41]=C:\Program Files\Microsoft Office 15\Root\Office15\olmapi32.dll
LoadedModule[42]=C:\Windows\system32\msi.dll
LoadedModule[43]=C:\Program Files\Microsoft Office 15\root\office15\1033\OUTLLIBR.DLL
LoadedModule[44]=C:\Windows\system32\mscoree.dll
LoadedModule[45]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[46]=C:\Windows\system32\DavClnt.DLL
LoadedModule[47]=C:\Windows\system32\DAVHLPR.dll
LoadedModule[48]=C:\Program Files (x86)\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\osppc.dll
LoadedModule[49]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\riched20.dll
LoadedModule[50]=C:\Program Files\Microsoft Office 15\Root\Office15\1033\mapir.dll
LoadedModule[51]=C:\Windows\system32\ntmarta.dll
LoadedModule[52]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[53]=C:\Windows\syswow64\urlmon.dll
LoadedModule[54]=C:\Windows\syswow64\iertutil.dll
LoadedModule[55]=C:\Windows\syswow64\WININET.dll
LoadedModule[56]=C:\Windows\syswow64\Normaliz.dll
LoadedModule[57]=C:\Windows\system32\DWrite.dll
LoadedModule[58]=C:\Windows\system32\d3d10_1.dll
LoadedModule[59]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[60]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[61]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[62]=C:\Windows\system32\d3d11.dll
LoadedModule[63]=C:\Windows\system32\igd10umd32.dll
LoadedModule[64]=C:\Program Files\Microsoft Office 15\root\office15\wwlib.dll
LoadedModule[65]=C:\Program Files\Microsoft Office 15\root\office15\oart.dll
LoadedModule[66]=C:\Program Files\Microsoft Office 15\Root\Office15\contab32.dll
LoadedModule[67]=C:\Program Files\Microsoft Office 15\Root\Office15\EMSMDB32.DLL
LoadedModule[68]=C:\Windows\system32\WSOCK32.dll
LoadedModule[69]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[70]=C:\Windows\syswow64\NSI.dll
LoadedModule[71]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[72]=C:\Windows\System32\netprofm.dll
LoadedModule[73]=C:\Windows\System32\nlaapi.dll
LoadedModule[74]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[75]=C:\Windows\system32\rsaenh.dll
LoadedModule[76]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[77]=C:\Windows\System32\npmproxy.dll
LoadedModule[78]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[79]=C:\Windows\system32\WINNSI.DLL
LoadedModule[80]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[81]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[82]=C:\Windows\SysWOW64\SFC.DLL
LoadedModule[83]=C:\Windows\system32\sfc_os.DLL
LoadedModule[84]=C:\Program Files\Microsoft Office 15\Root\Office15\MSPST32.DLL
LoadedModule[85]=C:\Windows\system32\mssprxy.dll
LoadedModule[86]=C:\Windows\system32\mswsock.dll
LoadedModule[87]=C:\Windows\System32\wshtcpip.dll
LoadedModule[88]=C:\Windows\System32\wship6.dll
LoadedModule[89]=C:\Windows\system32\DNSAPI.dll
LoadedModule[90]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
LoadedModule[91]=C:\Windows\system32\rasadhlp.dll
LoadedModule[92]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[93]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[94]=C:\Windows\system32\secur32.dll
LoadedModule[95]=C:\Windows\system32\credssp.dll
LoadedModule[96]=C:\Windows\SysWOW64\Kerberos.DLL
LoadedModule[97]=C:\Windows\system32\cryptdll.dll
LoadedModule[98]=C:\Windows\system32\bcrypt.dll
LoadedModule[99]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[100]=C:\Windows\system32\mlang.dll
LoadedModule[101]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\MSPTLS.DLL
LoadedModule[102]=C:\Windows\system32\explorerframe.dll
LoadedModule[103]=C:\Windows\system32\DUser.dll
LoadedModule[104]=C:\Windows\system32\DUI70.dll
LoadedModule[105]=C:\Windows\SysWOW64\actxprxy.dll
LoadedModule[106]=C:\Program Files\Microsoft Office 15\Root\Office15\ADDINS\ColleagueImport.dll
LoadedModule[107]=C:\Windows\system32\NETAPI32.dll
LoadedModule[108]=C:\Windows\system32\netutils.dll
LoadedModule[109]=C:\Windows\system32\srvcli.dll
LoadedModule[110]=C:\Windows\system32\wkscli.dll
LoadedModule[111]=C:\Program Files\Microsoft Office 15\Root\Office15\ONBttnOL.dll
LoadedModule[112]=C:\Program Files\Microsoft Office 15\Root\Office15\SOCIALCONNECTOR.DLL
LoadedModule[113]=C:\Program Files\Microsoft Office 15\Root\Office15\mfc100u.dll
LoadedModule[114]=C:\Program Files\Microsoft Office 15\Root\Office15\ADDINS\UmOutlookAddin.dll
LoadedModule[115]=C:\Windows\system32\MAPI32.dll
LoadedModule[116]=C:\Windows\system32\OLEACC.dll
LoadedModule[117]=C:\Program Files\Microsoft Office 15\root\office15\1033\UmOutlookStrings.dll
LoadedModule[118]=C:\Program Files\Microsoft Office 15\Root\Office15\FACEBOOKPROVIDER.DLL
LoadedModule[119]=C:\Program Files\Microsoft Office 15\Root\Office15\LINKEDINPROVIDER.DLL
LoadedModule[120]=C:\Windows\System32\msxml6.dll
LoadedModule[121]=C:\Windows\system32\UIAutomationCore.DLL
LoadedModule[122]=C:\Program Files\Microsoft Office 15\Root\Office15\SHAREPOINTPROVIDER.DLL
LoadedModule[123]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[124]=C:\Windows\system32\RASAPI32.dll
LoadedModule[125]=C:\Windows\system32\rasman.dll
LoadedModule[126]=C:\Windows\system32\rtutils.dll
LoadedModule[127]=C:\Windows\system32\sensapi.dll
LoadedModule[128]=C:\Windows\system32\SXS.DLL
LoadedModule[129]=C:\Windows\SysWOW64\schannel.dll
LoadedModule[130]=C:\Windows\system32\ncrypt.dll
LoadedModule[131]=C:\Windows\system32\GPAPI.dll
LoadedModule[132]=C:\Windows\system32\cryptnet.dll
LoadedModule[133]=C:\Program Files\Microsoft Office 15\Root\Office15\outlph.dll
LoadedModule[134]=C:\Windows\system32\tquery.dll
LoadedModule[135]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[136]=C:\Windows\system32\WINMM.dll
LoadedModule[137]=C:\Windows\system32\MMDevAPI.DLL
LoadedModule[138]=C:\Windows\system32\PROPSYS.dll
LoadedModule[139]=C:\Windows\system32\wdmaud.drv
LoadedModule[140]=C:\Windows\system32\ksuser.dll
LoadedModule[141]=C:\Windows\system32\AVRT.dll
LoadedModule[142]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[143]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[144]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[145]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[146]=C:\Windows\system32\msacm32.drv
LoadedModule[147]=C:\Windows\system32\MSACM32.dll
LoadedModule[148]=C:\Windows\system32\midimap.dll
LoadedModule[149]=C:\Windows\system32\msadp32.acm
LoadedModule[150]=C:\Windows\system32\apphelp.dll
Sec[0].Key=LCID
Sec[0].Value=1033
Sec[1].Key=skulcid
Sec[1].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Outlook
AppPath=C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE

Hello,
Did you try to create a new mail profile without exchange account?
Besides, I recommend you use CalCheck to check Outlook Calendars for problems.
And then you can delete corrupt calendar item or use Calendar Repair Assistant to repair the corrupt calendar item.
Here is the blog for your reference.
http://blogs.msdn.com/b/webdav_101/archive/2012/02/28/how-to-check-for-calendar-corruption.aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Outlook 2013 Crashes when sending mail

The system is a Windows 8.1 Pro x64, the Office installation is Office Home & Business 2013 32.
repeatedly the Outlook will crash after entering a contact email address when entering content into the subject line. Often it will crash when any attempt is made to enter content into the body.
All add-ins have been disabled.
If started in Safe mode, Outlook is able to send mail.
The error message in the event log is;
Faulting application name: OUTLOOK.EXE, version: 15.0.4551.1511, time stamp: 0x52947f7f
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f0c22
Exception code: 0xc0000005
Fault offset: 0x0003c558
Faulting process id: 0xeec
Faulting application start time: 0x01cf23061492ec78
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
Faulting module path: C:\Program Files\Microsoft Office 15\root\office15\MSVCR100.dll
Report Id: 693a0ed9-8ef9-11e3-be9f-b4b67633f44a
Faulting package full name:
Faulting package-relative application ID:
A capture of the add-ins dialog when Outlook is started in normal mode is shown below.
I have run scanpst on the local pst files and performed repairs.
I also disabled the use of auto-complete.
Nothing has worked.
Please provide some new suggestions.
Thx - Eli

Hi,
Since this issue doesn't occur when using Outlook in Safe Mode and it's not add-ins related, I suspect the NormalEmail.dotm is corrupted in your case.
NormalEmail.dotm is the default template that opens when creating a new mail message. When you start Outlook in Safe Mode, it is not loaded.
Please go to the following location:
C:\Users\<username>\AppData\Roaming\Microsoft\Templates
Find the NormalEmail.dotm file, rename it to ".old". Outlook then will create a new one, check if this issue persist with the new NormalEmail.dotm file.
Regards,
Melon Chen
TechNet Community Support

Outlook 2013 crashed when user sending email from Adobe Writer xi pro ver 11.0.07

I ask Adobe, but they are signaling to Outlook problem
PC-HP, Windows 8.1 Pro X64 connected to Windows 2008 R2 DC
Adobe Acrobat Pro ver 11,x
When user trying to send email from Adobe direct, Outlook 2013 Pro is crashing
The only way to send email is to save adobe ( PDF) file and attached to the email
All patches are installed

Log Name: Application
Source: Application Error
Date: 7/15/2014 8:05:38 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Liz7PM-HP.armadale.local
Description:
Faulting application name: Acrobat.exe, version: 11.0.7.79, time stamp: 0x536b812b
Faulting module name: SendMail.api, version: 11.0.7.79, time stamp: 0x536b7fd0
Exception code: 0xc0000005
Fault offset: 0x0003390b
Faulting process id: 0x139c
Faulting application start time: 0x01cfa024deec4218
Faulting application path: C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\Acrobat.exe
Faulting module path: C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\SendMail.api
Report Id: 553a89c7-0c18-11e4-be97-80c16ee27020
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-15T12:05:38.000000000Z" />
<EventRecordID>66128</EventRecordID>
<Channel>Application</Channel>
<Computer>Liz7PM-HP.armadale.local</Computer>
<Security />
</System>
<EventData>
<Data>Acrobat.exe</Data>
<Data>11.0.7.79</Data>
<Data>536b812b</Data>
<Data>SendMail.api</Data>
<Data>11.0.7.79</Data>
<Data>536b7fd0</Data>
<Data>c0000005</Data>
<Data>0003390b</Data>
<Data>139c</Data>
<Data>01cfa024deec4218</Data>
<Data>C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\Acrobat.exe</Data>
<Data>C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\SendMail.api</Data>
<Data>553a89c7-0c18-11e4-be97-80c16ee27020</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Log Name: Application
Source: Windows Error Reporting
Date: 7/15/2014 8:05:55 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Liz7PM-HP.armadale.local
Description:
Fault bucket 73304412188, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Acrobat.exe
P2: 11.0.7.79
P3: 536b812b
P4: SendMail.api
P5: 11.0.7.79
P6: 536b7fd0
P7: c0000005
P8: 0003390b
P9:
P10:
Attached files:
C:\Users\ewhitton\Desktop\140.pdf
C:\Users\ewhitton\AppData\Local\Temp\WER8000.tmp.WERInternalMetadata.xml
C:\Users\ewhitton\AppData\Local\Temp\WER8BB9.tmp.appcompat.txt
minidump.mdmp
These files may be available here:
C:\Users\ewhitton\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Acrobat.exe_2a26ba191a528da71b85271ed9509f7e426babf8_0d6f35c4_1735c074
Analysis symbol:
Rechecking for solution: 0
Report Id: 553a89c7-0c18-11e4-be97-80c16ee27020
Report Status: 4104
Hashed bucket: f6a7a946597169e4aea5077b3b7f0848
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-15T12:05:55.000000000Z" />
<EventRecordID>66131</EventRecordID>
<Channel>Application</Channel>
<Computer>Liz7PM-HP.armadale.local</Computer>
<Security />
</System>
<EventData>
<Data>73304412188</Data>
<Data>1</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>Acrobat.exe</Data>
<Data>11.0.7.79</Data>
<Data>536b812b</Data>
<Data>SendMail.api</Data>
<Data>11.0.7.79</Data>
<Data>536b7fd0</Data>
<Data>c0000005</Data>
<Data>0003390b</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
C:\Users\ewhitton\Desktop\140.pdf
C:\Users\ewhitton\AppData\Local\Temp\WER8000.tmp.WERInternalMetadata.xml
C:\Users\ewhitton\AppData\Local\Temp\WER8BB9.tmp.appcompat.txt
minidump.mdmp</Data>
<Data>C:\Users\ewhitton\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Acrobat.exe_2a26ba191a528da71b85271ed9509f7e426babf8_0d6f35c4_1735c074</Data>
<Data>
</Data>
<Data>0</Data>
<Data>553a89c7-0c18-11e4-be97-80c16ee27020</Data>
<Data>4104</Data>
<Data>f6a7a946597169e4aea5077b3b7f0848</Data>
</EventData>
</Event>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Log Name: Application
Source: Outlook
Date: 7/15/2014 8:06:05 AM
Event ID: 50
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Liz7PM-HP.armadale.local
Description:
The following providers do not implement fast shutdown APIs, but are being shut down using fast shutdown:
MDConnector.dll (MAPI Store Provider)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Outlook" />
<EventID Qualifiers="16384">50</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-15T12:06:05.000000000Z" />
<EventRecordID>66132</EventRecordID>
<Channel>Application</Channel>
<Computer>Liz7PM-HP.armadale.local</Computer>
<Security />
</System>
<EventData>
<Data>MDConnector.dll (MAPI Store Provider)
</Data>
</EventData>
</Event>

Excel 2013 crashes when creating VFP OLE DB Data connection

Hi all,
I don't know how often the DBF format is used in Office but it seems some demand still exists because Microsoft created 64 bit version of dBase ODBC and OLE DB driver (in Access data engine). Then I don't understand why Microsoft ignores its own FoxPro
DBF data format because FoxPro ODBC driver is not supported already and no 64 bit version of VFP OLE DB driver is planned...
I am testing DBF file import to Excel 2013 (32 bit) but it crashes instantly. I have VFP OLE DB driver (the last version), some small DBF file, and I am trying to read it as external data in Excel.
Steps to reproduce (menu prompts are translated, so some differences may occur):
Open empty worksheet
Click "Other data sources" on Data ribbon
Select Data Connection Wizard and from the list of available drivers select "Other" and click "Next"
A list of OLE DB providers installed appears, select Microsoft OLE DB Provider for Visual FoxPro and click "Next >>"
Excel 2013 crashes...
This process works in Excel 2010 and 2007 so the problem must be in Excel 2013...
The question is how to read DBF data in FoxPro format when there is no older Office version available?

To connect to a Visual FoxPro database or table in Excel
Open an Excel worksheet.
From the Data menu, point to Import External Data, and click
Import Data.
In the Select Data Source dialog box, click New Source Data Connection.
In the Data Connection Wizard, select Other/Advanced.
In the Provider tab, select Microsoft OLE DB Provider for Visual FoxPro.
The Connection tab in the Data Link Properties dialog box appears.
To connect to a Visual FoxPro database or table in Word
Open a Word document.
From the View menu, point to Toolbars, and click
Database.
On the Database toolbar, click the Insert Database icon.
In the Database dialog box, click Get Data.
In the Select Data Source dialog box, click New Source Data Connection.
In the Data Connection Wizard, select Other/Advanced.
In the Provider tab, select Microsoft OLE DB Provider for Visual FoxPro.
The Connection tab in the Data Link Properties dialog box appears.
To add a Visual FoxPro database or table folder
On the Connection tab and in the Select or enter a database name box, type path and name of the database or table folder you want.
-or-
To browse for a Visual FoxPro database or table folder, click the ellipsis (...) button to the right of the
Select or enter a database name box to open the Configure Connection dialog box.
Specify a different collating sequence if desired.
To test the connection, click Test Connection. If connection is successful, click
OK.

Outlook 2013 crashes when adding an event using an emailed ics file.

I use Outlook 2013, Hotmail and an Android phone to manage my calendar, with Outlook 2013 and Android synching to the Outlook.com account.
Scenario 1:
1. Receive meeting requests with attached ics files from an Apple Mac user
2. Drag ics file attachment to the Outlook calendar
3. "Meeting" window opens
4. Click "Accept" then "Send Response Now" OR "Do Not Send a Response"
OR "Edit the Response Before Sending" then "Send"
5. Outlook crashes (see event log below) and restarts
6. On restart the meeting request has been added to the Outlook calendar
7. Meeting is not in the Outlook.com calendar
8. Meeting organiser does not receive email response
Event Log:
Faulting application name: OUTLOOK.EXE, version: 15.0.4675.1003, time stamp: 0x548ba4b9
Faulting module name: pstprx32.dll, version: 15.0.4673.1000, time stamp: 0x54588166
Exception code: 0xc0000005
Fault offset: 0x0007278b
Faulting process id: 0x1320
Faulting application start time: 0x01d02a0fc01024ab
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.EXE
Faulting module path: C:\Program Files\Microsoft Office 15\Root\Office15\pstprx32.dll
Report Id: 2ce5a0d4-9603-11e4-8369-ac7ba12ac262
Faulting package full name:
Faulting package-relative application ID:
Scenario 2:
1. Receive meeting requests with attached ics files from an Apple Mac user
2. Double click on the ics file
3. Error message "The attempted operation failed. An object could not be found"
Observations:
Re-creating the Hotmail account OST file makes no difference.
The workaround described here:
http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/cannot-open-ics-meeting-invite/99ce57cc-5ffe-42f7-ba0a-87d6d928cb85
requires approximately 15 clicks, instead of two or three, so isn't workable for large numbers of meeting requests.
Meeting requests can be added to the local pst file calendar successfully. This calendar is not used because it doesn't allow synching with other devices.
System configuration:
Windows 8.1 - Most recent Windows Update check: "No updates are available"
Outlook 2013 (15.0.4675.1003), standalone installation (no Exchange Server) - Most recent Office Updates check: "The latest version of Office is installed on your computer"
Email containing ics attachments (and all other email) is sent to an email alias which is then forwarded to my ISP-provided email address
ISP email address is connected using IMAP/SMTP
Outlook.com / hotmail account is connected using EAS

Sorry for the delay. I was supposed to get alerts on this, but I never did. N2K has been built and rebuilt, and still the error comes up. For one Exchange user that's in the N2K file, I can look at it now, and it matches up with others on the same server.
But 2-3 days from now, it will somehow be changed to“/o=First Organization/ou=First Administrative Group/cn=Recipients/cn=user” and that starts Outlook crashing again. The error happened for several months, and during this time the user was moved to a new
Exchange server. A new profile was created after the move, but the problem followed him.
I removed the offending user again today. The entry in n2K is getting changed to “/o=First Organization/ou=First Administrative Group/cn=Recipients/cn=user”. I found that is is a legacyExchange issue, but I don't know from where it's being changed -
on the user who's Outlook is crashing, on the user sending the email, or on the AD server. I am not an Exchange expert, so reading a few websites that point out what this is didn't really help me figure out how to remove the legacyExchange problem. The customer
is using hosted Exchange, so I can't get onto the server to dig into it. Is it in the Global Address Book, or a user's individual contact?
I ran OffCAT and it pointed out two addins that had Resiliancy set. They were both Outlook Addins, DPOfcX.ComposeRibbon and OutlookChangeNotifier.Connect. So I hope they aren't the issue.

Outlook 2013 crashes when collapsing shared calendar

The following issues occurs when viewing shared calendars with Outlook 2013. It occurs on multiple workstations and with multiple users.
When collapsing a shared calendar by clicking the arrow to the left of the calendar name, if one or more users of the shared calendar are selected (i.e. the box next to their name is checked), the Outlook screen will appear to refresh the screen repeatedly
whilst the cursor flashes rapidly. Outlook then crashes and has to be re-started.
The work-around is to de-select any selected users of the shared calendar before collapsing it, but we cannot reasonably expect users to remember this.
Is there a fix for this issue? Others have had the same issue (see http://community.spiceworks.com/topic/419634-outlook-2013-stops-responding-when-trying-to-collapse-a-group-of-calendars).
Running outlook in safe mode makes no difference.
Thanks
Mark Johnstone

Hi,
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Outlook 2013 Crashes when Printing

All of my other Office 2013 applications print just fine, however Outlook crashes every single time i try to print - either to a regular or PDF printer.
Any help is greatly appreciated - i am very disappointed in the stability of the 2013 products - lots of crashing, in general.

For the issue you experience MARKY9074, this issue is poor coding in Outlook 2010 & 2013. Software bug related to Outlook's internal "security" interacting with external sources.
Typically happens with newsletter, email confirmation for travel - hotel or airline, etc.
To confirm that the issue is with OUTLOOK only, but not your computer or OutPrnt file, you can simply do the test as:
1) Print any other email that does not have embedded external graphic links - You should be able to print fine. Hence, the OutPrnt is not the issue
2) If you save the email in question in HTML and then open the saved HTML email to print, it should print fine, so the CONTENT OF THE EMAIL is also not an issue.
This issue has been around since Office 2010 SP1. Software bug that Microsoft is not fixing for whatever reason for last 3 years or so.

Outlook 2013 crash when sending mail to contact

Hi.
Big problem. When i write in to my Send . and target a Contact. name, lastname (email)
And press send and Outlook crashes. But if i delete the Contact and make a new one with the same infomation it works!
But i have 25 127 Contact and dont want to do it all again.
Help?

Hi,
I would suggest to try the following things:
1. Disable all the add-ins in Outlook.
2. Start Outlook in Safe mode by using the following command-line switch:
Outlook.exe /safe
3. Clear the clear the auto-complete list:
http://www.slipstick.com/outlook/suggested-contacts-and-auto-complete-lists/
4. Export all the contacts to an Outlook data file and then remove the contact items. Import all the contacts back to Outlook:
http://office.microsoft.com/en-001/outlook-help/export-items-to-an-outlook-data-file-pst-HA102809683.aspx
http://office.microsoft.com/en-001/outlook-help/import-outlook-items-from-an-outlook-data-file-pst-HA102919679.aspx
Best regards,
Rex Zhang
TechNet Community Support

SharePoint Designer 2013 crashes when creating a custom workflow...

I have never had this problem with SPD2010 and the default workflow 2013 templates do not provide the features that I need so creating this workflow using the online UI is not an option.
I have uninstalled SPD2013 two times now and I have tried creating a new list and I still have the problem. It's critical for my project that we are able to create custom workflows so this is a HUGE blocker for me so any help would be appreciated.
Thanks
Rick

Did you ever get a response?

Acrobat 10 crashes when "create pdf with scanner" command attempted.

Hello
For many months I have employed Acrobat 10 and an Epson V700 photo scanner successfully on a win 7 64 platform. I employ the create pdf from scanner command, select the custom scan option and allow the Epson scanning application to launch. Again this has worked without a problem.
For over a week, however, just as I am about to hand off scanning to the Espson scanning app, Acrobat crashes!!!
I have followed other threads in the Adobe Community with total reinstall of Acrobat 10, bcdedit command line commands, and a repair process through control panel of Acrobat 10. Nothing has worked.
I now have captured the process crash file with Sysinternals procdump.exe employing the c:\temp>prodump -e -ma Acrobat.exe c:\temp\01.dmp that I found on a similar Adobe Community thread. The file is over 154 mb!
Please advise me on how to provide diagnostic data and steps to take to recover this extremely important function of my Acrobat 10!
Thank you
H Flemming
Message was edited by: HFlemming

Hello
For many months I have employed Acrobat 10 and an Epson V700 photo scanner successfully on a win 7 64 platform. I employ the create pdf from scanner command, select the custom scan option and allow the Epson scanning application to launch. Again this has worked without a problem.
For over a week, however, just as I am about to hand off scanning to the Espson scanning app, Acrobat crashes!!!
I have followed other threads in the Adobe Community with total reinstall of Acrobat 10, bcdedit command line commands, and a repair process through control panel of Acrobat 10. Nothing has worked.
I now have captured the process crash file with Sysinternals procdump.exe employing the c:\temp>prodump -e -ma Acrobat.exe c:\temp\01.dmp that I found on a similar Adobe Community thread. The file is over 154 mb!
Please advise me on how to provide diagnostic data and steps to take to recover this extremely important function of my Acrobat 10!
Thank you
H Flemming
Message was edited by: HFlemming

Win 7 Pro 64-bit / DW CS5 crashes when opening files with external links

open any html, php, etc with a link to an external file - could be any type
dw cs5 crashes
this is on a fresh, clean install of win 7 and cs5 suite. hard drive was wiped clean before installing
Has anyone experienced this issue also?
This is extremely annoying... why I should pay for software that doesn't work?

"Enable Related Files" isn't the fix for this issue. It's slightly different - I wanted to still load related files, but only the ones local to the file I was editing.
The fix was to use DW's Resolve To IP Address feature. It required adding a registry value - it fixed the issue straight away
This Adobe support doc helped: http://kb2.adobe.com/cps/887/cpsid_88742.html

Scehudling assistant causes Outlook 2013 crash when creating meeting with external attendee

Similar Messages

Maybe you are looking for