Error: "Failed to set the current tree name. Can not continue"

  • 7000443
  • 21-May-2008
  • 17-Jan-2014


Novell Certificate Server
Novell NetWare 6.5
Novell Client for Windows


Error "Failed to set current tree name. Can not continue"

Error "Set Tree Failure

Error -319 when trying to set or change NDS password

Error -1497 when trying to set simple password


NICI was not installed on the workstation or is corrupt

If the SID of the Windows user account has been changed since when NICI was last used by this same user, these errors can occur as a result of the security applied to the NICI user directory on the local workstation. This condition can occur due to mechanisms such as ZENworks Dynamic Local User (DLU) deleting and re-creating a Windows account with the same name (but a different SID), or by mechanisms such as Microsoft Sysprep or other tools which explicitly and intentionally change the SID of existing user accounts.

Unable to change Universal Password from workstation with ZENworks/DLU installed

Dangers of using SYSPREP after NICI has been installed

If those conditions apply, or the SID is being changed due to other circumstances, the best solution may be enabling the NICI "EnableUserProfileDirectory" configuration as described in the referenced documents. If the SID on the Windows account is not being changed, the described errors may be due to an old or corrupted NICI installation, which can be addressed as follows:

Verify that the latest version of the Novell Client is installed, which will contain the latest version of NICI.

To do this, first uninstall NICI on the workstation using Add/Remove Programs. You must then manually delete the NICI system files located in the C:\WINDOWS\system32\novell\nici directory. It is best to simply delete the entire nici directory. This folder is protected and you will need to boot the workstation in SAFE MODE and then take ownership of the folder and files as the Administrator of the workstation before you can delete the files. Once the files are deleted, reboot the workstation in normal mode and then reinstall the latest version of the Client.

Additional Information

Formerly known as KB 10068331.