Newbie with TeamWork Problems!!

[Anonymous]

I apologize up front if this issue has been covered in the forum archives.

We are a small firm of three and have purchased AC 10 only three months ago.

We are having problems with Team Work. As we create a project to share (PLP) and each member saves and creates their respective (PLC) files, upon executing send/receive we receive messages that it cannot read the teamwork administration file. A second warning directs us to find (ADM) file manually, which doesn't work.

We are a new OSX firm with (2) 2.33 GHz Intel Core 2 Duo Mac Book Pro and (2) Mac Books networked to a 500 GB LaCie network hard drive, where the files reside.

The other weird thing is that while all of our individual PLC files are accessible, the original PLN appears corrupt as we receive a warning that the "plan file cant be read"

Please HELP!! we are sinking fast!!

[Anonymous]

My only guess is that there is some problem serving the files from the Lacie drive. I've never used NAS myself so I don't know any specifics. You could try sharing the file from one of the MacBooks. If that solves the problem you should consider getting a proper computer to act as file server. In your case an iMac or Mini would probably do in the short run (limited to 10 users on a peer to peer network).

[Anonymous]

Thanks for the reply. I have tried sharing the file from one of our Macbooks and we continue to get messages that the PLP file can't be found or adm file can't be read.

I have created a brand new test file and have recieved the exact same messages!

This has become extremely fustrating!!

No software package should be this difficult!!

If there are any other sugguestions out there I would appreciate it. I am starting to think I bought the wrong BIM software package!

[Anonymous]

I have never seen or heard of the problem you describe (in over 10 years of using teamwork) so I have to wonder if there is something you may be doing incorrectly - though the process is so simple this is hard to imagine.

I still think it may be a networking issue. The "file cannot be read" comes up for me when I disconnect from and then reconnect to a Windows network when running OSX on my MacBook Pro.

For a test try excluding the network altogether by sharing the file and then signing into it locally on a single, unconnected machine. If that works try two machines networked by Firewire. If that works then we know there must be some problem with the ethernet setup.

[TomWaltz]

What are the user permissions on the file, and more importantly, what are the users' umask settings?

It's possible that everyone is saving files that no one else can read.

[Aaron Bourgoin]

The problem rests with file permissions. I don't know all the reasons why, but here's what you have to do.

Until it starts creating Backups, the project consists of 3 files:

project.PLP
Project.adm
Project.txt

Do a 'Get Info' on these files at the machine where you shared the project. Change all of the permissions - down at the bottom to 'Read & Write'

If you receive a message stating either that you 'can't back up the file' or 'write Teamwork notes', you'll have to do this to the 'Project Backups' folder.

Sorry I'm not at a Mac right now and so can't post a screen shot. Hope this is clear.

Am waiting for a visit from the network guru at the office where this problem has been ocurring to see if he can shed light on a the problem and help solve future ocurrences.

[Anonymous]

Gentlemen Thanks for the support!!!!

Question, Tom you referred to user permission on the file and user "mask" setting. Please clarify

[TomWaltz]

The umask is a users' default permissions settings for saving files.

By default, Mac saves files with a permission that allows themselves to read/write and others to see, but neither read nor write.

As Aaron said, if you check the user permissions on a file(with Get Info), look at the Ownership and Permissions. You want everything to say "Read & Write". Anything else will mess with Teamwork pretty badly.

[Anonymous]

Gentlemen THANKS!!!

THIS ROUND OF DRINKS ARE ON ME!!!!!

The issue was a permission problem on OSX. Once we addressed the permission issue on all machines the Teamwork function has been working as advertised!

[Thomas Holm]

TomWaltz wrote:
The umask is a users' default permissions settings for saving files.

By default, Mac saves files with a permission that allows themselves to read/write and others to see, but neither read nor write.

Tom, if possible, how do you change the default umask setting? Or do you need to check and change permissons each time a user saves a new file to the server?