Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Highlighted
dcsimen Absent Member.
Absent Member.
260 views

What does minor code "could not convert name" mean in a CORBA::SystemException?

A CORBA call to a remote server process is throwing a CORBA::SystemException which prints out as follows: "IDL:omg.org/CORBA/UNKNOWN:1.0: minor = 0x49540100 (could not convert name), completion status = NO".  What does this exception mean?  Is it coming from the remote server's ORB, or from our own ORB?  (We are running Orbix 6.3.7 and this is a C++ CORBA client process.)

0 Likes
1 Reply
Micro Focus Contributor
Micro Focus Contributor

RE: What does minor code "could not convert name" mean in a CORBA::SystemException?

Hi,

An unknown exception could be thrown for user exceptions that are not specified in the method declaration and for non-CORBA exceptions. The "could not convert name" is thrown when the reason could not be determined for the given minor code. Is the server using Orbix or some other ORB?

We will need debug logs from client with GIOP Snoop logging enabled to check if the UNKNOWN exception with this minor code is coming from server or client.

If you have a support account, suggest to raise a case with us with the logs to further investigate the issue.

Regards,
Karthi.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.