Getting error 0x8866 (NO MORE ENTRIES ) while parsing with NWParseNetWarePath

> 
> <sanjaySsottjo.com> wrote in message 
> news:y2XNf.2802$oh5.2752prv-forum2.provo.novell.com...
> >>
> >> <sanjaySsottjo.com> wrote in
message
> >> news:Y1ENf.1889$oh5.1488prv-forum2.provo.novell.com...
> >> >I am trying to delete a home directory for
some user on my NDS setup.
> >> >
> >> > I do following to get the path to use for
subsequent Netware API
> >> >
> >> > ccode = NWParseNetWarePath(theLocation,
&conn, &dirHandle, ppath);
> >> >
> >> > The i/p parameters is
> >> > theLocation =
"<SeverName>\<VolumeName>:<Path>&q
uot;
> >> >
> >> > But I am getting error 0x8866 (NO MORE
ENTRIES).
> >> > The same API works on some of server in
our setup but troubles for 
two
> >> > servers.
> >> > The home directories are created on a
volume which is on different
> > server.
> >> > Do I need to consider anything special in
this case. But I cannt 
relate
> >> > the error I am getting with the
situation.
> >>
> >> While I've never used NWParseNetWarePath (I
use NWParsePath), I've 
dont
> >> recall encountering error 0x8866 in 15+ years
of NetWare programming. 
Is
> > the
> >> problem machine specific, or specific to a
client version? In 
particular
> > if
> >> using 4.9 Sp2, try an earlier client version.
> >>
> >> John
> >> DevSup SysOp 24
> >>
> >>
> >
> > John,
> > Thanks for your reply.
> >
> > This not specific to machine or client but to some
NDS setup I guess.
> > Because the same things work fine on other server.
> >
> > Can you give some pointers where should I look for
?
> > I searched extensively only to find one post (
back in 2001) with same
> > issue (same error for same API) but it didnt had
any useful information
> > for me :(
> 
> Given that we have no idea what the problem might be,
I'd try using 
> NWParsePath instead and hope it doesn't result in the
same error.
> 
> John
> DevSup SysOp 24 
> 
> 


John
One update on this !!

I have written very small program which accepts a path and
parse it. I am 
using both the functions now NWParseNetWarePath  and
NWParsePath (after 
call to NWParseNetWarePath  fails )

The argument passed is ;

<Server>\<Volume>:<DirectoryPath>
Where 
Server – Name of server
Volume – Physical volume on above server
DirectoryPath – path of directory.
 
Ex.
C:\>ParsePath.exe HOME\VOL1:\DIR2
Where HOME – Name of server
      VOL1 – physical volume on HOME server
      \DIR2 – Directoy path


Now the setup where this is happening is ;

I have created one user on local server and its home
directory exists on 
some remote volume (on remote server).

now when I try to parse the path ( in above format) where
the server is 
remote I get the error 0x8866 for NWParseNetWarePath  and
0x880F (SERVER 
NO CONN) for NWParsePath. But I can see the server
connection in Netware 
connection.
 
One more thing , My application is running as windows
service on Win2K. 


With all above setup if I create user with local server (
primary server 
to which I connect in my application or Novell client) and
also create the 
home directory on some volume of the same server (local)
then every thing 
works fine. 

Is it related to connection , But what is it realy ??

Thanks for your continued support 

Sanjay