Morning,
I don't know if anyone else has experienced the following.
Up until this morning my Windows 7/Visual Studio 2010 Ultimate/StyleCop 4.7.11.0 setup was working fine.
However when I booted my PC this morning, started Visual Studio 2010 and loaded a solution with stylecop enabled on various projects I found the IDE crashed when I tried to build any styelcop enabled projects. e.g. thjose with the following entries in .csproj
...
false
Removing these StyleCop entries from the .csproj files or uninstalling StyleCop "fixes" the problem on their own and allows me the build the solution. But re-instating the stlecop entries in the .csproj files and re-installing StyleCop v4.7.11.0 or v4.7.17.0 caused the problem to re-occur.
The only errors in the Event View referred to NTDLL.DLL
Faulting application name: devenv.exe, version: 10.0.40219.1, time stamp: 0x4d5f2a73
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc00000fd
Fault offset: 0x0002e17c
Faulting process id: 0x17d8
Faulting application start time: 0x01cd0cd0f8cd1730
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 56b93280-78c4-11e1-bef3-001cc0c2a2ac
or once CLR.dll
Faulting application name: devenv.exe, version: 10.0.40219.1, time stamp: 0x4d5f2a73
Faulting module name: clr.dll, version: 4.0.30319.239, time stamp: 0x4e181a6d
Exception code: 0xc00000fd
Fault offset: 0x00038b13
Faulting process id: 0x14c8
Faulting application start time: 0x01cd0cbf6cf79511
Faulting application path: c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: c82f5abd-78b2-11e1-b990-001cc0c2a2ac
I think I have answered my own question...
The change I did make but discounted was that I used the StyleCop Settings contextr menu option in Visual Studio to set settings file's to be merged with a parent settings file, e.g.:
Solution
Settings.StyleCop
Project1
Settings.StyleCop (merge with Solution\Settings.StyleCop)
the contents of the files were as follows:
Solution\Settings.StyleCop
<StyleCopSettings Version="105">
<GlobalSettings>
<StringProperty Name="LinkedSettingsFile">Settings.StyleCop</StringProperty>
<StringProperty Name="MergeSettingsFiles">Linked</StringProperty>
</GlobalSettings>
</StyleCopSettings>
Project\Settings.StyleCop
<StyleCopSettings Version="105">
<GlobalSettings>
<StringProperty Name="LinkedSettingsFile">..\Settings.StyleCop</StringProperty>
<StringProperty Name="MergeSettingsFiles">Linked</StringProperty>
</GlobalSettings>
</StyleCopSettings>
Deleting these Settings files solved the problem. Although I don't understand why. Could it be some form of circular reference in the merge/link settings?
Related
Microsoft Visual Studio 2019 shows a "Server Busy" dialog every time I open a dialog.
A Procmon search for devenv.exe finds at least 100 NO SUCH FILE entries for the following file:
C:\Users\jlavallet\AppData\Local\Microsoft\VSApplicationInsights\vstelf144292e-e3b2-4011-ac90-20e5c03fbce5\*.trn
FileInformationClass: FileBothDirectoryInformation
Filter: *.trn
I performed the search because I was following #Blaise's advice to the OP of this question: https://stackoverflow.com/a/39026817/969431
So now that I have found the offending file, what advice can you give me for resolving this issue?
UPDATE:
So I googled the path and filename and found this SO question: Visual Studio 2017 Enterprise installation stucks.
I tried the solution suggested by #Techrocket9, placing an empty TRN file in the folder.
I then started up Visual Studio again and tried to edit the Publish settings for a solution (this invokes a modal dialog) and as always, about five seconds later, I get that same "Server Busy" dialog:
I went back to Procmon and the NO SUCH FILE problem was gone but I decided to filter the remaining devenv.exe entries down to just those that were not SUCCESS or NO MORE FILES (this seemed innocuous). Here's what I have left:
Does anyone out there know what might be causing my Server Busy problem based on this information?
UPDATE 2
After multiple tries at reinstalling and working the issue through Microsoft here: https://developercommunity.visualstudio.com/t/com-returned-an-unexpected-error-code-details-are/1422343?from=email&viewtype=all, I cleared my Event Viewer Application Logs and isolated everything. The result was that I found this error message. Devenv.exe appears to be conflicting with my voice recognition software Nuance Dragon NaturallySpeaking 15. Since this is an accessibility issue, is there any chance that Microsoft will do something about this? What can I do?
Log Name: Application
Source: Application Error
Date: 5/14/2021 3:39:39 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DEVELOPMENT9.CC.Local
Description:
Faulting application name: devenv.exe, version: 16.9.31205.134, time stamp: 0x606b75b3
Faulting module name: textservice.dll, version: 15.61.200.14, time stamp: 0x5fb72e0e
Exception code: 0xc0000005
Fault offset: 0x00006644
Faulting process id: 0x3a40
Faulting application start time: 0x01d74900f8dd3c3e
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\devenv.exe
Faulting module path: C:\Program Files (x86)\Nuance\NaturallySpeaking15\Program\textservice.dll
Report Id: fa11cc8c-975c-42b8-af6a-3cd00b12dc7a
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-05-14T20:39:39.6605762Z" />
<EventRecordID>7267273707</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DEVELOPMENT9.CC.Local</Computer>
<Security />
<Data>devenv.exe</Data>
<Data>16.9.31205.134</Data>
<Data>606b75b3</Data>
<Data>textservice.dll</Data>
<Data>15.61.200.14</Data>
<Data>5fb72e0e</Data>
<Data>c0000005</Data>
<Data>00006644</Data>
<Data>3a40</Data>
<Data>01d74900f8dd3c3e</Data>
<Data>C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\devenv.exe</Data>
<Data>C:\Program Files (x86)\Nuance\NaturallySpeaking15\Program\textservice.dll</Data>
<Data>fa11cc8c-975c-42b8-af6a-3cd00b12dc7a</Data>
<Data>
</Data>
<Data>
</Data>
UPDATE 3:
So it turns out that the issue is some kind of conflict between Visual Studio 2019 and Nuance Dragon Professional Group 15. I am now working the problem with Microsoft and Nuance. If this has affected anyone besides me, you can follow the continued progress here: https://developercommunity.visualstudio.com/t/microsoft-visual-studio-2019-server-busy-every-tim/1416496?from=email&viewtype=all.
I am using VS2015 and trying to validate connection after importing publish profile generated by winhost, when I click on Validate connection VS2015 crashes.
I have tried cleaning up and rebuilding but hat didn't help, I have also restarted machine without any luck.
I have also enabled logging by running devenv /Log but can't make any sense out of ActivityLog.xml what went wrong exactly, I have uploaded it here
What went wrong with Visual Studio 2015 and how could I fix it?
UPDATE: I also tried resetting settings devenv /resetsettings but that didn't help.
EventLog shows following Error:
Faulting application name: devenv.exe, version: 14.0.24720.0, time stamp: 0x564ea97e
Faulting module name: clr.dll, version: 4.6.1063.1, time stamp: 0x5653653c
Exception code: 0xc0000005
Fault offset: 0x0007482d
Faulting process ID: 0x13f0
Faulting application start time: 0x01d17609c3c2b002
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report ID: 2fab7a5b-6003-417f-adb3-8f45ec987a72
Faulting package full name:
Faulting package-relative application ID:
Update2:
As per #magicandre1981 request. I ran procdump -ma -i C:\dumps from command line before doing anything else. Then ran VS2015, went to publish and clicked on Test connection when VS crashed, there was a .dmp file in C:\dumps. Here's zipped dump file
ok, the PDB is now online and I was able to look at the dzmp with Windbg. The crash (NULL_POINTER_READ_INVALID_POINTER_READ) happens at clr!MethodTableBuilder::CreateMethodChainHash+0x8a.
I have no idea how to fix it. Submit the issue to Microsoft via connect so that Microsoft can fix it with the Update 3.
Generally "Source Control Explorer" and "Team Explorer" windows can be opened but sometimes this windows cause crash independently. If it doesn't I try to get latest version but it crashes after downloading some files.
Non-controlled solutions work fine but if I can try to open a controlled solution VS crashes on loading solution.
This problem started today. I use Windows 10 but migrated from Windows 8.1 a couple of months ago. In this morning windows session could not start when I've entered my password to windows login screen. So I've resetted my computer by clicking reset button. But Windows 10 re-run its migration tool and I think that it repaired some applications. I checked the Programs and Features out then a lot of apps seems installed today.
Repaired my VS install from Programs and Features but it didn't solve. Tried WinThruster, it found issues over 1000 but it didn't solved, too.
VS adds these three logs together to event viewer when app crashes.
Error:
Fault bucket 128975310163, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: devenv.exe
P2: 12.0.40629.0
P3: 5590c8a4
P4: mscorlib
P5: 4.6.1038.0
P6: 5615c1ac
P7: 3b10
P8: 7
P9: System.InvalidProgramException
P10:
Attached files:
C:\Users\Onur\AppData\Local\Temp\WERF382.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WERFF3A.tmp.csv
C:\Users\Onur\AppData\Local\Temp\WERFF3B.tmp.appcompat.txt
C:\Users\Onur\AppData\Local\Temp\WERA2A.tmp.WERDataCollectionFailure.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_devenv.exe_d949c0dbc7d16a4f9e0b0cdb431782229fc6a1_5b0449f2_1c961310
Analysis symbol:
Rechecking for solution: 0
Report Id: 1b1069cb-61a5-4133-881d-e3ae5b11ae68
Report Status: 4105
Karma demeti (*): 944bc6d8e7edc70b70df076898124c29
(*) I translated from turkish but couldn't find the english equivalent of "Karma demeti" after googling. Maybe it can be "Mixed bucket".
Error:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidProgramException
Stack:
at Microsoft.TeamFoundation.VersionControl.Client.QueuedActionLimiter.DeliverAction(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
Info:
Faulting application name: devenv.exe, version: 12.0.40629.0, time stamp: 0x5590c8a4
Faulting module name: KERNELBASE.dll, version: 10.0.10586.0, time stamp: 0x5632da1c
Exception code: 0xe0434352
Fault offset: 0x000bd8a8
Faulting process id: 0x1ae4
Faulting application start time: 0x01d13672bb0a871a
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe
Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
Thanks in advance.
First, make sure you have upgraded both your TFS and VS to the latest edition of its version.
Then check whether you can reproduce this issue on another client machine, if the issue only occurs on your client machine, you can try resetting VS settings and add-in settings (devenv /ResetSettings) and (devenv /ResetSkipPkgs), try rebuilding all templates (devenv /setup).
If you already use the lasted Update, Update 5, you should report this crash on connect. You should also provide a crash dump. To do this you can configure Windows Error Reporting to generate dumps or install Procdump as post Mortem Debugger by running procdump -ma -i C:\dumps. Now repo your crash and if you got a dump, zip the dmp and attach it to the report.
I frequently have the following crash from cl.exe. This happens both when compiling and running other a help command on cl. This is happening on Windows Server 2008, but I think this happens sometimes on Windows XP also. This is occurring very frequently within Jenkins when when running waf configure.
I haven't been able to find anything online to fix this problem, although there are mentions of kernelbase.dll crashing in other programs.
Does anyone have any thoughts on how to avoid this problem?
Thanks
Log Name: Application
Source: Application Error
Date: 1/24/2012 4:25:51 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: cl.exe, version: 15.0.30729.1, time stamp: 0x488ef6ea
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
Exception code: 0x0eedfade
Fault offset: 0x0000b727
Faulting process id: 0xd74
Faulting application start time: 0x01ccdae720a1cbbd
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\cl.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 5e9f206e-46da-11e1-a28d-bc305bd1c68c
Event Xml:
1000
2
100
0x80000000000000
55240
Application
cl.exe
15.0.30729.1
488ef6ea
KERNELBASE.dll
6.1.7600.16385
4a5bdbdf
0eedfade
0000b727
d74
01ccdae720a1cbbd
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\cl.exe
C:\Windows\syswow64\KERNELBASE.dll
5e9f206e-46da-11e1-a28d-bc305bd1c68c
Check:
http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/05764562-0133-4e6d-a613-bfe1ec2f0c1d/.
This seems to be an issue with updated dlls. I would also suggest compiling your program outside of Jenkins just to be sure that it is not an issue with Jenkins (either paths, or anything else).
I've got an application we use at our company.
All of our Windows XP PCs and Windows 7 PCs use it.
I can run it in the debugger under Visual Studio 2008 and build the Installer that all of the other PCs use to install it with, but I can not get it to run after installing on my PC (the installation shows no errors).
Under Event Viewer > Windows Logs > Application, two (2) events are fired:
The Error thrown when I try to run the installed application:
Faulting application name: Suite.exe, version: 2.2.21.0, time stamp: 0x4d389f32
Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802
Exception code: 0xc00000fd
Fault offset: 0x00000000000076cf
Faulting process id: 0x1424
Faulting application start time: 0x01cbb8f485a2a9d8
Faulting application path: C:\Program Files\Aaon Coil Products, Inc\ACP Software Suite\Suite.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: c58bd590-24e7-11e0-b398-00248103a942
An Informational message fires up immediately after with Windows Error Reporting:
Fault bucket 28268826, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Suite.exe
P2: 2.2.21.0
P3: 4d389f32
P4: ntdll.dll
P5: 6.1.7600.16559
P6: 4ba9b802
P7: c00000fd
P8: 00000000000076cf
P9:
P10:
Attached files:
C:\Users\cp-jpool\AppData\Local\Temp\WER492A.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\cp-jpool\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Suite.exe_e131a0d577e0788f7db9b54fd53b35e27d8860e2_11df4dea
Analysis symbol:
Rechecking for solution: 0
Report Id: c58bd590-24e7-11e0-b398-00248103a942
Report Status: 0
This repeats every time I try to run the application I made with this PC ...on this PC, but no where else.
Could someone give me some idea of what's going on and how to fix it?
Do you get prompted to elevate Visual Studio when you run it?
If so, try running the app elevated.
Basically, isolate what's different between the two:
Can you run it in Visual Studio without debugging? Including when you set it to "Release"?
How about if you build and install it as "Debug" then start it and try to attach to it as it crashes? (You can set the JIT debugger via the registry here: http://msdn.microsoft.com/en-us/library/5hs4b7a6.aspx)
Good luck!
It turned out that my application uses a control that does not run on 64-bit environments.
Apparently, the debugger in VS2008 will not throw an error whenever one of these old style DLLs fails.