Troubleshooting

OLE Initialization or OLE Automation Errors

The most frequent cause of OLE Initialization and Automation errors is missing or incorrectly installed software. Ensure correct installation of the software specified below. Then make sure that you have specified method and property names correctly and that you have declared all "Oracle objects" as type "object".

Possible Cause	Solution
Your system does not contain the Microsoft OLE runtime files or these files are out of date. Note that Visual Basic does not include the OLE file TYPELIB.DLL.	Reinstall Oracle Objects for OLE and select the "Microsoft OLE Libraries" option.
OLE information was not registered in the Windows registration database.	Run REGEDIT.EXE or REGEDT32.EXE (for 32 bit) and merge the information from the file OLE2.REG, which is normally located in the SYSTEM directory.
The Oracle Objects for OLE object information was not registered in the Windows registration database.	Reinstall Oracle Objects for OLE and select the "Oracle Objects Server" option.
The Oracle Objects for OLE object information was not registered in the Windows registration database.	Run regedit.exe or regedt32.exe (for 32 bit) to register information. See Oracle Object for OLE Files.
Your system does not contain the Oracle Required Support Files ( ORA *.DLL, CORE*.DLL, NLS*.DLL, or ORAANSI.DLL).	Reinstall Oracle Objects and select the "Oracle Required Support Files" option or add to your PATH environment variable the directory where these files are located.
Your system does not contain Oracle networking or its files are not on the PATH.	Install Oracle networking or add to your PATH environment variable the directory where these files are located.
You have misspelled a method or property name.	Check the documentation to determine the correct spelling.
You have referenced a method or property from the wrong object.	Check the documentation to determine the correct object.
Your system does not contain ORAANSI.DLL	Reinstall Oracle Objects for OLE and select the "Oracle Objects Server" option, or add to your PATH environment variable the directory in which these files are located.

Oracle Network Errors

The most frequent cause of Oracle networking errors is incorrectly specified connection information. The connection information for Oracle Objects for OLE is specified differently than when using ODBC. Please verify that you have specified connection information correctly, and then make sure your network connection is working properly before using Oracle Objects for OLE. The appropriate Oracle network documentation contains information about testing your connection and about any Oracle network error that you may receive.

Possible Cause	Solution
Incorrect Connect property or argument to the OpenDatabase method.	See the topics on the Connect property or the OpenDatabase method for examples.
Incorrect DatabaseName property or argument to the OpenDatabase method.	See the topics on the DatabaseName property or the OpenDatabase method for examples.
Your system does not contain Oracle networking.	Install Oracle networking.

General Protection Faults

The most frequent cause of GPFs is installing Oracle Objects for OLE while other applications are running that require the OO4O In-Process Automation Server, Oracle Required Support Files or OLE. To avoid this, install Oracle Objects for OLE immediately after starting Windows and before running any other application.

Possible Cause	Solution
Duplicate Oracle Objects for OLE files exist in SYSTEM directories or along the PATH.	Remove any duplicate files. The files OIP8.DLL, and OIP8.TLB should only be located in the ORAHOME\BIN directory.
Duplicate Oracle Required Support Files DLLs exist in the SYSTEM directories or along the PATH.	Remove any duplicate files. Typically, the Oracle Required Support Files DLLs (ORA*.DLL, CORE*.DLL, and NLS*.DLL) are located in ORAHOME\BIN.
Duplicate OLE DLLs exist in the SYSTEM directories or along the PATH.	Remove any duplicate files. The OLE DLLs (listed in the Oracle Objects for OLE Files topic) should only be located in SYSTEM directories.