Critical error Server failed. Reason there are 1 nested errors

It took to much time to find the solution for this error "Critical Server failed. Reason: There are 1 nested errors: weblogic.management.ManagementException: Booting as admin server, but servername,xxxxx, does not match the admin server name"

This  error can be accured  in the start of Managed Server through Node Manager
Reasons
1- Wrong parameters  in the Config.xml file
2- Wrong parameters in the Server Start file ( startup.properties)
3- Startup the Managed Server for the first time via Node Manager

Solution:

1- Just check one of the two files above &try; find out the wrong parameters then start your managed Server.
In my case  I addede the wrong the Root Directory " The directory that this server uses as its root directory. This directory must be on the computer that hosts the Node Manager"

2- Try starting the managed server one time via the script startManagedWebLogic outside of using Node Manager for example: WL_HOME\user_projects\domains\base_domain\bin\startManagedWebLogic.cmd (name managed Server) http://localhost:7001 . Then stop the server and this time use Node Manager still using startWebLogic as the script.
Cheers,