07-19-2012 06:17 AM
The title pretty much says it all. I have to turn file guard off to get to my proteted files because it won't open even with the correct administrator name and password. This started happening a couple of days ago and it worked fine before then.
Solved! Go to Solution.
07-19-2012 11:05 AM
So sorry for the trouble. To help us troubleshoot further:
1. Download GatherSymantecInfo.zip from:
2. Expand GatherSymantecInfo.zip using Apple’s archive utility (other programs may not expand with proper permissions):
3. In GatherSymantecInfo folder, double-click GatherSymantecInfo.command.
4. When prompted, enter your computer user password.
5. Rename the generated SymantecInfo.zip to SymantecInfo.log.
6. Attach SymantecInfo.log to your reply.
07-24-2012 01:50 PM
Sorry for the problem. Can you explain with a little more detail what you are trying to do, and what happens? For example, how are you trying to open the documents, what kind of files are you trying to open, and what happens (any errors?) when you try to open the protected file?
07-26-2012 05:06 AM
I normally have File Guard enabled. Normally I can open a guarded file with my administrator name and password. However, it now gives me an error message stating the administrator name and password are incorrect, even though I know they are. (I'd send you a screen capture, but apparently this board doesn't allow PDFs.
Now I just enable File Guard until I need a protected file, disable it to open the file, and re-enable it when I'm done with the file.
I wonder if it has to do with moving files to a new folder, since File Guard doesn't work well with that either.
07-26-2012 06:10 PM
This may be a problem with File Guard populating the user name field with the full name instead of the short (aka, posix) user name. To determine the short user name:
1. Open /Applications/Utilities/Terminal.app
3. Press return
Your short (posix) user name will be shown by the whoami command. Use that name when File Guard prompts for your admin password. Please let us know if this helps.
07-28-2012 11:45 PM - edited 07-28-2012 11:47 PM
Sorry all. We've identified this as a problem that we introduced in NIS 5.3 to fix an issue in Mountain Lion. While fixing the issue in Mountain Lion, we broke File Guard in other ways. Sorry about that.
Please let us know if Corey's solution (above) works for you. This is the issue that we have identified; if there are others we'll want to know ASAP.
Sorry about the problem.
07-31-2012 04:26 AM
Using the Posix name did allow me to open the files. Guess I'll use this workaround until I'm sure my current apps will play nicely with Mountain Lion OS X.
Thanks for your help.