T440P [20AN] - Lync 2013 Crashing When Sharing Desktop - Intel Driver
Hello,
After updating to the latest video drivers from the ThinkVantage Update Retriever, our Lync clients crash when sharing desktop on our T440P series and X240 series. I noticed when I uninstall the video driver I am able to screen share without incident. Also, if I update the driver from Windows Update I am able to share successfully. We use the update retriever and thininstaller to install our drivers in our environment. I have tried uninstalling the Lync updates all the way down to the base version and experience the same issue at every level. It crashes 100% of the time when sharing desktop. I have tested it on T440p machines in our environment that do not have the latest display driver, and no crashes occurred. Here are the specifics:
Thinkpad X240 [20AL]
Thinkpad T440p [20AN]
ThinkVantage Update Retriever 5.00.0007
Thinkvantage Thin Installer 1.2.0010
Intel HD Graphics Driver - gid634ww (10.18.10.3412)
Microsoft Lync 2013 SP1 32 Bit (15.0.4569.1503)
Error Message from Application Log:
Faulting application name: lync.exe, version: 15.0.4569.1503, time stamp: 0x52b0af33
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x00000879
Fault offset: 0x0000c42d
Faulting process id: 0x220c
Faulting application start time: 0x01cf707ca316ae96
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: C:\WINDOWS\syswow64\KERNELBASE.dll
Report Id: 9bb7c6e4-dc70-11e3-b695-5c514fb23d46
Any help or insight is greatly appreciated.
Thank you,
John
Solved!
Go to Solution.
Just as an updated to this:
I'm still waiting on updated drivers to fix the issue, however, there is a workaround. If you disable Desktop Composition screen sharing will work.
Control Panel -> Performance and Information Tools -> Adjust Visual Effects -> Uncheck “Enable desktop composition
John
Similar Messages
-
Lync 2013 crashes when double-clicking on contact to send IM...
I have a 64 bit Windows 7 machine. I have Office 2010 and 2013 installed. I am able to successfully run Lync 2013 and login to the Lync Server and see my contacts and their statuses online. However, every time I double-click on a contact name to send
them an IM i get a message saying "Microsoft Lync has stopped working" and Lync shuts down and restarts. When I debug the error using Visual Studio 2010 I get an "Unhandled exception... Access violation" error.
Here is what I know so far... It has to do with some incompatibility with Office 2010, because when I uninstall Office 2010, Lync 2013 starts working properly. (However, I need Office 2010 installed for supporting my clients. <sigh>)
Here's is what I've done so far...
1. Uninstalled Office 2013 = Lync 2013 still crashes.
2. Uninstalled Office 2010 = Lync 2013 works fine now.
3. Reinstalled Office 2013 w/out Office 2010 present = Lync 2013 works fine.
4. Reinstalled Office 2010 followed by Office 2013 = Lync 2013 still crashes.
5. I've also delete the sip_ folder to have Lync recreate it = that doesn't work either.
I have also updated Lync 2013 to the latest version update provided by Microsoft, but nothing seems to help.
My Event Viewer says the following:
Faulting application name: lync.exe, version: 15.0.4675.1000, time stamp: 0x54629b57
Faulting module name: lync.exe, version: 15.0.4675.1000, time stamp: 0x54629b57
Exception code: 0xc0000005
Fault offset: 0x00f50000
Faulting process id: 0x1564
Faulting application start time: 0x01d024b896c56e36
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Report Id: 282d47fc-90ac-11e4-8ed2-14feb598d143
Any help will be greatly appreciated!!!Hi bihtime3,
I understand the inconvenience caused by this issue. I would like to confirm if you have tried the following scenarios.
1. Repairing Office 2013 after installing Office 2010.
2. Installing Office 2010 before installing Office 2013.
Best regards,
Eric -
Lync 2013 Crashes When Transferring From Response Group
Hello,
Seeing a very strange issue on a couple of our clients running Lync 2013. Whenever they transfer a call from their response group Lync will crash. Calls into their direct line will transfer just fine. Here are two of the event logs we have
seen from this.
Faulting application name: lync.exe, version: 15.0.4569.1503, time stamp: 0x52b0bd5c
Faulting module name: mso.dll, version: 15.0.4569.1506, time stamp: 0x52e0dcca
Exception code: 0xc0000005
Fault offset: 0x0000000001828520
Faulting process id: 0x1550
Faulting application start time: 0x01cf4766655f5ead
Faulting application path: C:\Program Files\Microsoft Office\Office15\lync.exe
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office15\mso.dll
Report Id: cbd75420-b38c-11e3-ae5c-0026b9dd72ee
Faulting application name: lync.exe, version: 15.0.4569.1503, time stamp: 0x52b0bd5c
Faulting module name: LyncDesktopViewModel.dll, version: 15.0.4569.1503, time stamp: 0x52b0c3a2
Exception code: 0xc0000005
Fault offset: 0x0000000000119795
Faulting process id: 0xee0
Faulting application start time: 0x01cf4757f9b12418
Faulting application path: C:\Program Files\Microsoft Office\Office15\lync.exe
Faulting module path: C:\Program Files\Microsoft Office\Office15\LyncDesktopViewModel.dll
Report Id: 9db0d18d-b359-11e3-ae5c-0026b9dd72ee
We have tried a number of things this to get this working, but nothing has worked.
Installed Office 2013 SP1
Completely re imaged the client's computers
Deployed new Polycom Lync phones
Completely removed clients from their response group and the Lync server and added them back
I'm not sure where to go from here or what might be causing this. I would appreciate any thoughts you might have. Thank you!By default, calls from Response Groups ignore call forwarding or simultaneous ring settings.
Lisa Zheng
TechNet Community Support -
Lync 2013 Crashes when presenters switch
I am running Windows 7 on a 64 HP Workstation, Lync 2013, Lync 2010 Server. When the presenter changes in a Lync meeting. Lync crashes hard, sometimes requiring a computer reboot. Windows Reports the following event error.
0
APPCRASH
Not available
0
lync.exe
15.0.4623.1000
5372814c
nvwgf2um.dll
9.18.13.668
5057781b
c0000005
0062022f
C:\Users\bzf9lm\AppData\Local\Temp\WER191D.tmp.WERInternalMetadata.xml C:\Users\bzf9lm\AppData\Local\Temp\WER1FF1.tmp.appcompat.txt C:\Users\bzf9lm\AppData\Local\Temp\WER2197.tmp.hdmp C:\Users\bzf9lm\AppData\Local\Temp\WER2D5B.tmp.mdmp
C:\Users\bzf9lm\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_lync.exe_cffcb765e1a532e26945899b4b55bbe99bff6e75_cab_2fc22ecf
0
646feb4e-3cfb-11e4-a673-10604b5c4584
36
The nvwgf2um.dll is a video driver from Nvidea. A colleague had the same Lync issue and his Intel Video driver on his computer was the reported file that caused his Lync 2013 client to crash. He has a different video card in his computer.
What cause Lync 2013 to crash. We both are using 15.0.4623.1000 version of Lync 2013Try to update to the latest Lync 2013 client version.
Try the latest update from september.
http://support.microsoft.com/kb/2889860
regards Holger Technical Specialist UC -
Connect crashes when sharing desktop Mac
User on a Mac with latest Connect Add In which crashes when attempting to share the Desktop..
Any ideas???I have the same problem:
Signature du problème :
Nom d’événement de problème: APPCRASH
Nom de l’application: lync.exe
Version de l’application: 15.0.4675.1000
Horodatage de l’application: 54629b81
Nom du module par défaut: ntdll.dll
Version du module par défaut: 6.1.7601.18247
Horodateur du module par défaut: 521ea8e7
Code de l’exception: c0000005
Décalage de l’erreur: 0004378b
Version du système: 6.1.7601.2.1.0.256.1
Identificateur de paramètres régionaux:
1036
Informations supplémentaires sur le problème :
LCID: 1033
Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c
Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt
Could anybody help? When I intend to share screens or receive a file or send one with Lync, the App crashes...
anybody in Microsoft who could help? Thks.
Pedro -
Lync 2013 crashes when video preview or video is loading
Hey all,
For my work I have Office 365 (tried 32bit and 64bit) and this is installed on my windows 8.1 laptop of Dell. There are no problem using the software. But when I'm running lync and on purpose or by accidant go over the video icon in a conversation,
my lync freezes and after a while it wants to restart. The other microsoft voip software (Skype) does not have this issue and works perfectly. Also it is possible to open my video settings, the webcam will show everything like it should. Only hovering the
video icon in a chat is enough to make lync crash. For my work I'm really relying on lync., so I hope ther is a solution for this problem.
The webcam is a Quanta H.264 Integrate Webcam and it was working on a combination of earlier versions of windows and lync.
With some my colleagues (same laptop) running earlier version of windows there are no issues.
Is there some way to fix this problem?
thanks,Mostly this problem is related with video driver.
Please try to update your video driver.
Lisa Zheng
TechNet Community Support -
Lync 2013 crashes on startup in Windows 8.1 on Dell latitude E6520 machines
Lync 2013 crashes on startup in Windows 8.1 on Dell latitude E6520 machines. Every E6520 with windows 8.1.
Error message is:
Log Name: Application
Source: Application Error
Date: 4/15/2014 3:54:06 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ***
Description:
Faulting application name: lync.exe, version: 15.0.4420.1017, time stamp: 0x5067326f
Faulting module name: igdumd32.dll_unloaded, version: 9.17.10.3517, time stamp: 0x532b0b5b
Exception code: 0xc0000005
Fault offset: 0x00001040
Faulting process id: 0x10a0
Faulting application start time: 0x01cf58ecd02118cc
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: igdumd32.dll
Report Id: 14b4ce16-c4e0-11e3-8255-8c705a44a074
Faulting package full name:
Faulting package-relative application ID:
Video driver in the image was originally out of date, changed the driver to the latest and greatest available straight from Intel for the Intel HD 3000 graphics card and this error still appears. Driver 9.17.10.3517 exceeds the minimum requirement
for Lync 2013. The faulting module is related to the graphics driver, but reinstalling does nothing, uninstalling and then reinstalling does nothing, it cannot further be upgraded. This same error affects all the Dell latitude e6520's. It
also only occurs in Windows 8.1. The windows 7 image using the exact same driver version (both the outdated driver and latest driver) works just fine with Lync 2013.
Running Lync with administrative permissions does nothing, disabling hardware acceleration did nothing. None of our laptops come with the bluetooth adapter, and also updated all other drivers such as chipset and soundcard. Error occurs on the
RTM version of Lync, and Lync with SP1 fully updated. The rest of Office 2013 works fine. I am currently at a loss here short of telling the help desk to not image E6520's with Windows 8.1 because Lync 2013 doesn't work on it. But there has
to be a reason for it. Calling out for some suggestions here.
Thanks!We also have the same issue with Dell E6420 running Windows 8.1. Lync application does not respond after start-up. Did you try looking for the error file under
C:\users\username\appdata\local\Microsoft\Windows\WER\Reportarchive
it should create file like AppHang_lync.exe_some numbers. search for the latest one.
Interesting, I don't have any 6420's handy but figured the issue would exist on those also. I looked up the location you mention and see many crash logs for Lync. Not really sure what the error is, just says it stopped working.
Version=1
EventType=BEX
EventTime=130420688460358806
ReportType=2
Consent=1
UploadTime=130420688461296414
ReportIdentifier=14b4ce17-c4e0-11e3-8255-8c705a44a074
IntegratorReportIdentifier=14b4ce16-c4e0-11e3-8255-8c705a44a074
WOW64=1
Response.BucketId=3a18275b4e359a3d32b33b327b07846b
Response.BucketTable=5
Response.LegacyBucketId=81648064370
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=lync.exe
Sig[1].Name=Application Version
Sig[1].Value=15.0.4420.1017
Sig[2].Name=Application Timestamp
Sig[2].Value=5067326f
Sig[3].Name=Fault Module Name
Sig[3].Value=igdumd32.dll_unloaded
Sig[4].Name=Fault Module Version
Sig[4].Value=9.17.10.3517
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=532b0b5b
Sig[6].Name=Exception Offset
Sig[6].Value=00001040
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=00000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
UI[3]=Microsoft Lync 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 (x86)\Microsoft Office\Office15\lync.exe
LoadedModule[1]=C:\windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\windows\system32\apphelp.dll
LoadedModule[5]=C:\windows\SYSTEM32\ADVAPI32.dll
LoadedModule[6]=C:\windows\SYSTEM32\ole32.dll
LoadedModule[7]=C:\windows\SYSTEM32\OLEAUT32.dll
LoadedModule[8]=C:\windows\SYSTEM32\MSVCR100.dll
LoadedModule[9]=C:\Program Files (x86)\Microsoft Office\Office15\LyncModelProxy.dll
LoadedModule[10]=C:\Program Files (x86)\Microsoft Office\Office15\LyncDesktopViewModel.dll
LoadedModule[11]=C:\Program Files (x86)\Microsoft Office\Office15\PropertyModel.dll
LoadedModule[12]=C:\Program Files (x86)\Microsoft Office\Office15\PropertyModelProxy.dll
LoadedModule[13]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMvrAs.dll
LoadedModule[14]=C:\windows\SYSTEM32\MSVCP100.dll
LoadedModule[15]=C:\windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.16384_none_dadf89385bc5c7d7\gdiplus.dll
LoadedModule[16]=C:\windows\SYSTEM32\IMM32.dll
LoadedModule[17]=C:\windows\SYSTEM32\MSIMG32.dll
LoadedModule[18]=C:\windows\SYSTEM32\DWrite.dll
LoadedModule[19]=C:\windows\SYSTEM32\msvcrt.dll
LoadedModule[20]=C:\windows\SYSTEM32\sechost.dll
LoadedModule[21]=C:\windows\SYSTEM32\RPCRT4.dll
LoadedModule[22]=C:\windows\SYSTEM32\combase.dll
LoadedModule[23]=C:\windows\SYSTEM32\GDI32.dll
LoadedModule[24]=C:\windows\SYSTEM32\USER32.dll
LoadedModule[25]=C:\windows\SYSTEM32\MSVCR110.dll
LoadedModule[26]=C:\Program Files (x86)\Microsoft Office\Office15\RtmPal.dll
LoadedModule[27]=C:\Program Files (x86)\Microsoft Office\Office15\RtmCodecs.dll
LoadedModule[28]=C:\windows\SYSTEM32\dxva2.dll
LoadedModule[29]=C:\windows\SYSTEM32\d3d9.dll
LoadedModule[30]=C:\windows\SYSTEM32\d3d11.dll
LoadedModule[31]=C:\windows\SYSTEM32\MSCTF.dll
LoadedModule[32]=C:\windows\SYSTEM32\SspiCli.dll
LoadedModule[33]=C:\windows\SYSTEM32\WINMM.dll
LoadedModule[34]=C:\windows\SYSTEM32\WS2_32.dll
LoadedModule[35]=C:\windows\SYSTEM32\PSAPI.DLL
LoadedModule[36]=C:\windows\SYSTEM32\POWRPROF.dll
LoadedModule[37]=C:\windows\SYSTEM32\pdh.dll
LoadedModule[38]=C:\windows\SYSTEM32\MSVCP110.dll
LoadedModule[39]=C:\windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[40]=C:\Program Files (x86)\Microsoft Office\Office15\dbghelp.dll
LoadedModule[41]=C:\windows\SYSTEM32\bcrypt.dll
LoadedModule[42]=C:\windows\SYSTEM32\SETUPAPI.dll
LoadedModule[43]=C:\windows\SYSTEM32\WTSAPI32.dll
LoadedModule[44]=C:\windows\SYSTEM32\PROPSYS.dll
LoadedModule[45]=C:\windows\SYSTEM32\VERSION.dll
LoadedModule[46]=C:\windows\SYSTEM32\dwmapi.dll
LoadedModule[47]=C:\windows\SYSTEM32\dxgi.dll
LoadedModule[48]=C:\windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[49]=C:\windows\SYSTEM32\WINMMBASE.dll
LoadedModule[50]=C:\windows\SYSTEM32\NSI.dll
LoadedModule[51]=C:\windows\SYSTEM32\WINNSI.DLL
LoadedModule[52]=C:\windows\SYSTEM32\CFGMGR32.dll
LoadedModule[53]=C:\windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[54]=C:\windows\SYSTEM32\DEVOBJ.dll
LoadedModule[55]=C:\windows\SYSTEM32\nvinit.dll
LoadedModule[56]=C:\PROGRA~2\Sophos\SOPHOS~1\SOPHOS~1.DLL
LoadedModule[57]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
LoadedModule[58]=C:\windows\SYSTEM32\d2d1.dll
LoadedModule[59]=C:\windows\system32\uxtheme.dll
LoadedModule[60]=C:\windows\SYSTEM32\WINSTA.dll
LoadedModule[61]=C:\windows\SYSTEM32\SHELL32.dll
LoadedModule[62]=C:\windows\SYSTEM32\SHLWAPI.dll
LoadedModule[63]=C:\windows\SYSTEM32\shcore.dll
LoadedModule[64]=C:\windows\SYSTEM32\kernel.appcore.dll
LoadedModule[65]=C:\Program Files (x86)\Microsoft Office\Office15\Uc.dll
LoadedModule[66]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMvrCs.dll
LoadedModule[67]=C:\windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[68]=C:\windows\SYSTEM32\HID.DLL
LoadedModule[69]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.16384_none_a9f4965301334e09\Comctl32.dll
LoadedModule[70]=C:\windows\SYSTEM32\msi.dll
LoadedModule[71]=C:\Program Files (x86)\Microsoft Office\Office15\1033\lyncDesktopResources.dll
LoadedModule[72]=C:\windows\SYSTEM32\DavClnt.DLL
LoadedModule[73]=C:\windows\SYSTEM32\DAVHLPR.dll
LoadedModule[74]=C:\windows\SYSTEM32\d3d10_1.dll
LoadedModule[75]=C:\windows\SYSTEM32\d3d10_1core.dll
LoadedModule[76]=C:\windows\SYSTEM32\D3D10Warp.dll
LoadedModule[77]=C:\windows\SYSTEM32\sppc.dll
LoadedModule[78]=C:\windows\SYSTEM32\Secur32.dll
LoadedModule[79]=C:\windows\SYSTEM32\clbcatq.dll
LoadedModule[80]=C:\Program Files (x86)\Microsoft Office\Office15\UccApi.dll
LoadedModule[81]=C:\Program Files (x86)\Microsoft Office\Office15\Win32MsgQueue.dll
LoadedModule[82]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.16384_none_7c55c866aa0c3ff0\Comctl32.dll
LoadedModule[83]=C:\Program Files (x86)\Microsoft Office\Office15\1033\ocapires.dll
LoadedModule[84]=C:\Program Files (x86)\Microsoft Office\Office15\Psom.dll
LoadedModule[85]=C:\Windows\SYSTEM32\msxml6.dll
LoadedModule[86]=C:\Program Files (x86)\Microsoft Office\Office15\OcImport.DLL
LoadedModule[87]=C:\Program Files (x86)\Microsoft Office\Office15\ocrec.dll
LoadedModule[88]=C:\windows\system32\mlang.dll
LoadedModule[89]=C:\windows\SYSTEM32\usp10.dll
LoadedModule[90]=C:\windows\system32\windowscodecs.dll
LoadedModule[91]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMediaManager.dll
LoadedModule[92]=C:\windows\SYSTEM32\AVRT.DLL
LoadedModule[93]=C:\Program Files (x86)\Microsoft Office\Office15\AppSharingMediaProvider.dll
LoadedModule[94]=C:\Program Files (x86)\Microsoft Office\Office15\RTMPLTFM.dll
LoadedModule[95]=C:\windows\SYSTEM32\WINTRUST.dll
LoadedModule[96]=C:\windows\SYSTEM32\CRYPT32.dll
LoadedModule[97]=C:\windows\SYSTEM32\MSASN1.dll
LoadedModule[98]=C:\ProgramData\Sophos\Web Intelligence\swi_ifslsp.dll
LoadedModule[99]=C:\windows\system32\mswsock.dll
LoadedModule[100]=C:\windows\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[101]=C:\windows\SYSTEM32\dhcpcsvc.DLL
LoadedModule[102]=C:\windows\SYSTEM32\wlanapi.dll
LoadedModule[103]=C:\windows\System32\MMDevApi.dll
LoadedModule[104]=C:\windows\SYSTEM32\MFPlat.dll
LoadedModule[105]=C:\windows\SYSTEM32\RTWorkQ.DLL
LoadedModule[106]=C:\Program Files (x86)\Intel\Media SDK\mfx_mft_h264ve_32.dll
LoadedModule[107]=C:\windows\SYSTEM32\EVR.dll
LoadedModule[108]=C:\windows\system32\NV\nvumdshim.dll
LoadedModule[109]=C:\windows\system32\nvd3dum.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Microsoft Lync
AppPath=C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
ApplicationIdentity=00000000000000000000000000000000 -
IMovie 10.0 crash when sharing or just idle
My first attempt at using the MBP as advertised on Apple commercials: Putting together a string of iPhone videos.
When sharing iMovie just crashes. Now it just crashes when I launch it.
The top center part of the keyboard becomes really hot and the lines below seem to indicate a GPU driver or hardware problem.
Concerning? Should I get my hardware checked out? This baby is 10 days old.
This is when iMovie crashes when sharing via email or file:
Process: iMovie [353]
Path: /Applications/iMovie.app/Contents/MacOS/iMovie
Identifier: com.apple.iMovieApp
Version: 10.0 (237802)
Build Info: iMovieX-23780002028000000~1
App Item ID: 408981434
App External ID: 84014429
Code Type: X86-64 (Native)
Parent Process: launchd [159]
Responsible: iMovie [353]
User ID: 501
Date/Time: 2013-11-10 15:38:52.689 -0500
OS Version: Mac OS X 10.9 (13A3017)
Report Version: 11
Anonymous UUID: 5DCD2C3D-0FFD-C30D-1E5E-4AE2D127BE69
Crashed Thread: 27 Dispatch queue: opencl_runtime
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x0000001f
This is when iMovie crashes when idle or just started:
Process: iMovie [419]
Path: /Applications/iMovie.app/Contents/MacOS/iMovie
Identifier: com.apple.iMovieApp
Version: 10.0 (237802)
Build Info: iMovieX-23780002028000000~1
App Item ID: 408981434
App External ID: 84014429
Code Type: X86-64 (Native)
Parent Process: launchd [159]
Responsible: iMovie [419]
User ID: 501
Date/Time: 2013-11-10 15:44:22.858 -0500
OS Version: Mac OS X 10.9 (13A3017)
Report Version: 11
Anonymous UUID: 5DCD2C3D-0FFD-C30D-1E5E-4AE2D127BE69
Crashed Thread: 7 Dispatch queue: opencl_runtime
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x0000001f
Thread 0:: Dispatch queue: com.apple.main-threadI still have the same problem, even after the 10.0.1 update.
Should I bring the computer back? Could it be that the gfx card is overheating?
Process: iMovie [2832]
Path: /Applications/iMovie.app/Contents/MacOS/iMovie
Identifier: com.apple.iMovieApp
Version: 10.0.1 (239055)
Build Info: iMovieX-23905005031000000~1
App Item ID: 408981434
App External ID: 141822634
Code Type: X86-64 (Native)
Parent Process: launchd [280]
Responsible: iMovie [2832]
User ID: 501
Date/Time: 2013-11-24 12:31:14.182 -0500
OS Version: Mac OS X 10.9 (13A3017)
Report Version: 11
Anonymous UUID: 5DCD2C3D-0FFD-C30D-1E5E-4AE2D127BE69
Sleep/Wake UUID: B58E1205-533A-4E38-B656-01B76B8BAF99
Crashed Thread: 25 Dispatch queue: opencl_runtime
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x0000001f -
Anyone know why Adobe X & Adobe XI Crashes my shared network printer driver when printing a PDF
Anyone know why Adobe X & Adobe XI Crashes my shared network printer driver when printing on a domain, this only happens when I print a PDF.
I then have to restart the print spooler to get my printouts sent to the printer. I am using a Windows 7 32 & 64 bit environment on a domain. Users who aren't on the domain experience no issues and their printer drivers remain online and not grayed out.
When I print a PDF using Foxit Reader or Nitro PDF then all works fine, the moment I open a PDF using Adobe Reader X or XI then the shared network printer driver bombs out and I am back restarting the print spooler. If we roll back to Adobe 9 then we dont have any issues.
When you create a local printer driver all works fine, the problem is we don't encourage local printer drivers due to security.
We use Ricoh printer drivers, the MPC5501 PCL5C, driver version 1.2.0.0 with PDK version 12.65. We have also tried the PCL6 printer driver and Universal printer driver. All give the same result. The printer uses Winiprint Print processor using RAW as the default data type.
We have contacted Adobe Global Support who advised that they cannot assist with this query as this is on a Domain environment and we have to contact our IT Department.
We would really appreciate some professional help here to get a fix for this issue in order to address potential future occurance'sTry to turn off any video acceleration on your graphic driver for your graphics card.
-
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. -
Sharpoint designer 2013 crashes when Workflow People/Group Selection after adding AAM
I have same issue as mention in this post. Sharpoint
designer 2013 Stopping when Workflow People/Group Selection. SharePoint designer crashing after selecting peopicker in workflow. This is happening after adding AAM url.
And also as answer mentioned My website has same thing. like http://<systemname> as
Default and http:\\mycompany.com as
intranet.
And aslo I opened in website in designer is http://<systemname> .
It used to work before I adding AAM url. Now it is not working.
ItsMeSri SP 2013 FoundationHi,
Please check ULS log for more information about error to help narrow down the issue.
If you find error message as "the service '/_vti_bin/spclaimproviderwebservice.svc' cannot be activated due to an exception during compilation, The exception message is: This collection already contains an address with scheme http, There can be
at most one address per scheme in this collection.
http://xblogs.kompas-xnet.si/post/SharePoint-Designer-2013-Crashing-when-using-select-peoplegroups-from-SharePoint-site.aspx
Then the issue might be caused by more than one IIS Site Binding in single web application.
Please firstly remove AAM settings following the steps below:
In IIS manager, remove the added url binding from IIS site for SharePoint web application.
In CA, remove url under AAM settings and execute IISReset. Now you can check if the issue is resolved.
If you need to configure AAM for your web application, please extend web application and set AAM on the extended web application.
Regards,
Rebecca Tu
TechNet Community Support -
Recently upgraded from 6 to 7 and now users are reporting that when sharing desktops there is a massive delay. Also recorded presentations frequently lock up or stutter and then restart from the beginning whereas in the past they were fine.
Any thoughts on this would be appreciated. ThanksWhen others control your desktop, it is unavoidable to see the flashing mouse pointer.
If you just want to share specific programs, you can choose share program only.
Lisa Zheng
TechNet Community Support -
Access 2013 crashed when I export a table from the access
Hi!
Access 2013 always crashed when I export a table from the access to the Database Symfoware.
1、The conditions of the Access 2013 crashed are the follows.
1)Create a table in the Access 2013.
2)Using the ODBC driver of the Database Symfoware to export the table from the access to the Database Symfoware.
2、The Environments are the follows.
1)Access 2013 X64(Version:15.0.4420.1017)
2)Win2008R2 X64
3)Symfoware V11.1 X64
3、The Application log from the Win2008R2 are follows.
ログの名前: Application
ソース: Application Error
日付: 2014/04/18 16:21:06
イベント ID: 1000
タスクのカテゴリ: (100)
レベル: エラー
キーワード: クラシック
ユーザー: N/A
コンピューター: WIN-29UTU2AIK6J
説明:
障害が発生しているアプリケーション名: MSACCESS.EXE、バージョン: 15.0.4420.1017、タイム スタンプ: 0x50674523
障害が発生しているモジュール名: ACECORE.DLL、バージョン: 15.0.4420.1017、タイム スタンプ: 0x506742b7
例外コード: 0xc0000005
障害オフセット: 0x0000000000171f36
障害が発生しているプロセス ID: 0xb6c
障害が発生しているアプリケーションの開始時刻: 0x01cf5ad638668c5b
障害が発生しているアプリケーション パス: C:\Program Files\Microsoft Office\Office15\MSACCESS.EXE
障害が発生しているモジュール パス: C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ACECORE.DLL
レポート ID: 00e87957-c6ca-11e3-ad2c-0050568d2ced
イベント 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-04-18T07:21:06.000000000Z" />
<EventRecordID>3442</EventRecordID>
<Channel>Application</Channel>
<Computer>WIN-29UTU2AIK6J</Computer>
<Security />
</System>
<EventData>
<Data>MSACCESS.EXE</Data>
<Data>15.0.4420.1017</Data>
<Data>50674523</Data>
<Data>ACECORE.DLL</Data>
<Data>15.0.4420.1017</Data>
<Data>506742b7</Data>
<Data>c0000005</Data>
<Data>0000000000171f36</Data>
<Data>b6c</Data>
<Data>01cf5ad638668c5b</Data>
<Data>C:\Program Files\Microsoft Office\Office15\MSACCESS.EXE</Data>
<Data>C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ACECORE.DLL</Data>
<Data>00e87957-c6ca-11e3-ad2c-0050568d2ced</Data>
</EventData>
</Event>
4、When the access crashed,I got the dump file .Then I use the Windbg got some information from the dump files.
The detailes are follows.
FAULTING_IP:
+58872faf03d6dd84
00000000`00000000 ?? ???
EXCEPTION_RECORD: 00000000001723c0 -- (.exr 0x1723c0)
ExceptionAddress: 000007fee3951f36 (ACECORE+0x0000000000171f36)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
FAULTING_THREAD: 00000000000010b8
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
PROCESS_NAME: MSACCESS.EXE
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ACECORE
FAULTING_MODULE: 0000000076eb0000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 506742b7
ERROR_CODE: (NTSTATUS) 0x80000003 - {
EXCEPTION_CODE: (NTSTATUS) 0x80000003 (2147483651) - {
MOD_LIST: <ANALYSIS/>
CONTEXT: 0000000000171ed0 -- (.cxr 0x171ed0)
rax=0000000001be3598 rbx=0000000000000000 rcx=01cf5d1b0f402a5c
rdx=0000000009cfad30 rsi=0000000006688ef0 rdi=0000000001be35d0
rip=000007fee3951f36 rsp=0000000000172490 rbp=00000000001727a0
r8=0000000009b409d0 r9=0000000006688ef0 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000001be19f0
r14=0000000009cfad30 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
ACECORE+0x171f36:
000007fe`e3951f36 4d3927 cmp qword ptr [r15],r12 ds:00000000`00000000=????????????????
Resetting default scope
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 000007fee395c095 to 000007fee3951f36
STACK_TEXT:
00000000`00172490 000007fe`e395c095 : ffffffff`ffffffff 00000000`00000000 00000000`01bddaa2 ffffffff`ffffffff : ACECORE+0x171f36
00000000`001727b0 000007fe`e388f8eb : 000007fe`e399dc10 000007fe`e399dc30 000007fe`e399dc50 00000000`000000f9 : ACECORE+0x17c095
00000000`00172b50 000007fe`e388f590 : 00000000`06688ef0 00000000`00000004 00000000`000000f9 00000000`00000000 : ACECORE+0xaf8eb
00000000`00172ba0 000007fe`e388f406 : 00000000`00000004 00000000`000000f9 00000000`11cb1130 00000000`000000f9 : ACECORE+0xaf590
00000000`00172c30 000007fe`e391aee7 : 00000000`00000000 00000000`00173198 00000000`06688ef0 00000000`11cb0998 : ACECORE+0xaf406
00000000`00172c70 000007fe`e3933a72 : 00000000`00400100 00000000`00000002 00000000`00000001 00000000`06688ef0 : ACECORE+0x13aee7
00000000`00172e50 000007fe`e384e5b1 : 00000000`00000000 00000000`11cb0020 00000000`06688ef0 00000000`00000001 : ACECORE+0x153a72
00000000`00172e90 000007fe`e38358d1 : 00000000`000007ff 00000000`06688ef0 00000000`01bd99f0 00000000`00000000 : ACECORE+0x6e5b1
00000000`00173280 000007fe`e38718eb : 00000000`000007ff 00000000`06688ef0 00000000`11cb0000 00000000`00000000 : ACECORE+0x558d1
00000000`00173340 00000001`3f3b0cd2 : 00000000`0a0945c0 00000000`000000fe 00000000`000007ff 00000000`00000000 : ACECORE+0x918eb
00000000`00173430 00000001`3f3b0b9b : 00000000`00173730 00000000`001741e0 00000000`065e5b00 00000000`00000100 : MSACCESS!CreateIExprSrvObj+0x16af32
00000000`00173630 00000001`3f3afcea : 00000000`00173730 00000000`00000000 00000000`00000000 00000000`065e5b00 : MSACCESS!CreateIExprSrvObj+0x16adfb
00000000`001736a0 00000001`3f983140 : 00000000`00174401 00000000`0a3235e0 00000000`0a319aa0 00000000`00179fc8 : MSACCESS!CreateIExprSrvObj+0x169f4a
00000000`00174290 00000001`3f3aabeb : 00000000`00000000 00000000`00000000 00000000`00179f38 00000000`00000000 : MSACCESS!FUniqueIndexTableFieldEx+0x26ab4
00000000`00174530 00000001`3f3a9670 : 00000000`001778e0 00000000`00179f38 00000000`00000031 00000000`00000000 : MSACCESS!CreateIExprSrvObj+0x164e4b
00000000`00177870 00000001`3f3a8c1b : 00000000`00000010 00000000`108c5990 003d0044`00570050 00000000`74ac3f69 : MSACCESS!CreateIExprSrvObj+0x1638d0
00000000`001779d0 00000001`3f5450df : 00000000`0a0945c0 00000000`0000009c 00000000`0a0945c0 00000000`00000000 : MSACCESS!CreateIExprSrvObj+0x162e7b
00000000`00179e30 00000001`3f64e915 : 00000000`43ed8000 00000000`00000000 00000000`3f800000 00000000`00000000 : MSACCESS!FillADT+0x5830b
00000000`0017c450 00000001`3f33b172 : 00000000`00000000 00000000`0006075e 00000000`0017e370 00000000`00000000 : MSACCESS!IdsComboFillOfActidIarg+0xaddf1
00000000`0017d730 00000001`3f33a9ef : 00000000`0017e0a0 00000000`00000b86 00000000`00000000 00000000`0fea0000 : MSACCESS!CreateIExprSrvObj+0xf53d2
00000000`0017d790 00000001`3f33a20c : 00000000`06620400 00000000`00000000 00000000`00000001 00000000`0017e420 : MSACCESS!CreateIExprSrvObj+0xf4c4f
00000000`0017e400 00000001`3f6019cd : 0071023b`007a000a 00000000`00374a30 00000000`00000005 00000000`0000000c : MSACCESS!CreateIExprSrvObj+0xf446c
00000000`0017e850 00000000`06706fd5 : e2504700`aa00ee81 00005d1b`0f2363ea 00000000`0017e9e0 00000001`3f200000 : MSACCESS!IdsComboFillOfActidIarg+0x60ea9
00000000`0017e8f0 00000000`0a30c378 : 00000000`00000000 00000000`00000008 00000000`067069ac 00000000`00000000 : 0x6706fd5
00000000`0017e960 00000000`00000000 : 00000000`00000008 00000000`067069ac 00000000`00000000 00000000`00000008 : 0xa30c378
FOLLOWUP_IP:
ACECORE+171f36
000007fe`e3951f36 4d3927 cmp qword ptr [r15],r12
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ACECORE+171f36
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ACECORE.DLL
STACK_COMMAND: .cxr 0x171ed0 ; kb
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS_80000003_ACECORE.DLL!Unknown
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/MSACCESS_EXE/15_0_4420_1017/50674523/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1
Followup: MachineOwner
5、Where the access crashed I used the ODBC trace to get the trace log of the ODBC API.
The ODBC API called by Access before it crashed are the follows.
I also ansysised the log,and I did not find any Abnormal.
Test 1174-10f0
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
6
SWORD
-8 <SQL_C_WCHAR>
PTR 0x00000000002C1F20 [
12] "LENGTH"
SQLLEN 62
SQLLEN * 0x00000000002C1E38 (12)
Test 1174-10f0
ENTER SQLGetData
HSTMT 0x0000000009F7C490
UWORD
10
SWORD
99 <SQL_C_DEFAULT>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x00000000002C1E38
Test 1174-10f0
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
10
SWORD
99 <SQL_C_DEFAULT>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x00000000002C1E38 (-1)
Test 1174-10f0
ENTER SQLFetch
HSTMT 0x0000000009F7C490
Test 1174-10f0
EXIT SQLFetch with return code 100 (SQL_NO_DATA_FOUND)
HSTMT 0x0000000009F7C490
Test 1174-10f0
ENTER SQLFreeStmt
HSTMT 0x0000000009F7C490
UWORD
0 <SQL_CLOSE>
Test 1174-10f0
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
0 <SQL_CLOSE>
6、I also did the test with the Access 2010,and with the Sql Srever/Oracle.
The results are the follows.
1) With the Access 2010(X86 or X64) and Access 2013 X86,it successes when I export the table to the DB Symfoware.But only with the Access 2013 X64,the Access crashed.
2)With the Access 2010(X86 or X64) and Access 2013(X86 or X64),using the Sql Srever/Oracle,it always successes .
According to all the descrived above, I wonder if it a bug of the Access2013 .
Could anyone can help me ?
Thanks for any help.George Zhao
Thank you for your help.
I have already install
the latest patches of the Office 2013.But it doesn't work.It is down also too. And ODBC
drive of Database Symfoware is the newest driver of the Database Symfoware. Now I wonder that
if it si a bug of the ODBC
drive of Database Symfoware,I should fix the bug,but I have analysised the odbc trace log and I do not find any wrongs ,so I think maybe it is a bug of the Access .
I have see many situations about the Access down on the internet . -
Lync 2013 Web App Sharing not working.
We are having a problem with Lync Web App 2013. Our external customers can open the meeting link and join the meeting without a problem. Once they are in the meeting an internal user begins the presentation by sharing his screen. The Lync
Web App just says "Loading..." for the external customer. The internal presenter sees this external customer continually change from "in collaboration session" to "not in collaboration session". The external customer
is never actually shown the screen share.
Other notes:
-->We tried this from an external wireless hotspot and it worked fine, thus, it seems something in this customer's company firewall that is blocking it.
-->We also tried sharing a powerpoint (we have a functional office web apps server), which produced the same results.
-->When we used the Lync 2010 Web App (before we upgraded to 2013), everything seemed to work fine, thus I am concluding that the 2013 Lync Web App (since it has more capabilities) is somehow trying to use more ports or something.
-->Internally, the Lync Web app works fine.
So, I assume something in the customer's company's firewall is blocking some access to Lync 2013 Web App. My question is: what needs to be enabled both on-premise and at the customer's side to access Lync 2013 Web App screen sharing and if the
company (for security reasons) doesn't want to open extra ports, is there some work around to force Lync Web App to use port 443 for screen sharing.
Thanks,
AdamThe ports 1024-65535 * are used for application sharing.
You can configure the port ranges for Lync clients.
http://technet.microsoft.com/en-us/library/jj204760.aspx
You can’t use 443 as port 443 is used for HTTPs.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
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!
Maybe you are looking for
-
IWeb 08 / Aperture 2 / MobileMe albums "No albums or movies available"
I've searched the forums and there doesn't seem to be a resolution for this. It seems the issue has been known about for quite some time now; hard to believe Apple is just ignoring this. basics: I created MobileMe albums via Aperture 2. I open iWeb '
-
Until a few weeks ago I have never had a problem opening more than one pdf at a time. Now Reader just shuts down when I try to do so. The same thing happens when I click on the yellow highlighted categories in settings. All the other categories open
-
How can I fix my iPhone? It doesn't turn on
I recently broke my home button. This morning I closed my phone/sleep and it wouldn't turn back on. I tried charging it for hours and I can't put it on recovery mode because the home button doesn't work. And, I can't restore it because it desn't show
-
Another New Quantum Bug.
Lately I sometimes have trouble turning off the VMS and Media Client boxes using the remotes. The light will go off, and then pop back on. Depending on when I get tired of pressing the STB button on the remote ( 5 times, 10 times), I'll go and use th
-
Help!! Circular Redirect error when submitting to iTunes
Howdo folks I'm really hoping someone can help me here, because I've totally run out of ideas trying to figure this out. I'm trying to submit my new podcast to iTunes, but when I type in the Feed URL (http://www.mifidpodcast.com/rss/feed.rss), I get