Hrrmmmm... I take it the SAN is actually providing CIFS storage?
How long are the file/directory path specifications for the files being copied? If they're greater than approximately 250 characters (x:\reall\long\directory\andfilename.rpt), the Windows file system doesn't like it (the Win32 API governs this, and character encoding, etc., play some role in exactly how many characters you can get away with). Robocopy used the Windows Native API, which allows for ridiculously long path names - something like 32k See, for instance, this: http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx Is it perhaps a limitation similar to that? Kurt On Tue, Mar 18, 2014 at 7:35 AM, David Lum <[email protected]> wrote: > Over the weekend there was an upgrade to our SAN systems. We now have this > bizarre issue where Crystal Reports .RPT files are unable to be copied from > a PC to the SAN shares via Windows 64-bit GUI. > > > > Renaming an Excel file to .RPT: works > > Use a 32-bit system to copy the file: works > > Any other file (PDF, XLS, etc.): works > > Using XCOPY on a 64-bit machine: works > > > > It only fails when using the GUI on a 64-bit system, and it’s only on > these Crystal Reports .RPT files. If I open one of these RPT files on a > 64-bit machine with Notepad, change one byte, save it to the PC I can then > copy it over. > > > > Ideas? > > > > > > > > *David Lum* > > *Network System Admin, Information Services* > > *office* 503-265-4728 | modahealth.com <http://www.modahealth.com/> > > *I’m excited to announce that ODS Health is now Moda Health. **Please > make a note of my new email address**, [email protected] > <[email protected]>, so we can stay connected.* > > This message is intended for the sole use of the individual and entity to > whom it is addressed, and may contain information that is privileged, > confidential and exempt from disclosure under applicable law. If you are > not the intended addressee, nor authorized to receive for the intended > addressee, you are hereby notified that you may not use, copy, disclose or > distribute to anyone the message or any information contained in the > message. If you have received this message in error, please immediately > advise the sender by reply email and delete the message. > > > > >
<<inline: image001.jpg>>
