Networks

Ask something
Discussion Locked

Upgrade Wizard NLS Problem

0 helpful
7 replies

by chris.riley 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I attempted to do a NetWare 4.11 - 5.1 Upgrade using Novell's Upgrade Wizard....

Everything was going well until the 5.1 Server rebooted itself with the identity of the old server. I then went to do the 'Continue Migration' section in the UpgradeWizard and it said that you must verify that Licensing is installed correctly before you go any further. I noticed that there was no licenses installed and that I was using a 'grace' login (when I looked in nwconfig at the installed products NLS wasnot there so it would not let me add a license). I looked around at various TIDS most of which suggested using setupnls but this would not allow me to do anything.

I tried to continue the migration anyway but it wouldn't let me go any further because it said I didn't have any console operator rights (presumably because there were no licenses installed and I was using a 'grace' login?).

I ended up restoring the source server because I could not see a way past this problem.

I think the problem was because the schema on the NW5.1 server had not been extended for use with NLS (had the migration messed up NDS??).

Has anyone seen this problem/know what caused it/know how to resolve??

7 replies

by jimbb

SETUPNLS doesn't really do much more than extend the NDS schema. I presume you inserted the licenses during the install? First of all, you need two kinds of licenses, one for the server and one for the connections (you may have a diskette saying server + xx connections, which is actually one of both kinds). You should verify you have added both during the install.
And second, in some cases the connection licenses are not assigned to a server during the install, and that needs to be corrected afterwards. You do that in NWADMN32.EXE, in the license object.

Jim

by shanghai sam

The MLA license was installed on the destination server (NW5.1) prior to the migration but once the volumes and NDS had been migrated the licenses were no longer there. As NLS was not in the list of installed products I could not add any licenses. As I had a 'grace' connection to the server I could not access any volumes so therefore could not use NWADMN32.EXE

by jimbb

Hi Chris,

An other attempt... the licensing in NW4 was different, but the most recent service-packs copied the "new" licensing system, including things like SETUPNLS.NLM. You weren't obliged to install it on a NW4 server, and most people didn't. But maybe doing so prior to the upgrade may make the difference?

Jim

by techdictator

I concur, had a similar problem and SetupNLS worked or installing SP9 which has the latest NLS files in it.

This discussion is closed to new replies.