Delete inhibit gets set when trying to delete RO files with Client2 SP3 IR5

[Anonymous_User]

All
I have run into what appears to be a bug in Client 2 SP3, all
releases. If I attempt to delete a Read Only file with a Win7 machine
(32 or 64 bit) running that client, it fails and after that point the
Delete Inhibit attribute ends up set on the file. Once DI is set it
becomes a real pain to get rid of the file, really miss the old FLAG
command line utility here. It gets real cumbersome when a whole
directory tree of files gets copied by some automatic archive process on
a W7 box, as the same happens to directories also. I have tried this
with plain SP3, IR3 and IR5 all appear to behave the same. This does
not happen with XP or W2K clients running the client for those. The
server I am running these tests against is 6.5 SP 8 fully patched.
Client file caching is enabled on the client boxes I have tested this
with and must remain so as it being enabled fixes another bug that had
been a big pain for some time.

Has anyone else run into this situation and more important, does
anyone have a solution?

Gus

[Raffke]

I can confirm for IR6 and IR7a - someone was reporting, it started with IR5 [1] and I definitely know it has not been from the beginning.
Is it true, this only applies to Netware server? Can anyone check with OES2/Linux please?

[1] https://groups.google.com/d/msg/de.comp.sys.novell/P7BKw7T2L6U/6UhSZQClaGcJ (German)

[laurabuckley]

Hi,

I am unable to duplicate this issue against an OES11SP1 server. I, unfortunately, don't have a NetWare server to test this against.

Cheers,

[Raffke]

Could this problem arise by the following change in IR5?

"Preserve existing Novell-specific file and directory attributes that do not translate into Windows platform attributes. (Bug 747049)"

[laurabuckley]

Hi,

I am not sure. I'm doing further testing with the IR7a client.

Cheers,

[Raffke]

Laura, thanks for trying!
But where did you set and unset the Readonly flag? (and which client are you running?)

I found it working, if you set/unset Readonly on the "Novell Info" tab (where you see the "Delete Inhibit" and "Rename Inhibit" flags).
But if you do it with the Windows internal "General" tab:
- open file properties "General", set "Readonly", close with "OK"
- open file properties again, on "Novell Info" find the Di checked, Ri unchecked and both Flags grayed out
(expected: both checked and grayed out)
- change back to "General", unset "Readonly" and again close with "OK"
- open file properties again, on "Novell Info" find the Di still checked but not grayed out
(expected: both unchecked)

[laurabuckley]

Hi,

I am using IR7a on Windows 7.

I am finding some anomalies with how the Novell Client is handling the setting of Novell Attributes on a file. I am getting some more folk to run further tests and I'll see if I can find out anything from Novell.

Note that if you use iManager to set the file attributes they apply/work correctly. Perhaps use iManager whilst we try get to the bottom of this.

Give me a day or two to get back to you.

Cheers,

[Raffke]

Okay, I do have a workaround, because it works as expected if you erase the Readonly flag on the "Novell Info" tab.
But users do forget about this and then MS Excel keeps copies of modified files, because the Di attribute is being kept on the temporary file.


Some more links that seem related to this problem:
https://www.novell.com/support/kb/doc.php?id=7007397
https://www.novell.com/support/kb/doc.php?id=7007201
https://forums.novell.com/showthread.php/466300-Novell-Client-2-SP3-for-Windows-8

In the meantime I checked the behaviour on Win2003 Server with 4.91 client. Everything works fine in this case. Di and Ri is being unset when you remove Readonly on the "General" tab as well as using "ATTRIB -r".

[mrosen]

On 21.05.2014 10:06, Raffke wrote:
>
> Could this problem arise by the following change in IR5?
>
> "Preserve existing Novell-specific file and directory attributes that do
> not translate into Windows platform attributes. (Bug 747049)"

Yes, and yes, it's known, and yes, it's Netware only.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

[Raffke]

mrosen;2319973 wrote:
[...] it's Netware only.

I'm happy to confirm it has been fixed in IR8 though:

https://www.novell.com/support/kb/doc.php?id=7015328&path=780&number=f.1
https://download.novell.com/Download?buildid=4bBKN2Ek76Q~