DataStage server connection
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 3
- Joined: Wed Jul 28, 2004 5:33 am
DataStage server connection
Hi,
We are unable to login on Designer/Manager/Administrator/Director
It gives the error as
Failed to connect to host: <host ip>, project: <Project name>
(Internal Error (80012))
We have checked the dsrpc demon is running on unix box. We have re started the datastage server 2-3 times and checked that dsrpc is up and running.
Please advise.
We are unable to login on Designer/Manager/Administrator/Director
It gives the error as
Failed to connect to host: <host ip>, project: <Project name>
(Internal Error (80012))
We have checked the dsrpc demon is running on unix box. We have re started the datastage server 2-3 times and checked that dsrpc is up and running.
Please advise.
Re: DataStage server connection
From your local system trying pinging the datastage server, or login via telnet to it.
This is probably something small which is wrong.
Ogmios
This is probably something small which is wrong.
Ogmios
-
- Participant
- Posts: 3
- Joined: Wed Jul 28, 2004 5:33 am
Re: DataStage server connection
Local server is running and we checked that via telnet.
ogmios wrote:From your local system trying pinging the datastage server, or login via telnet to it.
This is probably something small which is wrong.
Ogmios
Re: DataStage server connection
If you can login to the UNIX machine with the userid/password you use for the manager/director, my next hunch would be the access rights to the project directories are wrong.
Did this installation ever worked before, or this is the first time you're running DataStage on the UNXI server.
Ogmios
Did this installation ever worked before, or this is the first time you're running DataStage on the UNXI server.
Ogmios
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Error code 80012 decodes (from SYS.MESSAGE) to "unable to set remote uid or gid".
Check, therefore, that your user ID and password are correct.
If they are, check that that user is in a group that is allocated to an appropriate DataStage role.
Code: Select all
SELECT * FROM SYS.MESSAGE WHERE @ID = 080012 ;
If they are, check that that user is in a group that is allocated to an appropriate DataStage role.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Re: DataStage server connection
Check if the password is not more than 8 characters long.
goodluck
s
goodluck
s
we have this same error aftre a restart of the server. so user should be ok(connection was fine before restart).
I however think that the restart was done incorrect, mix up between root-user and datastage-admin-user stopping and starting the processes.
Could this cause this problem, and if so, how can we solve it? I suppose root has now created some files that can not be accessed by the dts-admin and that this is causing the problem.
I however think that the restart was done incorrect, mix up between root-user and datastage-admin-user stopping and starting the processes.
Could this cause this problem, and if so, how can we solve it? I suppose root has now created some files that can not be accessed by the dts-admin and that this is causing the problem.
We experienced a similar problem yesterday following a restart of the server. Stopped the engine again (as root) and started as dsadm. Same problem. One odd thing we observed was that, when starting as dsadm, we were getting prompted for logon credentials.jasper wrote:we have this same error aftre a restart of the server. so user should be ok(connection was fine before restart).
I however think that the restart was done incorrect, mix up between root-user and datastage-admin-user stopping and starting the processes.
Could this cause this problem, and if so, how can we solve it? I suppose root has now created some files that can not be accessed by the dts-admin and that this is causing the problem.
The solution was that $dshome/bin/uv is "owned by root" (which is correct). However, for some reason the sticky bit on the owner permissions had been removed. Once it was restored, the engine started by dsadm (without being prompted for credentials) and all was fine.
Rick H
Senior Consultant
Senior Consultant
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: