File is considered damaged when we try to save

[Dan S. Ross]

When some people try to save a document that is opened from a template to our XServe running OS X Server 10.4.7 back to a share on the server they are getting a message that the file is damaged and they can't save.

When they save it to their desktop and then move the file to the share everything is fine.

Any ideas?

[Peter_Truskier@adobeforums.com]

A few questions:


* What version of InDesign are you using?
* What version of Mac OS X are you running on the clients, and what type
of machines are they?
* Is the shared XServe volume on an XSan, or a local (to the server) disk?
* Can we assume that the shared volume is being mounted as AFP (not SMB
or NFS) on the client?
* What might be different about the machines or user accounts that have
this problem as compared to those that don't?

[Dan S. Ross]

A few answers:

1) 4.0.4
2) 10.4.7 predominantly G4's with Gigabit although we do have a few G5s
3) Local server drive
4) What might be different? Older models of G4? Um.....other than that I'm not sure.

[Peter_Truskier@adobeforums.com]

Hmm...

I'm kind of grasping at straws here, but how about the question of AFP/SMB/NFS? The reason I ask is that I've experienced Mac OS X (client) seemingly developing a mind of its own about what protocol to use in the case of a server that is sharing a volume with more than one protocol. One day, one of my machines up and decided to start using SMB when mounting one of my server volumes - not sure why.

How do these volume(s) get mounted on the users' machines - automatically, manually, via an alias? Just to be sure, you can see the protocol in use if you select the volume in the Finder on a client machine, and "Get Info."

Is the problem machine-related, or user-related? Are the users having problems different than those that are not in terms of their Admin privileges?

[Buko@adobeforums.com]

can you save locally?

[Peter_Truskier@adobeforums.com]

can you save locally?




Did you read the original message, Buko?

[Dan S. Ross]

I checked the mounted drives and they are afp.

Wouldn't it be a bit odd for several user accounts to experience the same problem?

I wonder if it could be a network issue? Maybe a bad ethernet cord that only a portion of the building is putting traffic through?

[Peter_Truskier@adobeforums.com]

I wonder if it could be a network issue?




I think that's certainly a possibility. If that's it, then it should be machine-based, not account-based. Have you seen any case in which two different accounts behave differently on the same machine?

What sort of network analysis tools do you have access to? If the problem is sufficiently predictable on one machine, could you move it to a different (non-problematic) network connection?

[Dan S. Ross]

Some days the problem seems to be there, other days it doesn't. But it DOES seem to always happen on one end of the room.

I checked permissions and those seem to be correct.

I have not tried different accounts. That will be my next step.

[Richard_Sohanchyk@adobeforums.com]

Is there a common router the affected machines share at the end of the room? If so, have you tried resetting the router by turning off and on again?

[Peter_Truskier@adobeforums.com]

But it DOES seem to always happen on one end of the room.




That's pretty interesting. Does that end of the room have any other networkish problems - InDesign, Photoshop, Illustrator, other apps?

[Dan S. Ross]

They are all predominantly on the same gigabit router that I and others not having the problem are on.

That's kind of what worries me. I'm worried that it's some wire in a wall somewhere.

[Buko@adobeforums.com]

I guess I missed the save local.

I would say its a network problem.

[JohnO@adobeforums.com]

Check the cable between the computer and the wall. They do go bad, by
getting kicked or wiggled too much or whatever. They're $5 online, so just
buy new ones...get CAT6 if they aren't too expensive. Buy another one that's
40 feet long and run the 'problem' computer to another jack in the wall.

If that doesn't work, call a network tech, one who has a cable certification
tester. That tool can pinpoint problems to within a foot or two.

-John O

[Richard_Sohanchyk@adobeforums.com]

You can get a box of 5 or 10 on ebay for the price of one at CompUSA.

[Eric_@_MCA@adobeforums.com]

Another possible way to test--make 50gb or so disk image, with checksum enabled. Cmd-drag it from the computer to the server and then cmd-drag it back from the server to your computer. Mount it and see if the checksum is still valid...

Rinse, lather and repeat about 10 times and if the checksums are okay, you can probably rule out network issues. :)

Or you could just ask the IT guy to log into the switches (assuming they're managed switches) and see if there are a lot of bad packets coming from the those computers.

[Brian_Hinther@adobeforums.com]

We're having the exact same problem with InDesign. We've tried hooking up directly to the switches with new cable, but didn't see an improvement. (This is with InDesign 4.0.4 using OS 10.4.7 on a Windows 2003 server.)

Our prepress people are also having trouble saving over the network with Photoshop CS2. They don't get a message; they just get half a file when they reopen.

[Peter_Truskier@adobeforums.com]

Brian,

Is the Windows share being mounted as AFP (with MS Services for Macintosh), or as SMB?

There are known issues with Mac OS X and AFP 2.x servers. Microsoft SFM is AFP 2, and it doesn't seem that MS has any plans to upgrade it to AFP 3. I think Tiger is even less tolerant of these servers than Panther was. There are third-party AFP 3 servers for WIndows (e.g., Group Logic's ExtremeZ•IP and Cyan Software's Mac Server IP) but they are not terribly cheap.

What version of Photoshop are you using? We had one client with similar problems (though they were already using ExtremeZ•IP), and upgrading from Photoshop 9.0 to 9.0.1 and from 10.4.6 to 10.4.7 seems to have solved the problem.

On the other hand, SMB mounts also pose certain problems. (You can see a description at <http://www.helios.de/products/FileTest.phtml> about half way down the page.)

Also, note that Adobe does not support network file systems for Photoshop (AFAIK).

[Brian_Hinther@adobeforums.com]

Thanks, Peter, and everyone else. I passed along your input to one of our IT guys who made changes to my connection and I can now save over the network. I'm not sure exactly what he did, but I'll try to find out in case it can help anyone else. Thanks again!

[Peter_Truskier@adobeforums.com]

I'm not sure exactly what he did, but I'll try to find out in case it
can help anyone else.




Brian, that's great! Please do let us know if you can so we can all (try to) remember it the next time this comes up...