Hello All,
I was wondering if anybody's ever encountered this type of error:
When a few of us upgraded to Windows XP professional, we started
getting chronic "Filename could not be saved; check disk space or write
access" errors when saving to a networked file server. The only
fool-proof workaround is to save to a local drive and then move the
files back later (and they may be "uncorrupted" after that).
Needless to say, the problem is not related to permissions or disk
space! The error is impossible to reproduce, and PTC is
stumped. It seems to happen every day, but we can't predict
when. The two common factors in each occurrence are 1) Seat has
Windows XP operating system, and 2) File is attempting to write to the
file server, which is a Powermac X-Raid system (perhaps an unorthodox
pairing, but I'm not knowledgeable with respect to IT). We have
been using this file server for years with earlier versions of windows,
and never encountered this problem.
I can't believe that we are the only company in the Pro/E universe to have this problem!
Thanks in advance for any help!
Chris
I was wondering if anybody's ever encountered this type of error:
When a few of us upgraded to Windows XP professional, we started
getting chronic "Filename could not be saved; check disk space or write
access" errors when saving to a networked file server. The only
fool-proof workaround is to save to a local drive and then move the
files back later (and they may be "uncorrupted" after that).
Needless to say, the problem is not related to permissions or disk
space! The error is impossible to reproduce, and PTC is
stumped. It seems to happen every day, but we can't predict
when. The two common factors in each occurrence are 1) Seat has
Windows XP operating system, and 2) File is attempting to write to the
file server, which is a Powermac X-Raid system (perhaps an unorthodox
pairing, but I'm not knowledgeable with respect to IT). We have
been using this file server for years with earlier versions of windows,
and never encountered this problem.
I can't believe that we are the only company in the Pro/E universe to have this problem!
Thanks in advance for any help!
Chris