Ciao Patrizia,

I'm afraid you need to contact Borland's support, or check Borland forums/newsgroups to get that information.

The error code seems pretty "high", and the fact that the error message is "UNKNOWN" makes me think that the type of problem could be (and i say again could be) hard to get.

This is a description of a UNKNOWN corba error... probably you already have this, but you never can tell:

Corba UNKNOWN error:

The server throws something other than a correct exception, such as a Java runtime exception.
There is an IDL mismatch between the server and the client, and the exception is not defined in the client program. In DII, if the server throws an exception not known to the client at time of compilation and the client did not specify an exception list for the CORBA::Request. Set the property vbroker.orb.warn=2 on the server to see which runtime exception caused the problem.