When I try starting Fiddler2 on my "windows 7 enterprise" box, I get this error message in a dialog box. What could be wrong ? I've tried uninstalling and reinstalling. I've probably restarted windows several times but even that doesn't seem to make a difference. Do I need to delete any files that might have been created during a previous aborted session ?
TITLE : fiddler startup aborted
message : fiddler appears to be running in this user account. Maybe in a terminal services session ?
This indicates that Fiddler's mutex cannot be created-- no lingering files or settings would cause this. If it repros after a reboot, then there's a problem elsewhere. Version 2.3.4.6 (https://www.fiddler2.com/dl/fiddler2alphasetup.exe) this blocking error is changed to a prompt.
Related
I have not found the solution to this problem:
Error: Apache shutdown unexpectedly.
This may be due to a blocked port, missing dependencies,
Apache-improper privileges, a crash, or a shutdown by another method.
Apache- Press the Logs button to view error logs and check
Apache- the Windows Event Viewer for more clues
Apache- If you need more help, copy and post this
Apache- entire log window on the forums
I have changed port numbers, dealt with firewall, and even installed the old version of xampp and suitecrm to import and export and nothing.
I am trying to enable some extensions in my php. If I want to initiate the changes I have to reset the apache server in XAMPP. But I just keep getting a window that says xampp-control.exe has stopped working and gives me options:
Debug Program
Close Program
Check Online for a Solution and Close Program
No matter which option I choose it will then give me this Application Error:
Exception EAccess in modele 'xampp-control.exe' at 001ABEFE. Access Violation at address 005ABEFE in module 'xampp-control.exe'. Read of address 00000042. I have read that I should just install a WAMPP server. Is there a way I can successfully reset the Apache Server?
Possible workarounds are listed on XAMPP's forum here
There are some possible workarounds:
Enable back the write privileges and to be aware of this potential issue
Modify the ini file with an editor the properties you need or
To run the XAMP Control panel as administrator
Running it as administrator worked for me.
For some reason as soon as I login into my PC, I get this error in Windows 7 Ultimate:
http://i51.tinypic.com/b9go6g.png
Any ideas how to get rid of this error and why is it poppoing up?
Find where this application came from (looking at the contents of files in c:\process and in the control panel will help, if not, you can search for that XXXX thing in the registry using regedit).
Then repair or reinstall it. Or uninstall it completely.
Or, if you're brave enough, debug it. For that you should start looking at the contents of the Windows event log and what Process Monitor(separate, downloadable tool) shows -- see what errors you get there for this process, they may give you some clues. Finally, you may even run it under a debugger (e.g. WinDbg, also separate from Windows and downloadable).
A message box periodically pops up with the title "Event Notification Application" and the text "Error in BIO read. Program will now exit"
Can anyone tell me what this error message is about? It occurs in a production environment and I have no idea where it's comming from.
Any clues very much appreciated!
We had this error message on an IBM xSeries and it was caused by the LSI MegaRAID Storage software. Use Process Explorer and check the properties of the pop up.
If it's actually BIO_read (with underscore), then it would be related to OpenSSL. Of course, whoever put the message there might have dropped the underscore - so I'd look for applications using the OpenSSL DLLs (libeay32.dll, libssl32.dll).
I've used Process Explorer to diagnose these issues before: start it when the message is showing, click the bullseye icon on the toolbar and hold it down, then drag over and release when the bullseye is on the target window. The process will be highlighted in the main program area. Also, check your Application event log for errors, and see if you have any services that are set for automatic startup that are not running after you close the error dialog.
For what it's worth, I'd bet this issue is related to an auto-updater for some software installed on your machine. Try to identify those auto-update services (I bet McAfee has one) and disable them for a time (if that's safe.) Only disable one at a time so you can be reasonably sure which one the culprit is; be sure to enable it if it is ruled out.
Best of luck!
Do you have norton installed? It seems to be related to Norton 2000's live update.
Try disabling that and see if the error goes away.
The culprit was some raid software.
I'm using VS2010 Beta 2 and I turned on .NET Framework source stepping, so I had to disable 'Just My Code'. But now the w3wp.exe process doesn't show up in the list of processes I can attach to. I've got both show all processes boxes ticked. Is this a bug or am I missing something?
Make sure you have the Show processes in all sessions checkbox checked!
Ok, I found how to make it work, I rebuilt the whole solution and it started seeing the process again. This doesn't make a whole lot of sense to me, but oh well.
I fixed this by clicking Debug > Start Debugging, then once it starts up click Stop Debugging. Then I returned to the Attach to Process dialog and W3WP was in the list again.
Are you sure that the w3wp.exe process didn't die while debugging? Does it show up in Task Manager?
I couldn't find the process because the web page was still showing an error dialog and hadn't finished processing.
Make sure you have ended the previous debugging session (and run the web code to the end).
Closing Visual Studio did not help, the same goes for restarting IIS and rebuilding the solution.
As long as I was, some weird way, still attached to w3wp it did not show up in the attach list. Once I made sure the web page had finished and no dialogs of any kind was open, w3wp returned again.
You might need to be a member of the Administrators/Local Admins group for your machine.
Had this happen to me on one of our VMs today. Closing, re-opening VS2010 made no difference, rebuilding the website (!) made no difference.
But I logged out, logged in as administrator, added myself to the Administrators group, logged out, logged back in as myself, and once every application was loaded up -- I could get w3wp.exe appearing in the processes list for attaching.
In the absence of some other confirmation, it is possible that the act of logging out/logging-in again did the trick all by itself.
Try restarting Visual Studio. This worked for me.