Corba development summary (6)---solutions to common problems

    Due to the company's new project requirements, I have been developing CORBA interfaces (ZTE+Huawei) for a period of time. I have stepped on various pits, and I have accumulated some experience. I am sharing this point. It is inevitable that there will be omissions due to the limitation of experience. Welcome Perfect discussion.

1. The initialization manager reports an exception org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No

     There are two possible reasons for this exception: (1) the account authority used is insufficient, and a higher authority can be granted through the network management platform; (2) the problem cannot be solved even when the account authority is set to the highest authority, that is, the administrator authority. Then the problem may be that the Huawei lisence has expired, and you need to contact Huawei to purchase the license.

Second, get the EmsSession reference object, exception! ---ProcessingFailureException---

     The reason for this exception is generally that the user name and password of the currently used login user are incorrect, or the permissions are insufficient, or the logged-in user has not yet logged out, or the user name is still logged in because the connection is not closed after the corba service was called before.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325036432&siteId=291194637