Mirrored Folder - Permission denied

When trying to upload a file to a mirrored folder, we get the error message "permission denied".
We use teaming 2.1 on SLES 11 SP1.
The mirrored folder is a file based one. (not WebDav)
This folder is a directory on the teaming server itself.
any ideas ?

Are you adding documents to the (mirrored) folder from the Teaming UI via a web-browser? If so, have you checked to make sure you have the access rights to add documents to the mirrored folder? During setup of mirrored folders, did you specify a list of users groups who have access to the folder?
-- Khurram

Similar Messages

  • Damaged SSD, need to delete user folder - permission denied

    Hi everyone, this is my first post.
    I have installed SL onto my Kingston ssdnow v100 128GB solid-state drive (SSD) and used it as my primary OS drive along side of optibay in my first generation Macbook Pro Core Duo 2.0.
    It has been funcioning perfectly until 2 months ago: my laptop would idel at the grey startup screen after a cold start with the progress indicator (circular) running indefinetly. The system files were being loaded but the process never completes. I reinstalled SL fresh a few times, all successfully, but the problem would return the next morning when switched on from cold. Traditional SATA drive was used and did not cause this problem.
    I have decided that it was a SSD failure and have arranged it to be sent back to the seller.
    SO here is the PROBLEM:
    I wish to delete only the USER FOLDER while preserving  system files on the SSD drive, so that when the seller tests it he is able to pick up the problem. If I format the entire drive, the seller may not pick up the fault as the drive would install OS fine and appear functional.
    So I connected the SSD drive via USB to my other MBP, the Finder pops up and  tells me that the SSD drive can not be repaired but can be READ to recover my files. I then try to drag my USER FOLDER to trash but a Finder message pops up and say: It can not be deleted. The info window showed that all listed users are greyed out and clicking on the permission (read & write & read and write) did not bring up any options, just as if you can not click it. I have unlocked the info window to allow changes using admin password.
    Is there anyway (maybe via Terminal.app) that I can override file permission and allow me to delete this USER FOLDER that is on the SSD drive?
    Thank you for answering.

    Hi there! Welcome to the Apple comminity.
    In Terminal, this is how you override something: Add "sudo " before your command. Here's an example:
    sudo rm -Rf /Volumes/SSDdrive/Users/*
    It will then prompt you for a password (if you are an administrator on your computer). Good luck!
    Cheers.

  • Permission denied on apps javascript folder

    I need to distribute an application that generates a folder-level script for writing to an XFA form. I want to store the script at the app level.
    app.getpath("app","JavaScript") returns this folder (on my machine, but some of the other users have later versions): C:\Program Files (x86)\Adobe\Acrobat 9.0\Acrobat\JavaScripts
    The problem is that when I try to save the script I get a "Permission Denied" error.
    Is there a way to overcome that without resorting to the user javascript folder?

    lrosenth wrote:
    Well, we made the change with Acrobat X, IIRC.   I honestly don’t remember whether there were complaints.  But most app-level scripts don’t get installed using the method that you are – they get installed once via a standard software installation tool (which will create the folder if missing)
    But this is a User-level script. I'm not even sure how I could check for the folder's presence without knowing what the USERNAME is.
    For example, this is the javascripts path on my laptop: \Users\Darrell\AppData\Roaming\Adobe\Acrobat\9.0\JavaScripts.
    How would I know if the javascripts folder should be under the USERNAME "Darrell"? There may be multiple User folders, and they may not be the same as the Windows login.

  • I am having problems installing creative cloud due to cookies dir(?)it says cannot make folder/cookies: permission denied(error 13)

    I am having problems installing creative cloud: It says "cannot make folder/Cookies:permission denied (error13)

    Try below steps
    Click on Finder and then hold Command + Shift + G keys on your keypad
    It will open Go to folder window, type  exactly ~/Library and click on Go  ( make sure to opeb ~/Library not /Library, there will two library )
    Then open Application Support
    Right click on Adobe folder
    Click on get info
    Under sharing and permission click on lock icon and unlock it
    Click on symbol and Add Administrator and your current user name ( if not added )
    Then give read and write permission to user name, admin, system and every one
    Then click on Gear icon and select 'Apply to Enclosed
    Click on lock icon
    Try to install Creative Cloud App.

  • I get an error stating cc cookies dir: cannot make folder / cookies: Permission denied (error 13) when I attempted to download the creative cloud installer on my Mac. Can anyone help with similar pop up window?

    I get an error stating cc cookies dir: cannot make folder / cookies: Permission denied (error 13) when I attempted to download the creative cloud installer on my Mac. Can anyone help with similar pop up window?  I'm trying to get a trial version of CS5. 

    You do not need to involve Creative Cloud to install/try the trial version of CS5...
    You can download the trial version of the software thru the page linked below and then use your current serial number to activate it.
    Be sure to follow the steps outlined in the Note: Very Important Instructions section on the download pages at this site and have cookies enabled in your browser or else the download will not work properly.
    CS5: http://prodesigntools.com/all-adobe-cs5-direct-download-links.html

  • I just purchased a Creative Cloud subscription and I was trying to install Photoshop, but I receive the error message 'Error Starting Creative Cloud - cookies dir: cannot make folder /cookies Permission denied (error 13)'

    I just purchased a Creative Cloud subscription and I was trying to install Photoshop, but I receive the error message 'Error Starting Creative Cloud - cookies dir: cannot make folder /cookies Permission denied (error 13)'

    Hi Arjun and tphc,
    try the solution I found and tested at this other thread:
    http://forums.adobe.com/message/5628798
    I think it could be helpful for you too!
    Cheers,
    Marco

  • What to do with this? "cookies dir: cannot make folder /cookies: Permission denied (error 13)"

    What to do in this case???
    cookies dir: cannot make folder /cookies: Permission denied (error 13)

    Re: Installing Creative Cloud Desktop but I got Error 13 an issue permission on my MacBookPro, why?

  • Getting an error message that says: "Error starting Creative Cloud"  "cookies dir: cannot make folder / cookies: Permission denied (error 13)"

    getting an error message that says: "Error starting Creative Cloud"  "cookies dir: cannot make folder / cookies: Permission denied (error 13)"

    Please refer the thread: Installing Creative Cloud Desktop but I got Error 13 an issue permission on my MacBookPro, why?.
    Regards,
    Romit Sinha

  • Cannot make folder /cookies: Permission denied (error 13)

    I can not successfully install the Creative Cloud Installer. I continually get
    Error Starting Creative Cloud
    cookies dir: cannot make folder /cookies: Permission denied (error 13)
    I have tried verifying disk permissions using the disk utility on my macpro retina. This is a brand new computer (less than a week). I've also tried changing cookies permissions to allow for third party cookies.
    I don't know what the problem is.

    I had this same irritating problem. Thanks to this forum and some helpful instructions from Adobe Customer Support online I have been able to sort it out. For those who've read this far down the thread, here are the instructions from Adobe, which worked a treat - and also cured a problem I was having with Adobe Reader XI for Mac (internal error message meaning I couldn't use Reader and none of my pdfs would open with Preview either!)
    1. Please Open Finder and click on Applications on left hand side of Finder window.
    2. Navigate　to Applications->Utilities ->Adobe Installers. Double click on Uninstall Adobe Creative Cloud and follow the onscreen instructions.
    3. Delete Adobe Application Manager folder from Applications/Utilities.
    4. Open Finder. Click on Go in Finder menu and choose Go to Folder. Type /Library/Application Support/Adobe in Go to folder and press return key. You will have Adobe folder open in Finder.
    5. Delete AdobeApplicationManager and OOBE folder.
    6. Click on Go in Finder menu and choose Go to Folder again. Type ~/Library/Application Support/Adobe in Go to folder and press return key.
    7. Delete AAMUpdater and OOBE folder from Adobe.
    8. Click on Go in Finder menu and choose Go to Folder again. Type ~/Library/Application Support and press return key.
    9. Right click on Adobe folder and choose Get Info.
    10. Click the lock icon at bottom of Get Info window to unlock it, then enter an administrator’s name and password.
    11. Click on + icon and choose select all users on pop up and window and choose Select.
    12. Change the permissions　for all Users to Read and Write.
    13. Choose "Apply to enclosed items" from the Action pop-up menu (looks like a gear).
    14. Try installing the Creative Cloud Desktop application from below link.
    https://ccmdls.adobe.com/AdobeProducts/KCCC/1/osx10/CreativeCloudInstaller.dmg
    Please launch Adobe Creative Cloud Desktop application and check if you are able to sign in.

  • I get an error starting cc cookies dir: cannot make folder / cookies: Permission denied (error 13)

    I get an error starting cc cookies dir: cannot make folder / cookies: Permission denied (error 13) when downloading the creative cloud installer on my imac osx desktop. Can anyone help with similar pop up window?

    Swallow what is the exact error which you are receiving?  Also what version of Mac OS are you using specifically?  Finally what Adobe software title are you currently attempting to install?

  • Error Starting Creative Cloud. Cookies dir: cannot make folder / cookies : permission denied ( error 13).

    After paying  for using CC, cant use it. it says:   Error Starting Creative Cloud. Cookies dir: cannot make folder / cookies : permission denied ( error 13)
    any ideas??

    Pablosanchezphotoshop do you have sufficient disk space?  Are you logged in under an administrator account?  Finally which operating system are you using?

  • Cookies did: cannot make folder/ cookies: permission denied (error 13)

    cookies did: cannot make folder/ cookies: permission denied (error 13)
    can't download creative cloud

    Well, then by all means check the user privileges on your user folder...
    Mylenium

  • Can't install always this cookies dir: cannot make folder /cookies: Permission denied (error 13), Guy

    Always following error by installing
    cookies dir: cannot make folder /cookies: Permission denied (error 13)
    Mvg,
    Guy Meurs

    HI Fotografiemeurs,
    Please check the following forum posts.
    Re: How do I fix error code 13 when starting Creative Cloud?
    Cheers,
    Kartikay Sharma

  • Apache user dir (13)Permission denied: access to /~simha/ denied

    I am getting Access forbidden! when I am trying to connect to http://localhost/~simha/ where simha is my user name
    my /var/log/httpd/error_log says
    [Thu Jul 08 17:44:30 2010] [error] [client 127.0.0.1] (13)Permission denied: access to /~simha/ denied
    I tried a lot and gave up. Can any one help me in this in regard
    The following are the permisions of my home dir simha and public_html
    drwx--x--x 130 simha users 16384 Jul 8 17:04 simha
    drwxr-xr-x 2 simha users 4096 Jul 8 17:02 public_html
    The following are my httpd.conf
    # This is the main Apache HTTP server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path. If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "/var/log/httpd/foo_log"
    # with ServerRoot set to "/etc/httpd" will be interpreted by the
    # server as "/etc/httpd//var/log/httpd/foo_log".
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path. If you point
    # ServerRoot at a non-local disk, be sure to point the LockFile directive
    # at a local disk. If you wish to share the same ServerRoot for multiple
    # httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "/etc/httpd"
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule authn_file_module modules/mod_authn_file.so
    LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_anon_module modules/mod_authn_anon.so
    LoadModule authn_dbd_module modules/mod_authn_dbd.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authz_host_module modules/mod_authz_host.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_owner_module modules/mod_authz_owner.so
    LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    LoadModule auth_digest_module modules/mod_auth_digest.so
    LoadModule file_cache_module modules/mod_file_cache.so
    LoadModule cache_module modules/mod_cache.so
    LoadModule disk_cache_module modules/mod_disk_cache.so
    LoadModule mem_cache_module modules/mod_mem_cache.so
    LoadModule dbd_module modules/mod_dbd.so
    LoadModule dumpio_module modules/mod_dumpio.so
    LoadModule ext_filter_module modules/mod_ext_filter.so
    LoadModule include_module modules/mod_include.so
    LoadModule filter_module modules/mod_filter.so
    LoadModule substitute_module modules/mod_substitute.so
    LoadModule deflate_module modules/mod_deflate.so
    LoadModule ldap_module modules/mod_ldap.so
    LoadModule log_config_module modules/mod_log_config.so
    LoadModule log_forensic_module modules/mod_log_forensic.so
    LoadModule logio_module modules/mod_logio.so
    LoadModule env_module modules/mod_env.so
    LoadModule mime_magic_module modules/mod_mime_magic.so
    LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule expires_module modules/mod_expires.so
    LoadModule headers_module modules/mod_headers.so
    LoadModule ident_module modules/mod_ident.so
    LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule setenvif_module modules/mod_setenvif.so
    LoadModule version_module modules/mod_version.so
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    LoadModule ssl_module modules/mod_ssl.so
    LoadModule mime_module modules/mod_mime.so
    LoadModule dav_module modules/mod_dav.so
    LoadModule status_module modules/mod_status.so
    LoadModule autoindex_module modules/mod_autoindex.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule info_module modules/mod_info.so
    LoadModule suexec_module modules/mod_suexec.so
    LoadModule cgi_module modules/mod_cgi.so
    LoadModule cgid_module modules/mod_cgid.so
    LoadModule dav_fs_module modules/mod_dav_fs.so
    LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule dir_module modules/mod_dir.so
    LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule speling_module modules/mod_speling.so
    LoadModule userdir_module modules/mod_userdir.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule rewrite_module modules/mod_rewrite.so
    LoadModule php5_module modules/libphp5.so
    <IfModule !mpm_netware_module>
    <IfModule !mpm_winnt_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch.
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User http
    Group http
    </IfModule>
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition. These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed. This address appears on some server-generated pages, such
    # as error documents. e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    #ServerName www.example.com:80
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "/srv/http"
    # Each directory to which Apache has access can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # features.
    <Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "/srv/http">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks includes
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    # Options FileInfo AuthConfig Limit
    AllowOverride None
    # Controls who can get stuff from this server.
    Order allow,deny
    Allow from all
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
    DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
    </FilesMatch>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "/var/log/httpd/error_log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
    # You need to enable mod_logio.c to use %I and %O
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "/var/log/httpd/access_log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "/var/log/httpd/access_log" combined
    </IfModule>
    <IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock /var/run/httpd/cgisock
    </IfModule>
    # "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "/srv/http/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
    </Directory>
    # DefaultType: the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value. If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain
    <IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type. The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall is used to deliver
    # files. This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    Include conf/extra/httpd-autoindex.conf
    # Language settings
    Include conf/extra/httpd-languages.conf
    # User home directories
    Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # phpMyAdmin configuration
    Include conf/extra/httpd-phpmyadmin.conf
    # Various default settings
    Include conf/extra/httpd-default.conf
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    Include conf/extra/php5_module.conf
    # Note: The following must must be present to support
    # starting without SSL on platforms with no /dev/random equivalent
    # but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>
    The following are my /etc/httpd/conf/extra/httpd-userdir.conf
    # Settings for user home directories
    # Required module: mod_userdir
    # UserDir: The name of the directory that is appended onto a user's home
    # directory if a ~user request is received. Note that you must also set
    # the default access control for these directories, as in the example below.
    UserDir public_html
    # Control access to UserDir directories. The following is an example
    # for a site where these directories are restricted to read-only.
    <Directory /home/*/public_html>
    AllowOverride FileInfo AuthConfig Limit Indexes
    Options MultiViews Indexes SymLinksIfOwnerMatch ExecCGI
    <Limit GET POST OPTIONS PROPFIND>
    Order allow,deny
    Allow from all
    </Limit>
    <LimitExcept GET POST OPTIONS PROPFIND>
    Order deny,allow
    Deny from all
    </LimitExcept>
    </Directory>
    I also tried adding user to the group http. BUt nothing is working.

    Do you have [or more like lack] +x on the user folder?

  • Permission denied error while CBS is building DCs

    Hi,
    from time to time we get an permission denied error when activating changes. The CBS server tries to check out files into the temporary build folders at the server and cannot do that for one file (see following error message).
    As already said this happens only sometimes and only for single files.
    Does anyone have the same experience and/or a suggestion how to solve this problem?
    When deleting the folder and activating again the error has gone.
    Build number assigned: 5843
    Change request state from QUEUED to PROCESSING
    ACTIVATION request in Build Space "CMS_EBYASZ_D" at Node ID: 9.611.151
         [id: 2.568; parentID: 0; type: 4]
         [options: NO OPTIONS]
    REQUEST PROCESSING started at 2005-09-30 12:53:00.074 GMT
    ===== Pre-Processing =====
    List of activities to be activated:
         1 activity in compartment "eon.com_EON_EBY_ASZ_R_1"
              Recherche Splitting Nachtrag 7 (30.09.05, 14:51)
                   [seq. no 23][created by H15430J at 2005-09-30 12:52:46.0][ID 4e1a116731af11daa5b00003ba1edce1]
    Analyse activities... started at 2005-09-30 12:53:00.172 GMT
         Synchronizing component "eon.com/eby/asz/recherch/util" from repository... finished at 2005-09-30 12:53:01.414 GMT and took 824 ms
              Component "eon.com/eby/asz/recherch/util" is to be CHANGED by this activation.
         1 component to be build in compartment "eon.com_EON_EBY_ASZ_R_1"
    Analyse activities... finished at 2005-09-30 12:53:01.574 GMT and took 1 s 402 ms
    Calculate all combinations of components and variants to be built...
         "eon.com/eby/asz/recherch/util" variant "default"
    Prepare build environment in the file system... started at 2005-09-30 12:53:02.173 GMT
         Synchronize development configuration... finished at 2005-09-30 12:53:02.176 GMT and took 2 ms
         Synchronize component definitions... finished at 2005-09-30 12:53:02.274 GMT and took 97 ms
         Synchronize sources...
    12:53:06.831  SYNC  (FAILED: Failed to create/open file:
    /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.CACHE/228/DCs/eon.com/eby/asz/recherch/util/_comp/src/packages/de/isenergy/eby/zaehlerwesen/recherche/util/UtilComp.wdcontroller
    (<b><u>Permission denied</u></b>))  UtilComp.wdcontroller   (/usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.CACHE/228/DCs/eon.com/eby/asz/recherch/util/_comp/src/packages/de/isenergy/eby/zaehlerwesen/recherche/util/UtilComp.wdcontroller)
    Prepare build environment in the file system... finished at 2005-09-30 12:53:08.555 GMT and took 6 s 382 ms
    ===== Pre-Processing =====  finished at 2005-09-30 12:53:08.560 GMT and took 8 s 411 ms
    Change request state from PROCESSING to FAILED
    ERROR! The following problem(s) occurred  during request processing:
    ERROR! The following error occurred  during request processing:Failed to synchronize
    /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.CACHE/228/DCs/eon.com/eby/asz/recherch/util/_comp/src/packages
    REQUEST PROCESSING finished at 2005-09-30 12:53:08.563 GMT and took 8 s 489 ms
    Thanks for any hint
    Helmut

    Hi Sidharth,
    good to hear that we are not the only company with this problem.
    We also do have this problem since months, from SP9 to SP11.
    First we thought that it would have been a CBS configuration or an OS problem but this cannot be the reason because as you already mentioned it works after serveral attempts. We also analysed the temporary CBS folders and noticed that only one file (the one that causes the error) does have other attributes than the others.
    That sounds very strange and I hope that someone from SAP will read this task.
    At the moment we are collecting all the problems and errors that appear with the JDI and the Netweaver Developeer Studio to present SAP this list in bulk. We cannot write an OSS note for every error we discover as suggested by SAP.
    Stability mainly of the NWDS plugins is the biggest problem we have at the moment. Did you make the same experience?
    Regards
    Helmut

Maybe you are looking for