Google 網路論壇不再支援新的 Usenet 貼文或訂閱項目,但過往內容仍可供查看。

ConsoleOne - "Failed to set current tree name"

瀏覽次數:23 次
跳到第一則未讀訊息

jash...@sbsu.com

未讀,
2003年3月12日 晚上8:20:172003/3/12
收件者:
When I try to open the properties of an object in ConsoleOne I get the
following error message:

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

I have tried the suggestions in TID10068331 and it still gives the error.
I've uninstalled NICI and reinstalled it several times. On other
workstations it works by having only NICI version 2.02 installed, but I
have tried installing versions 1.57, 2.02, and 2.42 in different
combinations and nothing gets rid of the error. My server is running
NW6SP2. After I close the error box the properties of the user or object
comes up, but I don't want to corrupt any objects if it isn't working
properly.

Any suggestions??

Jon.

Michiel van Dijk

未讀,
2003年3月20日 凌晨4:14:412003/3/20
收件者:
I ve the same problem, this problem always appear after some minutes when
you have started the server.

Michiel van dijk

<jash...@sbsu.com> schreef in bericht
news:l1Rba.17212$j15....@prv-forum2.provo.novell.com...

jann1

未讀,
2003年5月12日 凌晨4:28:432003/5/12
收件者:
same problem with:
c1 ver.135, nw6sp3, nici242, workstation w2k, client483.....
any ideas ?

greetings
--
Hermann Jannasch e-mail: h...@uni-landau.de

Garrett MacAskill

未讀,
2003年5月14日 上午11:56:082003/5/14
收件者:
I have the same problem on a BM3.7 server, NW6 - upgraded to NW6SP3 and now my iManager doesn't work either.   You may also see an error message in your Logger screen indicating a 10091 error when it tries to load SSL services.   I tried a patch on Novell's site SAS172FT.EXE which is supposed to fix the problem.   But it did not work for me.

>>> jann1<jann...@uni-landau.de> 05/12/03 01:28AM >>>

Patrick Pankratz

未讀,
2003年5月16日 清晨7:59:572003/5/16
收件者:
Hi there,
I've sometimes the same problem.
I figured out, that on an Win 2k machine in
%SystemRoot%\System32\Novell\NiCi,
directories exist, where two files are stored.
These directories are named like the Userid's, they belong
to.
*After* taking ownership of the directory, you're able
to delete the directory and the problem doesn't occur
for a time.

Patrick

"jann1" <jann...@uni-landau.de> schrieb im Newsbeitrag
news:3EBF5C4E...@uni-landau.de...

0 則新訊息