Publish calendar to WebDav enabled server.

I am trying to publish a calendar to my hosting companies' server. The server apparently is WebDav enabled. Though when I click the publish button in iCal I get this message:
"Publish failed for calendar Production"
"Access to the calendar http://[email protected]/Production.ics is not permitted."
My hosting company swears the server is WebDav enabled. Also I triple checked the login information.
Any idea what could be the problem?

I have a similar situation going on now with Spymac's servers. Are you running Tiger? When I upgraded to Tiger, I started having the same problem. Here's what I have to do to fix it.
Let's say, for example, I was trying to publish your calendar. Here's what the link would look like:
http://[email protected]:81/Production.ics
Notice the ":81". For some reason, Tiger seems to be having problems handling the addresses of calendars not on .Mac, where as Panther wasn't a problem.
I hope this gives you some ideas.

Similar Messages

  • Publish calendar from OS X server

    We run a OS X server on 10.8.5 with 20+ users on it. We mainly share folders. Our users sign up at the servers LDAP directory and most of them use mobile accounts.
    Actually we set up the calendar server function. Each user connects iCal at its Mac and iPhone to our server by CalDAV.
    We use the sharing functionality to share our calendars with each other internal.
    Now we want to publish some of these calenders to be able to share them with others like subscribing to external calendars. We know how to publish local calendars with the "publish"-function. But how can we do this on server stored calendars connected by CalDAV? Is there any functionality done at the server for publish to our WebDAV-Server?
    Any hint is welcome, thanks in advance.

    We run a OS X server on 10.8.5 with 20+ users on it. We mainly share folders. Our users sign up at the servers LDAP directory and most of them use mobile accounts.
    Actually we set up the calendar server function. Each user connects iCal at its Mac and iPhone to our server by CalDAV.
    We use the sharing functionality to share our calendars with each other internal.
    Now we want to publish some of these calenders to be able to share them with others like subscribing to external calendars. We know how to publish local calendars with the "publish"-function. But how can we do this on server stored calendars connected by CalDAV? Is there any functionality done at the server for publish to our WebDAV-Server?
    Any hint is welcome, thanks in advance.

  • How to publish a calendar to webdav (ical) server

    I have a Xserve running ical server, but when a user tries to publish a personal calendar on their desktop to the webdav service on the Xserve, it's prompting for a directory path.
    What directory we put there? Everything we've tried doesn't work.

    There is a difference between sharing and publishing. The latter means getting your calendar to display as an ordinary web page: firstly this cannot be done with a calendar listed under iCloud (this was also true with MobileMe) but only if it's listed under 'On My Mac'. The facility is still available in iCal for such calendars, but the problem is that it has to be published to a CalDav server because MobileMe, which used to take the published files and turn it into a web page, is not longer available. It's assumed in the Help that you are going to be running such a server yourself, which obviously requires a fair standard of technical knowledge. It's been claimed that Box.net can do this but I've seen complaints that it doesn't work.
    Sharing, which you can do with iCloud calendars, makes the calendars available for others to subscribe to in a CalDAV client - iCal itself is such a client, and you can also do this with Google calendar - this does require the recipient to have a Google account. The process with iCloud is described in this page and the pages following:
    http://help.apple.com/icloud/#mm6b1a8694
    BusyCal has various sharing options and there is a full user guide available here:
    http://www.busymac.com/busycal/userguide/index.html

  • Outlook 2013 is not publishing calendar to webdav using settings successful with Outlook 2010

    I am successfully publishing availability data (an ics file) to a webdav server, using Outlook 2010. The format of the URL is https://[domain]/public_html/calendar/
    When I use the same URL in Outlook 2013, it returns the message "Contacting web server" and then "The upload to 'Calendar' failed. Failed to sign in."
    Of course, there's no sign in dialog box provided. So, I change the URL to the format https://[login name]:[password]@URL/public_html/calendar/
    There is no "Contacting web server". Instead, Outlook goes directly to the error message "The upload of 'Calendar' failed. The calendar was not published because the connection to the server failed. Make sure your computer has a network connection
    and that you typed the correct Web address."
    There's nothing wrong with the connection; I've tried this and its failed many times. So, I conclude that Outlook 2013 doesn't like a web address that includes the login credentials.
    What changed with Outlook 2013 that prevents it from publishing to the same location successfully published to, by Outlook 2010?

    This problem continues, and it's a showstopper.  Honestly, this is so easy to reproduce and so fundamental that I'm surprised that Microsoft hasn't done anything with it.  Tony Chen, your answer isn't really an answer
    at all.  Why mark it as an answer? 
    Here are the specifics.  I have Microsoft Outlook 2013 (15.0.4667.1000) MSO (15.0.4667.1001) 32 bit (part of Microsoft Office Professional Plus 2013).
    In my calendar, I select "Publish Online > Publish to WebDAV Server".  I then have a dialog box that requires that I enter the publishing location URL.
    I enter a URL (which is my company's internal WebDAV server URL), in the same form as the example given:
        https://mycompany.com/calendars/
    and then I click "Advanced".  I select "Automatic Uploads: Upload updates periodically", with the Update Frequency checkbox checked (to select the server's recommended settings).  I click "OK", and my calendar is published
    periodically to the WebDAV server, as expected.
    If I monitor traffic with fiddler, I can see that outlook periodically does a PROPFIND and then PUT of my ical data to https://mycompany.com/calendars/myfile.ics.
    Next, suppose I want to change the publish settings in some way.  So in my calendar, I select "Publish Online > Change Publishing Options".
    Now, the "Location" text box has the previous URL I entered,
    plus the name of my .ics file.  So it looks like this in the text box:
        https://mycompany.com/calendars/myfile.ics
    I click "OK", and I get an error popup that says "The address you typed is not valid.  Check the address, and try again."  Note that I didn't type the address at all - it is what outlook put there for me.
    As a side note:  in Outlook 2010 the URL shown is the same (i.e., the URL includes the .ics file) but the text box is inactive (greyed out) and the "OK" button does not produce this error message).
    So, already something has gone very wrong.  In order to try to work around this, I then edit the text box to remove the .ics file (i.e., to put the URL back to what I originally typed,
    https://mycompany.com/calendars/).  But now, one of two things will happen, neither of which is ok.
    In some cases, Outlook will continue to publish periodically, but when it does, it will do a PUT to
    https://mycompany.com/calendars/ - without the myfile.ics suffix.  Naturally, this fails, because the server doesn't know what .ics file it's supposed to put the PUT payload into.
    In other cases, Outlook ceases publishing altogether.  It will do a PROPFIND to the URL, but then no PUT.  I have not yet figured out the circumstances of these two failure modes, so I'm not yet sure why one happens and not the other.  But
    they are both wrong.
    So, the long and short of this is, you cannot change publishing options in Outlook 2013, because the functionality (which worked fine in Outlook 2010) is just plain broken.  I have given the steps required to reproduce this problem, and it seems like
    it would be easy to address.  Yet it has been sitting for 1.5 years with no fix.  What will it take to get this fixed?  Microsoft people, please advise - if I can get it fixed by opening a support case then please say so; paying is not an obstacle. 

  • What is required for FM 9.0 to support WebDAV-enabled server functionality?

    I've read the FM 9.0 Help about WebDAV (Web-based Distributed Authoring and Versioning) but when I asked some of our IT folks about it, no one knew the answer or even what WebDAV is.
    We tried using a WSS server for some of our FM 7.2 files but it was not a successful experiment, as some of our files disappeared. We've just begun using a MOSS server, although to me it seems that is probably more friendly to Microsoft Office docs than to Adobe products. After the problems on the WSS server, we reverted to our previous version-control method using VSS -- however, with FM 9.0 having check-in/check-out options, I'm hopeful we can yet use a SharePoint server and HTTP protocol to access and maintain version control of our FM files.
    I posted a question about FM on SharePoint last year and response seemed to indicate others had experienced problems using SharePoint for version control of FM files (someone told me to think in terms of "SharePain", which made me smile through my tears). With FM 9.0, have things improved? Am I mixing apples and oranges by using SharePoint and WebDAV in the same sentence? How can I find out if our SharePoint servers are (or can be) "Web-DAV enabled"?
    As always, your expertise is greatly appreciated.
    Cheers,
    Gay

    Hi Arnis,
    Thanks for the links -- I had seen a couple of them but was put off by the references to CMS since we don't use a "real" CMS like Documentum.
    I read lots of the FAQs at www.webdav.org and also found a couple of excellent sources:
    For IIS 6 on Windows Server 2003: Mitch Tulloch's tutorial at http://www.windowsnetworking.com/articles_tutorials/WebDAV-IIS.html
    For IIS 7 on Windows Server 2008: http://learn.iis.net/page.aspx/350/installing-and-configuring-webdav-on-iis-7
    We won't be upgrading to the latter till later this year so will first go with IIS 6 on Server 2003 and see how we fare. Apparently we *should* be able to check out, open, edit and save a file on the server, but although SharePoint also offered that functionality, it apparently was limited to Microsoft products. So I won't celebrate prematurely -- but as always, my fingers are crossed!
    ~~Gay

  • Publishing Calendar Group to .Mac Causes Duplications

    I am running iCal 2.0 in Tiger. I have three calendars under the Calendar group "Published". I then publish the "Published" calendar group to my .Mac account. Every time I refresh the publication (which happens automatically with "auto-refresh") it duplicates every entry. This is repeatable so I can have four, five, etc. instances of the same event published. If I unsubscribe and republish, it starts over again.
    This only affects the published calendars on the .Mac server (ical.mac.com), not any local or .Mac Sync calendars.
    I'd appreciate any help.

    I seem to have this working now, G5 and Powerbook both running the same iCal calendar which is syncronised. Both machines have publish switched on along with auto update.
    One thing I noticed while testing this evening, the names I was originally publishing under were things like "Study Calendar" or "Myweb.net Calendar", when published using these types of names (spaces and punctuation) the .mac website calendar always had a last updated time of 1970.
    When I republished the calendar using a single word name like "Calendar", the published date was correct on the website.
    Once I saw the publish day as being correct, I turned on auto update and proceeded to make changes in iCal on both the PB and the G5. All the changes thus far have been syncronised correctly between the machine AND with the website without duplication.
    I am not sure if this is a long term solution as I've only been testing for 10 minutes or so. Perhaps the duplications will come back after a while but its certainly something to look into if your publishing your calendar with names longer than one word or with punctuation.
    Cheers
    Zeni

  • Publish iCal to OS X Server 10.3.9 with WebDAV enabled--not working

    I've published iCal calendars to other servers with WebDAV enabled, but so far have not been able to publish to OS X 10.3.9 server with WebDAV enabled.
    Error message is: Calendar could not be published. This access has been forbidden by server.
    I'm using an administrative username and password to eliminate any question about access to specific directories, I've ensured that the site is WebDAV enabled using the OS X Server Admin gui (so, web/sites/domain name/ editing section, under Options). I've been unable to find any more detailed instructions on publishing to OS X server. Any suggestions, webpage tutorials, etc., greatly appreciated.
    FWIW, I suspect the folder location for where the .ics file would go on the server may be the issue. The web content is in Library/WebServer/foldername and this is where I put the calendar folder.
    Marcus Duke
    Webmaster/Info Specialist
    Washington Sea Grant
    UW School of Aquatic & Fishery Sciences
    G4 1gHz   Mac OS X (10.3.9)  

    Hi Jovan
    I don’t think its a problem with 10.3 server as such. You’ve got to remember that 10.3 is getting on a bit. As far as supporting the latest drive sizes Apple as well as other interested parties would devote their energies in supporting the latest operating systems. For example Microsoft have recently released Vista. Most interested parties will get on board the Vista bandwagon and start developing and writing drivers and software for that rather than XP. After a while you will start to see less and less being developed for the older operating system. I think this is just one of those times.
    Tony

  • New Outlook 2013 User Unable to Publish default Calendar to WebDAV server

    We have a new user. Created new Active Domain account, made domain account administrator on local machine and setup Outlook 2013 with our Go Daddy pop and smtp email settings.
    Email messaging works fine.  When I try and share the default calendar there is no dialogue box for our WebDAV server.  Again, I right click the default calendar and see "Share", "Publish to a WebDAV Server..." but
    nothing after that.  The box for the server location and sharing details just does not come up.
    I created a new calendar and can share that.  A copy of the default calendar can be published, but not the default calendar itself.
    Any ideas? 

    Was able to finally get the default calendar to publish. Seems that it had something to do with how many shared calendars the user was subscribed to. The user had accepted about a dozen calendar invitations.
    Deleting the calendar subscriptions allowed the default calendar to publish to the WebDAV server.
           

  • Publish iCal Local Account Calendar on OS X Server

    I'd like to publish my iCal calendar (iCal>Calendar>Publish...>Publish on: A private server) on my OS X Server 10.6.7 ().
    Whenever I attempt to do this using my local account on tthe server, I get the error:
    http://username@domain_name/Home.ics is not a location that supports this request.
    I've tried all the obvious stuff: turning off the firewall, sanity checking the iCal service authentication settings, everything obvious. I believe that this is an authentication issue for local accounts on OS X Server. Because the server is set up as a standalone (i.e., no network accounts, all local accounts), Open Directory is turned off, and there's no Kerberos authentication that I'm aware of.
    Would someone please tell me how how to publish iCal calendars of local accounts on OS X Server?

    According to iCal Server Administration, OS X Server requires an Open Directory account, so you cannot publish your local account's iCal calendar.
    You can, however, use iCal itself and a modification of the OS X Hint "Publish iCal calendars with local WebDAV server" to publish local account calendars.
    0. Server Admin>Web>Sites Turn on the Web with an enabled host name. Make sure that WebDAV is enabled under Server Admin>Web>Sites>Options. Enable SSL with your server's certificate under Server Admin>Web>Sites>Security to ensure that your personal calendar information is SSL encrypted over the web.
    1. Append this directive to the end of the file /private/etc/apache2/httpd.conf:
    Include /private/etc/apache2/other/*.conf
    and make sure that there's no conf file in ./other that you may not wish to load, such as httpd-userdir.conf. Move these to *.conf.original or some such if necessary.
    2. Create the file /private/etc/apache2/other/httpd-webdav.conf with the contents:
    # WebDAV configureation for Publishing local account iCal calendars
    #  Based in part on Mac OS X Hint "iPublish iCal calendars with local WebDAV server Apps"
    # http://hints.macworld.com/article.php?story=20020912065811863
    # copied from /etc/apache2/sites/0000_any_443_myserver.conf
    # which is automatically generated by Server Admin>Web
    # No need to replicate these directives here, so comment out
    #<IfModule mod_dav.c>
    #       DAVLockDB "/var/run/davlocks/.davlock100"
    #       DAVMinTimeout 600
    #</IfModule>
    <IfModule mod_dav.c>
      <Directory "/Library/WebServer/Documents/webdav">
        DAV On
        AuthType Digest
        AuthName 'WebDAV'
        AuthDigestFile /private/etc/apache2/httpd/.htdigest
        AuthGroupFile /dev/null
    #    <LimitExcept GET HEAD OPTIONS>
          require valid-user
    #    </LimitExcept>
      </Directory>
    </IfModule>
    3. Create the apache htdigest authentication file:
    $ mkdir /private/etc/apache2/httpd
    $ chmod 0755 /private/etc/apache2/httpd
    $ touch /private/etc/apache2/httpd/.htdigest
    $ chmod 0644 /private/etc/apache2/httpd/.htdigest
    $ htdigest /private/etc/apache2/httpd/.htdigest WebDAV username
    Adding password for username in realm WebDAV.
    New password: md5 hashed password
    Re-type new password: md5 hashed password
    4. Create the WebDAV directory:
    $ mkdir /Library/WebServer/Documents/webdav
    $ chown www:www /Library/WebServer/Documents/webdav
    $ chmod 0755 /Library/WebServer/Documents/webdav
    $ mkdir /Library/WebServer/Documents/webdav/iCal
    $ chown www:www /Library/WebServer/Documents/webdav/iCal
    $ chmod 0755 /Library/WebServer/Documents/webdav/iCal
    and sanity check that the OS X Server davlocks directory /var/run/davlocks exists [it should!] and has www:www ownership with permissions 755 [it should!].
    5. Sanity check your apache config files:
    $ apachectl -t
    should yield "Syntax OK". Then Server Admin>Web>Stop and Start to restart your web server with the new configuration.
    5. Under your local account on OS X Server, iCal>Calendar>Publish... Publish on a private server with the URL:
    https://osxserver/webdav/iCal
    using OS X Server's local account username/password. Success will be reported with a URL of your calendar on the server.
    6. Under another client account from which you wish to subscript to your OS X Server local account's Calender, iCal>Calender>Subscribe... Enter the URL on OS X Server. You will be prompted for the htdigest name/password pair you created above -- enter this, not the username/password of your local account on OS X Server. Even though you should be protecting this channel with SSL and md5, don't reuse your username/password to access the WebDAV directory you created. You will now be subscribed to your local account's iCal Calendar residing on OS X Server.

  • Publish & Subscribe to Calendars on WebDAV?

    Hi all,
    I have looked through the discussions for the answer to this question, but it seems that everyone is saying "use .Mac."
    My small business uses iCal and we publish our calendars to our XServe (with WebDAV enabled).
    Does anyone know how others can publish items to a "shared" calendar as well? For example, suppose we have a "meetings" calendar that everyone could edit from any computer.
    Any ideas?

    Hi Amir,
    A few tutorials on enabling WEBDAV.
    http://hcs.harvard.edu/~westin/webdavforical.php
    http://www.shawnwall.com/teach/webdav-ical.php
    http://astcomm.net/hints/WebDAV/
    Or Google for more.
    http://www.google.com/search?q=enablewebdav+osx
    Choose the one you find easiest to follow.
    Best wishes
    John M

  • Cannot publish calendar

    I cannot publish a calendar to my own server.
    I get the following error:
    http://[email protected]/ical/Paul.ics is not a valid location for this request
    In the base URL I entered http://www.xxx.co.uk
    I am unsure why it is showing the @ because I did not add it.

    For iCal to be able to publish the server needs to be WebDAV enabled. See <http://www.webdav.org/> for more about WebDAV. WebDAV allows users to collaboratively edit and manage files on remote web servers.
    Do you have control of the server? If not, try asking whoever does whether the server is WebDAV enabled and, if so, instructions for setting up a WebDAV enabled folder on it.
    Best wishes
    John M

  • Impossible to publish iCal on Webdav Apache2

    The OS X Server is set-up using Apache2 and the webdav was correclty configured as discribed in the following useful pages:
    http://httpd.apache.org/docs/2.0/mod/mod_dav.html
    http://tldp.org/HOWTO/Apache-WebDAV-LDAP-HOWTO/
    I have no problem to access the webdav folder by ftp, browser, "connect to server" or to read the content with iCal after having copied the ics fiels.
    But it is impossible to publish an ical to that webdav folder.
    (Problem of authentification).
    The compliance test with Litmus is ok except for the "cond_put .." which Failed.
    Client: OS X 10.4.8
    iCal: 2.0.3
    OS X Server 10.4.8
    Any idea why it is impossible to publish Calendars?

    I found the solution:
    It work fine using ../davlocks/DAVLock for the DAVLockDB parameter.
    But the davlocks folder must have the rights to 777 (chmod -R 777 davlocks/)
    Hope this help.

  • Issue with Outlook 2013-Notifications from published Calendar

    Hi Every body,
    I'm setting up for my little company published calendars on a Webdav servers (i'm using IIS on a 2003 server and Office 2013).
    Publishing calendar works fine so far.
    But i'm facing up a real issue:
    When a user add other's published calendar the first user will also recieve Calendar alerts (appoitement alerts) from the added calendars (others users). Since i have arround 10 Shared calendar it's very frustating for users to be disturbed because of other's
    calendars.
    I've been looking for a way to disable those alerts but i can't find a way. on the Outlook settings. 
    (I also want to keep personal alerts up)
    Please help me i'm becoming very frustaded.
    Best regards 
    Fred

    Well that's not the same calendar in outlook it's a realy different calendar that you get from your webdav server.
    so i remind the whole process just to be clear =)
    10 differents users are publishing their own outlook calendar on the webdav server.
    So there is 10 differents ICS calendar into the server. But remember ICS calendar are copy from the originals calendar they need to be kept up to date.
    Then some users pick the calendars they need from the server and add it into they own outlook.
    in this way it appears as a whole different calendar in outlook.
    When you publish a calendar from outlook,(right clikc onto the calendar => share => publish into webdav server) your have 3 ways to publish it, 3differents options. I can't translate properly since my version is in french. But just to make it short:
    1)
    The first way to publish it is not useful in my case because it doesn't provide enougth information into my ics calendar. about my appoitements.
    2)
    The second option looks good to me because it does'nt provide VALARM option Inside the ICS calendar.
    But  with this option the message inside appoitements are missing.
    3)
    The third option Include everything about the appoitement (and the VALARM). An thats actualy my problem.
    And Yes i'm editing the ICS file that what make me understood how the whole process works.

  • ICal won't update published calendar

    I have a published calendar on .Mac and when I update in iCal, it won't update on my .Mac account. Also it shows that the published date is Dec 31, 1969. I have checked my date and time on system preferences. I have deleted and recreated this calendar, and it has not solved the problem. I have even unpublished and published several times, all to no avail. I have iCal 2.0.2 installed. Anyonw else come across this problem?
    Thanks.

    When you publish, is "Publish changes automatically" checked? This would explain why updates don't happen. Also in .Mac system preferences under the "Sync" tab, there is a choice of how often to sync. Even if this is set to "Automatically" the sync isn't instant. Check this setting. I don't know if it affects published calendars or not, but worth checking nonetheless.
    I wonder if in the Date and Time system preference ("Date & Time" tab) you have "Set date & time automatically" Checked?
    Mine publish fine, no problem: http://ical.mac.com/dancingbrook/Social
    Still no solution for web To Dos though perhaps via a webDAV server? Try:
    http://www.icalx.com/
    Also, can I assume you've tried trashing your ical preferences? ~/Library/Preerences/com.apple.iCal.plist

  • Publishing calendar changes automatically fails

    Switching from iCal on 10.4 to iCal 3.3 on 10.5.3 I've hit a problem publishing an iCal calendar to a "private" server (not .mac). When I go to the "Change Location" dialogue and hit the Publish button, all is fine. But automatic updates fail (Code 30). So to keep my published calendar up to date I have to remember to go to "Change Location" and hit the Publish button, which is not so great.
    On the server side I'm using PHP iCalendar. It all worked fine on 10.4.

    I have the same problem! I publish a cal to my server (Apache WebDav) and it works when I publish it initially but subsequent saves do not get updated. I have to do it manually which is a PITA.
    Krreagan

Maybe you are looking for