DS Repository Interface Error-Connection has timed out(81015

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
satish_valavala
Participant
Posts: 123
Joined: Wed May 18, 2005 7:41 am
Location: USA

DS Repository Interface Error-Connection has timed out(81015

Post by satish_valavala »

we are having a repeated problem:
Some users(and admin) are not able to login to DataStage 8.0, but existing/established users/connections are working fine.
If anybody tried to login to DS8.0, its throwing following error,

DataStage Repository Interface
Failed to connect to DataStage Server: <servername>:<port num>, project: Sample123
(The connection has timed out (81015))

We are doing re-start as a temporary fix.

Does anyone has any idea on it. What could be the root cause for this problem.

Thanks
VS
Regards
VS
satish_valavala
Participant
Posts: 123
Joined: Wed May 18, 2005 7:41 am
Location: USA

Post by satish_valavala »

DSEngine, Node Agent and Websphere server processes are running and have enough DS user licences. We are not getting any trace on it.
Regards
VS
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Check also that your servers are accessible (names can be resolved) and that your DHCP lease on the client has not expired.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
synsog
Premium Member
Premium Member
Posts: 232
Joined: Sun Aug 01, 2010 11:01 pm
Location: Pune

Post by synsog »

Greetings DS Doctors,
We are also facing similar time out issue. DS Engine/WAS/X-META db ever ty looks normal. Not sure why i am still getting this issue.

Issue persists, when logging from client tools on my local machine and Citrix server as well.

Am i missing to check something..?

Thanks your help and support in advance.
satish_valavala
Participant
Posts: 123
Joined: Wed May 18, 2005 7:41 am
Location: USA

Post by satish_valavala »

This issue is resolved for us during 2008, after IBM Support involved and moved the XMeta DB to another server. For this kind of issues, better contact Product support vendor (in our case IBM).
Regards
VS
Post Reply