Problems with calendars from outlook 2007: Error 0x80070005 error; HTTP 302
Ok I am able to add a sharepoint calendar to outlook, and pull the calendar down with no issues, but if I try to add an appointment from outlook I get the following error when i send and recieve: "0x80070005 error: "You do not have permission to view the Sharepoint List (ERP Calendar). Contact the Sharepoint Site administrator. HTTP 302" I have full admin rights to the list, and I am able to add items via the browser. Any one deal with this before? Cheers.
June 23rd, 2008 5:32pm

I'd like to add that I am able to complete a send and recieve from oulook and add a calender item if I connect directly to one of the WFE's, vs. our load balencer (Juniper Redline). Is there any thing you guys have delt with in the past in properly setting up a load balencer / firewall to allow outlook to add calender items?
Free Windows Admin Tool Kit Click here and download it now
June 24th, 2008 6:18pm

What version of outlook and Service pack are you using? Is the site listed in your IE "Intranet" Zone?
June 25th, 2008 3:56am

I had the same problem and for me worked this:MOSS admin -> alternate access mappings and from there internal URL and external URL to the sameHTTP 302 is redirection code and in sharepoint alternate accessmapping default zone was http://intranet and internet zone was https://intranet.domain.com Changed default zone to https://intranet.domain.com and problem solved for me..PS! also did redirection in IIS from http://intranet to https://intranet.domain.comPPS! I wanted to use HTTPS you don't have to..Raimo
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2008 11:05pm

Raimo,WHen you change the default zone to https:// , is the crawl is working? I just wondering it is not.
August 15th, 2008 1:57pm

I put a network monitor on my workstation and discovered the following: Scenario 1: Single WFE with NetBIOS name of machine in both internal and external URLs of AAM. IIS requires SSL (and client certs, too!). URL of Web app: https://machinename. URL of site: https://machinename/sites/sitename. Go into https://machinename/sites/sitename with a browser and pick any list, say events. Click on ActionsConnect to Outlook. Netmon shows https session between Outlook and Machinename to perform initial download of Events. Go into Outlook and add an appointment to the SharePoint Events list. Netmon shows a bizarre sequence. Outlook tries to open an http session with the site to pass his SOAP request. IIS dutifully returns http status 403, The page must be viewed over a secure channel. Outlook says, OK, here is the same SOAP request on https. This one succeeds. Thereafter, Outlook remembers that https must be used and never tries http again. Question: Why doesnt Outlook remember from the initial setup that a secure channel is indicated in the URL? The https URL is even in the Outlook pop-up message asking me if I really want to link to the list. Scenario 2: Multiple WFEs with an F5 on the front. DNS maps the site internal/external DNS name to the F5 pool. IIS requires SSL. URL of Web app: https://dnsname. URL of site: https://dnsname/site/sitename. The F5 has a rule on it that redirects http traffic to https (convenience for users who forget to use https and/or bookmarks). Go into https://dnsname/site/sitename with a browser and pick any list, say events. Click on ActionsConnect to Outlook. Netmon shows https session between Outlook and Machinename to perform initial download of Events. Go into Outlook and add an appointment to the SharePoint Events list. Again, Outlook tries to open an http session with the site to pass his SOAP request, but this time the F5 (could be ISA Server in your case) returns the http status 302, temporary redirection. Outlook cant handle it and spits out the you do not have permissions error. Scenario 3: Same as scenario 2 except the default zone has an additional internal URL for Project Server that uses http (its a long story) that by-passes the F5. The new possible site URL is http://projectserver/sites/sitename. Go into https://projectserver/site/sitename with a browser and pick any list, say events. Click on ActionsConnect to Outlook. Netmon shows https session between Outlook and Machinename to perform initial download of Events. Go into Outlook and add an appointment to the SharePoint Events list. Again, Outlook tries to open an http session with the site to pass his SOAP request, but this time, it succeeds! Outlook is able to reach the site through the alternate internal URL! From viewing the packets, Outlook KNOWS that he should be trying projectserver/site/sitename right from the start of the send/receive. He must pick up on that from the initial download, which being in https, netmon cannot decipher. Question: How is Outlook smart enough to know he has a URL that will work with http but not smart enough to know he is supposed to be using https?
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2009 7:59pm

does this apply to wss 3.0 im running wss 3.0 and outlook 2007. are those 2 even supposed to synchronize by design? im getting the same 0x80070005 errord3v
April 24th, 2009 8:46am

Well many of the users in my company experienced the similar problem with the error "you do not have permission to view this sharepoint list contact sharepoint administrator http 302" only for the users who were using windows Vista and Windows 7 not with Windows XP. So it has to do with the windows security. I tried the method and it worked for me as well as my users although this is not the permanent solution, It can be used. Open Internet Explorer with Administrator privilege i.e " Right click on internet Explorer and click on Run as Administrator" and open Sharepoint in the new opened browser and It works... I hope this will work for others as well...
Free Windows Admin Tool Kit Click here and download it now
April 28th, 2011 6:56am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics