Problems connecting Sharepoint Calendars to Outlook 2010
We're running MOSS 2007 and have our company directory on there. So far it's connected pretty seamlessly to everybody's Outlook. But we deployed Outlook 2010 on a couple test stations, and now we're getting these errors when trying to connect a Sharepoint Calendar to them: Task 'SharePoint' reported error (0x80040102) : 'Outlook cannot connect to the SharePoint List (Company Directory). The server may not be reachable from your location. Contact the SharePoint site administrator for more information. HTTP 0.' Task 'SharePoint' reported error (0x80070005) : 'You do not have permission to view this SharePoint List (Intranet Site - Company Directory). Contact the SharePoint site administrator. HTTP 401.' Anybody know what's causing these or how to overcome them? I tried searching on the web with no success.
July 7th, 2010 3:15am

We have been syncing Sharepoint Contacts just fine with previous versions of Outlook (up to 2007). But we recently deployed Outlook 2010 on a couple test machines, and now Sharepoint won't sync to them at all. Either we get the error: "error (0x80070005) : 'You do not have permission to view this SharePoint List HTTP 401" or "error (0x80040102) : 'Outlook cannot connect to the SharePoint List. The server may not be reachable from your location. Contact the SharePoint site administrator for more information. HTTP 0." I've checked the related solutions but it doesn't seem like the other posts have a relevant solution. Like I said, Outlook 2007 and 2003 work perfectly with Sharepoint.
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2010 10:36pm

FYI I did try changing the alternate access mappings. Right now the default is https://home.domain.com , with alternate mappings at http://home.domain.com and http://home for internal users. I've tried rearranging these any way possible and I now get this error in Outlook 2010: Task 'SharePoint' reported error (0x80040102) : 'Outlook cannot connect to the SharePoint List (Intranet Site - Company Directory). The server may not be reachable from your location. Contact the SharePoint site administrator for more information. HTTP 0.' If I don't get a reply in 24 hours I'll have to start a paid support case.
July 8th, 2010 11:31pm

Hi Ron, The error message could mean a couple of things. 1. IIS is rejecting the calls made by Outlook. - Check the IIS logs and look for correspendign requests with the 401 codes. If there are none then check the following check the next item. 2. When you do a connect to Outlook, you should prompted before it proceeds further. In the prompt it should display link similiar to this: stssync://sts/?ver=1.1&type=calendar&cmd=add-folder&base-url=http%3A%2F%2Fmoss&list-url=%2FLists%2FCalander%2F&guid=%7B8bf9cc47%2Db53f%2D4371%2Da12c%2Dbea5f9524fd1%7D&site-name=Live%20MOSS%20page&list-name=Calander Would it be possible to show the link your getting? Regards, Savoeurn Va Microsoft Online Community Support
Free Windows Admin Tool Kit Click here and download it now
July 8th, 2010 11:59pm

From: Home Program: Microsoft Outlook Address: stssync://sts/?ver=1.1&type=contacts&cmd=add-folder&base-url=http%3A%2F%2Fhome&list-url=%2FLists%2FCompany%2520Directory%2F&guid=%7Bec9585ef%2D7b62%2D4cd7%2D9dc2%2D0f1da5cf0fdf%7D&site-name=Intranet%20Site&list-name=Company%20Directory Checking up on the other thing now.
July 9th, 2010 12:37am

I have a feeling this is a Windows 7 issue rather than a Outlook 2010 issue ... the Outlook 2010 computers are both Windows 7 computers. But when I tried running this on Outlook 2007 on a Windows 7 computer, I get the same issue.
Free Windows Admin Tool Kit Click here and download it now
July 9th, 2010 3:01am

Hi, I’ve actually tested this on W7 x64 with Office 2010 Pro against a MOSS 2007 SP2 build 6535 site and it works just fine. I replicated your list and pulled out the connection section from the W7 box. stssync://sts/?ver=1.1&type=contacts&cmd=add-folder&base-url=http%3A%2F%2Fmoss&list-url=%2FLists%2Fcompany%2520directory%2F&guid=%7B313daf5b%2Dd471%2D45fa%2D96b9%2Da9a89f9d3be9%7D&site-name=Live%20MOSS%20page&list-name=company%20directory Here is what I would do next. On the W7 box with 2010, get a copy of Network Monitor and have it running before you hit the Connect to Outlook option. After you get the failure stop the Netmon. In the Display Filter box putt in the following “http” In the Frame Summary box look for Posts to _/vti_bin/lists.asmx in the Description column. Here is a sample of it working: 506 1:48:48 PM 7/9/2010 11.8061492 OUTLOOK.EXE 192.168.1.33 moss.sav.local HTTP HTTP:Request, POST /_vti_bin/lists.asmx , Using NTLM Authorization {HTTP:16, TCP:13, IPv4:11} 507 1:48:48 PM 7/9/2010 11.8075323 OUTLOOK.EXE moss.sav.local 192.168.1.33 HTTP HTTP:Response, HTTP/1.1, Status: Unauthorized, URL: /_vti_bin/lists.asmx {HTTP:16, TCP:13, IPv4:11} 508 1:48:48 PM 7/9/2010 11.8081285 OUTLOOK.EXE 192.168.1.33 moss.sav.local HTTP HTTP:Request, POST /_vti_bin/lists.asmx , Using NTLM Authorization {HTTP:16, TCP:13, IPv4:11} 509 1:48:48 PM 7/9/2010 11.8082718 OUTLOOK.EXE 192.168.1.33 moss.sav.local SOAP SOAP:xmlns="http://schemas.xmlsoap.org/soap/envelope/" {HTTP:16, TCP:13, IPv4:11} 512 1:48:48 PM 7/9/2010 11.8272521 OUTLOOK.EXE moss.sav.local 192.168.1.33 SOAP SOAP:xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" {HTTP:16, TCP:13, IPv4:11} 543 1:48:48 PM 7/9/2010 11.8493843 OUTLOOK.EXE 192.168.1.33 moss.sav.local HTTP HTTP:Request, POST /_vti_bin/lists.asmx {HTTP:16, TCP:13, IPv4:11} 544 1:48:48 PM 7/9/2010 11.8498240 OUTLOOK.EXE 192.168.1.33 moss.sav.local SOAP SOAP:xmlns="http://schemas.xmlsoap.org/soap/envelope/" {HTTP:16, TCP:13, IPv4:11} 550 1:48:48 PM 7/9/2010 11.8716273 OUTLOOK.EXE moss.sav.local 192.168.1.33 SOAP SOAP:xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" {HTTP:16, TCP:13, IPv4:11}Regards, Savoeurn Va Microsoft Online Community Support
July 9th, 2010 10:00pm

change the alternet access mapping under operation in central administration page make the default url of your site which has being created while installation of moss. when you have installed moss with standalone it by default creates on port 80 your New webApplication, mysite. Even ssp get created by default under SSP. so, do a change of default url as http://moss which should be your host name. eg : my hostname is "moss" and i do browsing by my hostname and url worked fine. I configured alternet access mapping by name http://home under intranet zone for url http://moss site. I browsed the url under Internet explorer http://home and open my list library, clicked on navigation pane under action select connect to outlook, it asked me to trust the url i selected ok it worked fine my site list got integrated and sync properly with outlook 2010.
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2010 8:02pm

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

Other recent topics Other recent topics