Thursday 16 October 2014

ZABBIX


Zabbix is an open source network monitoring tool that works with a centralized Linux-based Zabbix server. 
The Zabbix server automatically collects and parses data from monitored hardware so administrators can check availability and see trends in network performance. The server communicates to the native software agents that are available for many operating systems, including Linux, UNIX and Windows. For operating systems without an agent, generic monitoring protocols such as Simple Network Management Protocol (SNMP) or Intelligent Platform Management Interface (IPMI) can be used.
Zabbix can send out alerts and notifications if specific pre-defined events are occurring. It can also provide graphing functionality, which allows an administrator to get an overview of the current state of specific nodes and the network in general. Some of Zabbix's other features include automatic discovery for network hosts and devices, a web-based front end that allows full system control from a browser.
This video provides a quick look at the Zabbix user interface.

A NETWORK MANAGEMENT SYSTEM (NMS)

network management system (NMS) is a set of hardware and/or software tools that allow an IT professional to supervise the individual components of a network within a larger network management framework.

Network device discovery -  identifying what devices are present on a network.
Network management system components assist with: 
  • Network device monitoring - monitoring at the device level to determine the health of network components and the extent to which their performance matches capacity plans and intra-enterprise service-level agreements (SLAs).
  • Network performance analysis -  tracking performance indicators such as bandwidth utilization, packet loss, latency, availability and uptime of routers, switches and  other Simple Network Management Protocol (SNMP) -enabled devices.
  • Intelligent notifications - configurable alerts that will respond to specific network scenarios by paging, emailing, calling or texting a network administrator.

Wednesday 8 October 2014

How to fix a general protection fault

Note: It is not upcoming to randomly experience a General Protection Fault (GPF), you should not need to troubleshoot GPF errors unless they are occurring frequently.

Remove all TSRs

Disable or unload any TSRs or programs currently running before running the program causing the GPF.
  • How to remove TSRs and startup programs.

Delete all program temporary files

Delete all temporary files that may still be residing on the hard drive from currently or previously running programs.
  • How to remove temporary program files.

Run ScanDisk and Defrag

Run Scandisk and run Defrag on the hard drive as it could be possible your hard drive may have an issue causing the swap file or data files to become corrupt or invalid.

Verify your computer has more than 200 MB available

If your computer is running low on hard drive space, your Windows Swap File will be unable to increase in size when needed, causing programs to be swapped between memory and the hard drive more frequently. When this occurs it is more likely that a GPF can occur.
  • Determining available hard drive space.

Recently installed software or hardware

If you have recently installed new software or hardware uninstall or reinstall that software or hardware to verify it is not causing your issue.
  • Uninstalling Windows software.

Disable external cache

If your CPU utilizes external cache disable it temporarily to verify if it is causing your GPF error messages. If this option is available it can be disabled through CMOS Setup.
If this resolves your issue it is recommended that you contact the manufacturer of your computer, motherboard manufacturer, or CPU manufacturer for additional recommendations.
Tip: In some cases a BIOS update designed for this problem can also resolve cache related issues.

Disable Power Management and screen savers

If you are receiving GPFs when away from the computer or during durations when your computer is inactive, disable Power Management and screen savers to ensure that they are not causing your issue.
  • Power management help and support.

Operating System issue

Windows related files can cause a General Protection fault. For example, a General Protection Fault with Explorer and KRNL386.EXE. Reinstall Windows to resolve the issue with Windows related files.

Bad memory or other bad hardware

If you have followed all of the above recommendations and continue to experience GPFs there may be bad or failing hardware inside your computer. Often bad memory is the primary cause for random GPFs.
  • How can I test my memory to determine if it is bad?

Windows runtime errors

Before following the below recommendations for troubleshooting your runtime error if you're getting a runtime error with a runtime error code and error message such as "Runtime error 75 path/file access error", skip to the below runtime error listing for a listing of runtime error codes and additional information and causes for these errors.
Windows Runtime error

Confliction with TSR or other running program

If you are encountering a runtime error message while in Windows or above ensure that the issue is not being caused by a third-party program or TSR by end tasking all open programs.
If, after end tasking all TSRs, you continue to experience the same issue and are running Windows 95 or Windows 98, verify that no utility or program is being loaded in the autoexec.bat and config.sys that is causing your issue by temporally renaming the files. To do this, follow the instructions below.
  1. Boot to an MS-DOS prompt.
  2. Once at the MS-DOS prompt, type:

    cd\ <press enter>
    ren autoexec.bat autoexec.ch <press enter>
    ren config.sys config.ch <press enter>

    Once completed, reboot the computer.

Software issue

If your issue persists the program, utility, or game causing the runtime error may have issues. Verify through the developer's website that all updates or patches that may be available have been downloaded and applied.
If no patches or updates are available, uninstall, and reinstall the program that is causing the issue. If you are having a runtime error in your operating system, reinstall the operating system.

Add-on, plug-in, or other extra software

Many runtime errors are also caused by other add-ons, plug-ins, or other extra software that has been installed onto the computer and is associated with the program generating the error. If you have any extra software installed that is associated with the program generating the error make sure there are no available updates for the programs and try uninstalling each of them to verify they're not the cause of your issue.

Computer virus

Because computer viruses and malware can tamper with the system settings or memory it can cause a runtime error. If you are currently running a virus protection program on your computer ensure it has the latest updated patch or .dat file.
If you do not have a computer virus protection program it is recommended one be purchased or that a demo be temporarily downloaded to scan your computer hard drive for viruses.
  • Additional information about computer viruses can be found on our virus information page.

Memory issue

Finally, if you have followed all of the above recommendations and are still getting runtime errors, you may be encountering a hardware or memory related issue. We recommend that you first contact the developer of the program causing the issue for any possible solutions. If no solutions are found, we recommend you contact the computer or motherboard manufacturer for additional recommendations or service.
  • Out of memory errors.
  • Computer companies and contact information.

Runtime error listings

Below is a listing of Microsoft Windows and Windows software runtime error codes and related Runtime error messages. If you're encountering one of the below runtime error codes and have a matching runtime error message see the associated additional information column for causes and information about that runtime.
Code Runtime error Additional information
5 Illegal function call Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
6 Overflow Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
7 Out of memory This issue can be caused when the computer does not meet the programs system requirements or to much memory is already being used for the program to run. If your computer meets the requirements try first reinstalling the program to make sure it's not an issues with the program installation. If this does not resolve your issue see out of memory troubleshooting steps.
9 Subscript out of range Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
10 Duplicate definition Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
11 Division by zero Problem with a math formula in the program or the programs code. Verify no software updates are available for the program causing this error.
13 Type Mismatch Make sure your system regional settings are setup correctly and that the program you're running is made for your version of Windows.
14 Out of string space Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
19 No Resume Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
20 Resume without error Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
28 Out of stack space This issue can be caused by a program or memory error. First try going through the out of memory troubleshooting steps.
35 Sub or Function not defined Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
48 Error in loading DLL This issue is often caused with a bad installation or an issue caused after another program has been installed that replaced the programs DLL. Close all programs and TSRs and try installing the program again.
52 Bad file name or number Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
53 File not found File required by the program to run is not found. Program needs to be reinstalled or missing file(s) need to be copied back to the computer.
54 Bad file mode Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
55 File already open Program or file associated with program is being used and program does not have access to use it. Try closing all open and background programs and run program again.
58 File already exists Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
61 Disk full The disk, for example, the hard drive does not have enough space for the program to run or for associated files to be copied to. Free up disk space on the computer hard drive.
62 Input past end of file Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
63 Bad record number Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
64 Bad file name Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
68 Device unavailable A hardware device or necessary requirement for the program is not being found. Verify all hardware and software required by the program is installed. If you continue to have the same issues verify the latest updates are installed for the program as well as any hardware device the program needs.
70 Permission denied The location of where the program is being copied to does not have proper rights. Or a file that is trying to be copied over because it's currently being used. Try closing all programs and TSRs and running/installing the program again.
71 Disk not ready Verify you have proper rights to the location you are attempting to install the program to.
74 Can't rename with different drive Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
75 Path/File access error Program does not have rights or access to a file. Often this is caused when a program is trying to access a network file it doesn't have proper access to either because of network privileges or something is blocking the program. This issue can also be caused when the file is being used by another program or is read-only.
76 Path not found Directory of where the program needs to be copied to or files associated with the program need to be copied to is missing. Try reinstalling the program.
91 Object variable set to Nothing Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
93 Invalid pattern Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
94 Illegal use of NULL Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
102 Command failed Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
339 A file is missing or invalid An associated program file is missing or corrupt. Try reinstalling the program.
429 Object creation failed Program is corrupted, try reinstalling the program generating the runtime error.
438 No such property or method Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
439 Argument type mismatch Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
440 Object error Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
901 Input buffer would be larger than 64K Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
902 Operating system error Verify the program is compatible with your version of Windows and has any software updates.
903 External procedure not found Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
904 Global variable type mismatch Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
905 User-defined type mismatch A setting either in the program shortcut or being defined by the user is correct. Try running just the program without any additional settings or variables.
906 External procedure interface mismatch Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
1001 Out of memory This issue can be caused when the computer does not meet the programs system requirements or to much memory is already being used for the program to run. If your computer meets the requirements try first reinstalling the program to make sure it's not an issue with the program installation. If this does not resolve your issue run through the out of memory troubleshooting steps.
1025 DLL is not supported This issue is often caused with a bad installation or an issue caused after another program has been installed that replaced the programs DLL. Close all programs and TSRs and try installing the program again.
6025
Microsoft Windows r6025 runtime error.

Tuesday 7 October 2014

Formatting toolbar

The formatting toolbar is a toolbar in Microsoft Office applications such as Microsoft Word and Microsoft Excel that gives the user the ability to change the formatting of selected text.

Options available in the formatting toolbar

  • Change the font.
  • Change the size of the font.
  • Make the text bold, italics, or underline.
  • Change the justification.
  • Change the style to currency, percent, or comma.
  • Increase or decrease the decimal and indent.
  • Change the borders.
  • Fill (highlight) the text.
  • Change the font color.

How to enable the formatting toolbar

If you are running an early version of Word or Excel click View and then Toolbars and from within the Toolbars click Formatting to enable the formatting toolbar.
New versions of Office products no longer have toolbars and instead are using the Ribbon and most of what was found in the Formatting toolbar can now be found in the Home or Write tab of the Ribbon.

Computer POST and beep codes

The computer power-on self-test (POST) tests the computer to make sure it meets the necessary system requirements and that all hardware is working properly before starting the remainder of the boot process. If the computer passes the POST, the computer gives a single beep (with some computer BIOS manufacturers it may beep twice) as it starts up and will continue to start normally. However, if the computer fails the POST, the computer will either not beep at all or will generate a beep code, which tells the user the source of the problem.
If you're receiving an irregular POST or a beep code not mentioned below, follow the POST troubleshooting steps to determine the failing hardware component.
AMI BIOS beep codes
Award BIOS beep codes
Dell beep codes
IBM BIOS beep codes
Macintosh startup tones
Phoenix BIOS beep codes
Motherboard help

AMI BIOS beep codes

Below are the AMI BIOS Beep codes that can occur. However, because of the wide variety of different computer manufacturers with this BIOS, the beep codes may vary.
Beep Code Descriptions
1 short DRAM refresh failure
2 short Parity circuit failure
3 short Base 64K RAM failure
4 short System timer failure
5 short Process failure
6 short Keyboard controller Gate A20 error
7 short Virtual mode exception error
8 short Display memory Read/Write test failure
9 short ROM BIOS checksum failure
10 short CMOS shutdown Read/Write error
11 short Cache Memory error
1 long, 3 short Conventional/Extended memory failure
1 long, 8 short Display/Retrace test failed
two-tone siren Low CPU Fan speed, Voltage Level issue

AWARD BIOS beep codes

Below are Award BIOS Beep codes that can occur. However, because of the wide variety of different computer manufacturers with this BIOS, the beep codes may vary.
Beep Code Description
1 long, 2 short Indicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional information
Any other beep(s) RAM problem.
If any other correctable hardware issues are found, the BIOS displays a message.

Dell beep codes

Beep Code Description
7 beeps (repeated)Bad processor (CPU)
For other Dell beep codes, please refer to Dell's Beep Codes and PSA Diagnostics Chart page.

IBM BIOS beep codes

Below are general IBM BIOS Beep codes that can occur. However, because of the wide variety of models shipping with this BIOS, the beep codes may vary.
Beep Code Description
No Beeps No Power, Loose Card, or Short.
1 Short Beep Normal POST, computer is ok.
2 Short Beep POST error, review screen for error code.
Continuous Beep No Power, Loose Card, or Short.
Repeating Short Beep No Power, Loose Card, or Short.
One Long and one Short Beep Motherboard issue.
One Long and Two Short Beeps Video (Mono/CGA Display Circuitry) issue.
One Long and Three Short Beeps. Video (EGA) Display Circuitry.
Three Long Beeps Keyboard or Keyboard card error.
One Beep, Blank or Incorrect Display Video Display Circuitry.

Macintosh startup tones

Tones Error
Error Tone. (two sets of different tones) Problem with logic board or SCSI bus.
Startup tone, drive spins, no video Problem with video controller.
Powers on, no tone. Logic board problem.
High Tone, four higher tones. Problem with SIMM.

Phoenix BIOS beep codes

Below are the beep codes for Phoenix BIOS Q3.07 OR 4.X
Beep Code Description and what to check
1-1-1-1 Unconfirmed beep code. Reseat RAM chips or replace RAM chips as possible solution
1-1-1-3 Verify Real Mode.
1-1-2-1 Get CPU Type.
1-1-2-3 Initialize system hardware.
1-1-3-1 Initialize chipset registers with initial POST values.
1-1-3-2 Set in POST flag.
1-1-3-3 Initialize CPU registers.
1-1-4-1 Initialize cache to initial POST values.
1-1-4-3 Initialize I/O.
1-2-1-1 Initialize Power Management.
1-2-1-2 Load alternate registers with initial POST values.
1-2-1-3 Jump to UserPatch0.
1-2-2-1 Initialize keyboard controller.
1-2-2-3 BIOS ROM checksum.
1-2-3-1 8254 timer initialization.
1-2-3-3 8237 DMA controller initialization.
1-2-4-1 Reset Programmable Interrupt Controller.
1-3-1-1 Test DRAM refresh.
1-3-1-3 Test 8742 Keyboard Controller.
1-3-2-1 Set ES segment to register to 4 GB.
1-3-3-1 28 Autosize DRAM.
1-3-3-3 Clear 512K base RAM.
1-3-4-1 Test 512 base address lines.
1-3-4-3 Test 512K base memory.
1-4-1-3 Test CPU bus-clock frequency.
1-4-2-4 Reinitialize the chipset.
1-4-3-1 Shadow system BIOS ROM.
1-4-3-2 Reinitialize the cache.
1-4-3-3 Autosize cache.
1-4-4-1 Configure advanced chipset registers.
1-4-4-2 Load alternate registers with CMOS values.
2-1-1-1 Set Initial CPU speed.
2-1-1-3 Initialize interrupt vectors.
2-1-2-1 Initialize BIOS interrupts.
2-1-2-3 Check ROM copyright notice.
2-1-2-4 Initialize manager for PCI Options ROMs.
2-1-3-1 Check video configuration against CMOS.
2-1-3-2 Initialize PCI bus and devices.
2-1-3-3 Initialize all video adapters in system.
2-1-4-1 Shadow video BIOS ROM.
2-1-4-3 Display copyright notice.
2-2-1-1 Display CPU Type and speed.
2-2-1-3 Test keyboard.
2-2-2-1 Set key click if enabled.
2-2-2-3 56 Enable keyboard.
2-2-3-1 Test for unexpected interrupts.
2-2-3-3 Display prompt Press F2 to enter SETUP.
2-2-4-1 Test RAM between 512 and 640k.
2-3-1-1 Test expanded memory.
2-3-1-3 Test extended memory address lines.
2-3-2-1 Jump to UserPatch1.
2-3-2-3 Configure advanced cache registers.
2-3-3-1 Enable external and CPU caches.
2-3-3-3 Display external cache size.
2-3-4-1 Display shadow message.
2-3-4-3 Display non-disposable segments.
2-4-1-1 Display error messages.
2-4-1-3 Check for configuration errors.
2-4-2-1 Test real-time clock.
2-4-2-3 Check for keyboard errors
2-4-4-1 Set up hardware interrupts vectors.
2-4-4-3 Test coprocessor if present.
3-1-1-1 Disable onboard I/O ports.
3-1-1-3 Detect and install external RS232 ports.
3-1-2-1 Detect and install external parallel ports.
3-1-2-3 Re-initialize onboard I/O ports.
3-1-3-1 Initialize BIOS Data Area.
3-1-3-3 Initialize Extended BIOS Data Area.
3-1-4-1 Initialize floppy controller.
3-2-1-1 Initialize hard disk controller.
3-2-1-2 Initialize local bus hard disk controller.
3-2-1-3 Jump to UserPatch2.
3-2-2-1 Disable A20 address line.
3-2-2-3 Clear huge ES segment register.
3-2-3-1 Search for option ROMs.
3-2-3-3 Shadow option ROMs.
3-2-4-1 Set up Power Management.
3-2-4-3 Enable hardware interrupts.
3-3-1-1 Set time of day.
3-3-1-3 Check key lock.
3-3-3-1 Erase F2 prompt.
3-3-3-3 Scan for F2 key stroke.
3-3-4-1 Enter SETUP.
3-3-4-3 Clear in POST flag.
3-4-1-1 Check for errors
3-4-1-3 POST done - prepare to boot operating system.
3-4-2-1 One beep.
3-4-2-3 Check password (optional).
3-4-3-1 Clear global descriptor table.
3-4-4-1 Clear parity checkers.
3-4-4-3 Clear screen (optional).
3-4-4-4 Check virus and backup reminders.
4-1-1-1 Try to boot with INT 19.
4-2-1-1 Interrupt handler error.
4-2-1-3 Unknown interrupt error.
4-2-2-1 Pending interrupt error.
4-2-2-3 Initialize option ROM error.
4-2-3-1 Shutdown error.
4-2-3-3 Extended Block Move.
4-2-4-1 Shutdown 10 error.
4-3-1-3 Initialize the chipset.
4-3-1-4 Initialize refresh counter.
4-3-2-1 Check for Forced Flash.
4-3-2-2 Check HW status of ROM.
4-3-2-3 BIOS ROM is OK.
4-3-2-4 Do a complete RAM test.
4-3-3-1 Do OEM initialization.
4-3-3-2 Initialize interrupt controller.
4-3-3-3 Read in bootstrap code.
4-3-3-4 Initialize all vectors.
4-3-4-1 Boot the Flash program.
4-3-4-2 Initialize the boot device.
4-3-4-3 Boot code was read OK.
two-tone siren Low CPU Fan speed, Voltage Level issue

How to enter the BIOS or CMOS setup

Because of the wide variety of computer and BIOS manufacturers over the evolution of computers, there are numerous ways to enter the BIOS or CMOS Setup. Below is a listing of most of these methods, as well as other recommendations for entering the BIOS setup.
Note: This document does not help if you cannot enter the BIOS or CMOS setup because of a password.

New computers

Computers manufactured in the last few years allow you to enter the BIOS setup using one of the five keys shown below during the boot process. Typically it is one of the first three keys.
  • F1
  • F2
  • DEL
  • ESC
  • F10 *
* F10 is also used for the boot menu. If F10 opens a boot menu, your setup key is likely F2.
You will know when to press this key when you see a message similar to the example below as the computer is booting. Some older computers may also display a flashing block to indicate when to press the F1 or F2 keys.
Press <F2> to enter BIOS setup
Tip: If your computer is a new computer and you are unsure of what key to press when the computer is booting, try pressing and holding one or more keys on the keyboard to cause a stuck key error. Once you get this error, you should have the option to continue or enter setup.
Once you have successfully entered the CMOS setup, you should see a screen similar to the example below.
How do I change and save changes in CMOS setup?
Once in CMOS setup, the method for changing the settings often depends on the BIOS manufacturer. Typically you can change the settings by using the arrow keys to move to the option you want to change. Press Enter to select what to change and then use the arrow keys to select a new value. Some manufacturers may have you press the Page up and Page down keys to change the values.
Tip: All manufacturers list the steps on how to navigate on the bottom or right-hand side of the screen.
I cannot change the values to a setting I want to use.
If you are trying to change the clock settings, speed settings, or other setting and do not have an available option, it is because it is not supported by the motherboard. If you believe it should be supported, you may need a BIOS update.

Older computers

Unlike the computers of today, older computers (before 1995) had numerous different methods of entering the BIOS setup. Below is a listing of key sequences to press as the computer is booting to enter setup.
  • CTRL + ALT + ESC
  • CTRL + ALT + INS
  • CTRL + ALT + ENTER
  • CTRL + ALT + S
  • PAGE UP KEY
  • PAGE DOWN KEY
ACER BIOS
If your computer cannot boot or you want to restore the BIOS back to its bootable settings and your computer uses an ACER BIOS, press and hold the F10 key as you turn on the computer. While continuing to hold the F10 key, you should hear two beeps indicating that the settings are restored.
AMI BIOS
Older AMI BIOS could be restored back to bootable settings by pressing and holding the Insert key as the computer is booting.
BIOS or CMOS diskettes
Early 486, 386, and 286 computers required a floppy disk in order to enter the BIOS setup. These diskettes may be referred to as ICU, BBU, or SCU disks. Because these diskettes are unique to your computer manufacturer, you must obtain the diskettes from them. See the computer manufacturers list for contact information.

Early IBM computers

Some early IBM computers require you to press and hold both mouse buttons as the computer boots to enter the BIOS setup.

Other suggestions

Finally, if none of the above suggestions help get you into your CMOS setup, you can cause a stuck key error, which causes the CMOS setup prompt to appear and remain until you press a key to continue. To do this, press and hold any key on the keyboard and do not let go (you may get several beeps as you are doing this). Keep pressing the key until the computer stops booting and you have the option to enter setup.