Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies reply
    1
  • Subscribers subscriber
    1
  • Views views
    524
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

MigrationDeletedUser

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.)

Labels:

Orbix
  • 0
    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.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.