GMU Error 500. Detail: naming exception

[Gustavo Gama da Silva Figueiredo]

Using GMU for the first time and I'm stuck still trying to export the services from source gateway. Details are shown below, and images and some infos were partially covered for security reasons (you never know...):

 

source.args
host=gateway.ca.local username=admin password=<admin password> port=9443 results=results.xml encryptionPassphrase=<passphrase> trustHostname trustCertificate

 

[Zhijun He]

Does the policy you were trying to migrateOut refer to LDAP user/group?

 

If yes, when migrateOut, GMU will find all the dependencies, since the policy depends on LDAP user/group, GMU queries the LDAP server, if LDAP server fails to respond, we get the "naming exception” error.

 

If the LDAP server is slow to respond, try increasing the timeout limit,

ldap.connection.timeout
ldap.read.timeout

 

https://docops.ca.com/ca-api-gateway/9-3/en/reference/gateway-cluster-properties/ldap-cluster-properties

 

Regards,

Mark

[Gustavo Gama da Silva Figueiredo]

Thank you! I do have a local LDAP server in the Gateway. I just had to start it and everything worked out.

[Arun AK]

we had similar issue, service migrated without dependencies like EA and JDBC connection. Fix was installed EA and JDBC....then migrated service...it worked.