system corrupted

[Fadia Almarei]

HI All
i have a problem on my Hp server , the power has been off on it many times , and after i start the system i start to put my user name and password and when i press ok it give me the folowing message
"Unable to initialize or connect to the desktop messaging system.Check your $Home/.dt/errorlog for more information.Press Ok and your session will exit."

and when i press ok it give me the following message
"Messaging system Inoperative

To Restart.
1) Save all open data files.
2) logout.
3) Login again.

Note : The current session will not be saved. When you are ready to begin the restart process, click [Ok] and proceed to save your files.

Ok Help
"
what should i do for that and what is really happened.

BR,

[Simon Hargrave]

Have you checked the output of the .dt/errorlog as the message suggests? Perhaps attach that file to a message here?

[Shaikh Imran]

hi,
Are you trying to get into a application directly with this login ?
I mean is the .profile configured for the user to directly take you to the application?
Please check the following:
Have you tried to with other user login ?
Are all other users able to login properly ?
What does the login from console say ?
Can you try root login ?

Pls revert back ..


Regards,

[Naveej.K.A]

hi,

is your loopback address / ip address configured properly.

in short? is your network configuration proper??

with best wishes
Naveej

[sreejith_4]

Hi,

You must have some entries in your .profile file which loads some application which is related to the error you are getting.
Edit your .profile and remove those entries , log off and check it out.
It would be better if you can attach your .profile

Regards
Sreejith M

[Bill Hassell · Accepted solution]

This is most likely a networking problem. Your workstation is running Xwindows which requries a valid network connection to come up properly. If the LAN is connected and the communications light is on, then most likely name resolution is a problem. See if you can ping your workstation from another system, and if so, try telnet. If telnet works OK, rename the /etc/resolv.conf file temporarily and then go back to your console and try a login. If that works, DNS is not working properly and you'll need to have some fix your DNS server.

[doug hosking]

I agree with Bill. Often this is caused by problems with networking configuration, such as if you moved the system to a new location while the power was off and had to change the IP address to a different subnet, etc.

If you changed anything in the network configuration, it might be a good idea to run /sbin/set_parms to reset the appropriate network parameters consistently.

/sbin/set_parms hostname
/sbin/set_parms ip_address
/sbin/set_parms addl_netwrk