Home > Dt Messaging > Dt Messaging Service Could Not Be Started

Dt Messaging Service Could Not Be Started

If you still have problem, please post a comment and your /etc/nsswitch.conf file, if you have problem with NIS+ client, such as NIS+ cache problem, I'll try to give you a All rights reserved. I am not sure what is wrong. If the server is running, it prints a list of program and version numbers that are associated with the UDP protocol. http://strobelfilms.com/dt-messaging/dt-messaging-could-not-started.html

Only a reboot would detect the tape drive again for to ject it out. Any help would be appreciated. Another suggestion 1. The root user does have a .dtprofile file but everything in this file is commented out. http://www.unix.com/solaris/33110-solaris-10-cde-problem-dt-messaging-system-could-not-started.html

This will be true for all Solaris releases up to Solaris 10 update 9. To correct the problem 1. These errors and warnings should be resolved before CDE will run properly. 3.Check the error log /var/dt/Xerrors Check the error log $HOME/.dt/errorlog 4.The output from nslookup <hostname> and nslookup <IP> should No aliases] spc allow [hostnames or '*'.

Checked /etc/hosts 1. kediri:/# du -ks /app 4677918 /app kediri:/# df -k /app Filesystem kbytes used avail capacity Mounted on /dev/md/dsk/d60 17313526 15857366 1283025 93% /app I got this strange result only for this Run ps to get the PID, which is the value in the second column. # ps -ef |grep rpcbind solaris installation problem: DT messaging system could not be started.

Become superuser or assume an equivalent role. 2. Check to see that the hostname is correct in these locations: /etc/src.sh /etc/hosts In the following example, pyro is the system in question # # Internet host table http://osdir.com/ml/os.solaris.sunhelp/2001-12/msg00329.html Oracle Database MS SQL Server Unix OS Importing a DynamoDB Table From an S3 Export Video by: Phil In a previous video, we went over how to export a DynamoDB table

The following 3 lines were listed: "dtsession: Unable to start message server -- exiting" “dtsession: Unable to exec /usr/dt/install/oldrules/dtrmrules.driver. 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 Any information would be appreciated, thank you. -Gani- Next Message by Thread: tape drive keep giving problem Hello all. IPv6 Service [VerizonFiOS] by pappasbike284.

I have seen other documentation that indicates this is an acceptable step to take if the TT_DB databases get corrupt 3. https://community.hpe.com/t5/General/The-desktop-messaging-system-could-not-be-started/td-p/3190526 You're now being signed in. Internet Speed Upgrades [Mediacom] by MediacomChad286. Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free!

Here's Why Members Love Tek-Tips Forums: Talk To Other Members Notification Of Responses To Questions Favorite Forums One Click Access Keyword Search Of All Posts, And More... check over here Because logging in as root only checks root permissions on a local file system, find out if the /usr/dt or /usr/openwin directories are I changed the hostname and IP Address to match the values I put into the /etc/hosts file. Do pkgchk on the following packages: - SUNWtltk - SUNWxwplt - SUNWdtdte - SUNWdtwm

The end of the output from this script should give X ERRORs and X WARNINGs. A. Since access there is unrestricted on any local file system it will prove if the problem is permissions, or something else. http://strobelfilms.com/dt-messaging/dt-messaging-could-not-be-started.html Tooltalk Items to check involving tooltalk include: A.

Check the inetd.conf file for the tooltalk entry. Updated on 2013-04-01T14:26:38Z at 2013-04-01T14:26:38Z by SystemAdmin nagger 100000MRSJ 342 Posts Re: Keep getting “The DT Messaging System could not be started” error message ‏2013-03-25T22:59:06Z This is the accepted answer. To correct the problem: 1.

Quotas Verify that user's disk quota has not been exceeded by running the following command: #quota -v Also, you can

The | fix is to completely delete ALL of these directories (use find to locate | them) using "rm -rf /dir/TT_DB. | | These will be recreated as needed; no need Check ownership of home directory Check the ownership on the home directory of the user who is experiencing the problem. ====================================================================== 11. There are two NFS mounted systems that are each approximately 90% full but this would not be the cause of the problem. 1) If I changed the hostname and IP Address Though the NIS server really can't see within the VB host, the NIS must interact with CDE.

Check for the presence of a line file:hosts If this line exists, comment it out. ====================================================================== 3. Can't believe I overlooked that. Your system can still send mail (such as alerts) with this disabled. weblink Close this window and log in.

I suggest you to open a new thread. For additional info, see the DT User's Guide." I logged into a failsafe session and then changed the hostname and IP Address. We do have alot of old computers here and that is a running joke about putting them in a museum.