"ZENNW32.DLL is misssing the entry point nwappLoadOD."

Question

We are getting the error
"ZENNW32.DLL is misssing the entry point nwappLoadOD."
I have found this in some other threads in this forum, but they did
not go
in a useful direction for me. This error message is appearing on a
WinXP Pro
workstation before the NWgina appears after boot up. Zen policies are
not
working.
The history of this error is that we installed SP1b on ZfD 4. We thenupdated our workstations from client 4.83 to 4.9 and afterwards the
Zen
agent to the MSI version shipping with SP1b. I have tried deleting the
installpath registry key as suggested in TID 2967507 and also followed
the
other suggestions. No luck. I also think I got the same error at some
point
after rolling back from 4.9 client to 4.83, without updating the
agent.
ZfDagent.msi will install fine on a clean machine that has not had the
previous version of the agent or client installed and policies will
work.

Answer 1

> interesting, someone else has reported this problem, but it looked like
> a terminal server issue.
I also found a few thread with this on the forum, but they were with
Win98 or 2k on the workstations, and we have XP, so the client is
different. Also, their problem was different, and the error message about
the missing entry point was just another one of their symptoms. My
problem is that the agent is not working on my XP workstations and I
cannot apply policies or register a workstation (which I can do with the
new wstations where we never had client 4.83 or the Zfd4 agent installed,
and also on our Win98 workstations).
> I'm still not clear on the exact sequence;
Ok, we had client 4.83 and Zfd4 installed. All was well re policies etc.
We updated to SP1b with Zfd, then we updated all our clients from 4.83 to
4.9. Then we deleted the InstallPath key in the registry, uninstalled the
Zfd4 agent and installed the .msi version tht comes with SP1b.
> If so, what options did you choose with client 4.9 during install?
The tech who did the client upgrade tells me that when she did a custom
install of 4.9 (with the old management agent present), she didn't get
the ZfD options in the client she used to get with 4.83. There was only
one box which was ticked and greyed out (i saw this too when I was
playing around). But I have since discovered, that when I took the
management agent off and then uninstalled 4.83 and installed 4.9, I had
all the ZfD options to tick I had with 4.83.
> Have
> you tried 4.9sp1a?
We did try it on a few machines, but found that a staff member who logs
in on lab machines as xxxxx.staff could not log in on the patched
clients. When we put the 'staff.' into the context field in the advanced
section of the login and only his username at the top, it worked! We
tried this on all the patched client machines and it happened on all of
them (I won't be upset if you don't believe me, it's too weird for
words!).
I'll try patching the client and see what happens when I update to
the .msi agent.
Thanks for your help, Shaun.
Renate
>