General
cancel
Showing results for 
Search instead for 
Did you mean: 

The desktop messaging system could not be started

 
SOLVED
Go to solution
Highlighted
Occasional Advisor

The desktop messaging system could not be started

Dear forum

After fresh installation of HP UX 11 on a HP9000 server I'm getting "The desktop messaging system could not be started ..." error message when trying to connect to the CDE via Xmanager from my Win2k desktop.

Running the nslookup with both hostname and IP address of my Win2k desktop returns the same (successful) result.

The length of the hostname is less then 8 character.

Please advice,
Regards,
Ran.
14 REPLIES 14
Highlighted
Honored Contributor
Solution

Re: The desktop messaging system could not be started

Hi,

What errors are you getting if you run the command /usr/contrib/bin/X11/dr_dt?

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Highlighted
Occasional Advisor

Re: The desktop messaging system could not be started

Dear Sri,

Attached you can find the output of the dr_dt command.

Ran.
Highlighted
Honored Contributor

Re: The desktop messaging system could not be started

Since this is a new installation I wonder if the HPUX box knows it's own name and address. Not having the name and address configured properly will give the same error. Make sure that /etc/rc.config.d/netconf has the correct name and address. Also make sure the the first entries in /etc/hosts is:

127.0.0.1 localhost loopback
123.123.123.23 your_server.FQDN.com your_server

Where your_server is of course your HPUX box Fully Qualified Domain name and then short name.

If the host name and/or address is not correct in both files the CDE will not start up.

Also if you just want to start over you can, as root, just run:

set_parms initial

which will have you configure the entire system again. Not a big deal and you can see how it is set now. Also do a man 1M set_parms to see the other options like "address" "hostname" etc. It is a very handy tool.

If it has wheels or a skirt, you can't afford it.
Highlighted
Occasional Advisor

Re: The desktop messaging system could not be started

Thanks John,

Iâ ve double-checked all my network configuration files â all looks OK.

Any more advice?

Regards,
Highlighted
Honored Contributor

Re: The desktop messaging system could not be started

I replied the first time before you attached the ouput file. The first big problem I see is just as I suppected, it doesn't know it's own name and your env $DISPLAY is set to null "". Please follow my previous instructions with set_parms initial to get it all straight.
If it has wheels or a skirt, you can't afford it.
Highlighted
Honored Contributor

Re: The desktop messaging system could not be started

Ok if that is all fine then do this:

Telnet to your HPUX box from the Window box.
do a who -mT to get what the HPUX box thinks your Windows box really is.

Then do a export of the display:

export DISPLAY=your.windows.box:0

If you have the Windows Xmanager setup for full screen (some call it "single window") it should work.

If it has wheels or a skirt, you can't afford it.
Highlighted
Occasional Advisor

Re: The desktop messaging system could not be started

Dear John,

Tried all your advices but no luck, any idea?

Regards,
Ran.

Highlighted
Honored Contributor

Re: The desktop messaging system could not be started

Hi,

Sorry for the delay. Stuck up with some deadlines here.

Check your /var/dt/Xerrors and see if there are any messages printed.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Highlighted
Honored Contributor

Re: The desktop messaging system could not be started

Ok sorry, I got busy also. Let's see if dtlogin is running on the HPUX box:

ps -ef|grep dtlogin

Hopefully you will get something.

Check /etc/rc.config.d/desktop and make sure it says CDE:

root> cat desktop
# CDE Desktop enabled Mon Apr 22 14:25:39 EDT 2002
DESKTOP=CDE



If it has wheels or a skirt, you can't afford it.