Home > Dt Messaging > Dt Messaging Could Not Started

Dt Messaging Could Not Started

Close Box Join Tek-Tips Today! Select FailSafe Session from the login screen's option menu and *>* log in *>* 3. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by HomeForumsMIS/ITOperating Systems - UNIX basedSun: Solaris Forum DT messaging System Most of the replies said that CDE (Common Desktop Environment) issued are caused by network configuration. http://strobelfilms.com/dt-messaging/dt-messaging-could-not-be-started.html

Select Failsafe session from the login screen's option menu and log in. 3. Start a new thread here 3691088 Related Discussions nis client problem DT Messaging Problem Problem with Ping CDE error DT Messaging System Could not be Started waiting timeout for nis come Check that the first name after the IP address for the machine is the same as defined in /etc/hostname.* where * is the The problem is the output of two commands gave me a different result. https://www.ibm.com/developerworks/community/forums/message.jspa?messageID=14960889

When I attempted to log into the user's CDE, it gave me > a DT messaging system error: > > The DT messaging system could not be started. > > To I am hoping that once I get the networking services configured correctly on this machine that the “The DT messaging system could not be started..." error message will stop appearing when More...

Check for consistency and correctness of hostname and IP address throughout system files. Thanks. All Rights Reserved. Another suggestion was 1.

Hi All, I was able to resolve this issue by commenting out the line on dhcpcd in /etc/rc.tcpip. In this video, we show how to load the export from S3 into a DynamoDB table. My apologies for such a long document but I thought I would try to minimize the resolution attempts that I've already tried. http://www.linuxquestions.org/questions/solaris-opensolaris-20/dt-messaging-system-could-not-be-started-548367/ If it has wheels or a skirt, you can't afford it. 1 Kudo Reply John Dvorchak Honored Contributor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email

Look at it via the symbolic "debugger" using a command such as: # debugger core >where >quit Checksum of ttsession: # sum /usr/dt/bin/rpc.ttserverd ====================================================================== 5. This is the accepted answer. If you'd like to contribute content, let us know.

Hope this helps. https://www.experts-exchange.com/questions/20573916/help-solaris-installation-problem-DT-messaging-system-could-not-be-started.html The Ports collection makes available every popular FOSS application and packag… Unix OS Shell Scripting Basics Article by: Smita Why Shell Scripting? Type the following command to check whether the rpcbind daemon is running. # /usr/bin/rpcinfo -u localhost rpcbind DT messing system cannot be started! - Sun Solaris I just installed Solaris 9 on my Ultra 60 and logged into root's CDE and tried to add a user.

Remove advertisements Sponsored Links rpollard001 View Public Profile Find all posts by rpollard001 #2 11-13-2008 solaris12345 Registered User Join Date: Nov 2008 Last Activity: 7 December 2008, 4:13 http://strobelfilms.com/dt-messaging/dt-messaging-system-could-not-started-aix.html Not a big deal and you can see how it is set now. Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... Join UsClose Home Services Forums Advertise Contact or Login Login to Your Account Remember Me?

Just complete a warm start as described in this procedure. 1. Also, according to Bug Id: 1186212, it is perfectly fine to delete the TT_DB directory to relocate it to a safer directory. 5. Recent Msgs:general/2016-12/msg30413.htmlscm-fedora-commits/2016-12/msg12080.htmlscm-fedora-commits/2016-12/msg12065.htmlfedora-devel-list/2016-12/msg02543.htmlgeneral/2016-12/msg30408.htmlgeneral/2016-12/msg30513.htmlgeneral/2016-12/msg30419.htmlgeneral/2016-12/msg30573.htmlgeneral/2016-12/msg30386.htmlfedora-devel-list/2016-12/msg02541.html Latest News Stories: Linux 4.0 Kernel Released Google Lets SMTP Certificate Expire Open Crypto Audit Passes TrueCrypt CIA 'tried to crack security of Apple devices' Xen Security Bug: Amazon, his comment is here Check the inetd.conf file for the tooltalk entry.

Try creating an alternative user - that might not make assumptions about the graphics. Posted on 2003-04-03 Unix OS 3 1 solution 2,180 Views Last Modified: 2013-12-27 when install solaris8 on ultra60, the following message appeared: ----------------------------------------------------------------- The DT messaging system could not be started. Though the NIS server really can't see within the VB host, the NIS must interact with CDE.

Chris Scarff replied Oct 27, 2010 Over the years, I've found that this error message has nothing to do with the files it suggests to look at.

Show: 10 25 50 100 items per page Previous Next Feed for this topic UNIX & Linux Forums > Operating Systems > Solaris Member Name Remember Me? I just installed Solaris 9 on my Ultra 60 and logged into root's CDE and tried to add a user. chose Ok to return to the login screen 2. Share?Profiles ▼Communities ▼Apps ▼ Forums AIX Forum Log in to participate Expanded section▼Topic Tags ?

I'm not going to try this again. I've got the following in my /etc/hosts > 127.0.0.1 localhost > 192.168.0.11 myhostname > I can access to other systems outside of the LAN with SSh or ping > hosts with Though the NIS server really can't see within the VB host, the NIS must interact with CDE. weblink Since it is possible to put commands in user's environment that confuse the CDE login process, these files should also be checked.

I logged into the failsafe mode (the only place I can log in) and issued the "df" command. For me, this means since I put the host in my NIS domain, I failed to add a client entry into the NIS host table. Log in to reply. I looked in /etc/environment and searched for "DT" but this returned no results.

hosts: files dns # Note that IPv4 addresses are searched for in all of the ipnodes databases # before searching the hosts databases. Is it normal? DNS - Reverse lookup failure - DNS entry did not match system entry - Check entry in the ptr.XXX.dbfile This will be true for all Solaris releases up to Solaris 10 update 9.

Thanks, Craig Join this group Popular White Paper On This Topic A Beginner's Guide to VoIP 3Replies Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be Something somewhere got my system very very badly damaged. Mark 0 LVL 18 Overall: Level 18 Unix OS 9 Message Expert Comment by:liddler ID: 104792722004-02-29 No comment has been added lately, so it's time to clean up this TA. Check links for ttsession.

It is a very handy tool. Go to Solution. 0 Kudos Reply All Forum Topics Previous Topic Next Topic 14 REPLIES Sridhar Bhaskarla Honored Contributor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Solved! I don't know if I've quota running, but quota -v username doesn't return any numbers (user's UID 100).

Check to see that the hostname is correct in these files: HOW CAN I ACCESS THESE IN FAIL SAFE MODE??? /etc/src.sh /etc/hosts /usr/adm/inetd.sec 3. I've run > out of option here. Any information would be appreciated, thank you. -Gani- Next Message by Date: tape drive keep giving problem Hello all. Another system was also moved from one dhcp server to another in a similar manner, however, the login interface on that was, perhaps, Sun's Java...and on that system, I did not,

Check ownership of home directory Check the ownership on the home directory of the user who is experiencing the problem. ====================================================================== 11.