Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Legacy Products > 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac)
Register FAQ Today's Posts Search

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 07-15-2008, 06:51 AM
Dan Rose Dan Rose is offline
Member
 
Join Date: Jul 2008
Posts: 7
Default Workspace Access Problem

Hi,

I've got eight identical systems with OS 10.5.4 and Pro Tools LE 7.4.2 on Mac Minis with 003s and external Firewire drives. All were working fine for one day, and now, none can record. Starting a new session or opening an old session brings up the error that the session needs to be on a record volume, and opening the workspace browser (to set the volume to R) results in a blank browser and an error in the task window that I do not have access to the workspace.

I've tried this with the managed user accounts I'm using, I've tried it with the Administrator account, I've tried it with a brand new Administrator account. All of them fail. The drives are all Mac OS Extended (Journaled), and the external drive is owned by the user account, who has full read and write access to everything. I've also repaired permissions on all the drives. It's not a permissions problem.
Incidentally, in trying to determine if it was a permissions problem, I enabled the root user account, figuring that if anyone has access, root does... But Pro Tools can't run as root - I get a message saying it requires an Administrator account. Come on, Digi, who's more of an administrator than root?

So, what's up? Any guesses?
I've got one other clue - these were upgrades from older systems on 10.3.9 and Pro Tools 6.7. At least one new system worked fine with a _new_ session, but after opening an old session, the workspace is now "locked" and we can't start any new ones.
I've also tried deleting the Digidesign Database folder off each drive. No help.

Digi - where is the "workspace"? Is it just /Volumes/? Would it help if I chmod'd Volumes to give anyone r+w+x? I don't want to, that's idiotic, but if it will help, I will.
Or, is the "workspace" a database stored someplace else that's maybe inheriting an access control list from a parent folder?

Urgent reply needed... I've got 8 rooms offline.

Thanks,
-Dan
Reply With Quote
  #2  
Old 07-15-2008, 09:07 AM
Craig F Craig F is offline
Member
 
Join Date: Aug 2000
Location: Portland, OR
Posts: 12,606
Default Re: Workspace Access Problem

what are the OS permissions to the drives?
__________________
...

"Fly High Freeee click psst tic tic tic click Bird Yeah!" - dave911


Thank you,

Craig
Reply With Quote
  #3  
Old 07-15-2008, 09:16 AM
Dan Rose Dan Rose is offline
Member
 
Join Date: Jul 2008
Posts: 7
Default Re: Workspace Access Problem

The firewire drives are owned by the user (in this case "production"), who is a member (the only member) of the group "production", and the defaults are set - rwxrwxr-x.
Nonetheless, the drives are _also_ set to "Ignore ownership on this drive".
The system drive has the default ownership - root, admin, rwxrwxr-x.

Keep in mind that I get the same problem with the Administrator account, who has full read-write-execute on the system drive.

The /Volumes/ folder is owned by root and has permissions rwxrwxrwt (with t being the sticky bit)

As an added wrinkle, if I disconnect the Firewire drive, I _still_ can't browse the workspace.
I really don't want to try changing ownership of /Volumes/, 'cause that's insane, but I can give it a shot.
Reply With Quote
  #4  
Old 07-15-2008, 09:39 AM
Slim Shady Slim Shady is offline
Member
 
Join Date: Feb 2000
Location: Los Angeles, CA
Posts: 7,527
Default Re: Workspace Access Problem

How about just deleting the volumes folder, then see what permissions it has when PT generates a new one.
Reply With Quote
  #5  
Old 07-15-2008, 09:49 AM
Dan Rose Dan Rose is offline
Member
 
Join Date: Jul 2008
Posts: 7
Default Re: Workspace Access Problem

You can't delete /Volumes/ - it's the directory that the OS stores information about all drives.
Reply With Quote
  #6  
Old 07-22-2008, 07:38 AM
Dan Rose Dan Rose is offline
Member
 
Join Date: Jul 2008
Posts: 7
Lightbulb Solved

Figured out the problem. Not sure why it started, but just in case others run into it:
The folder Macintosh HD/Library/Application Support/Digidesign/ and everything in it were owned by "system", and members of the group "unknown" had read-write access to it. It was then locked to everyone else. This is what caused the "you don't have privileges to access the workspace" problem.

There are two ways to fix it:
A) Run the recent 7.4.2 patch. In spite of it supposedly being to fix an inadvertent "pre-release" dialog box, it also runs a script that modifies that folder to make it read-write accessible to everyone, whether a user or not. This works, but is a bad piece of code, because it creates a security hole in your Library folder that non-local users have full access to.
B) Open the terminal while logged into an Administrator account, and type in:
Code:
sudo chown -R :staff /Library/Application\ Support/Digidesign/
This makes the folder accessible to all Administrators (they're part of group "staff") and non-Administrators (regular "staff" users).

If you just want to examine the folder to see if you need to fix this, open the Library folder and the Application Support folder, and get info on the Digidesign folder, then look in the privileges and ownership tab. You should have read-write access. If you don't, this could eventually cause a problem if you need to change a drive from transfer to record at some point.

Disclaimer: The terminal is very powerful, and typing the wrong thing could cause unintentional effects. Use at your own risk. The above code has been applied on eight machines with no ill effects, but your mileage may vary. I don't have any plugins installed except Soundsoap and the Ignition Pack. "sudo" allows an administrator to make system changes, "chown" changes ownership, ":staff" changes the group ownership, and "-R" makes the command recursive and apply the same change to everything within the folder, and the backwards slash in "/Application\ Support/" is so that the terminal reads the space without assuming it's the end of the command. Google can verify all of the above information.
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Workspace cannot access HD Mwibe macOS 3 05-30-2011 01:26 PM
Can't access Sample folders in Workspace marcuspng 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 0 10-20-2010 08:43 PM
Can't access all files/samples via workspace zv yoda 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 1 06-03-2009 04:53 AM
HELP: "workspace" browser-I don't have "appropriate access" bongish 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 5 04-03-2009 12:24 PM
Cannot Access Networked Servers Through Workspace eth1979 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 1 10-21-2006 03:03 PM


All times are GMT -7. The time now is 09:34 PM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com