Troubleshooting
Problem
Cannot log into Datastage Designer client due to the following error: Error message: Failed to authenticate the current user against the selected Services Tier Exception type: Exception message: Exception stack trace
Symptom
This is usually seen on non-english client machines. To debug the problem, use the command
set USE_RMI=TRUE
to set the USE_RMI environment variable in a command window on the client machine and use
C:\IBM\InformationServer\Clients\Classic\DSDesign.exe
to start the DataStage Designer Client from the same command window. This allows the user to successfully login to Designer client.
Note: Setting USE_RMI to TRUE is not a work around for this problem. This environment variable should not be set except for debugging purposes or when instructed by IBM support to assist in problem determination.
Cause
Starting from Information Server 9.1, only the Designer client uses the new REST API to access the services tier. The REST API does not support HTTP proxy authentication.
Setting USE_RMI=TRUE, reverts to the older access methods which are still used by the other clients. However, as mentioned above USE_RMI=TRUE should not be used as a work around for this problem.
Diagnosing The Problem
Turn on spy trace by doing the following:
++++++++++++++++++++++++++++++++++++
On the client machine - create the following file
C:\IBM\InformationServer\ASBNode\conf\NewRepos.debug.properties and add the following lines:
NewRepos.spy.trace=true
log4j.logger.com.ibm.datastage=DEBUG
log4j.logger.com.ascential.dstage=DEBUG
After setting spy trace, start Designer Client in the usual way by double clicking the Designer Client icon on the desktop.
Now reproduce the problem by connecting to the server which is having problems.
++++++++++++++++++++++++++++++++++++
Finally, collect the following :
-> Collect all the output in ds_logs - this will include the dstage_wrapper_trace & spy_trace files. They are located here:
C:\Users\<USER ID>\ds_logs
-> Collect the following logs from the services tier /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1
SystemOut.log
SystemErr.log
In the dstage_wrapper_trace_<XX>.log, you would find entries like this:
2014-03-06 10:50:01,724 DEBUG com.ascential.dstage.proxies.NewRepos.log(NewRepos.java:5717) - (External) CRestRepository:UTF8ThenURLEncode - Original string: TESTSRVR:abc
...
2014-03-06 10:50:01,739 DEBUG com.ascential.dstage.proxies.NewRepos.log(NewRepos.java:5717) - (External) CRESTRepository.Login - Begin
2014-03-06 10:50:05,290 ERROR com.ascential.dstage.proxies.NewRepos.log(NewRepos.java:5717) - (External) CRestRepository:SendRequest - Error: Proxy server is not supported.
2014-03-06 10:50:05,290 DEBUG com.ascential.dstage.proxies.NewRepos.log(NewRepos.java:5717) - (External) CRESTRepository.HTTPPost. - No JSESSIONID cookie found: HTTP/1.0 407 Proxy authorization required
Proxy-agent: Netscape-Proxy/3.52
Date: Thu, 18 Mar 2014 02:49:46 GMT
Proxy-authenticate: basic realm="unspecified"
Content-type: text/html
Content-length: 271
WAS Systemout.log shows the following message:
[3/4/14 11:56:12:523 GMT+08:00] 0002b9f3 rest2 E <Null Message>
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.is.binding.rest2.Servlet.callOperation(Servlet.java:447)
at com.ibm.is.binding.rest2.Servlet.processRequest(Servlet.java:370)
at com.ibm.is.binding.rest2.Servlet.doRequest(Servlet.java:275)
at com.ibm.is.binding.rest2.Servlet.doGet(Servlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1219)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1027)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3703)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:962)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:522)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:311)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:87)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1783)
Caused by: com.ibm.datastage.repository.exception.DSObjectNotFoundException: The object does not exist.
at com.ibm.istools.rest.server.impl.ISToolsRESTServiceBean.getObjectRID(ISToolsRESTServiceBean.java:3740)
at com.ibm.istools.rest.server.impl.ISToolsRESTServiceBean.queryEObjectCR(ISToolsRESTServiceBean.java:402)
at com.ibm.istools.rest.server.impl.ISToolsRESTServiceBean.getEObjectCRJSON(ISToolsRESTServiceBean.java:3680)
at com.ibm.istools.rest.server.EJSRemoteStatelessISToolsRESTService2_a41bae5b.getEObjectCRJSON(Unknown Source)
at com.ibm.istools.rest.server._ISToolsRESTServiceRemote_Stub.getEObjectCRJSON(_ISToolsRESTServiceRemote_Stub.java:386)
... 31 more
Resolving The Problem
The REST API used by the DataStage Designer client has not since Information Server 9.1 supported HTTP Proxy Authentication. To solve the problem, login to the client machine and either remove any proxy settings that may exist in Contol Panel->Internet options or add an exception for the machine that hosts the Services and Engine tiers of Information Server by doing the following:
-> Go to Control Panel->Internet Options->Connections->LAN Settings.
-> Verify if 'Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections.)' under 'Proxy Server' section is checked.
-> If yes, check the option 'Bypass proxy server for local addresses'
-> Also, add the server address in 'Do not use proxy server for addresses beginning with:' text box.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21668528