Somehow, the Application Event log count ended up to 18,446,744,073,709,551,499. This causes MMC snap-in to fail when I want to see the event using Event Viewer, giving a System.OverflowException (Value was either too large or too small for an Int64.). Any thoughts, or should I just clear the log?
Maybe it helps if you activate the option to override old eventlogs when the log is full. This should prevent you from loosing the newest log entries when reaching the limit.
To activate navigate to your eventlog and go to their settings. There you find an option to override old entries if the log is full.
Before clearing the Application log I first tried "Save All Events As...", but the file it produced was empty.
I then copied C:\Windows\System32\winevt\Logs\Application.evtx to my desktop and that file DID open correctly. Not great, but an acceptable work-around for my needs.
Related
Every time I'm going through an entire file searching of occurrences of a string, VS shows a poop-up notifying me about that. I've unchecked the option to continue that behavior at number of times - to no avail.
I went to options and unchecked it there as well (see image for verification) but every time I restart VS, the settings in back there - checked and unaffected. I'm out of ideas what to try to remedy it. (Googled it. I haven't found anything that I recognized as useful.)
Those settings are saved (when you close Visual Studio) in this registry key:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\Find
"ShowEndOfSearch"="1"
"ShowNoFound"="1"
"ShowAllReplacementsNotAllowed"="1"
"ShowSomeReplacementsNotAllowed"="1"
"ShowNoMore"="1"
"ShowFindStart"="1"
"ShowCancel"="1"
"ShowCancelBeforeReplacementsMade"="1"
"ShowReplaceInFilesWarning"="1"
Do you have access to that key? Try setting these values to "0" in regedit.
Is there an easy way of generating the memory dump for the crashed application?
I have a situation in which the customer received the code which is generating the crash, as the code itself has no signal handlers for the backtrace generation on abort I was wondering if there is an easy way of telling windows to generate the memory dump of the crashing application.
Ideal solution wouldn't involve the installation of the debug tools (or the code modification) but if this is not possible, it would be really helpful to know.
One simple way to dump memory when application crashes is by using windows taskmanager.
When ever an exception or an application error occurs windows pops up an memory dialog and shows the address location which was causing a crash.Before you click ok on the message box open Task Manger and right click on the crashed application and select Create Dump file.Take a look at the screen shot below.
Select the file
2)Another way of generating user mode dumps is by adding the following registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting >\LocalDumps\application.exe
application.exe should be replaced by the application name which is under scanner.
under this key following values can be added
DumpFolder
The path where the dump files are to be stored. If you do not use the default path, then make sure that the folder contains ACLs that allow the crashing process to write data to the folder.
For service crashes, the dump is written to service specific profile folders depending on the service account used. For example, the profile folder for System services is %WINDIR%\System32\Config\SystemProfile. For Network and Local Services, the folder is %WINDIR%\ServiceProfiles.
DumpCount
The maximum number of dump files in the folder. When the maximum value is exceeded, the oldest dump file in the folder will be replaced with the new dump file.
DumpType
Specify one of the following dump types:
0: Custom dump
1: Mini dump
2: Full dump
CustomDumpFlags
The custom dump options to be used. This value is used only when DumpType is set to 0.
The options are a bitwise combination of the MINIDUMP_TYPE enumeration values.
I have found the answer myself, the msdn specifies the debug registery in the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error\LocalDumps
The following values need to be set:
DumpFolder
DumpCount
DumpType
CustomDumpFlags
The extensive documentation is available here.
If the registers do not exist it is possible to create them manually and windows will pick it up.
Also this is possible without directly modifying the registry with following steps:
Click Start, and then click Control Panel.
Double-click System, and then click Advanced system settings.
Click the Advanced tab, and then click Settings under Startup and Recovery.
In the Write debugging information list, click Small memory dump (64k).
Almost every time I use the debug console I have to right click and tick "Log request and response bodies". It's so annoying to forget it from time to time and then have to redo whatever I did to trigger it; and it clears every time I close and open the console.
Is there any way, such as an about:config variable, to make it log these bodies by default? I would even recompile Firefox from sources to do this if someone can tell me where the default is set.
As far as I understand from the relevant issue, this is not something controlled by about:config and the value lives while the developer tools are opened.
How to change the default Firefox error console buffer size? The problem is that there isn't enough time to read messages: old ones get overridden by the newer messages.
I know this is an old one, but this came up as my top search and the setting can now be found in the about:config settings.
Type about:config into the address bar and select ok to the dragons.
type this into the filter
devtools.hud.loglimit.console
AMO :: DevPrefs
Can increase buffer size from the options panel of that addon:
(source: mozilla.net)
EDIT: There are two parts to this answer. The Console Service has one limit, which applies when the Error Console is closed. The Error Console has another limit, which applies when it is open. Normally these limits are both set to 250.
It is not useful to have the Console Service limit is higher than the Error Console limit, since you need to open the Error Console in order to view the errors, but in theory you can do this by debugging the Firefox executable and setting a breakpoint on xul!nsConsoleService::nsConsoleSerice and set mBufferSize to a larger value. Symbols to allow you to do this are available on the Mozilla symbol server.
You can increase the Error Console limit by editing the consoleBindings.xml file. This file is stored in one of the .jar files provided with Firefox (omni.jar in Firefox 4). Note that editing a .jar file will stop partial updates from working, instead the Firefox updater will reinstall the full updated version.
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.