I am working on a very large MVC4 project.
Windows 7 64 bit, .NET Framework.4.5, Visual Studio 2012 Premium SP1
I work in a corporate environment and every night machines are updated. On 4/22 I left my machine on with VS running but not executing any code. On 4/23 in the morning I continued where I left off the night before. Machine response time seemed to be slow, so I rebooted. After the reboot I began getting this message when trying to debug:
Popup in VS: WebDev.WebServer40.exe has stopped working
Web page: This page can't be displayed
Fiddler displayed this message:
[Fiddler] The connection to 'localhost' failed.
Error: ConnectionRefused (0x274d).
System.Net.Sockets.SocketException No connection could be made because the target machine actively refused it [::1]:51043
The Windows Application log displays this error:
Faulting application name: WebDev.WebServer40.exe, version: 11.0.50727.1, time stamp: 0x5011ca7e
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b96f
Exception code: 0xc0000005
Fault offset: 0x000408a7
Faulting process id: 0x280
Faulting application start time: 0x01cf60dbe460d837
Faulting application path: C:\Program Files (x86)\Common Files\Microsoft Shared\DevServer\11.0\WebDev.WebServer40.exe
Faulting module path: C:\Windows\syswow64\ole32.dll
Report Id: 22f43805-cccf-11e3-866d-00270e269f58
NOTE: It looks like ole32.dll is implicated. Checking, I discovered that there is a known error in several versions, however, none of those versions exactly match 6.1.7601.17514 so I have been cautious about replacing it.
Working with networking engineers I determined that the issue is within VS. The app will run with Ctrl-F5 and WebDev.WebServer40.exe appears in the list of processes. Using F5 WebDev.WebServer40.exe appears briefly in the list of processes, then disappears as the error appears. Summoning the app from the browser works, too, however if I use F5 to try and debug WebDev.WebServer40.exe disappears from the list of processes.
I have tried the following:
Repaired .NET Framework 4.5.1
Cleared Visual Studio's temporary files
Operated other apps to determine if the cause is in the app. All other apps on my machine fail in the same way
Deleted browser cookies
Added/subtracted localhost entries in the Hosts file
Attempted to repair VS 2012 but that generates an error messages: (1) log files full and (2) some features were not installed
My associates and I are out of ideas and I am ready to completely uninstall VS2012 and reinstall, with all the time, effort and risk that entails unless someone else has a clearer idea of what might be happening and how to fix it.
Thanks in advance for any suggestions.
Thanks to Anthony and AlaN for your suggestions. It's important to check off possibilities with an error as vague as this one.
Microsoft support found the issue using the tttracing utility. A malware application had created a folder that contained: aecbbldsrvrc.dll.
...appdata\local\exction\aecbbldsrvrc.dll
That dll was getting added to the mix of dlls used for debugging. How that happens, I haven't a clue, yet. A Google search for aecbbldsrvrc.dll returns a lot of commentary.
And, btw, since I have disabled IPV6 and QOS on the network adapter I have noticed an improvement in network speed, thank you, Anthony!
Even i got the same error message in my application of MVC4
"webdev.webserver40.exe has stopped working" and throwing an stack overflow exception.
then you need to go through the code,check for the spellings used for proporties. change the spellings and check.
I found this article on the Microsoft forum.
http://social.msdn.microsoft.com/Forums/ro-RO/b2e47862-a7be-45c9-9569-c6e045bcda7d/webdevwebserver40exe-stops-responding-when-launching-specific-aspnet-web-app?forum=vsdebug
Maybe this is a problem worthy of posting on the ASP .NET forum? http://forums.asp.net/
Run SFC /Scannow
Reset IE via Tools>internet oprions>advanced >reset
Remove Temp ASP.net files (see: Can I safely delete the Temporary ASP.Net folder's contents?)
I had many "funny" issues worth my environment recently that wasn't even solved worth the win 8.1 update. The above tips solved my issues.
Update: I have also found this today:
Fix .NET 4.5/ 4.5.1 issues with Microsoft .NET Framework Repair Tool 1.2
http://betanews.com/2014/04/29/fix-net-4-5-4-5-1-issues-with-microsoft-net-framework-repair-tool-1-2/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed+-+bn+-+Betanews+Full+Content+Feed+-+BN
Related
After the installation of Office 365 on a Windows 7 PC, the Visual Studio 6 (VB6) debugger returns an error.
+ When you add a breakpoint and try to start debugging (F5) your code, the error pops right away.
+ Without breakpoint the error comes after clicking a button on a form.
The returned Exception Code: c0000005:
Problem signature:
Problem Event Name: BEX
Application Name: VB6.EXE
Application Version: 6.0.97.82
Application Timestamp: 403acf6c
Fault Module Name: StackHash_7e3b
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 07ba32ac
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 2060
Additional Information 1: 7e3b
Additional Information 2: 7e3beb1e9ccf6d519c5b994ca59a280f
Additional Information 3: 2ac0
Additional Information 4: 2ac004046dc496f347320c8826a4cbdc
Creating an exe file still works and the created exe file still works fine.
Any testimony of a working office 365 - visual studio 6 combination is helpful as it allows me to look for other (indirect) causes of the problem.
I don't have enough points to comment, so...
I'm a long time VB6 user and it has always been my experience that installing any version of Office from MS will usually cause severe problems with Visual Studio 6. This goes a long way back and I believe it is due to the thousands of changes that Office makes to the registry.
I have had some success fixing this problem in the past by:
Uninstall Office - reboot
Uninstall VS6 - reboot
Do a full registry clean (repeated runs with CCleaner or similar until there are no more issues detected)
Install Office - reboot
Install VS6 last
Cleaning the registry is the most important part. Office leaves behind a huge number of obsolete registry entries when uninstalled. Even though a full clean will catch a lot of them, it won't catch anywhere near all of them, so these orphan entries can still cause problems.
With at least with one version of Office, this process still didn't help. I was never able to use VS6 without problems again until I did a full OS reinstall without Office. Another version caused the VB6 IDE to crash immediately when opened, rendering it useless.
My ultimate solution was to ditch MS Office for OpenOffice. Since then, I've never had any problems with VS6 at all.
So the short of it is that MS Office and VS6 are not compatible, especially if VS6 is installed first.
(On a couple of occasions, I took snapshots of the registry before and after installing Office. One version (2007 I think) made over 12,000 changes to the registry. A later version (possibly 2012) made over 16,000 changes.)
I am teaching myself how to build websites using asp.net core/mvc6. For the same, I installed VS2015 update 3 community edition. I have extensive background with C# and .NET Framework, but not much with web applications
I am just trying to create a simple project and start debugging, but the debug mostly (say 90% times) fails with the below message
An error occurred attempting to determine the process id if the
{APPLICATION} which is hosting your application
You can reproduce my issue by following the below steps:
Create a new "ASP.NET CORE" application in visual studio, using default selections
Build the project successfully without errors or warnings
Click the "Start Debugging" button
I get the "Debug is starting" progressbar,
After that it mostly fails but sometimes succeeds in starting the debug session. When it fails, I get the below message.
When it succeeds I first get a dialog complaining about 64 bit debugging and then the debug session starts fine.
I have tried the below with no luck
I can run fine the website through Visual Studio without debugging.
I can also debug and run fine a .NET core console application from within VS.
I have Avira (antivirus) and ZoneAlarm (Firewall) installed on the machine where I am trying all this. I have tried exiting ZoneAlarm and stopping real-time protection on Avira and set my UAC to not prompt, and then try debugging, but no luck. I cannot uninstall those items for trying.
I have tried repairing VS2015.3. I have also tried uninstalling and installing cleanly VS2015.3.
If I follow the below steps, the debugger starts fine (sometimes with the 64 bit debugging warning). I am sure that attaching the debugger to the running website would also work fine:
Start Debugging using F5
Right click IIS Express and browse to the application quickly
The debug works fine, if I use the kestrel web-server
I have tried using ASP.NET Core 1.0.1 and 1.1.0.
Using IE instead of Chrome did not make any difference
I even tried using VS 2017 RC2
I would like to be able to debug without any "hacks" and also, get rid of the 64 bit slowness complains
It works fine in my VS2015.3 (version 14.0.25431.01) based on your steps and successful no matter how many times I debug it.
Please check your .NET Core version to make sure it is the latest version first. The latest version should be NET Core 1.0.3. You could get it from this link: https://www.microsoft.com/net/download/core
And according to the message when you could successful debugging, your are using some 3rd party networking software. So please make sure you closed all other programs when debugging.
In addition, I found you are debugging using Chrome. Please choose Internet Explorer to confirm whether this issue related to the Chrome.
I downloaded the ISO file of Microsoft Visual Studio 2013 Ultimate on the Microsoft MSDN website. I could install it on my home PC running Windows 8.1 without problems. However when I try to install it on my office PC running Windows 7 SP1, I get an error message. I even tried to install the "web installer" version, I always get the following error message:
In our case installing Sp1 for Windows 7 helped.
I was having the same problem (and it was killing me!). I solved it going to Control Panel > Programs > Programs and Features > Turn off windows features, then I Disabled Microsoft Framework 3.5 and then It worked! Of course, when you finished the installation, you should turn it on as it was before.
Hope this helps!
Bst Regards!
You may want to double check and ensure your video driver(s) are up to date, as there have been reports of the installer and the IDE crashing on startup, that are due to issues related to WPF's use of hardware acceleration.
I've seen a few issues resolved by disabling hardware acceleration via the registry key mentioned in the MSDN forum post : http://social.msdn.microsoft.com/Forums/vstudio/en-US/ee8e5918-877f-4399-9658-64e817d6ea1b/visual-studio-2013-crashes-on-setup?forum=vssetup.
Sincerely,
Having same problem. From the command line run the installer with /Full /Q. This will install it without the UI. A less than optimal solution if you want to change the default locations, but sometimes you just have to get it done.
Another solution to go through the installer with UI is to disable any hardware acceleration (and reenable it afterwards)
(windows 7) Go to Display, Screen Resolution, Advanced Settings, TroubleShoot, Change Settings
Set the slider for Hardware Acceleration to none, and accept.
The visual studio setup ui should be fine now.
For me, the problem was the stupid AMD 'Raptr' utility that installs with the AMD driver. Literally having this running was crashing the Visual studio installer:
From the Application Log viewer:
Faulting application name:
en_visual_studio_professional_2013_with_update_5_x86_web_install, version:
12.0.40629.0, time stamp: 0x544ac542
Faulting module name: ltc_game32-103398.dll, version: 1.0.0.1, time stamp:
0x560b0dcc
Exception code: 0xc0000417
Fault offset: 0x000aa069
Faulting process id: 0x2334
Faulting application start time: 0x01d1089e82a903a4
Faulting application path:
c:\Users[myusername]\Downloads\en_visual_studio_professional_2013_with_update_5_x86_web_installer_6815765.exe
Faulting module path: C:\PROGRA~2\Raptr\ltc_game32-103398.dll
Report Id: 6977618d-4f5f-40a2-b3a7-f34876626ea7
Faulting package full name:
Faulting package-relative application ID:
Seems utterly ridiculous, but as soon as I shut Raptr down, the installer worked fine.
Nothing like 2 days of fighting with the installer to figure this out.
Sigh.
I had issues installing VS2013 the log referred to framework 4.5 problems.
I attempted to fix this a number of times and then gave up.
I then went to Microsoft website 4.5.1 framework download and now its installed.
Hope that helps
Geoff
The web installer keeps crashing for me. The event log reported that the crash occurred in my graphics drivers (Intel HD Graphics). I am unable to update my graphics drivers, so that forced me to seek other means.
What solved it for me, was downloading the full ISO file for Visual Studio 2013, and installing using that. It seems it is either a separate build, or it doesn't touch the same execution-paths as the web installer.
Mine was faulting ltc_game32-96675.dll which is from the AMD Raptor overlay. Unloading that allowed me to install without crashing.
I have an intermittent issue when trying to debug local IIS sites.
Visual will hang and eventually displays the error:
The web server did not respond in a timely manner. This may be because another debugger is already attached to the web server
If I wait a minute and hit "Start Debugging" again it will work (sometimes I may get the error several times but it eventually works).
There is nothing in the Event Viewer around the times I try to debug.
The app pool is .net V4.0 Integrated.
I am running Windows 8 Pro with IIS 8 and Visual Studio 2010.
Also its a site using EpiServer 6 R2.
I have tried IISReset, stopping/starting the site, closing and reopening Visual, rebooting my machine. None of that seems to make a difference, its hit and miss whether the solution will debug or not.
Once the solution is debugging, it runs fine without issue. Until I stop debugging and try and start debugging again.
The site runs fine in all other aspects, its only when I try to debug.
So... I never fixed this issue, but have since upgraded to a solid state drive. So I now have a fresh install of Windows 8 Pro and Visual and the issue has not resurfaced.
All the sudden started getting the following error while trying to debug a worker role:
"Windows Azure Tools for Microsoft Visual Studio
There was an error attaching the debugger to the role instance 'deployment16(360)blah blah' with Process Id: '8780'. Unable to attach. The Microsoft Visual Studio Remote Debugging Monitor has been closed on the remote machine."
Restarting Visual Studio and the machine do not help.
As you start getting this problem all of sudden in your development machine something must have changed and it is mostly due to some of the OS auto-update and/or some application update you installed in your machine. There could be any random reason for this problem however if I would have hit the exact same problem here is what I would do to troubleshoot such issue:
To start, first thing is to just check it is not an application specific problem by creating a base app from web/worker template and see if that exhibit the problem.
If you have installed new release Windows Azure SDK 1.7 check with both SDK 1.6 and 1.7 to verify if both exhibit the problem.
Check if your could debug IIS based application as well outside Compute Emulator. This will isolate if the problem is specific to Windows Azure development Fabric or bind to your IIS itself.
If this is IIS specific issue, Check IIS configuration for all enabled functionalities, try resetting Application Pool configuration, running "ASPnet_regiis -i" etc to fix the issue.
If it is Windows Azure Computer Emulator specific, I know sometime OS updates may make application unstable so in that case, I will re-install .net 4.0 and VS2010 SP1 again respectively. (This does help so many time) then re-install Azure SDK 1.7 completely.
Such random problem mostly occur due to some change in your machine configuration, so restoring the VS2010 and the re-installing all other application does help to solve problems.
If you have an exception in the role's OnStart() or in Application_Start() that the debugger doesn't pick up, you may also receive this message. Application_Start() errors are especially pernicious because the debugger doesn't attach to the web process until after this method returns.
If you are wedded to cloud specific classes such as RoleEnvironment and cannot make the web role a startup project, you can use Ctrl-F5 to run the cloud project without debugging. With some luck you'll get a yellow screen of death to show you the true error.
Avkash covers the points.
I had the same issue recently. I set my web project as start-up rather than Azure and I discovered that that web project didn't actually run. Turned out somehow when of my projects was compiling for X64. I changed that and it worked.