J
jeffleeson
Hello everyone!
I've researched this for the past several days, but I've been unable
to find reports of this in the past.
I work in an animation company, and we're in the middle of production
of a couple new shows. We've never had any problems in this area in
the past, so I'm a little baffled as to why it's happening now. We're
a mainly PC company, with our file servers all running Windows 2003
Server on Dell servers. Our production people are all on Macs, using
both iMac G5's and Intel iMacs, all running 10.4.9 with Office 2004,
updated to 11.3.4.
The problem is working with Excel documents that are saved to the
server. The problem we're seeing is that when we open an Excel file
from the Mac, then do a Save As and save the file locally to the
computer, once you close the file, go to the copy you saved locally,
and try to open it. It doesn't open. It flashes like it's trying to
open it, but nothing happens. I've discovered the problem is that the
file has somehow become corrupted in the saving process, because if I
send the file to a PC and open it in Excel (and I've used both 2003
and 2007 to open it), it says the file was corrupted, and asks if I
want to try to recover it. It recovers the data only, and loses all
formating and formulas. When compared side by side, the file info
indicates the file on the server is identical, other than modified
date, to the file stored locally. They're the exact same size,
everything.
There's no problem saving the file back to the server, or doing a Save
As to another folder on the server. The same is true when the file is
local. The problem only occurs when the file is saved on the server,
and we try to do a Save As to the local machine. I've been able to
replicate this on several machines. I've tried creating a fresh user
and testing this, and it worked fine the FIRST time I did it. It
saved it locally fine, and reopened without any problems, but when I
tried it a second time, it failed like before.
All computers are connecting to the Windows server using SMB. I
haven't tested using AFP, because it's just not an option for us (I've
made a concerted effort to get everyone to switch to using SMB).
I've heard of problems with people saving files back to their
networked home folders, but all our users have local profiles, and
besides, they're not saving back to the share! This has honestly got
me quite baffled.
Any help would be appreciated!
Thanks,
Jeff Leeson
Systems Support Specialist
DIC Entertainment
I've researched this for the past several days, but I've been unable
to find reports of this in the past.
I work in an animation company, and we're in the middle of production
of a couple new shows. We've never had any problems in this area in
the past, so I'm a little baffled as to why it's happening now. We're
a mainly PC company, with our file servers all running Windows 2003
Server on Dell servers. Our production people are all on Macs, using
both iMac G5's and Intel iMacs, all running 10.4.9 with Office 2004,
updated to 11.3.4.
The problem is working with Excel documents that are saved to the
server. The problem we're seeing is that when we open an Excel file
from the Mac, then do a Save As and save the file locally to the
computer, once you close the file, go to the copy you saved locally,
and try to open it. It doesn't open. It flashes like it's trying to
open it, but nothing happens. I've discovered the problem is that the
file has somehow become corrupted in the saving process, because if I
send the file to a PC and open it in Excel (and I've used both 2003
and 2007 to open it), it says the file was corrupted, and asks if I
want to try to recover it. It recovers the data only, and loses all
formating and formulas. When compared side by side, the file info
indicates the file on the server is identical, other than modified
date, to the file stored locally. They're the exact same size,
everything.
There's no problem saving the file back to the server, or doing a Save
As to another folder on the server. The same is true when the file is
local. The problem only occurs when the file is saved on the server,
and we try to do a Save As to the local machine. I've been able to
replicate this on several machines. I've tried creating a fresh user
and testing this, and it worked fine the FIRST time I did it. It
saved it locally fine, and reopened without any problems, but when I
tried it a second time, it failed like before.
All computers are connecting to the Windows server using SMB. I
haven't tested using AFP, because it's just not an option for us (I've
made a concerted effort to get everyone to switch to using SMB).
I've heard of problems with people saving files back to their
networked home folders, but all our users have local profiles, and
besides, they're not saving back to the share! This has honestly got
me quite baffled.
Any help would be appreciated!
Thanks,
Jeff Leeson
Systems Support Specialist
DIC Entertainment