n4MsgSend and Error 140: User Lookup Failed

Keywords:     n4MsgSend Error 140 User Lookup Failed

Question:

I'm getting the Error 140: User Lookup Failed, on the N4MsgSend function below. I have the Novell client under NT 4.0.
AddExtender("wwn4x34I.dll") msg="Test Message from Chet's WS." obj = 4NameConvert("CAD_DEPT.KAI","CAD536",3) pause("Result",obj) N4MsgSend("\\CAD",msg,obj)
Can't find the user to send the message. The extender dll is original to the WinBatch program (Version 97D).

My station is running Windows NT 4.0 with service pack 3. It also has Client32 4.11A. Our N.O.S. is Novell 4.11 Intranetware.

Answer:

The scoop on that is that n4MsgSend is really just the bindery n3MsgSend with a different name.

The reason for this is that, last time we checked, Novell did not have a NDS SendMessage API available for us to use. The N4 and N3 extenders are in reality a thin covering over the Novell API's. If they (Novell client) do not give us the functions, there is little we can do in the way of implementing them.

The user name must be recognised as a user (via bindery emulation) on the server specified. Only those users on that server will get messages.
No context, decorated names, trees or anything enter into it. Use a plain undecorated user name, so do not user n4NameConvert. Must think "bindery".
Go into Network Settings in Control Panel, and set the workstation to boot up from the server NOT off a tree, but in bindery emulation.
Your user must be connected to the server.
The user needs to have an account on the server.

Article ID:   W13623

Filename:   n4MsgSend and Error 140 User Lookup Failed.txt

File Created: 2001:03:01:13:48:00

Last Updated: 2001:03:01:13:48:00

Database Search

TechHome

n4MsgSend and Error 140: User Lookup Failed

Question:

Answer: