• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 703
  • Last Modified:

VB and NetWare API

I'm having trouble geting past the NWCallsInit, which is returning a generic 35071.  

Nine times out of ten, NWCallsInit() failure implies not finding the NLS directory below some directory in the path.  Alas, that's not the case here.

So what's the deal here?  I have to run under the MS for NetWare client, not the client from Novell.  On boxes with the client from Novell, everything is OK.

On the box getting the error (W2K server), I've copied over the NetWare API DLLs and NLS files and am using the Novell provided declarations.

So, has anybody got to the NetWare API from VB not under the Novell client?
0
cookre
Asked:
cookre
  • 2
1 Solution
 
ShaneCourtrilleCommented:
I didn't even know you could call the Netware APIs without the netware client installed.  I would assume that the NWCallsInit requires something that just copying over the DLLs isn't provided.
0
 
cookreAuthor Commented:
It does appear to be more than just making sure the NLS directory is there.  I must admit, the 35071 (88FF, REQUESTOR FAILURE, SHELL NOT PRESENT, or UNKNOWN ERROR) would seem to suggest that.

(and to think I crab about bulding NLMs under Watcom)
0
 
cookreAuthor Commented:
After much fiddling to identify just which pieces were required, installation of the resultant package would have been almost as odious as the full client, so we relented and decided to require the Novell client.
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now