Cannot save to server
 

I teach in a lab using Leopard 10.5.5 and I'm using Managed User accounts for students. Students save their files to a network account (Novell running Apple services.) As I was testing today in preparation for lessons next quarter, I discovered that I cannot save files to the server when I am using a Manager account. I get the error: The document "whatever" could not be saved as "whatever". You do not have appropriate access privileges. When I use the computer's Admin account I can save.

Using the computer's student account I can save to the computer's hard drive (not my chosen methodology but an option if need be). Obviously OG is attempting to save something to a directory that the managed account doesn't have permissions to but I cannot figure out what/where. At first I thought it might be something to do with the student/teacher Novell account but using the student computer account and my Novell admin account I still could not save. So the issue seems to be something being saved to the local computer and not the server at all.

A rough guess would be that OmniGraffle is attempting to save the file out as a package, which may not be understood by whatever's running the server.

In the Document Inspector there are settings to force a file to save as a "flat", monolithic file type, or as a package or wrapper, that sort of thing.

Hope that helps,

Won't Save
 

I'll give that a try, thanks.

[QUOTE=Joel;48121]A rough guess would be that OmniGraffle is attempting to save the file out as a package, which may not be understood by whatever's running the server.

In the Document Inspector there are settings to force a file to save as a "flat", monolithic file type, or as a package or wrapper, that sort of thing.

Hope that helps,[/QUOTE]

That didn't solve it and now when I look at your answer again with fresh eyes I think you assumed what I originally did - that the problem lie with the server. I don't think that's it. Remember, using the computer's admin account I can save to the server whether I log onto the server using my teacher account, my student test account (access to fewer shares) or my Novell admin account. Saving to the server isn't the issue - saving under a Leopard managed account is the sticking point.

You did verify that [b]other[/b] applications can successfully save when OmniGraffle cannot, right? How about OmniOutliner, which also saves packages in at least some cases? (You can download a trial copy for free if the school doesn't have a license) Obviously, testing a non-Omni, non-package-writing application (TextEdit seems like a fine choice) to make sure that the problem isn't seen there would help to show that the problem is one that Joel should be chasing. I apologize if you've already done the obvious and assumed we would know you did so before asking...

[QUOTE=whpalmer4;48165]You did verify that [b]other[/b] applications can successfully save when OmniGraffle cannot, right? How about OmniOutliner, which also saves packages in at least some cases? (You can download a trial copy for free if the school doesn't have a license) Obviously, testing a non-Omni, non-package-writing application (TextEdit seems like a fine choice) to make sure that the problem isn't seen there would help to show that the problem is one that Joel should be chasing. I apologize if you've already done the obvious and assumed we would know you did so before asking...[/QUOTE]

Since I've done tech support I understand why you asked - Pages, Word, Teachtext, DrScheme, BlueJ, Photoshop, Photoshop Elements are just some of the programs we've used successfully since the start of the school year.

The issue is new to Leopard/OmniGraffle 5. Last year we were using Tiger and I hadn't yet upgraded to O5 and I had no trouble saving files using my managed user account. Naturally I've thrown OG4 away and don't have any computers with Tiger to isolate one from the other.

Just got the newest version of OO downloaded and with the Managed account I get the error "The document "test.oo3" could not be saved as "test". For the heck of it I changed the document name to test.oo3 but that did nothing other than change the error message.

At this point I'm idly wondering if there's some sort of permissions issue going on. No idea why it would differ between different applications, but something's amiss.

[QUOTE=davidwb;48181]Since I've done tech support I understand why you asked - Pages, Word, Teachtext, DrScheme, BlueJ, Photoshop, Photoshop Elements are just some of the programs we've used successfully since the start of the school year.

The issue is new to Leopard/OmniGraffle 5. Last year we were using Tiger and I hadn't yet upgraded to O5 and I had no trouble saving files using my managed user account. Naturally I've thrown OG4 away and don't have any computers with Tiger to isolate one from the other.

Just got the newest version of OO downloaded and with the Managed account I get the error "The document "test.oo3" could not be saved as "test". For the heck of it I changed the document name to test.oo3 but that did nothing other than change the error message.[/QUOTE]

Ah, good man :-)

You can download a trial copy of OG4 (which should be sufficient to see if it has this same problem) from [URL="http://www.omnigroup.com/ftp/pub/software/MacOSX/10.4/"]http://www.omnigroup.com/ftp/pub/software/MacOSX/10.4/[/URL]. I suppose it is possible that Omni has caused this bug with a framework change (thus causing both OG5 and OO3.7 to fail) and that they might have done so just long enough ago to make the copy of OG4.2 you can download there fail but not long enough ago to make whatever OG4 version you previously had fail, thus obfuscating matters a bit more rather than providing clarity, but Joel seems like a clever enough chap, up for a bit of a challenge now and then :-)

Hmm, another possibility might be the Quick Look preview, which is a new feature to OmniGraffle 5, so you may want to experiment with turning that preview off.

Downloading OG 4 now and I'll try out turning off quicklook. Yep - this has me flummoxed too. After getting the new computers in I quickly configured one, got my software on it, and began testing. (I've come to both dread and look forward to new computers.) At the time OG was on my want list but hadn't made my must have list. (Sorry, had to be realistic and I could make do with other software that had serious suckage issues but didn't have a choice about things like Office and Photoshop.)

So when I got approval for OG last week I decided I'd better see if there were any issues with the network and managed accounts. Some programs do have serious issues...I won't mention any names...MS. So I was surprised to find a save issue.

Still No Saving
 

Neither unchecking QuickLook nor OG4 did the trick. Must be something involving Managed User on Leopard. I've seen saving to server issues mentioned on Apple's discussion group but nothing like this.

You mentioned in one of the earlier posts that you could save successfully to the local disk. What happens if you do that, then copy the file to the server? Any errors? What about if you attempt to edit a pre-existing OG file residing on the server?

I'm still trying to tease out whether it is something about the file that causes the problem, or the way in which it is created/written...it's an interesting puzzle!

[QUOTE=whpalmer4;48230]You mentioned in one of the earlier posts that you could save successfully to the local disk. What happens if you do that, then copy the file to the server? Any errors? What about if you attempt to edit a pre-existing OG file residing on the server?

I'm still trying to tease out whether it is something about the file that causes the problem, or the way in which it is created/written...it's an interesting puzzle![/QUOTE]

Copying the file after saving it locally works fine - that is my fallback position. I just hate telling students all semester long to be sure to save to their drive and then say, okay for OG you save to the computer and then copy to your drive. That way lies madness as my programming mentor used to say.

Yeah, it is an interesting puzzle....interesting puzzles (and irrational supervisors) is what made me leave IT for teaching <grin>

Thought I would offer a little perspective in case you are still having this issue. I just tested saving from OG 5 to a AFP share point on our 10.5.4 Server and had no errors.

To me this would mean the issue is in the configuration of your server combined with how OG saves files.

What protocol does this share use?

I have the same issue. Copying my company server from my hard drive works fine, however directly saving results in an error. Of all my apps only omnigraffle seems to exhibit this behavior.

I never understood it, but the work around (for me) was easy.

[QUOTE=Haven;48439]Thought I would offer a little perspective in case you are still having this issue. I just tested saving from OG 5 to a AFP share point on our 10.5.4 Server and had no errors.

To me this would mean the issue is in the configuration of your server combined with how OG saves files.

What protocol does this share use?[/QUOTE]

We are using Novell with AppleShare services, but that is irrelevant. The student's [B]Novell[/B] account it totally separate from the [B]Mac User Account[/B]. In other words, the computers have three accounts: a standard account used by teachers which allows them to access all programs, managed account used by students which restricts them to certain programs, and my admin account.

Privileges from this account have no bearing on Novell access. To whit, using my Novell account, I can save an OG file if I log on to the computer using my admin account. I cannot save if I log onto the computer using my student test account. (Interestingly, I cannot recall if I tested the teacher account or what the result was if I did.) If I use my Novell student account I can save if I log onto the computer with my admin account but not my student account.

It seems to me that OG must be attempting to save a temporary file of some type in a location that the managed account has no priveleges to.