Strange behaviour with freehand files after upgrade from 10.2 to 10.4.6 Server (Intel)

[woody]

I’ve been asked for help in an really confusing setup of workgroup with strange file behaviour after an upgrade zo 10.4.

I try to explain as far as I have evaluated till now. It seems that only Freehand Files are affected, but I’m not shure, that’s the most used application there, but other apps, we tested, worked. It’s crazy and I’m banging my head since yesterday evening, so I’ll explain in detail.

[b]Given: [/b]
– PPC Mac, MacOSX 10.2. Stand-Alone-Server for a Workgroup of 5 Persons.
– 2 Volumes: 1 OS-Volume, 1 Data
– 2 Useraccounts, 2 Groups
Useraccount 1: Team,
Useraccount 2: CEO,
2Groups: 1 TeamG, 1 CeoG
User CEO is member of group TeamG and CeoG
– roundbaout: 6 Shares with group TeamG and permissions 777
– 3 shares only for CEO 770
– Only AFP is used, Clients MacOSX 10.3 and 10.4

This worked well for 2 or years now.

[b]Upgrade:[/b] They did an upgrade to 10.4.6 an new Intel-MacPro as Server.

The construction is the same, but runs into different problems:

1.The “connecting to server” – Dialog shows up inaccessible Shares for User “Team” but they are inaccessible. (Not nice, but small problem)

2. If somebody opens a file in the a teamfolder, they can work on it, but when saving the file, the “Save as…”-Dialog appears and they have to save it with a different filename. The file can’t be overwritten. No error Dialog, no error in any log. Instead of that, they can save the file to the desktop and overwrite the file on the share by copying.

Posix permissions are set up correctly, ACL’s are deactivated, Inheriting Permissions instead of POSIX for new Folders is activated.

[b]Reinstalling:[/b] We have reinstalled the Server from scratch (the datavolume wasn’t touched). Then we created the Accounts, Groups and Shares again. POSIX-Permissions(as far as I can see) are setup correctly.

Effect: Problem 1 is solved, Problem 2 is still remaining.

Now the clou: If we copy the whole content of a share to the desktop of a local client, and copy it (as User Team) back to the share (overwriting the existing files) everything works perfectly. THe Users Team and CEO can open the files and save them….

but when the User “CEO” has opened the file, this shows up the same behaviour as before for User “Team” again, they can’t save by overwriting…. In the file permissions nothing changed……

Excuse me for the long explanation, but it’s such crazy and it seems that only the Freehand-Files are affected.

Maybe that we are barking up the wrong, when looking for file permissions, maybe it is a Freehand-Problem. We have deleted e.g. the caches on the Client for any freehand-specific issues, no luck….

Any hints anybody

Thanks

Woody

[woody]

macshome, thanks for your reply.

We have tested different possible solutions now and there is none.

It seems to be a bug in MacOSX Server. They tested with an older version of 10.4 and did an upgrade to 10.4.6 step by step. The system worked until the update to 10.4.6. (7?).
It seems to be an issue with some special apps generating wrong permissions while saving. Because that should be a task of the OS, I guess it must be a bug in the Carbon-API in context with apps that create an new file and delete the old one, instead of overriding the existing files while saving,

The problem here was the Intel-MacPro that wouldn’t run on older Systems, so they now working with a PPC-Mac.

[Author]

Posts