Sponsored Content
Top Forums UNIX for Advanced & Expert Users The DT messaging system could not be started Post 302269111 by fpmurphy on Tuesday 16th of December 2008 11:44:35 PM
Old 12-17-2008
This message is to do with CDE and it's underlying messaging system i.e ToolTalk. If you are unfamilar with ToolTalk, conceptually it is similar to DBUS on Fedora/Redhat/CentOS. It was developed by Sun.

Generally caused by CDE not being able to write files in a user's home directory. Often caused when a user's directory is NFS mounted. Lots of information and good advise available if you search the Web.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

The Desktop Messaging System Could Not Be Started HP-UX

Hi People! I've just got a HP-UX system dumped on me. I've started it, followed all the install/setup questions, and everything was going ok, right upto when going into the desktop enviroment I got the message "The Desktop Messaging System Could Not Be Started". Now I've checked the... (8 Replies)
Discussion started by: cpiuk
8 Replies

2. HP-UX

HP VUE Messaginbg system could not be started

hi guys..its been a while since my last post... a friend of mine has a problem with their HP Openview and has the following error: The HP VUE messaging system could not be started. To correct the problem: 1. Choose to return to the login-screen. 2. Select failsafe session.... ... ... (2 Replies)
Discussion started by: inquirer
2 Replies

3. IP Networking

DT messaging could not be started

this id the message i get with a suggestions to check those files: /etc/src.sh /etc/hosts /usr/adm/inetd.sec i have little knowledge of hoe to edit those files/ i went to the etc library and didn't found src.sh file. what should i do? also didn't find the inetd.sec file In the host... (3 Replies)
Discussion started by: amirp
3 Replies

4. Solaris

Solaris 10 CDE problem - The DT messaging system could not be started

A Google search with: +Solaris +"The DT messaging system could not be started" returns 138 hits. All of the relevant possible solutions are in this document. My apologies for such a long document but I thought I would try to minimize the resolution attempts that I've already tried. System... (1 Reply)
Discussion started by: rpollard001
1 Replies

5. Solaris

Solaris 8, you boot the system but does not have anything on the screen (not started)

Greetings to all. I have two computers, Sun Blade 150. the first, had the Solaris 8 system, and that system needed to clone the "second" to start it with the same settings. Use a program to clone the drive, and then have cloned, had the error: Can't read disk label. Can't open disk... (4 Replies)
Discussion started by: feliz-58
4 Replies

6. HP-UX

Help needed HP UX 11.11i new install on C8000 Desktop messaging system error CAN'T FIX

Hi, I have a HP UX C8000 box , have installed 11.11i from 4 x cds numerous times to try to get a functioning Network or to try and get rid of this error on start up, after new install and 1st startup I get an error "The desktop messaging system could not be started" and then advice about... (12 Replies)
Discussion started by: C8000
12 Replies

7. Shell Programming and Scripting

The DT messaging system could not be started.

Good Morning, Users can no longer log into SunBlade 2500 Solaris 9 system (though root still can). Here's what I'm getting and what I've done. I'm most suspicious of the full drive since that pops up twice and I did see one looks full. What's a good way to reduce what's on it?- or.. what else... (2 Replies)
Discussion started by: Stellaman1977
2 Replies
tt_spec_file(library call)												tt_spec_file(library call)

NAME
tt_spec_file -- retrieve the name of the file that contains the object described by the spec SYNOPSIS
#include <Tt/tt_c.h> char *tt_spec_file( const char *objid); DESCRIPTION
The tt_spec_file function retrieves the name of the file that contains the object described by the spec. The objid argument is the identifier of the object involved in this operation. RETURN VALUE
Upon successful completion, the tt_spec_file function returns the absolute pathname of the file. The application can use tt_ptr_error(3) to extract one of the following Tt_status values from the returned pointer: TT_OK The operation completed successfully. TT_ERR_DBAVAIL The ToolTalk service could not access the ToolTalk database needed for this operation. TT_ERR_DBEXIST The ToolTalk service could not access the specified ToolTalk database in the expected place. TT_ERR_NOMP The ttsession(1) process is not running and the ToolTalk service cannot restart it. TT_ERR_OBJID The objid passed to the ToolTalk service does not reference an existing object spec. APPLICATION USAGE
The application should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. SEE ALSO
Tt/tt_c.h - Tttt_c(5), tt_ptr_error(3), tt_free(3). tt_spec_file(library call)
All times are GMT -4. The time now is 12:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy