Fatal Ni Connect Error 6413
Windows, 32-bit client) Technote (troubleshooting) Problem(Abstract) When creating a data source to an Oracle database on 64-bit Windows with a 32-bit Oracle client, an Oracle bug stops the connection from being successful. The following generic error message is returned by Cognos: "QE-DEF-0285 The logon failed" and "Test connection failed because of an error in initializing provider. ORA-06413: Connection not open" Symptom The following line should be seen within the sqlnet.log file: Fatal NI connect error 6413, connecting to: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=host)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=service_name)(CID=(PROGRAM=C:\Program Files (x86)\cognos\bin\BmtMDProviderMain.exe)(HOST=host)(USER=user)))) Cause This is caused by a bug with the Oracle client. Oracle client cannot resolve third party software applications which have "special" characters in their install paths (which includes parentheses). Environment 64-bit Windows, 32-bit Oracle client, installation path : Program Files (x86) Diagnosing the problem Perform a SQL Net trace to see whether the sqlnet.log file contains the error message noted above. Resolving the problem 1) Find the location of the application that is generating the error. Check the path to this location and see if it contains any parenthesis. If so, you must relocate the application to a directory without any parenthesis in the path. 2) Install patches to Oracle client install as per the link in the Related information section of this article. Related information Oracle forums Document information More support for: Cognos 8 Business Intelligence Install and Config Software version: 8.3, 8.4, 8.4.1 Operating system(s): Windows Software edition: All Editions Reference #: 1384623 Modified date: 2010-01-15 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
using the downloadable Fatal Ni Connect Error 6413 Repair Kit to fix Fatal Ni Connect Error 6413 errors The following discussion features detailed instructions for fixing Fatal Ni Connect Error 6413 errors in Windows system files. Both manual and automated techniques are described that are designed for novice and advanced users, respectively. The overview also provides basic troubleshooting procedures to follow in order to resolve typical causes of Fatal Ni Connect Error 6413 error codes. What are Fatal Ni Connect Error 6413 errors? A Fatal Ni Connect Error https://www-304.ibm.com/support/docview.wss?uid=swg21384623 6413 error code is caused by a Hexadecimal formatting error. That format is the most common one that software programmers employ for Windows system files and Windows OS-compatible hardware drivers and software apps. Manufacturers and developers of software apps and hardware drivers use different codes to indicate various types of errors. The Fatal Ni Connect Error 6413 error message appears as a long numerical http://thewinwiki.org/fatal-ni-connect-error-6413/ code along with a technical description of its cause. In many instances, a Fatal Ni Connect Error 6413 error code could have multiple Fatal Ni Connect Error 6413 parameters. Each hexadecimal code denotes a different memory address location that loaded instructions when the error was generated. Additional messages associated with this matter: Install Fatal Ni Connect Error 6413 Reinstall Fatal Ni Connect Error 6413 Fatal Ni Connect Error 6413 crash Fatal Ni Connect Error 6413 is missing Remove Fatal Ni Connect Error 6413 Download Fatal Ni Connect Error 6413 Fatal Ni Connect Error 6413 virus How are Fatal Ni Connect Error 6413 error codes caused? Most Fatal Ni Connect Error 6413 errors are due to damaged files in a Windows operating system. Windows system file entry corruption is a serious matter, as it often means a malfunction that may pose a major security risk. If left unchecked, it could result in total and permanent loss of all data and inoperability of the storage media and/or PC device. Numerous events may trigger system file errors. Most common examples include: 1) incomplete software installation; 2) incomplete software uninstallation; 3) improperly deleted h
help you fix it! Causes of the error: Windows Windows Fatal Ni Connect Error 6413 are caused by http://computerfixerrorsfree.com/windows-fatal-ni-connect-error-6413.php misconfigured system files. So, from my experience, If you received a Windows Fatal Ni Connect Error 6413 message then there is a 97.5% chance that your computer has registry http://stackoverflow.com/questions/10299518/connecting-to-oracle-10g-with-the-parenthesis-bug-db-from-vs-dev-server-on-a-6 problems. The Windows Windows Fatal Ni Connect Error 6413 are easy to repair. By downloading and running the registry repair tool RegCure Pro, you can quickly and effectively fix fatal ni this problem and prevent others from occuring. Simply click the links below for your free download. To Fix the problem you need to follow the 3 steps : STEP 1: Download & Install RegCure Pro for Free. NOTE: If the download link doesn't work you may need to Download it Directly from a Mirror Here. STEP 2: Click fatal ni connect "Quick Scan" Button to Scan Your Computer. STEP 3: Click the "Repair All" Button to Repair Your PC! That's All! Scott Chan Technical Description of System Error(for Experts only): Microsoft Windows [Version 5.2.4630] (C) Copyright 1985-2014 Microsoft Corp. C:\Documents and Settings\Administrator>RegCure Pro.exe Windows Windows Fatal Ni Connect Error 6413 may caused by some of the following errors Windows Explorer ErrorsJavascript ErrorsHardware MalfunctionError Symptom include:Can not printing fileBlue ScreenIO errorShutdown problemsHttp error Tags: Windows Windows Fatal Ni Connect Error 6413 4 Response to “RegCure Pro ” BrentonSays: at 9:22 PM Thank you so much! After spending countless hours on this stupid windows fatal ni connect error 6413 problem I almost gave up. RegCure worked like a charm on the first try. It took a bit longer than 10 minutes, closer to 30, but by the time it was finished my PC worked great again. Luke Says: at 3:47 AM Just ran this on my wife's computer and for the first time in a long time, it finally works again! Regcure found over 2500 errors including
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Connecting to Oracle 10g (with the parenthesis bug) DB from VS Dev Server on a 64 bit machine up vote 2 down vote favorite 1 there's a known bug while connecting to an Oracle 10g database from MS Visual Studio on a 64bit machine because of the parenthesis in "c:\program files (x86)" directory where VS is installed. This can be overcome by starting VS via: "C:\PROGRA~2\MICROS~2.0\Common7\IDE\devenv.exe" But when debugging a web app using VS Dev. Server, the same problem happens again since VS start the web server using the "WebDev.WebServer40.exe" path which also contains parenthesis. Is there a workaround that does not include re-installing VS in another directory nor updating Oracle? Here's the error in sqlnet.log: Fatal NI connect error 6413, connecting to: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleXE)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')))(CONNECT_DATA=(SID=XE)(CID=(PROGRAM=C:\Program Files (x86)\Common Files\Microsoft Shared\DevServer\10.0\WebDev.WebServer40.exe)(HOST=PEGASUS)(USER=meno)))) VERSION INFORMATION: TNS for 32-bit Windows: Version 10.2.0.1.0 - Production visual-studio oracle10g 64bit webdev.webserver share|improve this question edited Apr 24 '12 at 14:00 Joel Coehoorn 248k92440661 asked Apr 24 '12 at 13:59 meno 1931419 add a comment| active oldest votes Know someone who can answer