Neoview ADO.NET Provider Manual (R2.5)

For information about the .NET System.Diagnostics.Trace framework, see http://
msdn.microsoft.com/en-us/library/system.diagnostics.trace(VS.71).aspx
Property type: Boolean
Value: True | False
NOTE: Setting this property to an invalid value disables tracing output to the console.
Specifying a File for Tracing Output NeoviewTraceFile
Use the NeoviewTraceFile property to indicate the file to receive tracing output. One global trace
file is used per application.
Property type: String
Value: Valid pathname for a file.
NOTE: Providing an invalid pathname disables tracing output to a file.
The file is created at run time. If the name given is for a file that already exists, the contents of
that file are overwritten you lose any previous tracing information.
Configuring Tracing
Example 3-2 The Configuration File for Neoview Tracing
This example configuration file sets tracing to return all errors and warnings, disables output to
the standard tracing routine, System.Diagnostics.Trace, and logs tracing output to the file
C:\neoview-adonet.log.
<configuration>
<appSettings>
<add key="NeoviewTraceLevel" value="All" />
<add key="NeoviewTraceConsole" value="False">
<add key="NeoviewTraceFile" value="C:\neoview-adonet.log" />
</appSettings>
</configuration>
Error Messages
Two types of error messages are generated by the provider.
Messages from the Neoview Server these are returned as NeoviewExceptions, and indicate
database-specific errors that are documented in the Neoview Messages Manual.
Messages directly from the ADO.NET provider these messages follow the ADO.NET
specification and standard .NET convention. The exception type is based on the operation
that failed and the cause of the failure. For example, providing an invalid argument to a
function produces an ArgumentException. Possible exceptions for all interfaces are listed
in the in-source XML documentation that is distributed with the provider in the
HP.Data.Neoview.xml file.
In addition to the standard .NET Exceptions, three custom Exception message types are used for
Neoview:
NeoviewException occurs when an error occurs in the NeoviewServer
InternalFailureException occurs in the case of an unrecoverable internal error. Additional
information is provided in the message text. Report this type of message to HP Support.
CommunicationsFailureException occurs in the case of communication error with the
Neoview Server. An exception of this type requires the application to reconnect.
22 ADO.NET for Neoview