I have a user who gets invalid file handle copying files to a Netware server. Not all the time, but most of the time. Does not seem to be related to the file type. Even .txt files can produce the error. My office W7 PC does not get the error, so it seems a W7 tweak on the user's laptop should fix it. In researching this problem, people have reported this error copying files between W7 and Mac OS X. That fix was a OS X tweak. Seems to be related to the metadata associated with the file. Any ideas?Jay

Hi, Thanks for posting in Microsoft TechNet forums. This issue may happen if the file owns extended attributes. To work around this problem, I suggest you copying the file using command: Copy [source path] [destination path] Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, I also have this occasional problem on my Win7 Enterprise laptop and only found this thread after rebooting which solved the problem (at least temporarily) so haven't had a chance to test the command line but I will get back after I have. Thoughts are though that if extended file attributes are the cause then a reeboot shouldn't fix it should it? FYI: I also have Bitlocker enabled! Regards. Bill.

Bill218a wrote: Hi, I also have this occasional problem on my Win7 Enterprise laptop and only found this thread after rebooting which solved the problem (at least temporarily) so haven't had a chance to test the command line but I will get back after I have. Thoughts are though that if extended file attributes are the cause then a reeboot shouldn't fix it should it? FYI: I also have Bitlocker enabled! Regards. Bill. Do you have the same problem as the OP, who is copying to Netware filesystems? In this case it is essential how you access the Netware filesystem and what server type is holding the files. If you access real Netware via Novell Client 2 you should go at least to Novell Client 2 SP1 IR4, because all other clients have problems. And I am not sure if this latest one did solve all issues for 64-bit versions of WIN7. On the server side you should be at least at NW 6.5 SP8, especially NW 5.1 and older (=more than 12 years old), has problems with newer features like 64-bit etc. If you are not using Novell Client and accessing Netware servers via Windows client (CIFS access) there are problems and that is in my opinion simply not working as it should. If you access OES Linux Netware files via Windows client, you should not have issues if you are using SAMBA and are up to date with patches. If the server runs CIFS instead of SAMBA, there can be problems - but they would be seen on all PCs on the network. But reboot or logoff/logout and relogon/login solves those problems by releasing all open file handles. If you are accessing OES Linux Netware files via Novell Client, the situation is the same as for Netware. Wolfgang

Yes, sorry I should have said. Looks very similar to the OP. I'm copying from Win7 Enterprise Desktop to Novell 6.5 SP7 (??) servers with NSS file system. We will look at SP8 but are migrating away from Novell over the next few months so really don't want to spend too much time on that if we can avoid it. I am running Novell Client 32 SP1 but don't know how to determin the Interim Release level? Does this help? Regards. Bill.

Bill218a wrote: Yes, sorry I should have said. Looks very similar to the OP. I'm copying from Win7 Enterprise Desktop to Novell 6.5 SP7 (??) servers with NSS file system. We will look at SP8 but are migrating away from Novell over the next few months so really don't want to spend too much time on that if we can avoid it. I am running Novell Client 32 SP1 but don't know how to determin the Interim Release level? Does this help? Regards. Bill.   If you look at properties of Novell Client the first "Client" tab shows the product name - if you are at IR4 you should see something like: "Novell Client 2 SP1 for Windows 7 (IR4)" Wolfgang

Ah, that's why I didn't know where it was! Mine just says "Novell Client 2 SP1 for Windows 7" I'll get the techies to locate the IR's and see how it goes and let you know. Trouble is the problem is intermittent (not happening right now) so I might not get back quickly. Thanks for your help. Bill

Bill218a wrote: Ah, that's why I didn't know where it was! Mine just says "Novell Client 2 SP1 for Windows 7" I'll get the techies to locate the IR's and see how it goes and let you know. Trouble is the problem is intermittent (not happening right now) so I might not get back quickly. Thanks for your help. Bill   You can download IR4 of Novell Client2 SP1 for Windows 7 here: http://download.novell.com/Download?buildid=uRcQqWnz4kI~ Wolfgang

Its in place and looking good - but it was intermittent so will post back in a few days if still ok. Note that we are still at Novell 6.5 SP7 on the server. Regards. Bill.

Just to confirm that I have not had the problem since going to IR4. Thanks for the help.

Bill218a wrote: Just to confirm that I have not had the problem since going to IR4. Thanks for the help. Ok glad your problem is solved. Wolfgang