Permissions Problem Leopard PPC Client to 10.3 Server

I am having a problem with creating or copying a file to our 10.3 Server w/RAID. I am only having this problem when I am trying to copy or create a folder from a PowerPC computer running Leopard. This works fine when i am on an intel machine or on a PowerPC running Tiger(10.4). I have installed the latest updates on both the server and the clients. I have tested this on two powerpc's and have the same results. When I try to copy or create a file i get a folder with a little "-" in the corner. I then check the file permissions and it says drwx------ it says the owner is the admin and the group is the correct group I have setup to access. I have tried multiple logins and different users on the computers as well.
In the server tools i have the directory set up to inherit permissions from parent. The parent folder permissions are as follows drwxrwx--- and this is correct. I want the owner and group to have rwx permissions and everyone to have no access.
Is anyone else having these same issues or is there any workarounds.

nobody?

Similar Messages

Problem with socket - Client in C and Server in Java

Hi,
I am building a Java based TCP server socket class in Windows machine. The client is written in C running in Linux.
The client sends data in specified C struct: Eg.
{noformat}struct person {
    int   age;
    float weight;
    int height;
} I am having problem reading it in Java Server. I am using DataInputStream to read byte and trying to decode it in age, float etc. the problem is I can read first two but I cannot properly decode the 'height'.
My question is it possible to directly cast the input stream in corresponding Java object? I guess not but would like to know your ideas.
Is it a good idea to send the struct instead of string?
regards,
rnv

You are perpetrating mistake #1 here. Don't try to send C structs over the wire. The format is dependent on the hardware, the operating system, the compiler, the compiler version, compiler bugs, the #pragmas, and the compiler options in effect. Too many variables. What you should be doing is writing the primitive types to the network, in network byte order, and reading them inJava with the appropriate methods of DataInputStream.

TCP/IP problem: closes on client side, not on server side, can't reconnect!

Hey folks. I have a Java servlet that establishes a TCP/IP connection (via the Socket class) to a credit card processing company. Sometimes (usually early in the morning), for some reason the servlet starts timing out when using the socket (read timeouts), and the servlet responds by attempting to close() the socket, then re-open. The reopen doesn't work (no route to host).
The credit card processing company put a sniffer on their end, and they don't see anything when our reads time out or when we subsequently do a close(). Thus, they assume the connection is still established. When we try to open a new connection, our SYN packets do get through to them just fine, but they reply with RST packets because they think the prior connection is still established (thus they reject the new connection attempt)... but for us, that connection had gone dead.
They recommend we send FIN packets to them etc., i.e. that we do a proper TCP/IP close.... but if the connection suddenly goes dead to us, we can't do that... our close() attempts send absolutely nothing to them (no FIN packets, nothing at all).
Any ideas? Our servlet runs in Java 1.2 under BEA Weblogic 4.5.1 on an HP/UX box. I'm thinking that, after a long time (hours) with no data transferred, our socket times out somehow on our end only (the card company appears to have no such idle-timeout policy), and thus our read/write/close attempts send nothing to them (because the socket is now invalid), but of course the subsequent open attempt sends SYN's just fine. A search of the "weblogic.properties" file produces no apparent TCP/IP socket idle-timeout values to increase or eliminate.
Please help if you can... right now, the connection can be down for hours because of this (with many fruitless incidents of our open-attempt SYN's responded to with RST's), and we have to call the credit card processing company to have them reset the port, which allows our next open attempt to work.
Thanks!

Strange... You say:
Thus, they assume the connection is still established. When we try to open a new connection, our SYN packets do get through to them just fine, but they reply with RST packets because they think the prior connection is still established (thus they reject the new connection attempt)... but for us, that connection had gone dead.
According to me, normal TCP behavior shouldn't behave like that.
A connection is identified by the two ends. Each end is a pair of <IP><Port>... This pair is likely to be the same all the time on the server, but will change on the client. The first time you issue a connection to the server, you will have a TCP connection identified by <ClientIp><FreeLocalPort1>-<ServerIp><ServerListeningPort>. The second time you connect, another free local port will be used. The previous cannot be reused - either because still in use, or because of a kind of 'grace' period during which this port number cannot be reused (this is to prevent mis-interpretation of packets that might be delayed on the network - connection is in the state TIME_WAIT).
Therefore, I don't understand why the server replies with RST when your client tries to reconnect.
Unless it has nothing todo with the TCP layer itself... You will see the same RST packet if the server application itself (not the TCP layer) refuses the connection because of some logic that says 'only one connection per client host'. If the server didn't notice your first connection was dead, it is likely to refuse your second attempt. See what I mean?
Remember a TCP connection can be half-closed. This means that if your client closes the connection, the server won't be able to send you anything but can still read what you send. In this case, if the server sits waiting for your data, it will never detect the connection lost... This is why most tcp daemons start a timer when reading incoming data. After a predefined period of inactivity, they decide the connection is dead and will close their side of the pipe - the connection is now fully closed.
Hope it was clear (despites my poor English and the very late hour in the night ;-)
Can point you to more accurate TCP doc if needed.
-Bertrand

Are there any problems with Snow Leopard Server (Xserve) and PPC Clients

Hi,
are there any problems identified yet with Snow Leopard Server, installed on a Xserve and PPC Clients running Mac OS X Tiger and Leopard?
Currently I have a Xserve Intel running Leopard Server and about 12 Mac Minis PPC running Mac OS X Tiger and Mac OS X Leopard. The Xserve serves services like DNS, OpenDirectory, Software Update Server, NetBoot, etc. All users have Home Directories stored on the Xserve.
Now I want to install Snow Leoaprd Server on the Xserve, but I wonder if there are any problems using the PPC Clients? I have read something like this on a german website.
Thanks!

We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

Permissions problems with Shared files

In my office of two users I have set up file sharing between two Macs, one is is running Snow Leopard 10.6.2 and the other (a PPC machine) is running 10.5.8 (The Leopard Machine was migrated over from a Tiger Machine by doing a fresh install of Leopard and then using Migration Assistant to move the user account off of the Tiger Machine).
Occasionally, I need to send files to the Leopard Mac from my Snow Leopard machine, so I connect to the other Mac's Shared folder, navigate to the Drop Box, and pop the file in.
Looking at the file on the other machine, it comes through as Read Only, ie. if I Get Info on it, it says 'you have custom access' and lists users as Nobody: Read Only; (Unknown): Read Only and Everybody: Read Only. These permission remain like this once the file is copied or moved out of the Drop Box.
I've had a look at the Sharing Prefs on both machines and they are set up to have the admin account as Read and Write and Everyone as Read Only - the Drop box is then set to have the admin account as Read and write and Everyone as Write Only (Drop Box).
The permissions problems happen in either direction, whether copying from machine A to machine B or vice versa.
Can someone help me fix this.
Thanks

Easybourne wrote:
Thanks for the tip. Once the other user vacated their Mac last night I ran the commands but...
Unfortunately, I still seem to be having issues with files being 'read only' on the Leopard machine. If I send a file from the Snow Leopard Mac to the Leopard Mac's drop box, it shows up with what looks like read/write access for 'nobody', 'everyone' and 'unknown user', but if I open the file, work on it and try to save via an app's save dialog, it says the file is Read-only. In the words of t'internet: W T F?
I ran your commands on the Snow Leopard machine too, and curiously, if I send a file from the Leopard machine to the Snow's Drop box, I CAN read and write to the file.
One thing that troubles me is that My User name is now listed TWICE in the list of permissions I get (My User Name): Custom Access and (My User Name) Read/Write. That seems odd.
no, that's normal. this happens because of the ACLs.
Something similar is happening on the Leopard machine too.
I created a fresh user account on my Snow Leopard Machine to see what the default permissions should be and I get other entries in the permissions list that aren't present on either of the two Machine's main user accounts. Users such as 'Staff', for example. Frankly, I'm lost.
I've read somewhere that there could be permissions problems on machines where user accounts have been upgraded from Tiger to Leopard as is the case with one of the machines in question.
yes, that could be. we can fix that if necessary.
I've also read that I can do a complete reset of ACLs by using the Reset Password utility on the Leopard installer DVD. Would this be worth a go, and could it cause more problems if it doesn't work?
yes, you can try resettings ACLs on the leopard machine using the leopard install disk. however, the acl reset utility on the leopard disk is somewhat buggy and sets wrong groups on everything it touches. therefore after you are done with it, reboot normally and run the following terminal command
sudo chown -R `id -un`:`id -gn` ~
you'll have to enter your admin password (which you won't see). that's normal.
If you can bear it, could you please help me some more. Thanks very much.
Message was edited by: Easybourne

Disk Permissions Problem on External HD Accessed Wirelessly

Hello,
I recently purchased a LaCinema Connect MiniHD and have been using it with a Western Digital 750Gb drive (formatted Mac OS Case Sensitive, non-journaled). I also recently bought a D-Link DWA-125 wifi dongle to use with the LaCinema.
I can access and read/write to the drive without problem when it connected via USB to my computer or to my wife's laptop. However, when I try to trasnfer to it wirelessly over the network (i.e. when the drive is connected to the LaCinema which, in turn, is on the network) I receive error messages when I attempt to transfer files to certain folders (including the "root" folder). What is interesting is that the folders that I can transfer to appear to be ones that were created on my old work computer, with an earlier OS version (definitely not Snow Leopard).
I suspect that I have some sort of permissions problem, but "Repair Permissions" is not available to me for this drive in Disk Utility.
I have plugged in the drive into my computer and have reset the permissions so that the "owner", "staff", and "everyone" are able to read and write for all folders and sub-folders, but it has not solved the problem.
Any advice would be greatly appreciated.
Thanks,
Graeme.

Eric,
I, too, apologize for the delay in posting. I have been away from the discussions for a rather extended period.
Well, any NTFS formatted volume will only be accessible to you as read only. No, this is not something new, but has always been the case. To make matters worse, I have heard that Windows no longer provides any way to create a FAT-32 volume; one must use OS X to format the volume or use a third-party application in Windows. This information may be incorrect, but I wouldn't be surprised if it is true (we're talking about Microsoft, here).
If you can copy any data on this drive to some other location, then use Disk Utility to format it as FAT-32, the data can then be copied back and it can be used to transport the data cross-platform, with read/write access on both ends. Is this a possibility for you?
Scott

Permissions Problems PT.II The Empire Strikes Back

Hello all. I initially had a permissions problem with files on my computer after upgrading from Tiger to Leopard last week. I thought I had the problem solved with the doubleteam effort of RodneyW. and V.K. The topic is here:
http://discussions.apple.com/thread.jspa?threadID=1510598&tstart=0
Now all the folders in my Documents and Pictures are fully accessible to me.
A bit of background: when I log into the mac, I am always logged in as an administrator with my username.
Today, I checked the permissions of my applications, and some of them which I installed myself still say that I have 'custom' access, and at the same time showing on the list of users my username with "read and write" permissions!!! Argh!!!!!
Here is a list of programs that I had installed on my computer which are now showing that I have custom access while logged in using my regular username (and I am an admin).
*Application: User/Privilege:*
*Tax program* myusername(me)/ read & write
admin / read
everyone / read
*Bits on Wheels* myusername(me) / read & write
(unknown) / read
everyone / read
Firefox myusername(me) /read & write
admin / read
everyone / read
flip4mac system / read & write
admin / read & write
everyone / read
*Logitech Harmony remote* _unknown / read & write
(software for remote control) (unknown) / read & write
everyone / read & write
Maintenance system / read & write
admin / read & write
everyone / read
*Microsoft autoupdate* _unknown / read & write
admin / read & write
everyone / read
*Microsoft office 2008* system / read & write
admin / read & write
everyone / read
Opera myusername(me) / read & write
admin / read & write
everyone / read
Skype myusername(me) / read & write
(unknown) / read
everyone / read
Unarchiver myusername(me) / read & write
(unknown) / read
everyone / read
VLC myusername(me) / read & write
admin / read
everyone / read
*Yahoo Messenger* myusername(me) / read & write
admin / read
everyone / read
It seems as if the mac does not recognize me (in some cases) when I am logged in.. because why do I have 'custom' access, while in the list of users, I can see myself with "read and write" access.
Also, if you look at one of the codes given by V.K to input into terminal, specifically:
*chmod +a "everyone deny delete" ~/ ~/Desktop ~/Documents ~/Downloads ~/Library ~/Movies ~/Music ~/Pictures ~/Public ~/Sites*
*I don't see "applications" there.. could that have omitted the permissions fix?*
Thanks for your attention.
Message was edited by: fayjon99

I think I may have done something not so smart... because I don't know Terminal very well. I did not know that I had to wait for the prompt:
*Macintosh:~ myusername$*
before entering a new command. Because what I did after I entered the first command:
s*udo chmod -R - N /Applications*
and got the reply:
*chmod: N: No such file or directory*
there was a little grey box directly underneath it. So I put the rest of the commands in (pressing enter after each line, which gave me a little grey box on the next line).
Then after a minute or two I closed terminal, but it asked me if I wanted to close it since there were commands running. So I chose "Cancel" but then the terminal dissapeared!!!
Did I do something stupid?
Anyway, I redid it, but this time waited until the prompt with my username popped up and this is the result:
*Last login: Thu May 8 16:50:05 on ttys000*
*Macintosh:~ myusername$ sudo chmod -R - N /Applications*
*chmod: N: No such file or directory*
*Macintosh:~ myusername$ sudo chmod +a "everyone deny delete" /Applications /Applications/Utilities*
*Macintosh:~ myusername$ sudo chown -R root:admin /Applications*
*Macintosh:~ myusername$ sudo chmod -R g=rw,+X /Applications*
*Macintosh:~ myusername$*
I checked the applications folder afterwards, but nothing has changed in regards to my problem. Do I have to reboot to see changes?

Problem installing SCCM client in remote untrusted forest

Hi,
My configuration is :
My network is in two parts : intranet and a DMZ. In the DMZ there is another forest and domain. There is no trust between the forest in the DMZ and the internal network. I configured the remote forest in SCCM with a user account that has Domain Admin acces
in the DMZ forest/domain.
The primary site server is located in the internal part of my network. SQL is installed on a remote server. Management point, distribution point, Fallback Status Point roles are installed on the primary site server. SMS Provider is installed on the primary
site server.
In the DMZ part, I have a management point, distribution point installed on one server.
The forest discovery works fine. I can query AD in the remote forest (DMZ).
I have a problem installing the SCCM client on computers located in the remote forest with client push or with the command line.
CCMSETUP.EXE /MP:DMZ site server /DP:DMZ site server /FSP: primary site server SMSSITECODE:SIT
In CCMSetup.log I can see that the client try to communicate with my DMZ site server but it reverts to the management point and distribution point located in the internal part of the network. The installation fails and will try in 10 minutes.
Do anyone has seen this problem before? Am I missing something? Could it be a configuration issue?
Could you help me whit this please?
Thanks in advance for your time!
Jacques

Does the client installation work when you install the client manually on the untrusted domain client? What does the CCM.log say on the site server?
Have you double checked the firewall ports for the client push installation? The ports needed for the client push to work are as follows (from the site server to the client):
SMB - TCP 445
RPC Endpoint Mapper - TCP 135 / UDP 135
RPC Dynamic Ports
And to Management Point:
HTTP - TCP 80 (When using HTTP)
HTTPS - TCP 443 (When using HTTPS)
Also a quote from
TechNet: "In addition to the ports listed in the following table, client push installation also uses Internet Control Message Protocol (ICMP) echo request messages from the site server to the client computer to confirm whether the client
computer is available on the network. ICMP is sometimes referred to as TCP/IP ping commands. ICMP does not have a UDP or TCP protocol number, and so it is not listed in the following table. However, any intervening network devices, such as firewalls, must
permit ICMP traffic for client push installation to succeed."

A Java security or permissions problem?

First of all, I don't know much about Java, even its naming and version numbering nomenclature, and second, if there is a better group to ask this in, please let me know.
System is Mac with 10.4.4. I have Java 1.3.1, 1.4.2, and J2SE 5.0 (1.5.0) installed. The Java preferences application lets me choose J2SE 5 or 1.4.2 to run applets via a browser. The problem happens in both settings.
The problem is that we have a printer that serves a little Java-based management application to view history and otherwise manage it. When I hit the IP, I get the Java coffee cup for a few moments, then a blank area. It fails in both Safari and Internet Explorer.
I'm pretty sure this used to work in OS X 10.4.3. It works from Windows which has runtime 1.4.something.
In the Java console, I get the following. (I've snipped some lines.)
========================================
Java Plug-in 1.5.0
Using JRE version 1.5.0_05 Java HotSpot(TM) Client VM
User home directory = /Users/timmurray
java.security.AccessControlException: access denied
(java.lang.RuntimePermission accessClassInPackage.com.apple.mrj)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:264 )
at java.security.AccessController.checkPermission(AccessController.java:427)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
at java.lang.SecurityManager.checkPackageAccess(SecurityManager.java:1512)
<snipped 22 similar lines>
Exception in thread "Thread-17" java.lang.NullPointerException
at sun.plugin.util.GrayBoxPainter.showLoadingError(GrayBoxPainter.java:153)
at sun.plugin.AppletViewer.showAppletException(AppletViewer.java:1968)
at sun.applet.AppletPanel.runLoader(AppletPanel.java:664)
at sun.applet.AppletPanel.run(AppletPanel.java:320)
at java.lang.Thread.run(Thread.java:613)
java.lang.NullPointerException
at sun.plugin.util.GrayBoxPainter.showLoadingError(GrayBoxPainter.java:153)
at sun.plugin.AppletViewer.showAppletStatus(AppletViewer.java:1898)
at sun.applet.AppletPanel.run(AppletPanel.java:365)
at java.lang.Thread.run(Thread.java:613)
Exception in thread "thread
applet-com.efi.appls.webtools.WebToolsApplet.class"
java.lang.NullPointerException
at sun.plugin.util.GrayBoxPainter.showLoadingError(GrayBoxPainter.java:153)
at sun.plugin.AppletViewer.showAppletException(AppletViewer.java:1968)
at sun.applet.AppletPanel.run(AppletPanel.java:529)
at java.lang.Thread.run(Thread.java:613)
========================================
This appears like a permissions problem, but I've fixed permissions several times.
Any idea what the problem is, and is it fixable from my end?

Problem has finally -- over a year later -- just gone away.

Local KDC (LKDC) relating to Leopard clients logging into Tiger Server

This is a follow-up to my posting on this thread:
http://discussions.apple.com/message.jspa?messageID=5982070#5982070
Pursuing the problem I had when I upgraded to Leopard, I found it odd that trusted binding to Tiger OD from a Leopard client created a funny computer entry in the Workgroup Manger (WGM). Previously when using trusted binding from a Tiger machine to a Tiger server, one entry would be created. And Logging in as an OD user worked every time for me. However, it appears that under 10.5.1 Kerberos has changed significantly in that it is now being used extensively through the Leopard OS for Peer-to-Peer applications. This may account for the screwed up Computer account entries in WGM when a 10.5.1 client binds to 10.4.11 Server using trusted binding. The giveaway clue to this is the LKDC:SHA1 entry created in the WGM computer record (usually 3 seperate records for 10.5.1 instead of the normal single record with a Tiger client). My question is this:
Are there any changes that can be performed via command line on the 10.5.1 client to mimic the old 10.4 client Kerberos configuration without pervasive Peer-to-Peer use of Kerberos? Is is a config setting for the mit.kerberos file? Could it be as simple as flipping a switch to get the older more compatible Kerberos config of a 10.4 Tiger client? Can I dump the Local KDC present in Leopard, and get back to the good old days of non-local KDC under Tiger?
http://www.afp548.com/article.php?story=LeopardServerReview-LocalDirectory
"The Local KDC
Yes, you read that right, the local KDC. All Leopard client systems will now create a Local KDC for use with peer to peer file sharing.
While this isn't even as close to as scary as it seems, it is a topic worthy of at least a separate article, if not a whole series. I put on my thinking toque and sat in my thinking corner for a while on this, and I've not yet been able to come up with a reason for why having a KDC on every machine is less secure than how 10.4 did things. Having said that, though, I fully understand how this can seriously freak out your network security team as they don't quite grasp all the ins and the outs of this. Combine this with Back to My Mac, another article that's forthcoming, and you have a very interesting collection of some "sleeper" features in Leopard.
So, in a nutshell, a Local KDC, the LKDC, is created when 10.5 is installed. Local users will get LKDC authentication authorities allowing them to get Kerberos tickets and use that for single sign on to all the services hosted on that client system. Kerberos is supposed to be only used when you use Bonjour to discover the other machine. So primarily in peer to peer on the same LAN cases.
It works, you can see this for yourself. Screen share to another machine as a local user by picking the machine out of the sidebar in the Finder. You'll have to enter in your password the first time, but after that you can close out of that screen sharing session and restart it without having to re-enter your password. You can also see the ticket in the Kerberos.app, still buried in /System/Library/CoreServices."

Eric,
Thanks so much for your thoroughness and assistance. I think we have decided, for now, to forgo the 10.5 clients attaching to the 10.4 server because of too many intermittant issues. Similar machines on 10.5 gave different results. And at this point, our client is very skittish about the process working at all. I think we need more testing and that is the directon we'll take for now.
Here are some of our results:
I did find information on afp548 regarding the 10.5 preference. It was specificall referenced in this article:
http://www.afp548.com/forum/viewtopic.php?forum=18&showtopic=16064
Clearing the check box on the 10.4 server under OD > Settings > Security "Require password change on new user login" did solve the memory issue that kerberos was having. After clearing the setting, I:
* deleted all binding references at the server (WGM > Accounts > Lists > All Computers
* Deleted the bindings at the client and the the LDAP server references in Directory Access
* Restarted the machine
* Reconnected the LDAP server, Rebind the machine
* Check the LDAP search in issuing id <username> in Terminal
* OPen System PReferences > Accounts > Login Items, the preference is there!
* Yeehah
Oh, but the user still can't login in that machine. Uhm, why? I have no idea. I take a new machine, 10.5.1, no login accounts except a local admin, and no that user still cannot login. Other users, no problem, but not that user.
Take a new system, 10.4.11, set up the binding, the LDAP server, try to log in that same user: works every time. Ugh.
So of course, I think there is something up with that user, but nothing in logs gives an indication of what is going on. That I can find. THis is after 10 hours of testing and trying. Needless to state, the client is frustrated, and so am I.
You know, we do have one 10.5.1 client laptop that did work. After lots of binding and rebinding, it just somehow starting working as expected. But, the reason that we're sticking with 10.4 clients for now is that machine will not respond to password change mandates. I select that user in the WGM, check the "require password change on next login" and nothing happens on their end. They are not an admin, I have reset their account more times than I can count, and so I expect there are more non-working items with 10.5.1 clients and 10.4 server that will get me. It needs more testing for now.
So, back to your message, I haven't tried the SSL certificate, but I will give that a try.
In general, for your network, how are your laptop users configured? As mobile users? Network homes? Or Local homes?
Thanks again for your help. I really appreciate it.

Problem mit FDK-Client

Ein FDK-Client, der unter Windows XP einwandfrei funktioniert, unter Windows 7 funktioniert nur bei Benutzern mit lokalen Adminrechten. Bei Benutzern mit Standardrechten bricht die Ausführung ab mit Fehlermeldung „Interner Fehler 9004, 6919244, 9675646, 0“.

Ich spreche kein Deutsch...
Preferably, contact your supplier and get them to fix the DLL
The "0" at the end of the error message "internal error 9004, 6919244, 9675646, 0" indicates that your DLL is trying to use a null pointer. I suspect that a call to allocate a resource is failing because oif inadequate permissions, and returns 0. The DLL is then using the return value without checking it.
You might be able to fix the permissions problem by adding a manifest. Do one of the following:
if you have the source for the DLL, add the manifest as a resource, and recompile the DLL
if you do not have the source, add the manifest as a separate file in the same directory as the DLL( foo.dll would use foo.manifest).
I did this in a previous job, but no longer have any details, so cannot offer any further advice. Use your favourite search engine to get more help. You might also look at any .manifest files within FrameMaker,
Alternatively, try changing the Security settings for the DLL (right-click, Properties, Security tab). I have never done this, but it might have some benefit.

Weird Permissions Problem

I'm running the latest version of Leopard (10.5.5). Two days ago, I downloaded the latest update to MS Office 2008 (12.1.3). I have 12.1.2 installed. Upon downloading I tried to install the update. About 5 steps into the update, the installer asked me where to install the update. At that point, it identified all of my drives with a red exclamation point, making no choices possible. Since I had just installed other updates on my startup drive, the red exclamation point made no sense to me. So, I rebooted. Same problem. I repaired permissions. Same problem. I downloaded another copy of the update from a different server. Same problem. I inspected the drive permissions as well as the permissions on the Office 2008 folder. No problems identified. I ran TechTool Pro and found no problems.
At this point, I am unable to install the update on one machine - a Mac Pro quad core 2.66 machine with 4 physical hard drives plus two attached firewire drives. All my programs are installed on the startup drive - a Seagate 1 TB, 7200 RPM drive. I've succeeded in updating MS Office on all my other machines. Something is odd about the Mac Pro, but I'll be darned if I can figure out what it is. Hardware problem? Software problem? permissions problem? You guess because I don't have a clue.
I have been able to continue to update software without a hitch, except for the MS Office patch.
Any thoughts? This doesn't seem to be a Microsoft problem as my other experiences demostrate. I'm open to suggestions for a possible fix or a way to fool the installer.
Thanks for your help.

In the end, I solved the problem with a very large hammer. Because I keep extensive backups, I rebooted into a backup, blew away the startup drive completely, deleted the install of Office 2008, and then restored the startup drive from the backup. Before doing that, I used Disk Utility and Disk Warrior to comb the surface of the startup drive for any defects. None found. That done, the restoration permitted me to reinstall Office 2008, update with SP1 and then update using 12.1.3. In the end, all the permissions are exactly the same as they were beforehand. I have no idea what the problem was, but this is another lesson in why we keep backups around. SuperDuper! made this problem trivial, but time consuming. I now know that my backups are solid and that my startup drive is fresh. I had plenty of better things to do with my time, but I'll have another time to fix those messes.
Thanks for all attempts at help. This just turned out to be "one of those" kinds of problems that have no logical or rational explanations and for which the only solution is the big hammer.

Weird permissions problems

Solaris 9 sytem, recently patched.
I seem to have broken something. Many processes are working but giving permissions errors for users and daemons:
My pop server says it can't create .<name>.pop files in /var/mail and to check permissions. This has been working just fine and permissions have not been changed.
lpsched reports "Failed to exec child process (permission denied)" and fills the log file with this msg.
Can't ssh into the system: but the ssh client reports a failur to chdir to /export/home/<name> - permission denied, but the sshd log file accepted the passwd and reports no error. The home dir exists and this has been working.
As root, doing su - <name> reports back "No directory!" while su <name> says "su: No shell"
logins -x -l <name> reports everything is A-OK, the home directory exists, and is owned correctly. I can chdir into it as root and ls -n reports correct uid/gid.
There is some common thread to this that I'm not seeing... Any ideas? It is not a permissions problem - I seem to have broken some ability for root to run processes correctly.

About BOLT and Opera Mini, it's a signature problem.
your device will always ask you if an application can go on the internet, unless the application is signed.
you just have to download the signed version of the application.
The problem is that editors refuse to sign their application using the signing authorities trusted by RIM, and on the other side, RIM refuses to install on your device an application that is signed by an authority that RIM does not trust as "code signing".
The search box on top-right of this page is your true friend, and the public Knowledge Base too:

My iMac 8.1 was slowing down and had permissions problems. I backed everything up, and then re-installed. Now all I get is a black screen. Power+D gives me a hardware error message: HDD-1336. Help!

My iMac 8.1 (10.6.8 ) was slowing down and had recurrent permissions problems, mostly with Java. I backed everything up, and then re-installed from time machine. Now all I get is a black screen which says I need to reboot. Power+D gives me a hardware error message: 4 MOT/1/40000003: HDD-1336 or HDD-1327. When I reboot from the OSX CD and start disc utilities everything checks out OK. When I reload 10.5.2 from the OSX CD everything seems to work OK and no more permissions problems. But then I loose all my email and safari stuff. Anyone have any ideas short of going back to my old PC?

DonM. wrote:
Hi
Thanks for the help. No point in fooling around with it any more. Will I be able to use it as a monitor if I get a mimi mac?
Cheers. Don
No unfortunatley it's too old, you are referring to Target Display Mode which became avialble in 2009, your 2008 needs to have the HD replaced. I'd still do that if everything else is OK or you can simply buy a new MM and display or even a new iMac or an Apple refurbished iMac to save money.

I am trying to authorize my computer and I get an error message: The required directory was not found or has a permissions error. Correct this permissions problem and try again, or deauthorize this computer if the permissions cannot be changed. Help?

I am trying to authorize my computer and I get an error message: The required directory was not found or has a permissions error. Correct this permissions problem and try again, or deauthorize this computer if the permissions cannot be changed. Help?

I used Terminal to change the permissions on the folder in question. I followed the instructions in this article:
iTunes: Missing folder or incorrect permissions may prevent authorization
In my case, the folder was there, so I needed the command to change permissions on the folder, not to create one. I was hesitant to use Terminal b/c I know that if I made an error I could wipe out my hard drive or render my computer unusable. So to be SURE I didn't make an error, I carefully copied the command from that page and *pasted* it into Terminal. Also, before I could do anything in Terminal, I had to go change my admin password (it had been a blank password before and that's not acceptable for making changes in Terminal). I was just super careful when entering my password or doing anything else while Terminal was open (making sure I didn't accidently hit the spacebar or another key, etc.) And it fixed the problem right away.
What was confusing for me was that the iTunes error message said to change permissions in the FINDER, which is what I was trying to do. It didn't mention Terminal. What would really be helpful is if Apple included a link to a page like this in their error message.

Permissions Problem Leopard PPC Client to 10.3 Server

Similar Messages

Maybe you are looking for