Page 1 of 1

Can't Login to Datastage not as administrator(error 39202)

Posted: Thu Dec 18, 2008 8:49 am
by andy心&#262
I intalled ds7.5 on win2003se
When I remote connect to the win2003 server, I can login the ds project as administrator,but not testuser.
Failed to connect to host: localhost, project: UV
(Internal Error (39202)).

I have two user: administrator(administrators group) and testuser(dsadm group).
I granted dsadm group "DataStage Production Manager" role via ds administrator client as administrator user.

I have granted all right to dsadm group on "X:\Ascential\Datastage\" folder.

I am sure:
1. the license is valid.
2. the ds service is available.
3. I can log in as administrator, or a member of administrators group.
4.testuser can open "X:\Ascential\DataStage\Engine\bin\uv.exe"

I don't know which privilege should grant to testuser? When I add testuser to administrator group, testuser can log in ds project as well.

It is sth. about access control. I searched the forum and web, somebody have a same issue as me, but I didn't find the solution.
http://www.ibm.com/developerworks/forum ... &#13905017

Many Thanks!

andy

Posted: Thu Dec 18, 2008 3:25 pm
by ray.wurlod
What operating system group is associated with the DataStage Engine folder (a sub-folder within X:\Ascential\DataStage), and to which group(s) does testuser belong?

Posted: Thu Dec 18, 2008 8:13 pm
by andy心&#262
ray.wurlod wrote:What operating system group is associated with the DataStage Engine folder (a sub-folder within X:\Ascential\DataStage), and to which group(s) does testuser belong? ...
testuser belongs to dsadm group
and I assign full privilege for dsadm group to control "X:\Ascential\DataStage" folder.

Posted: Sat Dec 20, 2008 8:58 am
by andy心&#262
today, I installed win2003 x86 sp2 and ds7.5X2, and I set the access control successfully.

last time, I can't set right control on ds7.5, win2003 x64 sp2

I think it might sthing wriong between ds7.5 and win2003x64


thanks

Posted: Sat Dec 20, 2008 9:12 am
by chulett
Probably not so much a permissions problem as a 32bit v. 64bit issue, as the latter is not supported AFAIK.