|
Administrator
|
is the bottom of the error stack is REP-30000 or REP-300 ?
REP-3000: Internal error
so I guess you sent a wrong information here.
If so , I will tell you a story of mine;
One customer was encountering Rep-3000 errors, in some E-Business Suite concurrent programs --Oracle Reports..
Rep-3000 error was a common error for EBS systems in Linux/Unix, and the solution was disabling the access control for X sessions using xhost + command.. The command should be run from the Server itself, from a local connection.. But before running the xhost + command, DISPLAY environment variable should be set to the DISPLAY used in EBS concurrent managers..
So the display used in EBS concurrent managers of the customer's EBS system was hostname:0.0..
The problem was, after setting display variable to hostname:0.0 , xhost + command encountered errors.
The comand was;
export DISPLAY=exatest:0.0
xhost +
The error was;
xhost: unable to open display "exatest:0.0"
So, after some analysis, I found that a X server was actually listening on port :0, but its authorization was be sourced before the xhost + command .
I found the authorization of the relevant X server process, using proc filesystem.. and sourced it before running the xhost + command.. And the issue is fixed..
The solution was;
root@exatest ~]# export XAUTHORITY=/var/gdm/:0.Xauth
[root@exatest ~]# export DISPLAY=exatest:0.0
[root@exatest ~]# xhost +
access control disabled, clients can connect from any host
|