Earlier getting error 34960 (0x8890) and now 34948 (0x8884)

Hi All,
      I have one application which runs as windows service.
I was getting error 34960 (0x8890 OBJECT ALREADY AUTHEN) when I was 
calling NWDSLogin() API.

I posted this on
http://www.ndsengineers.com/showthread.php?
t7329&highlight=error+code+0x8890

As per suggestion there I used following API to find out connection 
existing from my machine to the NDS server , so that I could find out if 
there are already any users (applications) logged into the server beacause 
of which I was getting the above error.

NWCCScanConnRefs
NWCCGetAllConnRefInfo
NWDSMapIDToName

As I was expecting nothing was displayed in logs. Later I found out from 
this forum that this is due the WIN NT security context issue and without 
going into the workarounds given there, I just executed my application 
from commandpromt and now it was displaying all the information.

The stragne thing is now I am not getting the error 34960 but 34948 .

my seq of authenticating to the NDS server is 

NWCallsInit
NWInitUnicodeTables
NWDSCreateContextHandle
NWDSSetContext ........
NWDSLogin
NWDSOpenConnToNDSServer
NWDSAuthenticateConn
 
I was getting the error 34960 for API NWDSLogin earlier and now I am 
getting it on NWDSOpenConnToNDSServer

I am using Novell client 4.90, can this be some setting/configuretion 
issue with my client.

why I am not getting the same error for which I was doing all the 
investigation but some new error.

Any help is greatly appreciated.

Thanks in Advance.
Sanjay

<sanjay_sutar@persistent.co.in> wrote in message 
news:SWtsf.2151$012.395@prv-forum2.provo.novell.com...
> Hi All,
>      I have one application which runs as windows service.
> I was getting error 34960 (0x8890 OBJECT ALREADY AUTHEN) when I was
> calling NWDSLogin() API.
>
> I posted this on
> http://www.ndsengineers.com/showthread.php?
> t7329&highlight=error+code+0x8890
>
> As per suggestion there I used following API to find out connection
> existing from my machine to the NDS server , so that I could find out if
> there are already any users (applications) logged into the server beacause
> of which I was getting the above error.
>
> NWCCScanConnRefs
> NWCCGetAllConnRefInfo
> NWDSMapIDToName
>
> As I was expecting nothing was displayed in logs. Later I found out from
> this forum that this is due the WIN NT security context issue and without
> going into the workarounds given there, I just executed my application
> from commandpromt and now it was displaying all the information.
>
> The stragne thing is now I am not getting the error 34960 but 34948 .
>
> my seq of authenticating to the NDS server is
>
> NWCallsInit
> NWInitUnicodeTables
> NWDSCreateContextHandle
> NWDSSetContext ........
> NWDSLogin
> NWDSOpenConnToNDSServer
> NWDSAuthenticateConn
>
> I was getting the error 34960 for API NWDSLogin earlier and now I am
> getting it on NWDSOpenConnToNDSServer
>
> I am using Novell client 4.90, can this be some setting/configuretion
> issue with my client.

My first guess would be an issue with your SLP configuration. The code 
behind various APIs for server location is of varying robustness, for 
example, there are circumstances under which 
NWGetObjectNamesBeginA/NextA/EndA wont find a server to which your 
workstation is already connected via IP! I've not used 
NWDSOpenConnToNDSServer, I've always used NWCCOpenConnByName which seems 
pretty reliable. It will succeed in connecting to a server that the 
NWGetObjectNamesxxxA combo cant find. I suggest you try it.

John
DevSup SysOp 24 

> 
> <sanjay_sutar@persistent.co.in> wrote in message 
> news:SWtsf.2151$012.395@prv-forum2.provo.novell.com...
> > Hi All,
> >      I have one application which runs as windows service.
> > I was getting error 34960 (0x8890 OBJECT ALREADY AUTHEN) when I was
> > calling NWDSLogin() API.
> >
> > I posted this on
> > http://www.ndsengineers.com/showthread.php?
> > t7329&highlight=error+code+0x8890
> >
> > As per suggestion there I used following API to find out connection
> > existing from my machine to the NDS server , so that I could find out

if
> > there are already any users (applications) logged into the server 
beacause
> > of which I was getting the above error.
> >
> > NWCCScanConnRefs
> > NWCCGetAllConnRefInfo
> > NWDSMapIDToName
> >
> > As I was expecting nothing was displayed in logs. Later I found out 
from
> > this forum that this is due the WIN NT security context issue and 
without
> > going into the workarounds given there, I just executed my
application
> > from commandpromt and now it was displaying all the information.
> >
> > The stragne thing is now I am not getting the error 34960 but 34948 .
> >
> > my seq of authenticating to the NDS server is
> >
> > NWCallsInit
> > NWInitUnicodeTables
> > NWDSCreateContextHandle
> > NWDSSetContext ........
> > NWDSLogin
> > NWDSOpenConnToNDSServer
> > NWDSAuthenticateConn
> >
> > I was getting the error 34960 for API NWDSLogin earlier and now I am
> > getting it on NWDSOpenConnToNDSServer
> >
> > I am using Novell client 4.90, can this be some setting/configuretion
> > issue with my client.
> 
> My first guess would be an issue with your SLP configuration. The code 
> behind various APIs for server location is of varying robustness, for 
> example, there are circumstances under which 
> NWGetObjectNamesBeginA/NextA/EndA wont find a server to which your 
> workstation is already connected via IP! I've not used 
> NWDSOpenConnToNDSServer, I've always used NWCCOpenConnByName which seems 
> pretty reliable. It will succeed in connecting to a server that the 
> NWGetObjectNamesxxxA combo cant find. I suggest you try it.
> 
> John
> DevSup SysOp 24 
> 
> 


Thanks for your reply John

I will check the SLP config and will try to use NWCCOpenConnByName 

I found one more thing regarding this.

My application runs find on other machine.
On that machine , when I run it as windows service , I dont have to login 
through ConsoleOne client , and it works just fine.
 But on the same mahcine when I run the application from command prompt 
and if I dont login through the Novell client (consoleOne) I get error 
34948 on NWDSLogin. If I login with ConsoleOne and then restart my 
application , everything goes fine.

Why this is so ? why it is necessary to connect to the NDS server when the 
application is run from command prompt ? But it doesnt require any 
connection when it run as windows service. ?



Thanks for your help

<sanjay_sutar@persistent.co.in> wrote in message 
news:%dMsf.2662$012.1938@prv-forum2.provo.novell.com...
>>
>> <sanjay_sutar@persistent.co.in> wrote in message
>> news:SWtsf.2151$012.395@prv-forum2.provo.novell.com...
>> > Hi All,
>> >      I have one application which runs as windows service.
>> > I was getting error 34960 (0x8890 OBJECT ALREADY AUTHEN) when I
was
>> > calling NWDSLogin() API.
>> >
>> > I posted this on
>> > http://www.ndsengineers.com/showthread.php?
>> > t7329&highlight=error+code+0x8890
>> >
>> > As per suggestion there I used following API to find out
connection
>> > existing from my machine to the NDS server , so that I could find
out
> if
>> > there are already any users (applications) logged into the server
> beacause
>> > of which I was getting the above error.
>> >
>> > NWCCScanConnRefs
>> > NWCCGetAllConnRefInfo
>> > NWDSMapIDToName
>> >
>> > As I was expecting nothing was displayed in logs. Later I found
out
> from
>> > this forum that this is due the WIN NT security context issue and
> without
>> > going into the workarounds given there, I just executed my
application
>> > from commandpromt and now it was displaying all the information.
>> >
>> > The stragne thing is now I am not getting the error 34960 but
34948 .
>> >
>> > my seq of authenticating to the NDS server is
>> >
>> > NWCallsInit
>> > NWInitUnicodeTables
>> > NWDSCreateContextHandle
>> > NWDSSetContext ........
>> > NWDSLogin
>> > NWDSOpenConnToNDSServer
>> > NWDSAuthenticateConn
>> >
>> > I was getting the error 34960 for API NWDSLogin earlier and now I
am
>> > getting it on NWDSOpenConnToNDSServer
>> >
>> > I am using Novell client 4.90, can this be some
setting/configuretion
>> > issue with my client.
>>
>> My first guess would be an issue with your SLP configuration. The code
>> behind various APIs for server location is of varying robustness, for
>> example, there are circumstances under which
>> NWGetObjectNamesBeginA/NextA/EndA wont find a server to which your
>> workstation is already connected via IP! I've not used
>> NWDSOpenConnToNDSServer, I've always used NWCCOpenConnByName which
seems
>> pretty reliable. It will succeed in connecting to a server that the
>> NWGetObjectNamesxxxA combo cant find. I suggest you try it.
>>
>> John
>> DevSup SysOp 24
>>
>>
>
>
> Thanks for your reply John
>
> I will check the SLP config and will try to use NWCCOpenConnByName
>
> I found one more thing regarding this.
>
> My application runs find on other machine.
> On that machine , when I run it as windows service , I dont have to login
> through ConsoleOne client , and it works just fine.
> But on the same mahcine when I run the application from command prompt
> and if I dont login through the Novell client (consoleOne) I get error
> 34948 on NWDSLogin. If I login with ConsoleOne and then restart my
> application , everything goes fine.
>
> Why this is so ? why it is necessary to connect to the NDS server when the
> application is run from command prompt ? But it doesnt require any
> connection when it run as windows service. ?

I'm not familiar with running NetWare aware apps as windows services, but on 
the machine on which you get the 34948 error, does the client have a 
preferred tree set? Check under "Red N" - Client properties ->
Client tab.

John 

> 
> <sanjay_sutar@persistent.co.in> wrote in message 
> news:%dMsf.2662$012.1938@prv-forum2.provo.novell.com...
> >>
> >> <sanjay_sutar@persistent.co.in> wrote in message
> >> news:SWtsf.2151$012.395@prv-forum2.provo.novell.com...
> >> > Hi All,
> >> >      I have one application which runs as windows service.
> >> > I was getting error 34960 (0x8890 OBJECT ALREADY AUTHEN) when
I was
> >> > calling NWDSLogin() API.
> >> >
> >> > I posted this on
> >> > http://www.ndsengineers.com/showthread.php?
> >> > t7329&highlight=error+code+0x8890
> >> >
> >> > As per suggestion there I used following API to find out
connection
> >> > existing from my machine to the NDS server , so that I could
find 
out
> > if
> >> > there are already any users (applications) logged into the
server
> > beacause
> >> > of which I was getting the above error.
> >> >
> >> > NWCCScanConnRefs
> >> > NWCCGetAllConnRefInfo
> >> > NWDSMapIDToName
> >> >
> >> > As I was expecting nothing was displayed in logs. Later I
found out
> > from
> >> > this forum that this is due the WIN NT security context issue
and
> > without
> >> > going into the workarounds given there, I just executed my 
application
> >> > from commandpromt and now it was displaying all the
information.
> >> >
> >> > The stragne thing is now I am not getting the error 34960 but

34948 .
> >> >
> >> > my seq of authenticating to the NDS server is
> >> >
> >> > NWCallsInit
> >> > NWInitUnicodeTables
> >> > NWDSCreateContextHandle
> >> > NWDSSetContext ........
> >> > NWDSLogin
> >> > NWDSOpenConnToNDSServer
> >> > NWDSAuthenticateConn
> >> >
> >> > I was getting the error 34960 for API NWDSLogin earlier and
now I am
> >> > getting it on NWDSOpenConnToNDSServer
> >> >
> >> > I am using Novell client 4.90, can this be some 
setting/configuretion
> >> > issue with my client.
> >>
> >> My first guess would be an issue with your SLP configuration. The
code
> >> behind various APIs for server location is of varying robustness,
for
> >> example, there are circumstances under which
> >> NWGetObjectNamesBeginA/NextA/EndA wont find a server to which
your
> >> workstation is already connected via IP! I've not used
> >> NWDSOpenConnToNDSServer, I've always used NWCCOpenConnByName which

seems
> >> pretty reliable. It will succeed in connecting to a server that
the
> >> NWGetObjectNamesxxxA combo cant find. I suggest you try it.
> >>
> >> John
> >> DevSup SysOp 24
> >>
> >>
> >
> >
> > Thanks for your reply John
> >
> > I will check the SLP config and will try to use NWCCOpenConnByName
> >
> > I found one more thing regarding this.
> >
> > My application runs find on other machine.
> > On that machine , when I run it as windows service , I dont have to 
login
> > through ConsoleOne client , and it works just fine.
> > But on the same mahcine when I run the application from command
prompt
> > and if I dont login through the Novell client (consoleOne) I get
error
> > 34948 on NWDSLogin. If I login with ConsoleOne and then restart my
> > application , everything goes fine.
> >
> > Why this is so ? why it is necessary to connect to the NDS server when

the
> > application is run from command prompt ? But it doesnt require any
> > connection when it run as windows service. ?
> 
> I'm not familiar with running NetWare aware apps as windows services, 
but on 
> the machine on which you get the 34948 error, does the client have a 
> preferred tree set? Check under "Red N" - Client properties ->
Client 
tab.
> 
> John 
> 
> 




I am getting the error on client setup.
I will check that. But on my setup where the application runs fine , the 
preferred tree was set. I cleared it and ran my applicaiton , even then it 
was working fine.

On the setup where the application gives error, there are more than one 
server under same tree.

I observered one more thing , on the m/c where the application gives error.

The API that I added to display all connection from the workstation , 
shows one conneciton ( that is not licenced ) but to diff server. THis is 
not the same server to which I am trying to connect in my application.
I guess the first server that responds is returned to me. as a result 
whenever I try to connect to desired server (either through Novell client 
or my application) a diff server is returned to me.

I found that this is desired behaviour on part of Novell client . ie. its 
fine with the novell client even if it gets connection to diff server than 
whatever it requested.  But my application ,is supposed to connect to 
specific server and send other request to it only. 

I have two question 

1. If it is possible to *always* connect to the desired server only 
(through Novell client and then my applicaion will just follow it.)
2. In a setup of multiple server under same tree (  if its fine with the 
client that it gets connection with diff server than it specified ) Is 
there any way so that I can also succeed in connecting with any server 
under the same tree.
   Is it possible at all ?

Thansk for your continued support.