GMU migrateOut Execution failed. Reason: Internal Server Error. Detail: Service Not Found.
search cancel

GMU migrateOut Execution failed. Reason: Internal Server Error. Detail: Service Not Found.

book

Article ID: 250406

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

Environment:  Gateway 10.0 CR2 and GMU 1.5 in our environment. 

We are seeing an issue while exporting the policies from one of our gateway node.

Please find below details.

Migration Error: 

------------------

C:\GatewayMigrationUtility-1.5.00-479>gmu migrateOut -z config/<gatewayHostname>.properties --serviceName "DMZ/Client Bundle R1/Services/POC/Login V5 POC1" -d destination/aws/c2/ivr1 -f directory
Warning: TLS hostname verification has been disabled
Warning: TLS server certificate check has been disabled
Running....
Execution failed. Reason: Internal Server Error. Detail: Service Not Found.  The request may have been sent to an invalid URL, or intended for an unsupported operation.

Gateway Audit Logs:

-------------------------

INFO  Message was not processed: Service Not Found.  The request may have been sent to an invalid URL, or intended for an unsupported operation. (404)

3017 Policy evaluation for service  resulted in status 404 (Service Not Found.  The request may have been sent to an invalid URL, or intended for an unsupported operation.)

3208 Resolution failed; multiple services match the current request

3005 Service not found

The Rest man query also having issue and with below errors:

----------------------------------------------------------------------

https://<gatewayHostname>:8443/restman/1.0/doc/restDoc.html

<l7:policyResult xmlns:l7="http://www.layer7tech.com/ws/policy/fault" status="Service Not Found. The request may have been sent to an invalid URL, or intended for an unsupported operation."/>

 

Or in gateway 11 return the flowwing message:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>Policy Falsified</faultstring>
<faultactor>https://{Server}:8443/restman/1.0</faultactor>
<detail>
<l7:policyResult xmlns:l7="http://www.layer7tech.com/ws/policy/fault" status="Service Not Found. The request may have been sent to an invalid URL, or intended for an unsupported operation."/>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

Environment

Gateway 9.x, 10.x, 11,  GMU 1.5

Cause

There was duplicated restman (old version) installed.   The issue could happen if there is duplicated policy active. 

Resolution

One of the services from the source Gateway has a conflicting URI.  Go to service properties, click "check resolution conflict" .  If it is not successful, then resolve the conflict: 

1) If it is the service, change the resolution name to be unique before migration:

- Find the service that is failing.

- Right-click and select Service Properties.

         - Select the HTTP/FTP tab In the field, Custom Resolution Path change the service path.

2) If it is restman, find other copy of restman and disable or remove it. 

Additional Information

-