Connecting via ODBC, getting an error code of 39204.   Familiar with 39202, (which is usually invalid chars in passwd), but haven't seen this before and can't seem to find it in documentation.    Google search found a few references, but none that seemed pertinent - and there's nothing in this forum regarding it.

I suspect that it has to do with user/domain authentication, but that's more hunch than fact based.

So, that being said - can anyone point me to what this error code means?

Thank you.

------------------------------
Allen Egerton
Developer
SS&C Technologies Inc
CT US
------------------------------

Allen,

Error Code 39204 can be returned for several reasons and it is normally returned if the API Slave process cannot be started. There are several approaches to get to the bottom of the error.

The first step would be turning on the debug logging for the unirpc process, the method for turning this one varies between Unix and Windows but information on turning on the debugging can be found in our knowledge base.

On UNIX platforms, you can manually start up the UniRPC daemon and specify a logging level of "9". The output needs to be redirected to a path specifying the log file name. The following example shows how to do this at UNIX level.

nohup "$unishared"/unirpc/unirpcd -timeout10 -d9 >> unirpc.log 2>&1 &

Notice the timeout of 10 seconds. This means that if the connection can't be established within 10 seconds, abort the attempt. This frees the UniRPC daemon to service future incoming requests, which can be helpful when there are problems on the client's interface.

On Windows platforms, you can turn on debugging for the UniRPC daemon by starting the service through the Windows Control Panel and specify "-d9" in the "Start parameters"

For UniData only, you can also provide server-side logging for connections using the TRACE_LEVEL parameter in ud_database file. The ud_database file is located in /usr/udnn/include (where "nn" represents the version of UniData). The TRACE_LEVEL parameter can be set to the following:

0 = All fatal errors
1 = All UCI commands in addition to level 0 errors
2 = All parameter and column descriptions plus level 0,1 data
3 = Includes data values plus level 0,1,2 information

The log file generated will be written to $TMP/udsrv_<database-name>.<pid>. "database-name" is the name defined as DATABASE in ud_database file. "pid" is the process-id of the server process handling the connection.

Example entry:

DATABASE=dbase3
UDTHOME=/disk1/ud73
UDTACCT=/home/test/newtest
TRACE_LEVEL=3

To enable server-side logging for ODBC connections in UniVerse, create a file named "TRACEuci" in the UniVerse home account at the operating system level. Logging will be output to a path specified by UniVerse configuration parameter UVTEMP. File name is UVUCIlog_<pid> where "pid" is the process-id of the server process handling the connection.

Hopefully this should help you understand why the message is occuring.


------------------------------
Jonathan Smith
UniData ATS
Rocket Support
------------------------------

---