Invalid version blah blah, mismatch blah blah

ja...@nestfamily.com

unread,

Nov 24, 2003, 3:01:05 PM11/24/03

to

Netware 5.1 sp6, BorderManager 3.7 sp2, NFS 3.0 sp5. When nfsstart is
executed the following message displays on the console:

The module "GATEWAY" has an invalid version number of 3207. It should be
3606. Load the version displayed on the screen. Version mismatch between
NFS Gateway and NSS, ensure you have the right version.

I have reapplied nw5.1sp6 and nfs3.0sp5 to no avail. I then applied
NSS5q.exe, again to no avail. Anyone have any suggestions for this?

Brad Doster

unread,

Nov 29, 2003, 2:31:26 PM11/29/03

to

I'll pass this on to Novell for review.

bd
NSC Volunteer SysOp
www.InsightNetSolutions.net

Brad Doster

unread,

Dec 2, 2003, 10:38:04 PM12/2/03

to

OK, here's the scoop... NSS5q.exe is newer than nw51sp6, so once you've
installed the former, reapplying the SP will NOT replace because the SP
install does not replace newer files. IOW, you're currrently "stuck"
with NSS5q, AND the NFS product doesn't know what to do with it. So,
to get NFS to work you need to manually roll the NSS files back to the
SP6 level. To do so, copy the following from expanded SP6 set of files
to SYS:SYSTEM and reboot the server...

CD9660.NSS
CDHFS.NSS
DOSFAT.NSS
GSEG.NSS
MAL.NSS
MALHLP.NLM
MALHLP9.NLM
MBCOMN.NSS
MBMMPRV.NSS
MBNWSA.NSS
MENUCFG.NSS
MENUNSS.NSS
NSS.NLM
NSSWIN.NLM
NWPRV.NSS
SCAN.NLM
VCU.NLM
ZLSS.NSS

..UNLESS there is a specific fix in the NSS5q patch that you need. If
there is, then we'll have to wait for Novell to fix the NFS side so it
will recognize this patch. Let us know which way works for you.

ja...@nestfamily.com

unread,

Dec 5, 2003, 12:56:32 PM12/5/03

to

> ...UNLESS there is a specific fix in the NSS5q patch that you need. If

> there is, then we'll have to wait for Novell to fix the NFS side so it
> will recognize this patch. Let us know which way works for you.
>
> bd
> NSC Volunteer SysOp
> www.InsightNetSolutions.net
>

Looks like we are getting closer to the solution. After deleting and
reapplying the files from sp6, we now get an error that says:

NSS<NSS>-2.98b-403: nssRegistration.c<180> The module "mbCOMN" has an

invalid version number of 3207. It should be 3606. Load the version

displayed on the screen. Load of MBCOMN.NSS failed, status=9.

Brad Doster

unread,

Dec 5, 2003, 11:59:40 PM12/5/03

to

In article <kF3Ab.632$19....@prv-forum3.provo.novell.com>, wrote:
> The module "mbCOMN" has an
> invalid version number of 3207. It should be 3606.
>

OK, it looks like you missed deleting that, or for some other reason
it's still installed from NSS5q... hmmm, it could be that it was
installed to C: and is still being loaded from there -- if you do
MODULES MBCOMN, does it show where it was loaded from?

ja...@nestfamily.com

unread,

Dec 10, 2003, 5:13:47 PM12/10/03

to

I will check the nwserver directory on C: then sir, thanks.

Brad Doster

unread,

Dec 10, 2003, 9:40:31 PM12/10/03

to

OK, I hope that's it!

ja...@nestfamily.com

unread,

Dec 11, 2003, 10:17:03 AM12/11/03

to

There were not any of the listed files anywhere on the C: partition. They
are all loading from SYS:\SYSTEM. When we try to load mbcomn we are
getting "LOADER CANNOT FIND PUBLIC SYMBOL" for a great number of keys. I
am going to post about this in the NSS forum. Thanks for the help.

Brad Doster

unread,

Dec 11, 2003, 10:53:38 PM12/11/03

to

OK, hope you find the answer!