webMethods Integration Server - An error occurred while loading information from the webMethods Cloud environment

What product/components do you use and which version/fix level are you on?

10.5.0.0

IS_10.5_SPM_Fix9
Trading Networks Server 10.5 Fix 10
Trading Networks Server 10.5 Fix 3
Trading Networks Server 10.5 Fix 5
Trading Networks Server 10.5 Fix 11
IS_10.5_Core_TestPatch_PIE-74269_v3
Trading Networks Server 10.5 Fix 13
IS_10.5_Core_Fix20

Is your question related to the free trial, or to a production (customer) instance?

Prod

What are you trying to achieve? Please describe it in detail.

Get rid of error we are getting during each integration server restart

Do you get any error messages? Please provide a full error message screenshot and log file.

2023-03-08 09:03:29 CET [ISS.0028.0012I] (tid=72) WmCloud: Startup service (wm.client.integrationlive.admin:loadTenantAccountInfo)

2023-03-08 09:03:29 CET [ISS.0021.6004E] (tid=760) An error occurred while loading information from the webMethods Cloud environment.

Have you installed all the latest fixes for the products and systems you are using?

Yes

@martin.hajducik , is there any additional Errors reported in Error logs? Also, are you using Hybrid Connectivity for your envs? If you are not using Hybrid Connectivity, you can disable WmCloud package.

Regards,
Kalpesh

Hi Kalpesh, thanks for the answer. No we are not using Hybrid connectivity. Would you also know what that error code means exactly ? ISS.0021.6004E

I w did also check and we do have also IS_10.5_WmCloud_Fix5 installed. As I was cehcking there is also IS_10.5_WmCloud_Fix6 released. But we do not think that might help us because on some server we do experiencing this issue "ISS.0021.6004E " but on some nodes we do not.

It is always when we restart integration server appplication.

Thanks for your reponse

How about just disabling the WmCloud package for now since you are not using hybrid integration. Just a thought.
Obviously if you need to use hybrid integration with wM.io Integration then this needs to be resolved.

package is disabled now and error message is no longer in the server.log. Thank you both for help !

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.