I've enabled two step authentication on my Windows Live account. I then load Visual Studio 2013 and go to open an application (it uses TFS and I sign in to my account to access it).
I get a 'this application is not responding' message.
Faulting application name: devenv.exe, version: 12.0.30501.0, time
stamp: 0x5361f453 Faulting module name: KERNELBASE.dll, version:
6.3.9600.17055, time stamp: 0x532943a3 Exception code: 0xe0434352 Fault offset: 0x00011d4d Faulting process ID: 0x2d4c Faulting
application start time: 0x01cf8fec4ff9c2b7 Faulting application path:
C:\Program Files (x86)\Microsoft Visual Studio
12.0\Common7\IDE\devenv.exe Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll Report ID:
a096268c-fbdf-11e3-bfef-f46d049726f3 Faulting package full name:
Faulting package-relative application ID:
I've tried rebooting, signing out of my account within VS and signing back in.
As soon as I disable two step authentication then the problem goes away.
If I go to file - new project, it creates a new project. Just as it finished loading the new project I get the same error.
Has anyone experienced this before?
Thanks!
Related
I'm on a Surface Book 3 running Windows 10 build 21292, attempting to install the Sphere SDK downloaded from here. The Azure Sphere splash screen pops up when I run the exe, but immediately goes away. In Event Viewer, I see the following error with exception code 0xc0000005:
Faulting application name: Azure_Sphere_SDK_20_11.exe, version: 20.11.0.58388, time stamp: 0x5e17c1e6
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x006f0072
Faulting process id: 0x1c20
Faulting application start time: 0x01d6f00a874a864c
Faulting application path: C:\Users\rymcin\AppData\Local\Temp\{8D6BD41B-D05F-470D-97F4-D074C6E501D0}\.cr\Azure_Sphere_SDK_20_11.exe
Faulting module path: unknown
Report Id: 7064b0b0-caf1-4814-bdfb-ab2cde6421d1
Faulting package full name:
Faulting package-relative application ID:
I've tried rebooting, running the installer as admin, I've run the System File Checker (SFC), I've run chkdsk, no issues and no change. Everything else on this PC is working fine so I'm not sure where else to look.
Recently I've configured the dblink using OraOLEDB provider, the DBLINK was working, however when I'm trying to use distributed transaction on the DBLINK, my SQL Server service is crashed and when I traced the event viewer log, it produced me below information:
Faulting application name: sqlservr.exe, version: 2017.140.2027.2, time stamp: 0x5d04c374
Faulting module name: ntdll.dll, version: 10.0.18362.815, time stamp: 0xb29ecf52
Exception code: 0xc0000374
Fault offset: 0x00000000000f9229
Faulting process ID: 0x2504
Faulting application start time: 0x01d65806f5dbe7a2
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS02\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 5ebfb503-7d08-4ce5-8fc5-a002f3171d65
Faulting package full name:
Faulting package-relative application ID:
Has anyone faced this issue before? Mind to share with me? thanks.
I have created Visio (VSTO) Com Add-in.
After one of my users installed Visio 2016, Visio with the following error:
"Visio is running into problems with the '[add in name]' add-in.
If this keeps happening, disable this add-in and check the available updates.
Do you want to disable it now?"
I not sure it's got to do with Visio 2016 only, but we've tried reinstall both 32/64 bit
(on Windows 10 64 bit operating system)
**
Here's what I've seen in the "Event Viewer"
**:
Faulting application name: VISIO.EXE, version: 16.0.11328.20368, time stamp: 0x5d173494
Faulting module name: ntdll.dll, version: 10.0.17763.1158, time stamp: 0x67e7a2b6
Exception code: 0xc0000374
Fault offset: 0x000e0e03
Faulting process id: 0x2c58
Faulting application start time: 0x01d637f389d9c14d
Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\VISIO.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 3d86d759-b344-4d14-9487-1078fb895664
Faulting package full name:
Faulting package-relative application ID:
I've done deep debugging and the location is random,
but I have noticed that in many cases the crash is at "save" location:
this.Application.ActiveDocument.Save();
I've done lots of web research and so far didn't find meaningful information.
Can anyone help on this?
Maybe out of your scope but I had same error without Visio add-in or whatever
Fix this by going to File - Options - Advanced in Visio, and checking out the "Disable Enhanced Metafile optimization" box to disable this option, under Display
source : https://learn.microsoft.com/en-us/answers/questions/767543/visio-crashes-when-opening-file.html
worked fine for me
Rémi
I have a VB.net 2013 program compiled on a Windows 7 machine. The executable will not run on Windows 10. The application references a third-party COM component. I have an old VB6 program that uses the same component that runs fine on Windows 10 so I know that the .ocx file is registered.The event log shows the following error:
Faulting application name: TestOCX.exe, version: 1.0.0.0, time stamp: 0x5b065e47
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00001a5
Fault offset: 0x079b32a0
Faulting process id: 0xb4
Faulting application start time: 0x01d3f332b4651dda
Faulting application path: C:\Users\Val Macduff\AppData\Local\Apps\2.0\P44NCGBZ.EOJ\ONNATDJR.36P\test..tion_40667f0699a0b5ed_0001.0000_8fc40dff6b9f71d7\TestOCX.exe
Faulting module path: unknown
Report Id: 3be87708-a4c1-4166-90bc-680be71ed4bc
Faulting package full name:
Faulting package-relative application ID:
Followed by an Application failed to start error: 0xc0000005
The TestOCX program has a single form with the one COM control on it.
My question is: what is the best way to find out why this program won't run.
I wrote a VSTO application that runs perfectly fine in Windows 7. However, when running it on Windows 8, it will occasionally throw this error. I tried searching on the internet, but could not find anything.
Faulting application name: winproj.exe, version: 15.0.4517.1005, time stamp: 0x51b961d1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x0c047de0
Faulting process id: 0xc70
Faulting application start time: 0x01ce8964a6e2b407
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\winproj.exe
Faulting module path: unknown
Report Id: f71ab2f7-f557-11e2-be7c-001f2900a8e5
Faulting package full name:
Faulting package-relative application ID: