[nForce]: Trouble Shooting Guide V1.6a

Hello.
Here is a guide to help solve some problems with K7N2 motherboards.
Problems arise in systems because some components do not work as they should.
Typical issues found with these boards consist of Non-nForce2 Approved RAM & a weak power supply. Other issues could be a cpu won't run at its rated fsb speed or an incorrectly mounted cpu cooler.
Sound problems - too many or incorrectly placed metal standoffs, bad drivers.
Windows won't install or you get a file read error - Incorrectly mounted CPU heat sink, RAM or power supply (PSU).
I've listed some instructions below to help those users that need a basic comprehensive guide to troubleshoot their systems with. Please read through the entire guide prior to posting for help on the forum.
Before you start doing anything, remove the power cord and make sure that you have touched the metal case of your system. This is called "Grounding yourself" and if you don't you could damage your system due to static discharge!
Thanks to Arioch and Dragon60 for comments on this.
1) BIOS/Startup POST reports wrong cpu or frequency
Check if jumper j10 and j11 are set to safemode and also check fsb settings in bios. If the jumpers are set to safe mode set them to normal, this is found in your motherboard manual. The jumpers vary with motherboards and manufacturers.
SafeMode sets cpu and memory to 100mhz.
Both memory and cpu are double pumped.
Data is clocked on the rise and fall of each clock cycle.
That means that 100mhz real frequency is 200mhz virtual frequency.
This is NOT without error and so your results may vary a little.
Non-Delta supports all cpu up to fsb 333
Delta supports all Socket A cpu
Duron upto 1300MHz = 100MHz (=200DDR)
Duron from 1400MHz = 133MHz (=266DDR)
Athlon B type = 100MHz (=200DDR)
Athlon C type = 133MHz (=266DDR)
Athlon XP - C type = 133MHz (=266DDR)
Athlon XP - D type = 166MHz (=333DDR)
Athlon XP - E type = 200MHz (=400DDR)
Support for new Duron 1400, 1600, 1800 with 266Mhz FSB (applebred)
The following boards support them:
(If a board is not on the list then it's not supported!)
-K7N2 6570 V1.0
-K7N2G-L 6570 V1.0
-K7N2G-ILSR 6570 V1.0
-K7N2 Delta 6570 V1.0
-K7N2GM-L 6777 V1.0
Thanks to DeathStalker
The best way to identify a processor is by using the OPN (Ordering Part Number) which can be found on the processor (E.g. AXDA 2700 D K V 3 D).
How to check which cpu you have:
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/Electrical_Specification_Rev04_ENG.pdf
2) Over temp CPU
Is the Heat Sink and Fan rated for the CPU?
The CPU Heat Sink could be mounted wrong! Carefully remove it and check it. It can and will fit 2 ways but ther is only 1 right way.  Examine the installation very carefully!
The Heat Sink has a recessed edge that has to be installed over the ridge (higher part or bump) of the socket. If installed backwards then it won't cool the entire area of the processor 'die' and could cause it to burn, thus killing it, or give you trouble as outlined in this guide.
Make sure that you use a QUALITY Thermal Compound/Paste and DO NOT reuse old compound! Note that some Heat Sinks are shipped with Thermal Pads, these are ok for some but will not give you the best heat transfer that a quality paste will.
Below are three images, the first two are incorrect, the last is correct.
Again..It is important to match the notch or step in the heatsink to the socket or it will not seat properly, causing immediate shutdowns, and ultimately damage your CPU.
If you use too much Silver based Thermal Compund you risk shorting the bridges on the CPU. This could cause damage to the CPU itself so use sparingly! If you feel that you've used too much then clean the die and substrate (the brown or green fiberglass material that the die is mounted on) and re-apply. Orange Clean TM is excellent for cleaning any type of thermal compound from a processor. Isopropyl Alchohol is ok but may leave traces of silver on the substrate. Using a 10X eye loupe will ensure that no traces of silver are shorting any bridges together after cleaning. DO NOT clean your processor while it rests in its socket on the motherboard. You run the risk of cleaner mixed with compound and dirt settling into your socket and that will cause further problems.
Last but not least. DO NOT use acetone to clean anything inside your PC. (or outside for that matter) It MAY not do any damage BUT it may dissolve some parts. Especially the coating on capacitors and resistors.
Silverbased compounds are not recommended by most manufacturers and if any traces are detected by them from an RMA'd processor they will usually void the warranty!
The latest AMD XP CPU's (XP-2000 and above) require a copperbased heatsink because their die are smaller and generate far more heat per square centimeter than the "old" CPU's did.
a)How to check the Heat Sink before taking it off:
There is a simple way to check the Heat Sink without taking it off. You do this by first checking your idle temp with SpeedFan or MBM, it should be below 50-55C.
Download Prime95 and run torture test for about 10 minutes while monitoring the temps, after about 1 minute or so it should stabilize and your temp should have gone up about 10-15C (max).
If it still goes up or the system crashes, there is a chance that you've mounted the heat sink incorrectly.
If your system can't run this check, (i.e. freezes or crashes) try setting your  FSB to 100. Try to run the test again. If it still fails to run  it could well be that the heat sink is mounted wrong or your power supply doesn't have enough power.
You cant check if the heatsink only has partial contact with the CPU die by looking on temperature monitor programs. The heatsink needs to be removed to see that.
If, after reading the guide regarding CPU Heat Sinks, you don't understand what we are talking about, then refer this link: AMD CPU & Cooling guide
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/23986.pdf
3) Power Supplies
Most common cheap 300-350W power supply units (PSU for short) can't handle an XP-1700 or above, try a better one to be sure.
Make sure your PSU has 200W combined on the +3.3v & +5V rails and that the +3.3V rail is rated for 20A (A = Amps or Amperage) or above. This should be enough for most systems.
On the latest boards the +12V rail has become very important too, expecially with AMD ThunderBird & above CPU's. Make sure your PSU can supply 16A or more.
Alway's make sure you have a decent PSU, it never fails to spend a bit more on that part!
Borrow a bigger one from a friend if you are not sure.
Here's a good post on choosing the right power supply:
Choosing The Right Power Supply
This is the bare minimum that you should see on a PSU running an AMD processor. Intel is a bit more forgiving in some cases but with the amount of devices we use these days this minimum is a good guidline:
+3.3V - 28A or better
+5V - 35A or better
+12V - 16A or better
Watch out!! Cheap PSU's like Q-Tec come nowhere near these figures!! Do NOT trust the 300W or 400W rating on them!!! Q-Tec is about the worst of them all!!
4) Metal Stand-offs
Sometimes we are all a bit careless when it comes to changing a motherboard and forget to look at the layout of the stand-offs (those little silver or brass pieces that the screws screw into to hold the motherboard in the case) that are left from the old motherboard. Some motherboards use more than others thus some overlook the 'extra' one and mount that new board and never know the difference. Until they try to start their new baby up!
Remove the board and check for to see if you have too many of them by counting the holes or screws that you took out and then count the number of stand-offs you have in the case. Remove any uneeded stand-offs then remount your motherboard. Having 'extra's' can short out circuitry and cause all sorts of problems most of which are audio related.
Here are what typical stand-offs look like:
5) Sound
Two types of audio chipsets are used in these boards:
a) The -ILSR version uses Soundstorm and has drivers supplied from MSI or nVidia.
b) The -L version uses RealTek sound and has drivers supplied by MSI and Realtek.
There have been a lot of issues regarding the -L board and its drivers supplied by MSI. Realtek drivers seem to repair these issues and can be found here:
www.realtek.com.tw
Follow the ALC650 link.
6) RAM
Most of the issues involving these boards have been memory related. For various reasons cheaper generic memory doesn't run with nForce2 chipsets well and you should get nForce2 Approved RAM. Here is a link to nVidia's compatibility list as well as a list of what has worked for some:
Good Memory Choices for ALL K7N2 nF2 released boards
It's not a good idea to try to run DDR266 RAM when you have a 333FSB CPU, get DDR333 ram of decent quality.
If you think that you're having RAM issues then replace the ram with another brand to see if it fixes it or borrow some from a friend to check. Make sure it isn't cheap quality RAM or what you borrow isn't cheap quality. You can run to the local CompUSA (if you live in the USA that is) and buy some better quality RAM and return it later if you find that it isn't the problem.
DDR ram speeds:
Duron up to 1300/Athlon-B = 100FSB = PC-1600 = DDR200
Duron from 1400 = 133FSB = PC-2100 = DDR266
Athlon-C/XP up to 2600 = 133FSB = PC-2100 = DDR266
Athlon XP D-type and above = 166FSB = PC-2700 = DDR333
Athlon XP E-type and above = 200FSB = PC-3200 = DDR400
Set Fsb / Dram Ratio to 1:1 that means that the memory is working at the same speed as the fsb does.
Higher DDR speeds are only a must if you try to overclock. You can use faster RAM on a slower system and the motherboard bus will switch down in speed accordingly. The speeds given above are what should be used as a minimum, otherwise you're creating a serious bottleneck of data from the RAM.
Use a decent RAM testing utility such as Memtest86 if you suspect RAM is faulty. Typical failures of RAM include but are not limited to:
a) BSOD (Blue Screen of Death!)
b) Data Corruption
c) Machine won't cold boot
Try your system always with 1 RAM module at a time to see if you have a bad module. Swap modules if you have more than 1 to see if one or the other is bad. When upgrading remeber that adding more modules can give you trouble too. Especially if you mix manufacturers. Some sticks just won't work in pairs and some fail when you put 3 or more in the system. When you want to use 3 sticks, make very sure you use the nVidia tested and approved modules, they are your best chance that they will work without problems.
If still nothing try to seat the ram in another slot, sometimes they work better in another slot.
Thanks boost
Or raise the RAM voltage a little but be careful doing this! Sometimes this works when you have a lot of ram in the system.
7) BIOS
Sometimes when we play with our BIOS settings and set something wrong in it or set something incompatible with our hardware this causes the motherboard to not boot up. Sometimes they come from the factory that way as well. If so then clear the CMOS and start with the default settings. If it works try setting ONLY A FEW SETTINGS at a time and nothing more! If it works then go further from there a couple of settings at a time.
There are issues when changing VCORE and it gets stuck.
There are 3 ways to work around this issue.
1. Updating to the latest bios seems to fix it most of the time.
2. Clear CMOS, change VCORE in the BIOS, save changes then reboot and it should be changed.
3. Change VCORE in BIOS, save changes, turn off pc then disconnect PSU from wall outlet by either disconnecting the power cord or use the switch on the backside of the psu if there is one. Reconnect the power cord or turn the switch on again. Boot up the system, go into the BIOS and check under pc health to see if it has changed.
For RAID boards only!!
If you recieve a message at boot saying:
No Hard disk/drive present...BIOS will not be installed...
or something comparable, it means that there are no drives connected to the raid controllers and it's not installing the drivers needed to support the function of that particular device FROM BIOS ONLY! This is nothing to worry about and all of the other functions of your machine should work properly.
Modded bios to fix problems when using multiplier 10 and 10.5 and also to be able to use a higher FSB than with the MSI bios.
http://www.nforcershq.com/forum/viewtopic.php?t=46052
8) Clearing the CMOS chip
Disconnect the system power cord and push the case power button to drain all remaining power in the psu for approximately 15 seconds
Then move jumper jbat1 and wait 10 seconds and move it back to the original position. You should ensure that the jumper has metal inside of it when removed, sometimes (rarely) they don't. This process resets or clears the CMOS chip and is shown in most motherboard manuals.Now connect the power cord and restart your system.
Some motherboards require that the battery must be removed for 20 minutes before putting the battery and jbat1 back for the CMOS chip to be cleared.
***Starting your K7N2 Delta2 at default settings***
By "labtech1"
As some of you will be aware there is no safe mode jumper J10 on the K7N2 Delta2 series of boards. This has been replaced by the "insert" key method as used by Abit and Epox. To start your board at its default settings following an unsuccessful overclocking attempt you need to do the following using a ps2 keyboard. Turn off your machine and disconnect from the mains or turn off the switch on the back of the power supply. Press the front panel power switch several times to discharge any charge remaining in the power supply capacitors. Reconnect the power by plugging into wall socket or turning on psu power switch. Press and hold down "insert" on the keyboard and press the case front panel power switch. If you are successful it should start the cpu and memory at 100Mhz FSB. If it does press "delete" to reenter the bios to change your settings to known safe settings. Good luck.
9) Harddisks
If your hard drive is giving you problems:
Western Digital (WD) drive's are jumpered somewhat strange compared to others:
No jumper = Stand-Alone drive with no other drive attached to the cable.
Jumper master = Use this setting on your main drive if you have a slave drive installed in your system.
Jumper slave = Use this setting if you have a second hard drive installed in your system.
Cable Select - the preferred jumper setting
If your Hard Drive is doing weird things:
Make sure you have connected the color-coded connectors to the color-coded connectors on the motherboard and connect the other END of the cable to the hard drive. The middle connector can be left unattached without problems if not needed.
Not all motherboards have color-coded connectors.
IBM harddisks seem to fail a lot, try Drive-Fitness-Test on it, see if it has problems.
Run drive fitness test (DFT)
Maxtor also has its own version of hard drive check for their drives and is available from their website.
Any brand of hard drive can have problems so check the manufacturer website to see if there is a testing utility to use to make sure they are ok. Hard drive failures can cause some of the strangest problems with computers and should be checked via the Event Viewer of your Operating System or using the mfg's utility. Sometimes the Event Viewer will give you clues that you have bad sectors leading you to a potential hard drive failure. You could also find IDE/SCSI controllers that are suspect by looking there as well. Win9x and ME DO NOT have Event Viewers.
Alway's be sure your harddisk is in tip-top shape! If you suspect that it's not, replace it to verify.
IDE devices and hard drive guide (Written by Assaf & Bas)
IDE devices and hard drive guide(Written by Assaf & Bas)
To enable a hard drive over 137GB in Win2000 edit this registry key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters]
"EnableBigLba"=dword:00000001
The K7N2G & Delta -ILSR boards support 2 IDE Devices on IDE 1 & 2, 1 IDE hard drive on IDE3 and 2 SATA drive's on the SATA Ports.
There is a modded bios that allows 2 drives on IDE3. USE THIS AT YOUR OWN RISK!!! Here is a link to it:
http://www.nforcershq.com/forum/viewtopic.php?t=27626&highlight=
Harddisk/power LED not functioning:
If your Hard Drive or Power LED doesn't work try turning the plug around on the motherboard connector. Some manufacturers don't mark or wire the LED cables properly and the LEDs will only work when + and - is correct.
Hard drive LEDs do not work with SATA drives but O&O Drive LED opens a little window and there you can see when a harddrive or cd is accessed. Works on both ide and sata drives.
10) Floppy Drives
If your floppy drive doesn't work or the LED stays on all of the time make sure the floppy is set correctly in the BIOS because the BIOS doesn't autodetect a floppy drive.
Check the cable making sure that the twist in the cable is at the floppy-drive side and flip the connector at the around. If it stays on after that or you still can't read a floppy disk try another drive or a different manufaturer type drive.
11) USB Ports
USB 2.0 ports are supported ONLY in Win2000 w/SP3 and XP w/SP1. Update your OS from Windows Update and let the OS install the ports after reboot and they should work.
If your USB ports aren't working:
Check in the BIOS if the ports are enabled. If you're using the front USB ports of your case check to see if all of the wires are connected properly.
There are 4 wires for each USB channel.
In some manufaturer's cases they are supplied with a wire called USBOC. Don't connect this as it can cause problems.
Also different mfg's mark the wires with different names so the basic nomenclature would be something like this:
+5v = +VCC
-D = -USB
+D = +USB
Note: Normally the cables are marked as +USB1 or -USB1, +USB2 or -USB2 and so on...please ensure that all of the 1's are together and all of the 2's are together.
12) Replacing parts and the system won't boot after
It's never a good idea to replace stuff like CPU and ram without taking the board out of the case. But if you do so please support the board because if you don't you might bend the board a little and cause trace breakage or component connections to the board to crack or break causing a bad contact. Always support the board when you replace components no matter what!
Also make sure your system is compatible with any replacement component. For example your PSU may not be able to handle a video card upgrade from a GeForce2 440MX to a GeForce4 Ti-4600 because the +12v rail is too low or the motherboard isn't rated to output the proper voltage to the AGP port.
If you have parts that work in another computer with a different chipset this DOES NOT mean they will work with the nforce2 chipset.
13) Graphics Card
If there is stability problem and/or can't use agp 8x then update to the latest bios and it should work. Also try to disable the 8x feature of the motherboard in the BIOS. If neither of these work then you may have a PSU that is under-powered and needs to be replaced. You could also have a faulty video card, AGP port on the motherboard among other things. If you have to disable the 8x feature in the BIOS then there is still a problem even if the card starts working. That may mean the motherboard is bad. Also use the latest drivers available from the respective manufacturer and don't forget to uninstall the old drivers first!! There is a sticky post in the VGA forum that details this process.
14) Checking the power supply
Don't do this if you don't know what you are doing!
a) Disconnect the power supply.
b) Orient the 20-pin power connector with the clip up.
c) Locate pin 4 and pin 8 top row, mostly green and black wire. (Usually the PSU manufacturer will have a drawing labeling the pins on their website)
d) Use a wire to short them (or better a 12V test lamp).
e) Now connect the power cord and the fan inside the power supply should start spinning. If it doesn't your power supply might be dead.
15) Windows
a) If you find that Windows2000/XP won't run stable:
Try to disable APIC and install again. Not all drivers/devices like the APIC.
b) Windows2000/XP won't install USB 2.0:
Install the latest service pack using Windows Update (SP3 Win2000 or SP1 WinXP). Windows should detect the USB ports on reboot and install the drivers for them. They should work now but if not you could have a faulty motherboard.
If you use a current or slipstreamed copy of Win2K or XP with the latest service pack they include these new drivers. This download will no longer be available on Windows Update.
USE THESE AT YOUR OWN RISK!!!
Slipstreaming Win2K with Service Packs and Creating a Bootable CD:
http://old.bink.nu/bootcd/
Slipstreaming Windows XP Service Packs and Creating a Bootable CD
http://www.windows-help.net/WindowsXP/winxp-sp1-bootcd.html
16) Raid
Configure a raid array:
After you have connected 1 or 2 hard drives to your Raid IDE port(s) press CTRL + F during boot and create a raid array.
It is possible to have 2 raid arrays working at the same time.
To boot from a raid array set SCSI as the first boot device.
To install windows on a raid array you have to press F6 to load raid drivers during the initial install of windows. This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives. A default driver is loaded at bootup so that the drives can be accessed until the real drivers are loaded from the MB disk.
Raid 0 sets up striping which gives more performance for applications. Raid 1 sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a raid array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
nForce 2 raid FAQ
(Mostly by Wonkanoby)
The third IDE only works with harddrives not optical drives such as CD,DVD. It only supports one drive.
You must create an array first, weather you are using 2 drives or just one
or nothing will happen .
You must also have a 3.5 floppy with the appropriate drivers handy.
INSTALLATION
To install raid as a boot drive.
Control + F and make the array.
Set SCSI second to cdrom in boot order.
Boot to xp cd and hit F6 as it prompts you to do right at the beginning and then insert the floppy.
This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives.
The rest of the format/install is all as normal.
Drivers for the raid can be found here.
http://us-download.msi.com.tw/support/dvr_exe/sata48N.exe
Promise PDC20376 Serial-ATA RAID Utility
http://us-download.msi.com.tw/support/dvr_exe/37653.exe
If you make a new floppy, unrar them.
Then copy every thing including the text files to the floppy.
(no text files, nothing happens)
MODDED BIOS
such as
http://www.nforcershq.com/forum/viewtopic.php?t=27626
There are several offering full RAID.
They add ability to have 2x drives on ide 3.
I'm skeptical running raid 0 with both on the same ide myself.
Now these you must get the bios and the drivers.
The drivers are not the same as those for the RAID MSI includes.
The drivers are linked on that BIOS page I have provided.
RAID 0, sets up striping, which gives more performance for applications.
RAID 1, sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a RAID array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
17) Good Links
J*A*G'S *Updated* nForce Cooling Guide (written by JAG)
Suggestions on posting and getting better answers (written by GlennVidia)
Good Memory Choices for K7N2G- IL and ILSR Board (written by Bonz)
ati problem ,post vga card model and bios (written by Wonkanoby)
Powersupplies(Written by Bas)
Moan Guide (Written by Wonkanoby)
A few good websites to have around!!
The Freeware Thread
NFORCE 2 OVERCLOCKING AND MODDING GUIDES
Use these guides, including the content of this entire guide, at your own risk!
This forum and it's members, including MSI, assume no liability whatsoever!
Part One
Part Two
I am not an expert on computers so I have most likely forgotten a lot of things. Please send me a private message or email me and I will add it if it's applicable. If you feel that something here is in error then please contact me via the above as well.
I also want to thank everyone that helped put this guide together.
All Star Lineup!
Arioch
DeathStalker
maesus
ClarkKent57
boost
Assaf
Bas
Tweetyoost
Stygge
HansH
GlennVidia
RoganJosh
Bonz
Wonkanoby
Dragon60
[T-A]_Super_10
labtech1

Hello.
Here is a guide to help solve some problems with K7N2 motherboards.
Problems arise in systems because some components do not work as they should.
Typical issues found with these boards consist of Non-nForce2 Approved RAM & a weak power supply. Other issues could be a cpu won't run at its rated fsb speed or an incorrectly mounted cpu cooler.
Sound problems - too many or incorrectly placed metal standoffs, bad drivers.
Windows won't install or you get a file read error - Incorrectly mounted CPU heat sink, RAM or power supply (PSU).
I've listed some instructions below to help those users that need a basic comprehensive guide to troubleshoot their systems with. Please read through the entire guide prior to posting for help on the forum.
Before you start doing anything, remove the power cord and make sure that you have touched the metal case of your system. This is called "Grounding yourself" and if you don't you could damage your system due to static discharge!
Thanks to Arioch and Dragon60 for comments on this.
1) BIOS/Startup POST reports wrong cpu or frequency
Check if jumper j10 and j11 are set to safemode and also check fsb settings in bios. If the jumpers are set to safe mode set them to normal, this is found in your motherboard manual. The jumpers vary with motherboards and manufacturers.
SafeMode sets cpu and memory to 100mhz.
Both memory and cpu are double pumped.
Data is clocked on the rise and fall of each clock cycle.
That means that 100mhz real frequency is 200mhz virtual frequency.
This is NOT without error and so your results may vary a little.
Non-Delta supports all cpu up to fsb 333
Delta supports all Socket A cpu
Duron upto 1300MHz = 100MHz (=200DDR)
Duron from 1400MHz = 133MHz (=266DDR)
Athlon B type = 100MHz (=200DDR)
Athlon C type = 133MHz (=266DDR)
Athlon XP - C type = 133MHz (=266DDR)
Athlon XP - D type = 166MHz (=333DDR)
Athlon XP - E type = 200MHz (=400DDR)
Support for new Duron 1400, 1600, 1800 with 266Mhz FSB (applebred)
The following boards support them:
(If a board is not on the list then it's not supported!)
-K7N2 6570 V1.0
-K7N2G-L 6570 V1.0
-K7N2G-ILSR 6570 V1.0
-K7N2 Delta 6570 V1.0
-K7N2GM-L 6777 V1.0
Thanks to DeathStalker
The best way to identify a processor is by using the OPN (Ordering Part Number) which can be found on the processor (E.g. AXDA 2700 D K V 3 D).
How to check which cpu you have:
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/Electrical_Specification_Rev04_ENG.pdf
2) Over temp CPU
Is the Heat Sink and Fan rated for the CPU?
The CPU Heat Sink could be mounted wrong! Carefully remove it and check it. It can and will fit 2 ways but ther is only 1 right way.  Examine the installation very carefully!
The Heat Sink has a recessed edge that has to be installed over the ridge (higher part or bump) of the socket. If installed backwards then it won't cool the entire area of the processor 'die' and could cause it to burn, thus killing it, or give you trouble as outlined in this guide.
Make sure that you use a QUALITY Thermal Compound/Paste and DO NOT reuse old compound! Note that some Heat Sinks are shipped with Thermal Pads, these are ok for some but will not give you the best heat transfer that a quality paste will.
Below are three images, the first two are incorrect, the last is correct.
Again..It is important to match the notch or step in the heatsink to the socket or it will not seat properly, causing immediate shutdowns, and ultimately damage your CPU.
If you use too much Silver based Thermal Compund you risk shorting the bridges on the CPU. This could cause damage to the CPU itself so use sparingly! If you feel that you've used too much then clean the die and substrate (the brown or green fiberglass material that the die is mounted on) and re-apply. Orange Clean TM is excellent for cleaning any type of thermal compound from a processor. Isopropyl Alchohol is ok but may leave traces of silver on the substrate. Using a 10X eye loupe will ensure that no traces of silver are shorting any bridges together after cleaning. DO NOT clean your processor while it rests in its socket on the motherboard. You run the risk of cleaner mixed with compound and dirt settling into your socket and that will cause further problems.
Last but not least. DO NOT use acetone to clean anything inside your PC. (or outside for that matter) It MAY not do any damage BUT it may dissolve some parts. Especially the coating on capacitors and resistors.
Silverbased compounds are not recommended by most manufacturers and if any traces are detected by them from an RMA'd processor they will usually void the warranty!
The latest AMD XP CPU's (XP-2000 and above) require a copperbased heatsink because their die are smaller and generate far more heat per square centimeter than the "old" CPU's did.
a)How to check the Heat Sink before taking it off:
There is a simple way to check the Heat Sink without taking it off. You do this by first checking your idle temp with SpeedFan or MBM, it should be below 50-55C.
Download Prime95 and run torture test for about 10 minutes while monitoring the temps, after about 1 minute or so it should stabilize and your temp should have gone up about 10-15C (max).
If it still goes up or the system crashes, there is a chance that you've mounted the heat sink incorrectly.
If your system can't run this check, (i.e. freezes or crashes) try setting your  FSB to 100. Try to run the test again. If it still fails to run  it could well be that the heat sink is mounted wrong or your power supply doesn't have enough power.
You cant check if the heatsink only has partial contact with the CPU die by looking on temperature monitor programs. The heatsink needs to be removed to see that.
If, after reading the guide regarding CPU Heat Sinks, you don't understand what we are talking about, then refer this link: AMD CPU & Cooling guide
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/23986.pdf
3) Power Supplies
Most common cheap 300-350W power supply units (PSU for short) can't handle an XP-1700 or above, try a better one to be sure.
Make sure your PSU has 200W combined on the +3.3v & +5V rails and that the +3.3V rail is rated for 20A (A = Amps or Amperage) or above. This should be enough for most systems.
On the latest boards the +12V rail has become very important too, expecially with AMD ThunderBird & above CPU's. Make sure your PSU can supply 16A or more.
Alway's make sure you have a decent PSU, it never fails to spend a bit more on that part!
Borrow a bigger one from a friend if you are not sure.
Here's a good post on choosing the right power supply:
Choosing The Right Power Supply
This is the bare minimum that you should see on a PSU running an AMD processor. Intel is a bit more forgiving in some cases but with the amount of devices we use these days this minimum is a good guidline:
+3.3V - 28A or better
+5V - 35A or better
+12V - 16A or better
Watch out!! Cheap PSU's like Q-Tec come nowhere near these figures!! Do NOT trust the 300W or 400W rating on them!!! Q-Tec is about the worst of them all!!
4) Metal Stand-offs
Sometimes we are all a bit careless when it comes to changing a motherboard and forget to look at the layout of the stand-offs (those little silver or brass pieces that the screws screw into to hold the motherboard in the case) that are left from the old motherboard. Some motherboards use more than others thus some overlook the 'extra' one and mount that new board and never know the difference. Until they try to start their new baby up!
Remove the board and check for to see if you have too many of them by counting the holes or screws that you took out and then count the number of stand-offs you have in the case. Remove any uneeded stand-offs then remount your motherboard. Having 'extra's' can short out circuitry and cause all sorts of problems most of which are audio related.
Here are what typical stand-offs look like:
5) Sound
Two types of audio chipsets are used in these boards:
a) The -ILSR version uses Soundstorm and has drivers supplied from MSI or nVidia.
b) The -L version uses RealTek sound and has drivers supplied by MSI and Realtek.
There have been a lot of issues regarding the -L board and its drivers supplied by MSI. Realtek drivers seem to repair these issues and can be found here:
www.realtek.com.tw
Follow the ALC650 link.
6) RAM
Most of the issues involving these boards have been memory related. For various reasons cheaper generic memory doesn't run with nForce2 chipsets well and you should get nForce2 Approved RAM. Here is a link to nVidia's compatibility list as well as a list of what has worked for some:
Good Memory Choices for ALL K7N2 nF2 released boards
It's not a good idea to try to run DDR266 RAM when you have a 333FSB CPU, get DDR333 ram of decent quality.
If you think that you're having RAM issues then replace the ram with another brand to see if it fixes it or borrow some from a friend to check. Make sure it isn't cheap quality RAM or what you borrow isn't cheap quality. You can run to the local CompUSA (if you live in the USA that is) and buy some better quality RAM and return it later if you find that it isn't the problem.
DDR ram speeds:
Duron up to 1300/Athlon-B = 100FSB = PC-1600 = DDR200
Duron from 1400 = 133FSB = PC-2100 = DDR266
Athlon-C/XP up to 2600 = 133FSB = PC-2100 = DDR266
Athlon XP D-type and above = 166FSB = PC-2700 = DDR333
Athlon XP E-type and above = 200FSB = PC-3200 = DDR400
Set Fsb / Dram Ratio to 1:1 that means that the memory is working at the same speed as the fsb does.
Higher DDR speeds are only a must if you try to overclock. You can use faster RAM on a slower system and the motherboard bus will switch down in speed accordingly. The speeds given above are what should be used as a minimum, otherwise you're creating a serious bottleneck of data from the RAM.
Use a decent RAM testing utility such as Memtest86 if you suspect RAM is faulty. Typical failures of RAM include but are not limited to:
a) BSOD (Blue Screen of Death!)
b) Data Corruption
c) Machine won't cold boot
Try your system always with 1 RAM module at a time to see if you have a bad module. Swap modules if you have more than 1 to see if one or the other is bad. When upgrading remeber that adding more modules can give you trouble too. Especially if you mix manufacturers. Some sticks just won't work in pairs and some fail when you put 3 or more in the system. When you want to use 3 sticks, make very sure you use the nVidia tested and approved modules, they are your best chance that they will work without problems.
If still nothing try to seat the ram in another slot, sometimes they work better in another slot.
Thanks boost
Or raise the RAM voltage a little but be careful doing this! Sometimes this works when you have a lot of ram in the system.
7) BIOS
Sometimes when we play with our BIOS settings and set something wrong in it or set something incompatible with our hardware this causes the motherboard to not boot up. Sometimes they come from the factory that way as well. If so then clear the CMOS and start with the default settings. If it works try setting ONLY A FEW SETTINGS at a time and nothing more! If it works then go further from there a couple of settings at a time.
There are issues when changing VCORE and it gets stuck.
There are 3 ways to work around this issue.
1. Updating to the latest bios seems to fix it most of the time.
2. Clear CMOS, change VCORE in the BIOS, save changes then reboot and it should be changed.
3. Change VCORE in BIOS, save changes, turn off pc then disconnect PSU from wall outlet by either disconnecting the power cord or use the switch on the backside of the psu if there is one. Reconnect the power cord or turn the switch on again. Boot up the system, go into the BIOS and check under pc health to see if it has changed.
For RAID boards only!!
If you recieve a message at boot saying:
No Hard disk/drive present...BIOS will not be installed...
or something comparable, it means that there are no drives connected to the raid controllers and it's not installing the drivers needed to support the function of that particular device FROM BIOS ONLY! This is nothing to worry about and all of the other functions of your machine should work properly.
Modded bios to fix problems when using multiplier 10 and 10.5 and also to be able to use a higher FSB than with the MSI bios.
http://www.nforcershq.com/forum/viewtopic.php?t=46052
8) Clearing the CMOS chip
Disconnect the system power cord and push the case power button to drain all remaining power in the psu for approximately 15 seconds
Then move jumper jbat1 and wait 10 seconds and move it back to the original position. You should ensure that the jumper has metal inside of it when removed, sometimes (rarely) they don't. This process resets or clears the CMOS chip and is shown in most motherboard manuals.Now connect the power cord and restart your system.
Some motherboards require that the battery must be removed for 20 minutes before putting the battery and jbat1 back for the CMOS chip to be cleared.
***Starting your K7N2 Delta2 at default settings***
By "labtech1"
As some of you will be aware there is no safe mode jumper J10 on the K7N2 Delta2 series of boards. This has been replaced by the "insert" key method as used by Abit and Epox. To start your board at its default settings following an unsuccessful overclocking attempt you need to do the following using a ps2 keyboard. Turn off your machine and disconnect from the mains or turn off the switch on the back of the power supply. Press the front panel power switch several times to discharge any charge remaining in the power supply capacitors. Reconnect the power by plugging into wall socket or turning on psu power switch. Press and hold down "insert" on the keyboard and press the case front panel power switch. If you are successful it should start the cpu and memory at 100Mhz FSB. If it does press "delete" to reenter the bios to change your settings to known safe settings. Good luck.
9) Harddisks
If your hard drive is giving you problems:
Western Digital (WD) drive's are jumpered somewhat strange compared to others:
No jumper = Stand-Alone drive with no other drive attached to the cable.
Jumper master = Use this setting on your main drive if you have a slave drive installed in your system.
Jumper slave = Use this setting if you have a second hard drive installed in your system.
Cable Select - the preferred jumper setting
If your Hard Drive is doing weird things:
Make sure you have connected the color-coded connectors to the color-coded connectors on the motherboard and connect the other END of the cable to the hard drive. The middle connector can be left unattached without problems if not needed.
Not all motherboards have color-coded connectors.
IBM harddisks seem to fail a lot, try Drive-Fitness-Test on it, see if it has problems.
Run drive fitness test (DFT)
Maxtor also has its own version of hard drive check for their drives and is available from their website.
Any brand of hard drive can have problems so check the manufacturer website to see if there is a testing utility to use to make sure they are ok. Hard drive failures can cause some of the strangest problems with computers and should be checked via the Event Viewer of your Operating System or using the mfg's utility. Sometimes the Event Viewer will give you clues that you have bad sectors leading you to a potential hard drive failure. You could also find IDE/SCSI controllers that are suspect by looking there as well. Win9x and ME DO NOT have Event Viewers.
Alway's be sure your harddisk is in tip-top shape! If you suspect that it's not, replace it to verify.
IDE devices and hard drive guide (Written by Assaf & Bas)
IDE devices and hard drive guide(Written by Assaf & Bas)
To enable a hard drive over 137GB in Win2000 edit this registry key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters]
"EnableBigLba"=dword:00000001
The K7N2G & Delta -ILSR boards support 2 IDE Devices on IDE 1 & 2, 1 IDE hard drive on IDE3 and 2 SATA drive's on the SATA Ports.
There is a modded bios that allows 2 drives on IDE3. USE THIS AT YOUR OWN RISK!!! Here is a link to it:
http://www.nforcershq.com/forum/viewtopic.php?t=27626&highlight=
Harddisk/power LED not functioning:
If your Hard Drive or Power LED doesn't work try turning the plug around on the motherboard connector. Some manufacturers don't mark or wire the LED cables properly and the LEDs will only work when + and - is correct.
Hard drive LEDs do not work with SATA drives but O&O Drive LED opens a little window and there you can see when a harddrive or cd is accessed. Works on both ide and sata drives.
10) Floppy Drives
If your floppy drive doesn't work or the LED stays on all of the time make sure the floppy is set correctly in the BIOS because the BIOS doesn't autodetect a floppy drive.
Check the cable making sure that the twist in the cable is at the floppy-drive side and flip the connector at the around. If it stays on after that or you still can't read a floppy disk try another drive or a different manufaturer type drive.
11) USB Ports
USB 2.0 ports are supported ONLY in Win2000 w/SP3 and XP w/SP1. Update your OS from Windows Update and let the OS install the ports after reboot and they should work.
If your USB ports aren't working:
Check in the BIOS if the ports are enabled. If you're using the front USB ports of your case check to see if all of the wires are connected properly.
There are 4 wires for each USB channel.
In some manufaturer's cases they are supplied with a wire called USBOC. Don't connect this as it can cause problems.
Also different mfg's mark the wires with different names so the basic nomenclature would be something like this:
+5v = +VCC
-D = -USB
+D = +USB
Note: Normally the cables are marked as +USB1 or -USB1, +USB2 or -USB2 and so on...please ensure that all of the 1's are together and all of the 2's are together.
12) Replacing parts and the system won't boot after
It's never a good idea to replace stuff like CPU and ram without taking the board out of the case. But if you do so please support the board because if you don't you might bend the board a little and cause trace breakage or component connections to the board to crack or break causing a bad contact. Always support the board when you replace components no matter what!
Also make sure your system is compatible with any replacement component. For example your PSU may not be able to handle a video card upgrade from a GeForce2 440MX to a GeForce4 Ti-4600 because the +12v rail is too low or the motherboard isn't rated to output the proper voltage to the AGP port.
If you have parts that work in another computer with a different chipset this DOES NOT mean they will work with the nforce2 chipset.
13) Graphics Card
If there is stability problem and/or can't use agp 8x then update to the latest bios and it should work. Also try to disable the 8x feature of the motherboard in the BIOS. If neither of these work then you may have a PSU that is under-powered and needs to be replaced. You could also have a faulty video card, AGP port on the motherboard among other things. If you have to disable the 8x feature in the BIOS then there is still a problem even if the card starts working. That may mean the motherboard is bad. Also use the latest drivers available from the respective manufacturer and don't forget to uninstall the old drivers first!! There is a sticky post in the VGA forum that details this process.
14) Checking the power supply
Don't do this if you don't know what you are doing!
a) Disconnect the power supply.
b) Orient the 20-pin power connector with the clip up.
c) Locate pin 4 and pin 8 top row, mostly green and black wire. (Usually the PSU manufacturer will have a drawing labeling the pins on their website)
d) Use a wire to short them (or better a 12V test lamp).
e) Now connect the power cord and the fan inside the power supply should start spinning. If it doesn't your power supply might be dead.
15) Windows
a) If you find that Windows2000/XP won't run stable:
Try to disable APIC and install again. Not all drivers/devices like the APIC.
b) Windows2000/XP won't install USB 2.0:
Install the latest service pack using Windows Update (SP3 Win2000 or SP1 WinXP). Windows should detect the USB ports on reboot and install the drivers for them. They should work now but if not you could have a faulty motherboard.
If you use a current or slipstreamed copy of Win2K or XP with the latest service pack they include these new drivers. This download will no longer be available on Windows Update.
USE THESE AT YOUR OWN RISK!!!
Slipstreaming Win2K with Service Packs and Creating a Bootable CD:
http://old.bink.nu/bootcd/
Slipstreaming Windows XP Service Packs and Creating a Bootable CD
http://www.windows-help.net/WindowsXP/winxp-sp1-bootcd.html
16) Raid
Configure a raid array:
After you have connected 1 or 2 hard drives to your Raid IDE port(s) press CTRL + F during boot and create a raid array.
It is possible to have 2 raid arrays working at the same time.
To boot from a raid array set SCSI as the first boot device.
To install windows on a raid array you have to press F6 to load raid drivers during the initial install of windows. This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives. A default driver is loaded at bootup so that the drives can be accessed until the real drivers are loaded from the MB disk.
Raid 0 sets up striping which gives more performance for applications. Raid 1 sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a raid array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
nForce 2 raid FAQ
(Mostly by Wonkanoby)
The third IDE only works with harddrives not optical drives such as CD,DVD. It only supports one drive.
You must create an array first, weather you are using 2 drives or just one
or nothing will happen .
You must also have a 3.5 floppy with the appropriate drivers handy.
INSTALLATION
To install raid as a boot drive.
Control + F and make the array.
Set SCSI second to cdrom in boot order.
Boot to xp cd and hit F6 as it prompts you to do right at the beginning and then insert the floppy.
This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives.
The rest of the format/install is all as normal.
Drivers for the raid can be found here.
http://us-download.msi.com.tw/support/dvr_exe/sata48N.exe
Promise PDC20376 Serial-ATA RAID Utility
http://us-download.msi.com.tw/support/dvr_exe/37653.exe
If you make a new floppy, unrar them.
Then copy every thing including the text files to the floppy.
(no text files, nothing happens)
MODDED BIOS
such as
http://www.nforcershq.com/forum/viewtopic.php?t=27626
There are several offering full RAID.
They add ability to have 2x drives on ide 3.
I'm skeptical running raid 0 with both on the same ide myself.
Now these you must get the bios and the drivers.
The drivers are not the same as those for the RAID MSI includes.
The drivers are linked on that BIOS page I have provided.
RAID 0, sets up striping, which gives more performance for applications.
RAID 1, sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a RAID array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
17) Good Links
J*A*G'S *Updated* nForce Cooling Guide (written by JAG)
Suggestions on posting and getting better answers (written by GlennVidia)
Good Memory Choices for K7N2G- IL and ILSR Board (written by Bonz)
ati problem ,post vga card model and bios (written by Wonkanoby)
Powersupplies(Written by Bas)
Moan Guide (Written by Wonkanoby)
A few good websites to have around!!
The Freeware Thread
NFORCE 2 OVERCLOCKING AND MODDING GUIDES
Use these guides, including the content of this entire guide, at your own risk!
This forum and it's members, including MSI, assume no liability whatsoever!
Part One
Part Two
I am not an expert on computers so I have most likely forgotten a lot of things. Please send me a private message or email me and I will add it if it's applicable. If you feel that something here is in error then please contact me via the above as well.
I also want to thank everyone that helped put this guide together.
All Star Lineup!
Arioch
DeathStalker
maesus
ClarkKent57
boost
Assaf
Bas
Tweetyoost
Stygge
HansH
GlennVidia
RoganJosh
Bonz
Wonkanoby
Dragon60
[T-A]_Super_10
labtech1

Similar Messages

  • About three days ago my iphone5 stopped connecting to my home wifi. I've tried everything in the trouble shooting guides and everything in all the support comments here.Is there anything else it could be? my other devices connect no probs.

    About three days ago my iphone5 stopped connecting to my home wifi. I've tried everything in the trouble shooting guides and everything in all the support comments here.Ive reset network, reset all phone settings, turned wifi on and off, forgotten network. Nothing works. Is there anything else it could be? The wifi is fine as all my other devices connect to it no probs. appreciate any help?

    About three days ago my iphone5 stopped connecting to my home wifi. I've tried everything in the trouble shooting guides and everything in all the support comments here.Ive reset network, reset all phone settings, turned wifi on and off, forgotten network. Nothing works. Is there anything else it could be? The wifi is fine as all my other devices connect to it no probs. appreciate any help?

  • Apple Trouble Shooting Guide TS3304

    Apple has posted a new Trouble Shooting Guide addressing the WiFi problems that some iPad users have been having. See http://support.apple.com/kb/TS3304?viewlocale=en_US
    There are work arounds in the TS, some of which have been suggested in these forums. There is promise of a S/W update to address these problems.

    When connecting to a "hotspot" be it public or inside a business, you have only 2 options provided by this TS. Either renew IP or turn off "auto" screen brightness. Flimsy at best.
    I predict with the next software update those like me who have yet to connect to wifi at a hotel, coffee shop or fast food joint will continue to be wifi-less. Meaning I think it's a hardware problem. The good news is you can spin the referb roulette wheel by trading in your factory fresh model for one that's been assembled, disassembled and reassembled.
    Hope I'm wrong because I would like to use this device away from home and I don't want a referb. Went through several of those dogs with the iPhone. My advice, wait until the update or at least 3 months to get the dogs out of the system. Jaded.
    Message was edited by: jbhmacpro

  • Trouble shooting guide! Read this first!!!! rev 13-1-2004

    (Revision 13-1-2004)  
    Hi there,
    Follow everything on the list, even if it doesn't look like it would solve your problem, most problems are created somewhere else!
    To give some examples:
    CPU won't run FSB133....mostly powersupply or CPU-cooler.
    Videocard won't load drivers....mostly powersupply.
    Sound won't work.....mostly metal-standoff's.
    Windows won't install, file read error.....mostly CPU-cooler, Bad-ram or powersupply.
    That is why you need to go over the entire list and check all!
    Before you start doing anything, remove the power and make sure that you have touched the metal case of your system. If you don't you could damage your system due to static discharge!  
    Thanks to Arioch and Dragon60 for comments on this.
    There are several reasons why this happens.....to name the most commen:
    CPU speeds  
    You have a Duron, that CPU is 100FSB!
    You have a Athlon(XP) and it's showing the wrong speed, set the CPU-FSB to 133....
    Or 166 when it's a FSB333 CPU....or 200 when it's a FSB400 CPU....
    Some boards have a jumper to set it, other do it in the BIOS.
    Check your manual for this.
    Speeds must be:
    Duron upto 1300MHz = 100MHz (=200DDR)
    Duron from 1400MHz = 133MHz (=266DDR)
    Athlon B type = 100MHz (=200DDR)
    Athlon C type = 133MHz (=266DDR)
    Athlon XP - C type = 133MHz (=266DDR)
    Athlon XP - D type = 166MHz (=333DDR)
    Athlon XP - E type = 200MHz (=400DDR)
    Use this link to see if your motherboard actually supports your CPU.
    The TBred CPU's (0.13) start from XP-1700 and up, but not all boards support this CPU and they either show on the D-LED all red or don't start at all!!
    The K7T266pro2 is an exception, it can be made to support the TBred CPU's, on this link you find all the info on how to make it work.
    Many reports have told us that FSB333 CPU's work on KT3-Ultra boards work just fine, but it's unsupported by MSI, we don't know why....
    As for mulipliers with AMD CPU's, just set them Automatic, as they are hardcoded on the CPU themselves and will allway's be correctly, even if if you think the BIOS doesn't know it.
    How to recognise the CPU:
    If you look on the dice, there are letters after the speed.
    The last letter will tell you the FSB of the CPU.
    B=100MHz (=200DDR)
    C=133MHz (=266DDR)
    D=166MHz (=333DDR)
    E=200MHz (=400DDR)
    To recognise a CPU quickly, checkout this link.
    Thanks Mellops.
    The MHz setting must match your setting in the BIOS for FSB value, as it translates to the correct FSB setting for the CPU.
    The best way to identify a processor is by using the OPN (Ordering Part Number) which can be found on the processor (E.g. AXDA 2700 D K V 3 D).
    Detailed information on the code can be found in this AMD document. (Thanks Hans)
    CPU Cooling  
    CPU cooler not made for your CPU, check if it can handle your CPU....
    CPU cooler mounted wrong!, take it off and check it as it will fit 2 way's, but only 1 is the right one, examine very carefull!
    The cooler has a lower part that needs to go over the bump (higher part) of the socket, if it's not over there it won't cool the entire dice and WILL give you trouble.
    Also check if it's making contact with the entire dice of the CPU...
    Make sure you regrease it again, the same grease/paste can't be used twice!
    YOU MAY NEVER USE A THERMALPAD OR GREASE AGAIN! APPLY NEW EVERY TIME YOU TAKE THE COOLER OFF!!  
    top 2 show how not to do it
    Used too much silver-grease! It will shorten the bridges on the CPU, clean it and use white-paste.
    (Silver-paste is not recommended in any case!)
    The latest AMD XP CPU's (XP-2200 and above) require a copperbased heatsink because the dice is smaller and generates far more heat per square cm then the "old" CPU's do.
    How to check the cooler before taking it off.
    There is a simple way to check the cooler without taking it off.
    You do this by first checking your idle temp with PCAlert, it should be below 50-55C.
    Then you download a client from www.distributed.net, let this client run for about 10 minutes while monitoring the temps, after about 1 minute or so it should stabilize and your temp should have gone up about 10-15C (max).
    If it still goes up or the system crashes, there is a big chance you mounted the CPU-cooler wrong.
    When you can't run this check, try with FSB100, if the system does run the check then, it could be well that the cooler is mounted wrong or your powersupply doesn't have enough power.
    ***** YOU CAN'T CHECK THE CPU COOLER ON TEMPS OR FAN RUNNING, IT MUST BE TAKEN OFF THE CPU!!! *****  
    Cleaning the CPU and Cooler - thanks to Dragon60 for his addition.
    An additional comments about this is what you clean the CPU with in this situation. The best thing to use is isopropyl alcohol. If this is not available then metholated spirits would do.
    Make sure you allow the CPU to dry properly before you put it back in. This also means DO NOT try and clean it whilst it is still in the socket as some of the cleaning fluid, grease and dirt may get underneath and short some pins.
    Last but not least. DO NOT use acetone to clean anything inside your PC. (or outside for that matter) It MAY not do any damage BUT it may disolve some parts.
    Thanks Dragon60.  
    If you don't understand what we are talking about on this cooler matter, then read this link: AMD CPU & Cooling guide  
    Powersupplies  
    Powersupply too little, most commen cheap 300W CPU's can't handle an XP-1700 or above, try a better one to be sure.
    Make sure your powersupply has about 185W combined on the 3.3+5V and that the 3.3V has 20A or above.
    That should be enough for most systems.
    On the latest boards the 12V has become very important too, expecialy with TBred CPU's.
    Make sure yours can give 18A or more on the 12V line too.
    I have found that a lot of cheap 350W will fail with modern boards and TBred CPU's.
    Allway's make sure you have a decend PSU, it never fails to spent a bit more on that part!
    Borrow a bigger one from a friend if you are not sure....
    More info about powersupplies: Click here.
    And the second you must read: Click here.
    Powersupplies with these type of numbers on them or higher should be fine:
    3.3V - 28A or better
    5V - 30A or better
    12V - 18A or better
    Watch out!! Cheap PSU's like Q-Tec come nowhere near these figures!!
    Do NOT trust the 300W or 400W rating on them!!!
    Q-Tec is about the worst of them all!!  
    Metalclips  
    Stand-off's left between the board and the case, take the board out and check for too many of those metal-clips, they can shorten circuits and cause al sorts of problems (most of the time audio problems)
    RAM
    Ram problems, don't try to run with PC100 (SDram boards) when you have a 133FSB CPU, get PC133 ram of decend quality.
    In any case, don't use cheap quality ram (Crucial seems decend, but give's a lot of problems, I consider these cheap quality too :P ), replace the ram with another brand to see if it fixes it....
    DDR ram speeds:
    Duron upto 1300/Athlon-B =100FSB=PC-1600=DDR200
    Duron from 1400 =133FSB=PC-2100=DDR266
    Athlon-C/XP upto 2600 =133FSB=PC-2100=DDR266
    Athlon XP D-type and above =166FSB=PC-2700=DDR333
    Athlon XP E-type and above =200FSB=PC-3200=DDR400
    Higher DDR speeds are only a must if you try to overclock, they have no speed gain if run at the correct speed. You may use faster ram on a slower system, the speeds given are what is needed minimum.
    Perform RAM test tools, ie http://www.memtest.org if you suspect RAM is faulty, such as BSOD or data corruption. [added by Maesus]
    Try your system allway's with 1 stick of ram, adding more sticks can give all the trouble too.
    Some sticks just won't work in pair and a lot fail when you put 3 or more in the system.
    When you want to use 3 sticks, make very sure you use the MSI tested ones, they are your best chance that they work without problems.
    If still nothing, try to seat the ram in another slot, sometimes they work better in another slot.
    Thanks boost
    Or rise the Ram voltage a little, be carefull doing this!
    Sometimes this works when you have a lot of ram in there.
    BIOS  
    BIOS settings not right, clear the CMos and start with the default settings, if it works, try setting ONLY the FSB to 133 if needed, nothing more.....
    And go further from there......
    Clearing CMos
    When you clear the CMos, make sure that all power is cut from the system.
    This is done by takeing the wall-plug out or use the switch on the powersupply to turn it off.
    On most boards, as far as I know all MSI boards, you must set the JBat1 to position 2-3 (clear position) for about 10 seconds, then set it back to 1-2 (keep data position)
    After this your CMos should be cleared and you can turn the system back on.
    In some rare cases it's needed to take the battery out too for a minute or so.
    It can happen that the system will prompt you to set the BIOS again, go into the BIOS and set everything you need, then save the settings.
    Thanks fguevara.
    Harddisks  
    Harddisk is giving problems, most of the time with WD drive's, they are jumpered somewhat strange compared to others:
    No jumper = Stand-Alone no other drive attached to the cable.
    Jumper master = if you have a slave drive attached
    Jumper slave = when it's slave to another drive
    Harddisk is doing weird things:
    Make sure you have connected the blue connector to the board, and don't let the other end of the cable unused, make sure there is a device connected to it.
    The middle connector can be left into the air without problems if not needed.
    IBM harddisks seem to fail a lot, try Drive-Fitness-Test on it, see if it has problems.
    Click here for DFT
    Other brand drives can have problems too, make sure they are ok, as harddisk failure can cause all sorts of problems.
    Allway's be sure your harddisk is in tip-top shape, if not, replace it and try another to verify.
    For more information read this: Click here.
    To know what harddisks your motherboard support, use this link.
    To enable harddisk over 137GB in Win2000 edit this registry key:
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters]
    "EnableBigLba"=dword:00000001
    The KT4 raid boards only support 1 harddisk on IDE3, the rest must be SATA drive's!!
    Harddisk/power led not functioning - thanks to Tweetyoost
    If your HD led or power led not work try to switch(wrong + or - side) the connectors on the motherboard.
    leds will work only when + or - is correct
    Thanks Tweetyoost.  
    Floppy drive's  
    If your floppy drive doesn't work or the led stay's on all the time.
    Make sure the floppy is set correctly in the BIOS, as the BIOS doesn't autodetect a floppy drive.
    Check the cable, make sure the twist in the cable is at the floppy-drive side.
    If the light stay's on, flip the connector at the floppy-drive arround.
    Sometimes it happens that even after all this, they still don't work, try with another drive from another brand.
    Not able to enter the BIOS or lockup  
    When you try to enter the BIOS it won't go in there or
    lockup, but your system is running fine.
    This symtom can happen when your CPU-Cooler is giving spikes on the coolerwire.
    Try with another brand of cooler to test if it solves it.
    Keyboard and optical mouse lights stay on after power off[/U]
    Some motherboards have a jumper called JKBV1, this jumper is located (mostly) near the keyboard connector, put it in the other position.
    If your board doesn't have the jumper, try to find the following BIOS settings and turn them off:
    resume on KBC
    resume on PS/2
    resume by alarm
    USB ports not working[/U]
    Check in the BIOS if the ports are enabled.
    USB2.0 ports are supported in Win2000+SP3 and XP+SP1, just let the OS reinstall the ports and they should work.
    Thanks Stygge
    Replacing parts and the system won't boot after
    It's never a good idea to replace stuff like CPU and ram without taking the board out of the case.
    But if you still like to do so, please support the board, because if you don't you might bent the board a little and cause other components to make bad contact.
    Allways support the board when you replace stuff, no matter what!
    Also make sure your system can take the replacement, it could happen for example that your powersupply can't handle your changed videocard from GF2MX to GF4Ti4600.
    Test all the parts in another system
    Make sure that the new part is in good working order in the first place (in particular: videocard, CPU, memory): try it in another system, or have it demonstrated by the one you bought it from if possible.
    Testing might also give you a clue on what is actually wrong in your own system.
    Thanks HansH.
    Checking the powersupply
    Don't do this if you don't know what you are doing!
    Disconnect the powersupply.
    Orientate the 20pin Powerconnector with the clip up.
    Locate pin 4 and pin 8 top row, mostly green and black wire.
    Use a wire to short them (or better a 12V test lamp).
    Now connect the power and the fan inside the powersupply should start spinning.
    If it doesn't your powersupply maybe dead.
    Thanks HansH.
    KT4 users  
    Please read the Un-Official KT4 guide if you have CRC errors or strange crashes.
    These can be BIOS problems.
    In any case !!!Only flash if the system is stable!!!
    Set default-settings and FSB100 to make it stable first!!!
    Motherboards making a Siren-sound
    If your board is making the sound of a firetruck, BEEP-BOOP-BEEP-BOOP...
    Check the folowing:
    1. CPU too hot
    2. chassis intrusion was enabled in the BIOS
    3. PSU is below min/max allowable value
    Stutter in audio
    Remove your antivirus software.
    We have heard a few cases where the stuttering was created by badly behaving antivirus software.
    Disable cpu halt command if it's in the BIOS (Thanks Pascal16)
    Windows  
    Windows2000/XP won't run stable, try to disable APIC and install again....
    Not all drivers/devices like the APIC.
    Windows2000/XP won't install USB2.0, install the latest servicepak (SP3 Win2000 or SP1 WinXP).
    Let Windows rediscover the USB ports, they should work now.
    If you have driver or other problems and don't know what to do anymore but Windows does function without crashing, read this: Click here.
    Audio [added by Maesus, 20/2/2003]
    Can't stream AC3 via SPDIF to external DD decoder? try this ac3filter [info provided by Manfred ]
    Lan not working 100MBit
    You could try this patch, seems to work on some boards.
    The download-link is at the bottom of this post.
    I think I have about covered all most commen problems....
    Check those first before you ask us, as it's not fun to type the same over and over again.... :(
    Another good link for trouble shooting is here: Link
    If you have more issues that can solve problems, please write your thing below......
    I will insert your comments in this guide, with credits, offcourse 8)
    !!I will delete any attempt for discussion or problem report below this message.....!!
    Please report back, in another thread, if your problem was solved and how you did it, this will help others a great deal.
    It's only ment to help people as a guide to where the problem can be, start a new thread if this guide didn't solve your problem and you need more help!
    This thread is only for the experts to guide you into a solution :]

    Dude thank-you for your wonder detailed knowldge, I have descovered that lets say xp 1700 in a ultra 2 can only handle at the most 143fsb mult at 12.
    Given the settings" irq's are a major",part of directing traffic and power? example:
    Sound blaster Live , uses two irq's most common at"Auto" is, irq 10, or 5, and Sound blaster 16 emulation usually takes irq 5,. I have found that the sound card in slot3 works great , but to do this I had to change the Bio's and assign slot 3 irq 7 . and make sure printer port has share irq enabled
    Problems that accure with bad traffic are like this. Start a dedicated server. minimize than start your game?":censored:  no sound what could be wrong"? Shoot another problem Connection problem?. The computer nerd is getting trouble over the ordeal. ANSWER! IRQ can fix the problem, Study the irq and make changes as you go. "what would it be like with no stop signs,,,that is the same as a irq. with the same knowldge this topic brings IRQ need to be clearly understood.
    I can honestly say my system is error free and running like a dream.
    xp 2500 barton 333
    creative sound 5.1gamers.
    512 mb kingston ram 400 mhz
    boadband either onboard.
    MSI 5700 128 mb ddr
    Setting are:
    163 fsb
    mult of 11
    ddr 333
    video memory clock down to 450mhz
    3d clock to 390mhz
    The delta is a smooth running board also I want to mention to the person with crackling sounds, change the irq like I did, that fix the problem and the power is totaly too good to be true.

  • TS1702 WHY EVERYTIME APPLE PUTS OUT A NEW VERSION OF IBOOKS DOES IT CRASH HAPPENED LAST TIME AND NOW WITH V6 i HAVE DONE EVERYTHING IN THE TROUBLE SHOOTING GUIDE LIKE SIX TIMES AND IT STILL WONT LOAD MY BLOODY BOOKS

    Why does ibooks crash everytime there is an update? I am so sick to death of having to stuff around and do all the trouble shooting rubbish to try and get ibooks working again, everytime there is an up date. I have wiped restored re synced changed usb leads turned my computer off unplugged and replugged every bloody thing  about a dozen times and still after a week, instead of reading my books I have a very expensive paperweight. What is the problem and why does this keep happening with every new update. I am so frustrated and annoyed that I can't just read my book, it is why I bought the **** thing.  Anybody got any other ideas before I go insane?

    Dude thank-you for your wonder detailed knowldge, I have descovered that lets say xp 1700 in a ultra 2 can only handle at the most 143fsb mult at 12.
    Given the settings" irq's are a major",part of directing traffic and power? example:
    Sound blaster Live , uses two irq's most common at"Auto" is, irq 10, or 5, and Sound blaster 16 emulation usually takes irq 5,. I have found that the sound card in slot3 works great , but to do this I had to change the Bio's and assign slot 3 irq 7 . and make sure printer port has share irq enabled
    Problems that accure with bad traffic are like this. Start a dedicated server. minimize than start your game?":censored:  no sound what could be wrong"? Shoot another problem Connection problem?. The computer nerd is getting trouble over the ordeal. ANSWER! IRQ can fix the problem, Study the irq and make changes as you go. "what would it be like with no stop signs,,,that is the same as a irq. with the same knowldge this topic brings IRQ need to be clearly understood.
    I can honestly say my system is error free and running like a dream.
    xp 2500 barton 333
    creative sound 5.1gamers.
    512 mb kingston ram 400 mhz
    boadband either onboard.
    MSI 5700 128 mb ddr
    Setting are:
    163 fsb
    mult of 11
    ddr 333
    video memory clock down to 450mhz
    3d clock to 390mhz
    The delta is a smooth running board also I want to mention to the person with crackling sounds, change the irq like I did, that fix the problem and the power is totaly too good to be true.

  • Trouble shooting guide required

    Hi Gurus,
    Can any one provide me any documents for error handling guide for SAP BODS. Where we can check our errors and can resolve them.
    Thanks in Advance,
    DJ

    Hi Akhilesh,
    Can you give me some documents on this.
    Thanks & Regards,
    DJ

  • TS1538 I've been through the trouble shooting guides, and even wiped my ipod touch back to factory settings,  Itunes will not see it. My laptop has seen it before. I'm at a loss. Can any one help?

    Here are my stats from the diagnostics.
    Microsoft Windows 7 x64 Home Premium Edition Service Pack 1 (Build 7601)
    Hewlett-Packard HP Pavilion dv6 Notebook PC
    iTunes 11.0.2.26
    QuickTime 7.7.3
    FairPlay 2.3.31
    Apple Application Support 2.3.3
    iPod Updater Library 10.0d2
    CD Driver 2.2.3.0
    CD Driver DLL 2.1.3.1
    Apple Mobile Device 6.1.0.13
    Apple Mobile Device Driver 1.59.0.0
    Bonjour 3.0.0.10 (333.10)
    Gracenote SDK 1.9.6.502
    Gracenote MusicID 1.9.6.115
    Gracenote Submit 1.9.6.143
    Gracenote DSP 1.9.6.45
    The current local date and time is 2013-05-02 10:41:33.
    iTunes is not running in safe mode.
    WebKit accelerated compositing is enabled.
    HDCP is supported.
    Core Media is supported.
    Video Display Information
    Intel Corporation, Intel(R) HD Graphics 3000
    **** External Plug-ins Information ****
    No external plug-ins installed.
    **** Device Connectivity Tests ****
    iPodService 11.0.2.26 (x64) is currently running.
    iTunesHelper 11.0.2.26 is currently running.
    Apple Mobile Device service 3.3.0.0 is currently running.
    Universal Serial Bus Controllers:
    Renesas Electronics USB 3.0 Host Controller.  Device is working properly.
    Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26.  Device is working properly.
    Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D.  Device is working properly.
    No FireWire (IEEE 1394) Host Controller found.

    If you have been through all of the steps in the knowldge base article, especially restarting the Apple Mobile Device Service, have you tried connecting in recovery mode?  Start iTunes, connect the USB end of the cable, and then while pressing the home button connect the dock connecter end of the cable to the iPod.
    But most basic, have you tried connecting using different cables to be sure there is not a wiring fault?

  • ATI vid.card trouble shoot guide

    True,
    There seem to be some stabilty issues with ATI, all of which can be overcome.
    First is the VPU recover option. That option makes it less stable and does nothing beneficial, best turn it off.
    Also faste write (bios option), it doesn't enhance performance, only decreases stabalitity.
    If it is still unstable, set AGP to 4x. This makes it slighly (less then 1pct. ) slower, but might make it more stable.
    Other drivers occasionly might help. For older cards, older drivers are best suitable. E.g. a R9700 runs best on Cat 4.5. Do make sure the driver you use supports the DirectX version that you need !
    Last resort is upping the AGP voltage (no more then 0,1v !). If it is still instable, RMA it !
    Despite the issues, I still think ATI makes very good vid.cards. My next card wil probably be an ATI again 

    And I thougt you were my friend     
    Look here for the performance difference fast write and AGP4x make:
    http://www.pctuning.cz/Default.aspx?CatID=75&LayId=2&ArtId=19189&ChapID=4944
    These tests have been done with a 9700PRO the difference will probably be more significant with a faster card.
    Furthermore, take into account that a 9600 draws from the 5v line, the 9700, 9800 and X800 draw from the 12v line as well.

  • Where can I find motherboard general trouble shooting guide?

    "Refer to http://www.msi.com.tw/program/e_service/forum/index.php?threadid=1131&boardid=13&styleid=1"
     dont work..

    Just post your problems here, and let the community answer your problems..

  • HT3964 My internal camera is no longer registering on any application or in the system utillities even ater i followed the trouble shooting instructions on mac, what do i de next?

    I have resently updated to mavericks and  my camera has been working fine, then it has just stopped registering on the comuter. I have followed all the instructions of the trouble shooting guide for isight and still nothing is registering.

    I have resently updated to mavericks and  my camera has been working fine, then it has just stopped registering on the comuter. I have followed all the instructions of the trouble shooting guide for isight and still nothing is registering.

  • I have an iMac with mountain lion 10.8.3 with boot camp 5.0.2 .i installed windows 7 -64 bit with boot camp but the boot camp didn't install drivers for windows please guide me for trouble shooting .

    i have an iMac with mountain lion 10.8.3 with boot camp 5.0.2 .i installed windows 7 -64 bit with boot camp but the boot camp didn't install drivers for windows please guide me for trouble shooting .

    Kappy wrote:
    Boot Camp doesn't install the drivers. You have the drivers on a separate USB device if you followed directions. Once in Windows connect the USB drive with the driver software. It should startup automatically and install the drivers.
    You don't even need to do that. As downloading the drivers from within Boot Camp Assistant can be unreliable, it is better to get the package directly from here:
    http://support.apple.com/kb/DL1638
    Copy the .zip file to a USB flash drive or burn it to a DVD in OS X. Install Windows as normal, insert the flash drive/DVD in Windows, copy the .zip file to the hard drive, extract it, then run the setup executable.

  • Kisight: How do I get my iSight working ?  Trouble Shooting an iSight Camera.  (Version 3)

    Replacement for the second draft of this Thread   (To be removed if Published as Tip)
    kisight: How do I get my iSight working ?
    Trouble Shooting an iSight Camera.  (Version 3)
    Hi,     On many subjects Apple has Articles and Documents that can help.
    In some case they are written by an Engineer or similar and can miss the mark for the average user.
    In other cases they are crafted, detailed responses to an issue that has popped up many times in the Apple Discussions and take the best from many responses in those User-to-User Discussions, creating something that can not be surpassed.
    This is the case of the Apple Article HT2090 on Trouble Shooting an iSight.
    It lists steps and processes to go through for both Internal iSights and External ones.
    However as with most things it does sometime pay to reword things differently so that people grasp the points in language they understand.
    The info here is a reworking itself of two pages at ralphjohns.co.uk/EZ Jim pages namely EZ JIm's page 2 Where can I Find Help With My iSight ? and his page 4, How Can I Test My iSight is Completely Functional ?  which were written several years ago and predate the Apple Article, being aimed at the External iSight.  They have been updated since to address the Internal iSight as well but some of the comments are useful between the two types.
    External First.  For Internal iSights Start at 2b)  (you will need to adjust some options/steps as the Internal is USB)
    Steps
    1) Pre Purchase
    If buying an External iSight you should if you an get to see it in action.Apple no longer sells the External iSight so you will be buying it second hand.If you cannot get to see the device plugged in and working on  Mac then check the smaller print of the seller and selling site as to nature of Returns and Faulty Goods.
    2) Does it work ?
    a) First of all Plug it in.  It should come with a suitable mount (although there are variants on this) and a 6 pin to 6 pin Firewire cable.
    Ideally it should have it's own Firewire port/socket on your computer. Connecting it "DaisyChained" to other devices can be a problem as they do not all use Firewire at the same Data speed.
    It will then go through some checks as the OS powers it up and checks it's firmware.
    Do not be concerned that the little green indicator light atop your iSight illuminates for a few seconds and then goes dark when you first connect your iSight or power on your Mac. Do not be concerned if you hear a soft whir as iSight attempt to focus either. Both these occurrences are normal. If your iSight passes the following tests, do not worry about this sound or the status of the green light.
    There is no ON switch as such.  It does have an iris mechanism that can be controlled by the User.  The iris should be turned so you can see the Lens for the iSight to send pictures to an application.
    b) Pick an Application to see the picture the iSight produces.iChat is one application you can use. Photobooth is another. iMovie (Version 4 or above for external iSight -- Version 6 or above for in-built iSight) and Comic Book (if bundled on your Mac) are yet more.
    See this Users Tip for more applications Or this page for yet more.
    Photo Booth is probably the simplest as it has no Preferences to choose a camera in the original version and is done from the Menu items in later versions  (nor is there any setting in the OS) and Photo Booth will default to the External Camera if one is plugged in before the application is started.     If you see your self or what the camera is pointing at, It Works !!
    3) If it does Not Work
    a) Check Cables/leads.  Re-seat the cable at both ends. DO this carefully as although Firewire cables are keyed to fit the right way it has been known to force them the wrong way.
    Try another 6 pin to 6 pin firewire cable.
    b) Unplug the cable from any other FireWire device and give the iSight it's Own FireWire port/socket on the Mac (exclude issues with other FireWire devices). It is important that this be a port/socket on your computer and that you know that it works. Do not use a port in a FireWire hub or another FireWire device or a FireWire port in an Apple Display for testing.  (Also see d below if you have an 800 FIreWIre Computer)
    c) Check System Profiler (Apple Icon menu top Left > About this Mac. > More Info Button)Open the Reveal Triangles to see the list and go to Hardware > FireWire.  (Use USB for Internal Cameras)
    If it appears here try booting or Logging in as another user on the Mac (Create a Test account if you don't have one) and try item 2b) above again.
    d) With FireWire 800 computers you may have to change your FireWire 400 to 800 Adaptor or Cable to get full Audio functionality with Lion Apps
    If it is not in the System Profiler you are almost certainly going to need the Trouble Shooting Article from Apple at this point.  This Article may also be of help (number HT1317 What to do if your computer won't recognise a FireWire or USB device).
    If you have not resolved things at this stage it is going to be time for an Engineer with Apple credentials.There are no user serviceable parts inside any iSight.
    Other Items
    Audio.
    The External Camera has two mics inside.The volume it records at or plays through for iChat is controlled in System Preferences > Sound > Input tab (select device) and this should be set to get the blue response bar to at least half way (preferably three quarters) when you talk.The same applies to any other Mic, even the Internal one on laptops and some other Macs.
    Firmware.
    The System Profiler as detailed above should tell you the Firmware the iSight has.  The current version is 1.0.3 and was updated in Panther.  (Essentially it is an Audio compatibility update but does seem to help in other situations)
    If your computer is running Panther (10.2.x) then use this Updater
    If running Tiger (10.4.x) or Leopard (10.5.x) then navigate manually to your Hard Drive/System/Library/Core Services/iSight Updater and run the updater found there.
    If an iSight is Plugged in on the Computer when you do an  OS update and the firmware needs updating on the iSight this app is supposed to be triggered but it seem it may need a hand at times.
    Focusing on the External iSight
    Essentially the External iSight is self or Autofocusing.
    If in doubt then try better lighting and strong colours as opposes to light or pastels.
    (All built-in iSights are fixed focus. Therefore, unless a built-in iSight lens cover is dirty or smudged, any built-in iSight whose image is blurry needs service by an Engineer with Apple credentials.)
    EZ Jim has these more specific recommendations for piece of mind.
      Make a cross whose lines are about one-half inch or more wide on a plain background to use as a focus target. (I have even used black electrical tape.)
    Turn on plenty of light and hold the target very still at about two or three feet from the lens. Watch iSight focus. (You may need to use a tripod or brace yourself to hold the target still enough.)
    Then quickly move the target and hold it very still at about one foot away from the lens. Watch iSight focus.
      Finally, move in to about six inches from iSight, and check focus there, too. (Holding the target still is more important as you get closer to iSight.)
    This Users Tip by Ian Bickerstaff  can give you clues for any application really  "Look  and sound good in iChat"
    Other Info and Links
    iSight Support info at Apple Links to Users Guide, Manual and many other topics on the External iSight.
    Apple's iSight Firewire Connectivity FAQs
    Apple's iSight Service FAQs
    If you feel you have not understood or think you have not grasped something here or in the links so far try the iSight Discussion Forum
    1:13 PM      Saturday; October 8, 2011
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb( 10.6.8)
     Mac OS X (10.6.8),
    "Limit the Logs to the Bits above Binary Images."  No, Seriously

    Replacement for the second draft of this Thread   (To be removed if Published as Tip)
    kisight: How do I get my iSight working ?
    Trouble Shooting an iSight Camera.  (Version 3)
    Hi,     On many subjects Apple has Articles and Documents that can help.
    In some case they are written by an Engineer or similar and can miss the mark for the average user.
    In other cases they are crafted, detailed responses to an issue that has popped up many times in the Apple Discussions and take the best from many responses in those User-to-User Discussions, creating something that can not be surpassed.
    This is the case of the Apple Article HT2090 on Trouble Shooting an iSight.
    It lists steps and processes to go through for both Internal iSights and External ones.
    However as with most things it does sometime pay to reword things differently so that people grasp the points in language they understand.
    The info here is a reworking itself of two pages at ralphjohns.co.uk/EZ Jim pages namely EZ JIm's page 2 Where can I Find Help With My iSight ? and his page 4, How Can I Test My iSight is Completely Functional ?  which were written several years ago and predate the Apple Article, being aimed at the External iSight.  They have been updated since to address the Internal iSight as well but some of the comments are useful between the two types.
    External First.  For Internal iSights Start at 2b)  (you will need to adjust some options/steps as the Internal is USB)
    Steps
    1) Pre Purchase
    If buying an External iSight you should if you an get to see it in action.Apple no longer sells the External iSight so you will be buying it second hand.If you cannot get to see the device plugged in and working on  Mac then check the smaller print of the seller and selling site as to nature of Returns and Faulty Goods.
    2) Does it work ?
    a) First of all Plug it in.  It should come with a suitable mount (although there are variants on this) and a 6 pin to 6 pin Firewire cable.
    Ideally it should have it's own Firewire port/socket on your computer. Connecting it "DaisyChained" to other devices can be a problem as they do not all use Firewire at the same Data speed.
    It will then go through some checks as the OS powers it up and checks it's firmware.
    Do not be concerned that the little green indicator light atop your iSight illuminates for a few seconds and then goes dark when you first connect your iSight or power on your Mac. Do not be concerned if you hear a soft whir as iSight attempt to focus either. Both these occurrences are normal. If your iSight passes the following tests, do not worry about this sound or the status of the green light.
    There is no ON switch as such.  It does have an iris mechanism that can be controlled by the User.  The iris should be turned so you can see the Lens for the iSight to send pictures to an application.
    b) Pick an Application to see the picture the iSight produces.iChat is one application you can use. Photobooth is another. iMovie (Version 4 or above for external iSight -- Version 6 or above for in-built iSight) and Comic Book (if bundled on your Mac) are yet more.
    See this Users Tip for more applications Or this page for yet more.
    Photo Booth is probably the simplest as it has no Preferences to choose a camera in the original version and is done from the Menu items in later versions  (nor is there any setting in the OS) and Photo Booth will default to the External Camera if one is plugged in before the application is started.     If you see your self or what the camera is pointing at, It Works !!
    3) If it does Not Work
    a) Check Cables/leads.  Re-seat the cable at both ends. DO this carefully as although Firewire cables are keyed to fit the right way it has been known to force them the wrong way.
    Try another 6 pin to 6 pin firewire cable.
    b) Unplug the cable from any other FireWire device and give the iSight it's Own FireWire port/socket on the Mac (exclude issues with other FireWire devices). It is important that this be a port/socket on your computer and that you know that it works. Do not use a port in a FireWire hub or another FireWire device or a FireWire port in an Apple Display for testing.  (Also see d below if you have an 800 FIreWIre Computer)
    c) Check System Profiler (Apple Icon menu top Left > About this Mac. > More Info Button)Open the Reveal Triangles to see the list and go to Hardware > FireWire.  (Use USB for Internal Cameras)
    If it appears here try booting or Logging in as another user on the Mac (Create a Test account if you don't have one) and try item 2b) above again.
    d) With FireWire 800 computers you may have to change your FireWire 400 to 800 Adaptor or Cable to get full Audio functionality with Lion Apps
    If it is not in the System Profiler you are almost certainly going to need the Trouble Shooting Article from Apple at this point.  This Article may also be of help (number HT1317 What to do if your computer won't recognise a FireWire or USB device).
    If you have not resolved things at this stage it is going to be time for an Engineer with Apple credentials.There are no user serviceable parts inside any iSight.
    Other Items
    Audio.
    The External Camera has two mics inside.The volume it records at or plays through for iChat is controlled in System Preferences > Sound > Input tab (select device) and this should be set to get the blue response bar to at least half way (preferably three quarters) when you talk.The same applies to any other Mic, even the Internal one on laptops and some other Macs.
    Firmware.
    The System Profiler as detailed above should tell you the Firmware the iSight has.  The current version is 1.0.3 and was updated in Panther.  (Essentially it is an Audio compatibility update but does seem to help in other situations)
    If your computer is running Panther (10.2.x) then use this Updater
    If running Tiger (10.4.x) or Leopard (10.5.x) then navigate manually to your Hard Drive/System/Library/Core Services/iSight Updater and run the updater found there.
    If an iSight is Plugged in on the Computer when you do an  OS update and the firmware needs updating on the iSight this app is supposed to be triggered but it seem it may need a hand at times.
    Focusing on the External iSight
    Essentially the External iSight is self or Autofocusing.
    If in doubt then try better lighting and strong colours as opposes to light or pastels.
    (All built-in iSights are fixed focus. Therefore, unless a built-in iSight lens cover is dirty or smudged, any built-in iSight whose image is blurry needs service by an Engineer with Apple credentials.)
    EZ Jim has these more specific recommendations for piece of mind.
      Make a cross whose lines are about one-half inch or more wide on a plain background to use as a focus target. (I have even used black electrical tape.)
    Turn on plenty of light and hold the target very still at about two or three feet from the lens. Watch iSight focus. (You may need to use a tripod or brace yourself to hold the target still enough.)
    Then quickly move the target and hold it very still at about one foot away from the lens. Watch iSight focus.
      Finally, move in to about six inches from iSight, and check focus there, too. (Holding the target still is more important as you get closer to iSight.)
    This Users Tip by Ian Bickerstaff  can give you clues for any application really  "Look  and sound good in iChat"
    Other Info and Links
    iSight Support info at Apple Links to Users Guide, Manual and many other topics on the External iSight.
    Apple's iSight Firewire Connectivity FAQs
    Apple's iSight Service FAQs
    If you feel you have not understood or think you have not grasped something here or in the links so far try the iSight Discussion Forum
    1:13 PM      Saturday; October 8, 2011
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb( 10.6.8)
     Mac OS X (10.6.8),
    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • Trouble shooting XI interfaces

    What are the different methods of trouble shooting XI Interfaces.
    Regards,
    -Naveen.

    Hi Naveen,
    Refer to the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283">SAP XI Troubleshooting Guide</a>
    Also refer to these Problem Analysis Scenarios
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/29/e0194120ddf223e10000000a155106/content.htm">Mapping fails for certain message type</a>
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm">Sending XI thru XI failed</a>
    Hope this helps.
    Rgds,
    Sam Raju]

  • TROUBLE SHOOTING PROBLEM ON SQL*NET, NET8.X, AND NET SERVICES

    제품 : SQL*NET
    작성날짜 : 2002-11-24
    TROUBLE SHOOTING PROBLEM ON SQL*NET, NET8.X, AND NET SERVICES
    (GENERATING TRACE FILE OF SQL*NET, NET8.X, AND NET SERVICES)
    ==========================================================
    PURPOSE
    이 글은 고객들이 Oracle Server의 Oracle Networking 제품들을 사용하다가
    Networking과 관련된 문제를 만났으나 스스로 해결할 수 없는 경우, 예를
    들어 http://metalink.oracle.com 에서 같은 case를 발견할 수 없는 경우,
    원인을 찾기 위하여 Networking 제품의 trace를 떠 보는 방법을 설명합니다.
    Explanation
    Oracle Networking 제품을 사용 중에 어떠한 문제를 겪는 경우 무엇보다도
    OS의 Networking Protocol Stack 쪽을 살펴보는 것이 선행되어야 합니다.
    일부 고객분들은 Oracle Networking 제품들이 OS의 Protocol Stack이 동작
    하는데 어떤 중대한 영향을 주는 것이 아닌가 하고 문의를 합니다만
    그러한 의문은 Oracle Networking 제품도 OS의 Protocol Stack을 사용하는
    하나의 network client라는 것을 이해함으로써 해소가 됩니다.
    Oracle Networking 제품도 OS의 Protocol Stack을 이용하는 하나의 network
    client이기 때문에 Oracle Networking 제품이 OS Protocol Stack의 동작에
    어떠한 식으로든 영향을 준다던가 하는 것은 있을 수 없기 때문입니다.
    고객의 관점에서 OS의 Protocol Stack은 정상적으로 설정이 되었다고 믿고
    있으며 기타 networking 환경을 정확히 판단할 수 없는, 예를 들어
    host설정은 잘 되어 있다고 믿고 있으나 firewall을 통해야만 하는 등의
    다소 접근하기 어려운 networking 환경에서 networking이 잘 되지 않는,
    예를 들어, Oracle Server에 연결이 잘 안되거나 연결 중 networking
    error가 발생하는 경우에는 http://metalink.oracle.com에서 같은 case를
    찾는 것이 가장 빠른 해결 방법입니다.
    그러나 드물게 http://metalink.oracle.com에서 같은 case가 나오지 않는
    경우 Oracle Networking 제품의 trace file을 떠서 원인을 찾게 됩니다.
    Oracle Networking 제품은 Oracle 7.x에서 SQL*Net, Oracle 8.x에서 Net 8.x,
    Oracle 9.x에서 Oracle Net Services라는 이름이 가지고 있으나 여기에서는
    편의상 모두 Oracle Networking 제품으로 부르도록 하겠습니다.
    아울러 여기서 언급하는 Trace File은 Oracle Server의 Trace File과
    다른 것입니다. Oracle Server의 Trace File은 database instance의 대한
    내용만을 기록하며 Oracle Networking 제품의 Trace File은 networking에
    대한 내용만을 기록합니다.
    Trace File의 작성 방법은 Oracle 7.x부터 9.x까지 같습니다.
    Solution Description
    1. Client가 되는 host에서 어떠한 문제를 경험한 경우, 간혹 문제의 발생
    빈도가 낮거나 network나 server 쪽에 이상을 느끼시면서도 문제를 확인하기
    여러운 경우가 있습니다. 이런 경우엔는 문제가 다시 발생될 때 까지
    Client에서 Client Trace File를 작성하여 보아야 합니다.
    a. prompt$ echo $TNS_ADMIN
    b. $TNS_ADMIN이 설정되어 있으면, prompt$ cd $TNS_ADMIN
    아니면, prompt$ cd $ORACLE_HOME/network/admin
    c. vi sqlnet.ora
    # 다음 line들을 추가
    TRACE_LEVEL_client=16
    TRACE_FILE_client=<filename>
    TRACE_DIRECTORY_client=<directory>
    TRACE_UNIQUE_client=TRUE
    :wq
    prompt$
    예를 들어, client가 Windows OS인 경우 다음과 같이 합니다.
    prompt> notepad sqlnet.ora
    TRACE_LEVEL_client=16
    TRACE_FILE_client=client
    TRACE_DIRECTORY_client=D:\temp
    TRACE_UNIQUE_client=TRUE
    prompt>
    d. SQL*Plus와 같은, 또는 사용하던 Client software를 계속 이용
    e. 다시 문제가 발생
    f. 작성된 trace file들의 날자를 보아 문제가 발생한 시간과
    거의 같은 시간에 작성된 file들이 있는지 확인
    prompt> dir D:\temp
    client_<PID1>.trc ...
    client_<PID2>.trc ...
    prompt>
    g. trace를 중단합니다.
    prompt$ vi sqlnet.ora
    TRACE_LEVEL_client=0
    :wq
    prompt$
    h. Trace Assistant를 이용하여 Oracle Networking 제품의 error code
    (이하 TNS error code)를 trace file에서 찾아냅니다.
    prompt$ cd <directory of TRACE_DIRECTORY_client>
    prompt$ trcasst <filename of TRACE_FILE_client>_<PID>.trc > trcasst.out
    prompt$ vi -R trcasst.out
    Trace Assistant (trcasst command)는 Oracle 8.x부터 제공되며,
    Oracle 9.x의 Trace Assistant를 사용할 것을 권합니다.
    i. oerr command로 tns error에 대한 error message를 봅니다.
    예를 들어, 흔한 경우 중에 listener가 실행 중이지 않거나 잘못된
    tnsnames.ora 설정으로 client가 listener가 service 중이지 않은
    network address로 연결을 시도하다가 TNS-12541 TNS-12560 TNS-511
    error가 차례대로 나왔다면 다음과 같이 하여 각 TNS error code에
    대한 message와 설명 및 해결방법을 볼 수 있습니다.
    prompt$ oerr tns 12541
    prompt$ oerr tns 12560
    prompt$ oerr tns 511
    j. Trace Assistant가 알려준 TNS error code를 http://metalink.oracle.com
    에서 검색하여 같은 case가 있는지 확인합니다.
    Web browser에서:
    1) Go to http://metalink.oracle.com, then login
    오른쪽 위 HTML frame에서 :
    2) "Advanced" Button을 누릅니다.
    오른쪽 아래 HTML frame에서:
    3) "Enter Keyword" text box에 tns error code를 모두 입력합니다.
    예를 들어, tns-12541 tns-12560 tns-511
    4) "Search" button을 누릅니다.
    k. http://metalink.oracle.com에서 검색이 거의 되지 않거나
    문제가 매우 이상한 경우 이 글 아래를 보시기 바랍니다.
    2. Client에서 SQL*Plus나 Oracle Client를 사용하는 다른 3rd party
    appliction은 잘 동작하나 유독 tnsping command에서 error가 나는 경우가
    드물게 있습니다. 이 때에는 tnsping command의 trace file을 작성해봅니다.
    prompt$ vi sqlnet.ora
    TNSPING_TRACE_LEVEL=16
    TNSPING_TRACE_DIRECTORY=<directory>
    :wq
    prompt$ tnsping <tns alias>
    3. Server, 즉 listener에 문제가 있다고 생각되는 경우 우선 listener의
    log file을 봅니다. listener의 log에 대해서는 bulletin.18364를
    이용합니다.
    4. listener의 trace file은 다음과 같이 설정합니다.
    listener의 trace 설정은 parameter 이름에 trace file을 작성하고자 하는
    listener의 이름이 오는 점, 설정 후 listener process를 restart해야 하는
    점 두 가지를 제외하면 나머지 절차가 앞서 설명드린 client와 같습니다.
    prompt$ vi listener.ora
    TRACE_LEVEL_<listener name>=16
    TRACE_FILE_<listener name>=<filename>
    TRACE_DIRECTORY_<listener name>=<directory>
    :wq
    prompt$ lsnrctl stop <listener name>
    prompt$ lsnrctl start <listener name>
    5. 만일 위와 같이 http://metalink.oracle.com을 검색하여도
    같은 case가 전혀 없거나 찾아낸 error message들이 원인과 관련이 없어
    보일정도로 매우 이상한 경우 다음과 같이 해봅니다.
    a. Oracle Software의 version과 OS의 version이 certification matrix에
    있는 지 확인합니다.
    Web browser에서:
    1) Go to http://metalink.oracle.com, then login
    왼쪽 menu에서 :
    2) "Certify & Availabilty" menu item을 click합니다.
    오른쪽 아래 HTML frame에서:
    3) 현재 사용중인 Product와 그 version 및 OS와 그 version을 선택하
    여 검색합니다.
    Certification Matrix는 매우 정확하게 정보를 보여주고 있습니다.
    Matrix에 없는 Oracle Product와 OS version은 certify되어 있지 않으며
    모든 Oracle 제품을 Certify되지 않은 OS version에서 사용하는 것은
    그 어떠한 이유로든 보증과 지원이 되지 않습니다.
    만일 사용중인 제품이 certify되지 않은 경우, 무조건 certify된 제품
    과 OS의 version으로 install하여 다시 시도를 해야 합니다.
    예를 들어, Windows OS의 경우 그 어떠한 Oracle 제품도 Windows Me 및
    Windows XP Home Edition에 certify되어 있지 않습니다.
    Windows 2000 Professional 이상에 Certify된 제품은 Oracle 8.1.6부터
    이며 XP Professional 이상에 Certify된 제품은 Oracle 9.0.1부터
    입니다.
    Oracle 제품은 software이기는 하나 매우 완벽한 수준의 제품이라고 할
    수 있습니다. 그러나 Oracle 제품은 하나의 OS의 process로써 실행이
    되고 시간이 지나며 많은 환경이 major upgrade가 되면서 그러한 환경
    에 따라 Oracle software도 새로운 version으로 제작이 되면서 다시
    certification이 이루어지게 됩니다.
    그렇기 때문에 고객들은 특히 다수의 client나 고가의 server를 계획하
    시는 고객들은 저희 certification matrix를 사전에 철저히 확인하셔야
    합니다.
    앞서 Certification Matrix이전에 Installation Guide에 명시된
    OS version만이 certify되어 있다고 생각하시면 되겠습니다.
    b. Unix에서는 Oracle Software를 install한 후 OS의 Networking patch를
    씌우고 사용하다보면 문제가 되는 경우가 있습니다.
    이런 경우 relink를 해주어 바뀐 OS환경에서 Oracle 실행 file들을 다
    시 만들어 주어야 합니다.
    자세한 내용은 http://metalink.oracle.com에서
    다음 글을 읽어 보시기 바랍니다.
    Note:131321.1 How to Relink Oracle Database Software on UNIX
    c. Certify된 환경에서도 원인을 찾을 수 없는 경우 trace file을 가지고
    Oracle Support Services에 문의를 합니다. (지원 계약 고객에 한함)
    Reference Documents
    Chapter 17 Trouble shooting Oracle Net Services
    Oracle 9i Net Services Administrator's Guide
    SQL*Net, Net8.x, Net Services 9.x Network Administration Guide/Reference

    제품 : SQL*NET
    작성날짜 : 2002-11-24
    TROUBLE SHOOTING PROBLEM ON SQL*NET, NET8.X, AND NET SERVICES
    (GENERATING TRACE FILE OF SQL*NET, NET8.X, AND NET SERVICES)
    ==========================================================
    PURPOSE
    이 글은 고객들이 Oracle Server의 Oracle Networking 제품들을 사용하다가
    Networking과 관련된 문제를 만났으나 스스로 해결할 수 없는 경우, 예를
    들어 http://metalink.oracle.com 에서 같은 case를 발견할 수 없는 경우,
    원인을 찾기 위하여 Networking 제품의 trace를 떠 보는 방법을 설명합니다.
    Explanation
    Oracle Networking 제품을 사용 중에 어떠한 문제를 겪는 경우 무엇보다도
    OS의 Networking Protocol Stack 쪽을 살펴보는 것이 선행되어야 합니다.
    일부 고객분들은 Oracle Networking 제품들이 OS의 Protocol Stack이 동작
    하는데 어떤 중대한 영향을 주는 것이 아닌가 하고 문의를 합니다만
    그러한 의문은 Oracle Networking 제품도 OS의 Protocol Stack을 사용하는
    하나의 network client라는 것을 이해함으로써 해소가 됩니다.
    Oracle Networking 제품도 OS의 Protocol Stack을 이용하는 하나의 network
    client이기 때문에 Oracle Networking 제품이 OS Protocol Stack의 동작에
    어떠한 식으로든 영향을 준다던가 하는 것은 있을 수 없기 때문입니다.
    고객의 관점에서 OS의 Protocol Stack은 정상적으로 설정이 되었다고 믿고
    있으며 기타 networking 환경을 정확히 판단할 수 없는, 예를 들어
    host설정은 잘 되어 있다고 믿고 있으나 firewall을 통해야만 하는 등의
    다소 접근하기 어려운 networking 환경에서 networking이 잘 되지 않는,
    예를 들어, Oracle Server에 연결이 잘 안되거나 연결 중 networking
    error가 발생하는 경우에는 http://metalink.oracle.com에서 같은 case를
    찾는 것이 가장 빠른 해결 방법입니다.
    그러나 드물게 http://metalink.oracle.com에서 같은 case가 나오지 않는
    경우 Oracle Networking 제품의 trace file을 떠서 원인을 찾게 됩니다.
    Oracle Networking 제품은 Oracle 7.x에서 SQL*Net, Oracle 8.x에서 Net 8.x,
    Oracle 9.x에서 Oracle Net Services라는 이름이 가지고 있으나 여기에서는
    편의상 모두 Oracle Networking 제품으로 부르도록 하겠습니다.
    아울러 여기서 언급하는 Trace File은 Oracle Server의 Trace File과
    다른 것입니다. Oracle Server의 Trace File은 database instance의 대한
    내용만을 기록하며 Oracle Networking 제품의 Trace File은 networking에
    대한 내용만을 기록합니다.
    Trace File의 작성 방법은 Oracle 7.x부터 9.x까지 같습니다.
    Solution Description
    1. Client가 되는 host에서 어떠한 문제를 경험한 경우, 간혹 문제의 발생
    빈도가 낮거나 network나 server 쪽에 이상을 느끼시면서도 문제를 확인하기
    여러운 경우가 있습니다. 이런 경우엔는 문제가 다시 발생될 때 까지
    Client에서 Client Trace File를 작성하여 보아야 합니다.
    a. prompt$ echo $TNS_ADMIN
    b. $TNS_ADMIN이 설정되어 있으면, prompt$ cd $TNS_ADMIN
    아니면, prompt$ cd $ORACLE_HOME/network/admin
    c. vi sqlnet.ora
    # 다음 line들을 추가
    TRACE_LEVEL_client=16
    TRACE_FILE_client=<filename>
    TRACE_DIRECTORY_client=<directory>
    TRACE_UNIQUE_client=TRUE
    :wq
    prompt$
    예를 들어, client가 Windows OS인 경우 다음과 같이 합니다.
    prompt> notepad sqlnet.ora
    TRACE_LEVEL_client=16
    TRACE_FILE_client=client
    TRACE_DIRECTORY_client=D:\temp
    TRACE_UNIQUE_client=TRUE
    prompt>
    d. SQL*Plus와 같은, 또는 사용하던 Client software를 계속 이용
    e. 다시 문제가 발생
    f. 작성된 trace file들의 날자를 보아 문제가 발생한 시간과
    거의 같은 시간에 작성된 file들이 있는지 확인
    prompt> dir D:\temp
    client_<PID1>.trc ...
    client_<PID2>.trc ...
    prompt>
    g. trace를 중단합니다.
    prompt$ vi sqlnet.ora
    TRACE_LEVEL_client=0
    :wq
    prompt$
    h. Trace Assistant를 이용하여 Oracle Networking 제품의 error code
    (이하 TNS error code)를 trace file에서 찾아냅니다.
    prompt$ cd <directory of TRACE_DIRECTORY_client>
    prompt$ trcasst <filename of TRACE_FILE_client>_<PID>.trc > trcasst.out
    prompt$ vi -R trcasst.out
    Trace Assistant (trcasst command)는 Oracle 8.x부터 제공되며,
    Oracle 9.x의 Trace Assistant를 사용할 것을 권합니다.
    i. oerr command로 tns error에 대한 error message를 봅니다.
    예를 들어, 흔한 경우 중에 listener가 실행 중이지 않거나 잘못된
    tnsnames.ora 설정으로 client가 listener가 service 중이지 않은
    network address로 연결을 시도하다가 TNS-12541 TNS-12560 TNS-511
    error가 차례대로 나왔다면 다음과 같이 하여 각 TNS error code에
    대한 message와 설명 및 해결방법을 볼 수 있습니다.
    prompt$ oerr tns 12541
    prompt$ oerr tns 12560
    prompt$ oerr tns 511
    j. Trace Assistant가 알려준 TNS error code를 http://metalink.oracle.com
    에서 검색하여 같은 case가 있는지 확인합니다.
    Web browser에서:
    1) Go to http://metalink.oracle.com, then login
    오른쪽 위 HTML frame에서 :
    2) "Advanced" Button을 누릅니다.
    오른쪽 아래 HTML frame에서:
    3) "Enter Keyword" text box에 tns error code를 모두 입력합니다.
    예를 들어, tns-12541 tns-12560 tns-511
    4) "Search" button을 누릅니다.
    k. http://metalink.oracle.com에서 검색이 거의 되지 않거나
    문제가 매우 이상한 경우 이 글 아래를 보시기 바랍니다.
    2. Client에서 SQL*Plus나 Oracle Client를 사용하는 다른 3rd party
    appliction은 잘 동작하나 유독 tnsping command에서 error가 나는 경우가
    드물게 있습니다. 이 때에는 tnsping command의 trace file을 작성해봅니다.
    prompt$ vi sqlnet.ora
    TNSPING_TRACE_LEVEL=16
    TNSPING_TRACE_DIRECTORY=<directory>
    :wq
    prompt$ tnsping <tns alias>
    3. Server, 즉 listener에 문제가 있다고 생각되는 경우 우선 listener의
    log file을 봅니다. listener의 log에 대해서는 bulletin.18364를
    이용합니다.
    4. listener의 trace file은 다음과 같이 설정합니다.
    listener의 trace 설정은 parameter 이름에 trace file을 작성하고자 하는
    listener의 이름이 오는 점, 설정 후 listener process를 restart해야 하는
    점 두 가지를 제외하면 나머지 절차가 앞서 설명드린 client와 같습니다.
    prompt$ vi listener.ora
    TRACE_LEVEL_<listener name>=16
    TRACE_FILE_<listener name>=<filename>
    TRACE_DIRECTORY_<listener name>=<directory>
    :wq
    prompt$ lsnrctl stop <listener name>
    prompt$ lsnrctl start <listener name>
    5. 만일 위와 같이 http://metalink.oracle.com을 검색하여도
    같은 case가 전혀 없거나 찾아낸 error message들이 원인과 관련이 없어
    보일정도로 매우 이상한 경우 다음과 같이 해봅니다.
    a. Oracle Software의 version과 OS의 version이 certification matrix에
    있는 지 확인합니다.
    Web browser에서:
    1) Go to http://metalink.oracle.com, then login
    왼쪽 menu에서 :
    2) "Certify & Availabilty" menu item을 click합니다.
    오른쪽 아래 HTML frame에서:
    3) 현재 사용중인 Product와 그 version 및 OS와 그 version을 선택하
    여 검색합니다.
    Certification Matrix는 매우 정확하게 정보를 보여주고 있습니다.
    Matrix에 없는 Oracle Product와 OS version은 certify되어 있지 않으며
    모든 Oracle 제품을 Certify되지 않은 OS version에서 사용하는 것은
    그 어떠한 이유로든 보증과 지원이 되지 않습니다.
    만일 사용중인 제품이 certify되지 않은 경우, 무조건 certify된 제품
    과 OS의 version으로 install하여 다시 시도를 해야 합니다.
    예를 들어, Windows OS의 경우 그 어떠한 Oracle 제품도 Windows Me 및
    Windows XP Home Edition에 certify되어 있지 않습니다.
    Windows 2000 Professional 이상에 Certify된 제품은 Oracle 8.1.6부터
    이며 XP Professional 이상에 Certify된 제품은 Oracle 9.0.1부터
    입니다.
    Oracle 제품은 software이기는 하나 매우 완벽한 수준의 제품이라고 할
    수 있습니다. 그러나 Oracle 제품은 하나의 OS의 process로써 실행이
    되고 시간이 지나며 많은 환경이 major upgrade가 되면서 그러한 환경
    에 따라 Oracle software도 새로운 version으로 제작이 되면서 다시
    certification이 이루어지게 됩니다.
    그렇기 때문에 고객들은 특히 다수의 client나 고가의 server를 계획하
    시는 고객들은 저희 certification matrix를 사전에 철저히 확인하셔야
    합니다.
    앞서 Certification Matrix이전에 Installation Guide에 명시된
    OS version만이 certify되어 있다고 생각하시면 되겠습니다.
    b. Unix에서는 Oracle Software를 install한 후 OS의 Networking patch를
    씌우고 사용하다보면 문제가 되는 경우가 있습니다.
    이런 경우 relink를 해주어 바뀐 OS환경에서 Oracle 실행 file들을 다
    시 만들어 주어야 합니다.
    자세한 내용은 http://metalink.oracle.com에서
    다음 글을 읽어 보시기 바랍니다.
    Note:131321.1 How to Relink Oracle Database Software on UNIX
    c. Certify된 환경에서도 원인을 찾을 수 없는 경우 trace file을 가지고
    Oracle Support Services에 문의를 합니다. (지원 계약 고객에 한함)
    Reference Documents
    Chapter 17 Trouble shooting Oracle Net Services
    Oracle 9i Net Services Administrator's Guide
    SQL*Net, Net8.x, Net Services 9.x Network Administration Guide/Reference

  • Trouble Shooting using SXMB_MONI

    I have developed a scenario which uses XML Message to File Based Adapter.
    When I execute SXMB_MONI, I can see the message paiing through PI successfully and also I can see the message coming to target directory. But I am not able to get all the fields as per the Outbound message type. I have two fields missing.
    I wanted to trouble shoot the issues.
    I checked the payload in each stage. I could see these fields in Inbound Message, Reciever Identification, Interface Determination, Reciever Grouping, Message Branching according to Reciever List. But I am not able to see these fields in the payload of Request Message Mapping and Technical routing.
    So, What could be the problem and can any one please give conceptual overview of trouble shooting. What should be my next step.
    Thanks,

    But I am not able to see these fields in the payload of Request Message Mapping and Technical routing.
    I dont think you need an extensive troubleshooting guide for this....the inbound message has the fields but the output message doesnt.....this means that the mapping is not defined properly.
    The fields that you are looking for are either not mapped in the mapping or there is validation defined in the mapping which is not fulfilled for the source values
    Did you test the mapping in IR --> Message Mapping --> Test tab with the payload from SXMB_MONI .....is it showing the fields at the target?
    Regards,
    Abhishek.

Maybe you are looking for

  • IPod app crashes after 3.1 update

    I just updated to 3.1 and now the iPod app crashes whenever I try to make a Genius playlist. I do this every day so understandably I would like a solution. In the log, it points to low memory as the cause. I don't have much stuff running, I have Wi-F

  • Changing the pulse width of a counter on-the-fly - ?

    I'm seeing strange behavior when trying to change the pulse width of a counter while it is running continuously.  Using the property node I can set the DAQmx Channel Properties "Low Time" and "High Time" when the values are changed by the user (see a

  • Debugging Jni Dll with VC6

    I'm having problems debugging my JNI DLL hosted by a tomcat application. Starting Tomcat under the vc debugger causes a lot of first chance exceptions (0c0000005) to be thrown by JVM.DLL. This happens before my jni dll is even loaded, here's a short

  • How to use Labview to output the coordinates from Pattern Matching result

    I tried to add some labview commands into the vi program created by IMAQ Pattern Matching scrip to output the coordinates of a target point found in Pattern Matching because i need to do some calculations for the point coordinates and I don't want ju

  • IOS 7.1 Random Reboots

    So, according to all the reports, iOS 7.1 is meant to fix the white/black screen reboots. Well, HUGE fail. Ever since I upgraded from iOS 6 to iOS 7, I''ve had reboots, including during a couple of phone calls. Now, with iOS 7.1, they continue. It wo