Siebel IP2017: Connection To Target Fails Through REST API With Different Username/pwd

(Doc ID 2318183.1)

Last updated on OCTOBER 16, 2017

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.

Symptoms

Siebel IP2017: Connection to Target fails through REST API with different username/pwd


Created migration application to perform repo migration etc...as per migration application setup steps. Able to access migration application and create source connection without any issues, but while creating target connection, it is failing with "500 Internal error"


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create migration application
2. Create source connection
3. Target connection is failing with error

Error in migration.log

=============

2017-09-08 15:56:31,266 [TRACE] - com.siebel.migration.server.MigrationLogger:logTrace DB Utill Url : https://qde2le.de.t-internal.com:9001/siebel/v1.0/service/describe?searchspec=%5BName%5D%20LIKE%20%27Migration*%27
2017-09-08 15:56:31,332 [TRACE] - com.siebel.migration.server.MigrationLogger:logTrace Response Code : 200
2017-09-08 15:56:31,332 [DEBUG] - com.siebel.migration.server.MigrationLogger:logDebug Connected to Server : https://qde2le.de.t-internal.com:9001/siebel/v1.0/service/describe?searchspec=%5BName%5D%20LIKE%20%27Migration*%27
2017-09-08 15:56:31,332 [DEBUG] - com.siebel.migration.server.MigrationLogger:logDebug Output Response Message : {"status":"success","msg":""}
2017-09-08 15:56:31,333 [DEBUG] - com.siebel.migration.server.MigrationLogger:logDebug Output Response org.apache.catalina.connector.ResponseFacade@494819ac
2017-09-08 15:56:57,421 [TRACE] - com.siebel.migration.server.MigrationLogger:logTrace Entering in Post Method
2017-09-08 15:56:57,421 [DEBUG] - com.siebel.migration.server.MigrationLogger:logDebug Input Request org.apache.catalina.connector.RequestFacade@525b592f
2017-09-08 15:56:57,421 [TRACE] - com.siebel.migration.server.MigrationLogger:logTrace Entering in Method to Save Connection
2017-09-08 15:56:57,422 [DEBUG] - com.siebel.migration.server.MigrationLogger:logDebug Input Request : {"connectionid":"","name":"Target","url":"https:\/\/qde2ne.de.t-internal.com:9001\/siebel\/v1.0","isFav":false,"SRN":"5407"}
2017-09-08 15:56:57,422 [TRACE] - com.siebel.migration.server.MigrationLogger:logTrace Entering in initConnection Function
2017-09-08 15:56:57,423 [TRACE] - com.siebel.migration.server.MigrationLogger:logTrace Entering in Method to Invoke Rest Call with URL : https://qde2ne.de.t-internal.com:9001/siebel/v1.0
2017-09-08 15:56:57,423 [TRACE] - com.siebel.migration.server.MigrationLogger:logTrace DB Utill Url : https://qde2ne.de.t-internal.com:9001/siebel/v1.0/service/describe?searchspec=%5BName%5D%20LIKE%20%27Migration*%27
2017-09-08 15:56:57,424 [DEBUG] - com.siebel.migration.server.MigrationLogger:logDebug DB Utils Describe Request URL: https://qde2ne.de.t-internal.com:9001/siebel/v1.0/service/describe?searchspec=%5BName%5D%20LIKE%20%27Migration*%27
2017-09-08 15:56:58,953 [TRACE] - com.siebel.migration.server.MigrationLogger:logTrace HTTP Response Code: 500
2017-09-08 15:56:58,953 [ERROR] - com.siebel.migration.server.MigrationLogger:logError Could not connect to the server : https://qde2ne.de.t-internal.com:9001/siebel/v1.0/service/describe?searchspec=%5BName%5D%20LIKE%20%27Migration*%27 :{"status":"error","msg":"INTL_SRVR_500","data":""}
2017-09-08 15:56:58,953 [ERROR] - com.siebel.migration.server.MigrationLogger:logError

EAI*log in target environment contains messages as : Invalid Userid/password .

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms