Problems with NWADMIN32.EXE and BM v.3
Robert Duerr
Since I installed Border Manager Version 3 on my NetWare 5 server I have
got problems starting NWADMIN32. Server has Service pack 1 installed,
which provides for newest version of NWADMIN32.
I get following message:
Runtime error
Nwadmin32.exe
Abnormal program termination
When I remove (or delete) bsmon.dll (11/10/98) out of Snapins-directory
NWADMIN32 starts, but with degraded Border-Manager configuration
support.
What's wrong?
Robert
Craig Johnson
I would try reinstalling the snapins.
Craig Johnson
Novell Support Connection SysOp
Robert Duerr
Tried this several times before, but nothing changed.
Robert
Craig Johnson
Sorry, I haven't got an answer, except to hope that the first service
pack for Bmgr 3.0 fixes the problem. Or open an incident.
On the other hand, I had some very strange problems with a BMgr server
last night, and ultimately I think they may have been related to
NDS/licensing issues. I was getting error messages about a snapin that
turned out to be unrelated to the snapin. Perhaps if you take a close
look at your licensing you may find some issue there that can be
cleared up and fix your problem. A long shot, but...
Loren Clark
configure BM3. I keep getting the runtime errors that seem to be
associated with BSMON.DLL since they disappear if I rename or delete
BSMON. However, then I can not configure BM.
Loren
Craig Johnson
I've not seen that myself. I have been able to install the latest
ZENworks (beta) NWADMN32 to a non-BMgr server and then install the BMgr
snapins there as well, and that worked. You might want to try it - get
bcltsp4.exe from support.novell.com.
Johns Stevens
to solve a simple problem like this for a shipping product. There must be
a 5.09 client for Nw 4.11 that is not beta somewhere. The 1.1 Zen works
cd I have has 5.07 on it, and does not work with BorderManager.
Thanks,
Neal Vadekar.
Craig Johnson
Something else to try - see if removing other (non-Bmgr) snapins helps.
With BMgr 3 beta, the WANMAN snapin caused problems, and perhaps some
others.
Craig Johnson
Sorry, I guess you'll have to wait until the ZEN 1.11 Starter Pack
update is released, probably this month.
Johns Stevens
5.09, the border manager snap-ins still do not work, with the same
problems as before. I have re-installed the brdmgr snapins, same
problem. However when I load nwadmn32.exe from the nw 5 server, then
it works. Any ideas?
Neal Vadekar.
Craig Johnson
Check all the files in the win32 directory and those below it (NLS) -
are there any differences between the NW5 server and the other?
Loren Clark
workstations I have tried it from, three different servers [one is NW5
without BM3 installed, on is the NW5 server with BM3 installed and one is a
NW411 server], I have tried running the BM uninstall routine located in the
Win95 Add/Remove programs utility and then reinstalled using the BM3 snapin
setup program, I have tried editing the Win95 registry to remove as many of
the additional/optional snapins as I can. I think that about covers the
different things I have tried.
I mainly get three different symptoms:
1. The MS Visual C ++ runtime error;
2. A message saying that BM is not installed on this server when I click
the BM setup page for the server that has BM3 installed;
3. A message saying that this snapin only administers BM 3 and an earlier
version of BM was detected on this server.
Novell had me do the uninstall routine, reboot the workstation, reinstall
the snapins today. This produced symptom #3 listed above. I'm waiting to
see what they want me to try next. They do not want me to try the NWadmin
from the beta ZEN release.
This stuff sure is getting old! :-(
Loren
Craig Johnson
> 3. A message saying that this snapin only administers BM 3 and an earlier
> version of BM was detected on this server.
>
1. I merged a temporary tree holding BMgr to the production tree
2. I moved all the objects I could (some - license-related objects - cannot
be moved, but must be recreated) to a new OU
Somewhere about this point I had a problem I couldn't resolve with -614
errors trying to update rules, so I had to not enforce rules for the
moment. ACLCHECK wasn't reading any of my Allow rules, and everyone was
denied access. I couldn't fix this, and the BM3REMOV.EXE utility wasn't
then available.
My plan was to come in late at night, and remove NDS from the server and
reinstall it to blow away the server object and associate BMgr attributes.
-It was a good plan in the end, but the BM3REMOVE utility would have
obviated that need to do this.
3. I tried installing the licenses for the server into the new OU, with the
idea I would assign them to the server later (probably not a good idea)
4. I deleted the old NLS-server object and the licenses
5. I removed NDS from the server
6. I attempted to reinstall NDS to the server - had a lot of problems at
this point, partly because some servers didn't want to synch up right away.
Eventually I got NDS restored.
- Now I got the error you have - could not set up BMgr because snapin
reported an older version. This was clearly incorrect, I in retrospect I
think it must have had something to do with licensing not being installed -
everything else had already been installed.
To fix this, I:
1. Ran SETUPNLS on the server holding the master of Root (the partition the
BMgr server was now in).
2. Ran NLSLSP on the server holding the master of Root
3. Ran SETUPNLS on the BMgr server
4. Reran the entire BMgr 3 install (basically to get to the end where it
installed the licenses for me). I didn't try to just install the licenses
again. Curiously, I was also forced to reinstall IWSP6 as BMgr3 install
wouldn't run - said I needed to install IWSP6 first!
While the reinstall was running, I deleted those license objects I had
installed earlier and not assigned.
The installation of the files completed and I was prompted to insert the
license disk. That went without problems.
Once the install finished, and I rebooted the server, the snapin worked
again and I proceeded to set up the Bmgr configuration in about 10 minutes.
It's worked fine since then.
Loren Clark
the Novell BorderManager snapins through Win95's Add/Remove programs feature,
reboot the workstation, reinstall the BM Snapins with the Setup.exe routine and
then run NWAdmin32 from the BM3 server using a mapped drive. This did not work.
They had me restart the BM3 server and I was then able to access the BM setup
pages in NWAdmin32. Novell did not have a good explanation for this but they
are aware that these symptoms are occurring frequently. To quote, "it could be
a million different things." They told me that deleting the registry entries,
uninstalling and then reinstalling the snapins will usually work.
I'm told they are trying to consolidate much of their findings into a TID that
should be available shortly.
Loren
Craig Johnson
--
Craig Johnson
Novell Support Connection Volunteer Sysop
Using Virtual Access
http://www.soft-shop.com
Loren Clark
2947067
Loren