| INMUCE0001 | Error while creating Axis2 SOAP Service Stub for UDDI Security API |
| Explanation |
This error may happen if the host or port specified in RegistryConfiguration is not valid or if there is an incorrect version of Axis jars in the classpath. |
| Action |
Please make sure the host and port of the registry provided in RegistryConfiguration are valid. And also make sure that the classpath has the correct version of Axis2 jars. |
| INMUCE0002 | Error while creating Axis2 SOAP Service Stub for UDDI Inquiry API |
| Explanation |
This error may happen if the host or port specified in RegistryConfiguration is not valid or if there is an incorrect version of Axis jars in the classpath. |
| Action |
Please make sure the host and port of the registry provided in RegistryConfiguration are valid. And also make sure the classpath has the correct version of Axis2 jars. |
| INMUCE0003 | Error while creating Axis2 SOAP Service Stub for UDDI Publish API |
| Explanation |
This error may happen if the host or port specified in RegistryConfiguration is not valid or if there is an incorrect version of Axis jars in the classpath. |
| Action |
Please make sure the host and port of the registry provided in RegistryConfiguration are valid. And also make sure the classpath has the correct version of Axis2 jars. |
| INMUCE0004 | Error while creating Axis2 SOAP Service Stub for UDDI Subscription API |
| Explanation |
This error may happen if the host or port specified in RegistryConfiguration is not valid or if there is an incorrect version of Axis jars in the classpath. |
| Action |
Please make sure the host and port of the registry provided in RegistryConfiguration are valid. And also make sure the classpath has the correct version of Axis2 jars. |
| INMUCE0005 | Error while creating Axis2 SOAP Service Stub for Taxonomy API |
| Explanation |
This error may happen if the host or port specified in RegistryConfiguration is not valid or if there is an incorrect version of Axis jars in the classpath. |
| Action |
Please make sure the host and port of the registry provided in RegistryConfiguration are valid. And also make sure the classpath has the correct version of Axis2 jars. |
| INMUCE0006 | Not able to connect to the UDDI Registry. get_authToken call failed. |
| Explanation |
Remote exception thrown while connecting to UDDI registry. |
| Action |
Please make sure the host and port provided in RegistryConfiguration are valid. |
| INMUCE0007 | Not able to connect to the UDDI Registry. discard_authToken call failed. |
| Explanation |
Remote exception thrown while connecting to UDDI registry. |
| Action |
Please make sure the host and port provided in RegistryConfiguration are valid. |
| INMUCE0008 | Not able to fetch the modified date of service with key {0}. get_operationalInfo call failed due to RemoteException. |
| Explanation |
Remote exception was thrown while getting operational info for the given service. |
| Action |
Please make sure the registry is running the host and port provided in RegistryConfiguration. |
| INMUCE0009 | Not to able to fetch the virtual services for the specified target {0} |
| Explanation |
Not to able to fetch the virtual services for the specified target {0}, as remote exception was caught in find_service call. |
| Action |
Please make sure the registry is running the host and port provided in RegistryConfiguration. |
| INMUCE0011 | Not able to fetch the service with name {0}. find_service call failed due to RemoteException. |
| Explanation |
Remote exception was thrown while inquiring the registry for services. |
| Action |
Please make sure the registry is running the host and port provided in RegistryConfiguration. |
| INMUCE0012 | Not able to fetch the details of the service {0}. get_serviceDetail call failed due to RemoteException. |
| Explanation |
Remote exception was thrown while inquiring the registry for service details. |
| Action |
Please make sure the registry is running the host and port provided in RegistryConfiguration. |
| INMUCE0013 | Not able to fetch the details of the tModel {0}. get_tModelDetail call failed due to RemoteException. |
| Explanation |
Remote exception was thrown while inquiring the registry for tModel details. |
| Action |
Please make sure the registry is running the host and port provided in RegistryConfiguration. |
| INMUCW0010 | Unable to find the virtual service with specified name {0} |
| Explanation |
There is not virtual service with the specified name in the UDDI registry. |
| Action |
Please make sure the UDDI registry has a virtual service with the specified name. If it exists please make sure the user provided in RegistryConfiguration has the privilege to view the virtual service. |
