Accents in path problem

[ILW]

One of our 2 Paris servers (NW5.1 SP6) crashed over Xmas (hardware failure). Since then, any attempt to save a file to a folder with an accented character in the path (é, ê, etc) from a W2K workstation returns an "Out of memory/disc space" error. There is plenty of both (2.5GB RAM, 15GB free disc) A reboot makes no difference; the other server (identical) has no problem. This is driving me mad!

 

[TheLad]

Did you have to rebuild the server? If so, have you reapplied SP6? Does the error only occur on W2k or does it happen on other operating systems as well? If only W2k, what version of the NetWare Client are you running?

What version of LONG.NAM is your server running?

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ILW]

Didn't need to rebuild server - just replaced the faulty card. I don't have access to a PC running an OS other than W2K(!)
Client is 4.83.1.1 SP1
LONG.NAM is not loaded on either server (the working or non-working one)

 

[TheLad]

That would be strange if long filename support is not loaded on your servers because it is enabled as standard on NetWare 5.x servers. It would also restrict you to DOS 8.3 file and directory names.

Are you sure?

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ILW]

Sorry - was looking for LONG.NLM. Where do I find LONG.NAM?

 

[TheLad]

At the server console, type:

MODULES LONG

This will bring up the version info (you can also shorten MODULES to just M if you wish!)

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ILW]

In that case, it's definitely not running on any of our company servers. But we can use long file names.

 

[marvhuffaker]

Another thing to look at, in regard to the long names.. see if the long name space is actually applicable on the volume. Do a VOLUMES at the console,and it will tell you all name spaces that are active on each volume. If I recall correctly, the volume won't mount unless all namespace modules that apply to the volume are loaded.

Another thing you might do is run a scandisk on your DOS partition. that is where the Name Space modules are kept, and it's possible that the DOS partition got corrupted when you had your failure.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[ILW]

"Volumes" shows DOS & LONG against each volume. I didn't setup the original build, but I've checked over the C: drive and still can't see long.*

 

[marvhuffaker]

Wild goose chase. Sorry. I was looking at a nw5.1 server and there is no LONG.NAM. At some point in there, they must have built LONG.NAM into one of the other modules, but I'm not sure exactly when. It's been ages since I actually had to think about it.





Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[TheLad]

Me too, would probably suggest a VRERPAIR on your volume to see if that resolves the issue

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ILW]

I was beginning to think I was cracking up!
Will give the VRepair a go; not sure when (we're only allowed to down servers at stupid o'clock in the morning.
Thanks all.

 

[marvhuffaker]

ILW, from what I can tell, Long name space fuctionality is built into the FILESYS.NLM module in NW5.1. FILESYS.NLM loads internally from SERVER.EXE unless a different version is placed in the server boot folder (C:\NWSERVER).

You might want to check to see what version your FILESYS.NLM is, and where it's loading from. If your server is patched to SP6, it should be loaded internally unless you've applied a beta patch after the fact.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com