T.R | Title | User | Personal Name | Date | Lines |
---|
23.1 | Try clock or something
| DECWIN::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Thu Jan 26 1989 15:12 | 5 |
| Please try starting something "simple" like clock and see what happens.
That might remove some of the variables.
Burns
|
23.2 | Clock does the same thing | HORSEY::GENTILE | | Thu Jan 26 1989 16:17 | 9 |
| Clock does exactly the same thing.
XIO: non-translatable vms error code: 0x2DBA002, vms message:
%decw-e-cnxabort, connection aborted
%XLIB-F-IOERROR, xlib io error
I seem to get this for anything I start up.
|
23.3 | Another way of getting the message | WINERY::ROSE | | Thu Jan 26 1989 22:18 | 24 |
| Re .0: I get a very similar error message when I try to run a VMS
client using my Ultrix machine as a server. Both are on SDC DECwindows.
XIO: non-translatable vms error code: 0x2DBA002, vms message:
%decw-e-cnxabort, connection aborted
%XLIB-F-IOERROR, xlib io error
Also, the Ultrix server freezes for a few seconds.
Maybe the server is rejecting the connect for security reasons? I've
tried various syntaxes for specifying the VMS node in Customize
Security... The syntax host:: works fine if the other machine is
running Ultrix.
The application, by the way, is tiny, freshly compiled and linked, and
dies on the XOpenDisplay. If output is directed to a VMS server
which I'm authorized to access, it works fine. If output is directed
to a VMS server which I'm not authorized to access, I get a nice
message
Client is not authorized to access server
Any suggestions would be VERY much appreciated.
|
23.4 | Get an Xliddy trace | STAR::BRANDENBERG | Intelligence - just a good party trick? | Fri Jan 27 1989 09:36 | 2 |
|
|
23.5 | Let's find out what transport | DECWIN::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Fri Jan 27 1989 15:26 | 14 |
| re .0 et al: Can you run applications from a terminal emulator window? If
not, type $SHOW DISPLAY. Then try the following:
$DEFINE DECW$DISPLAY node::0
and run it again.
BTW, the security syntax for VMS-VMS is nodename::username. From Ultrix to
VMS, you need to specify the Ultrix UIC on the VMS server in place of the
username. Or you can use *, although this is obviously less secure.
Burns
|
23.6 | Rebooting cures problem | HORSEY::GENTILE | | Mon Jan 30 1989 10:19 | 4 |
| I ended up rebooting my vaxstation and that cured the problem. Any
ideas on what happened?
|