From: KDC David on
A user has their outlook configured to synchronize with a calendar hosted on
our SharePoint site (WSS 3.0). Recently, it stop syncing. The following error
appears in the Outlook Send/Receive Progress.

Task: 'SharePoint' reported error (0x80004005): 'An error occurred in this
SharePoint List ( Name of Calendar)- Try updating the folder again. If the
problem continues, contact the SharePoint site administrator - HTTP 500. The
server returned the follow error message: Exception of type
'Microsoft.SharePoint.SoapServerExeception' was thrown.'

Only a single user is experiencing this problem, while others have no
issues. Any ideas of what's causing this?
From: Diane Poremsky [MVP] on
That's a question for the SPS experts - but I would try removing the
subscription and resubscribing.

--
Diane Poremsky [MVP - Outlook]
Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com

Outlook Tips by email:
mailto:dailytips-subscribe-request(a)lists.outlooktips.net

EMO - a weekly newsletter about Outlook and Exchange:
mailto:EMO-NEWSLETTER-SUBSCRIBE-REQUEST(a)PEACH.EASE.LSOFT.COM

Do you keep Outlook open 24/7? Vote in our poll:
http://forums.slipstick.com/showthread.php?t=22205

"KDC David" <kdcdavid(a)discussions.microsoft.com> wrote in message
news:42A5E8E3-CC5C-4691-8619-A1029A111181(a)microsoft.com...
> A user has their outlook configured to synchronize with a calendar hosted
> on
> our SharePoint site (WSS 3.0). Recently, it stop syncing. The following
> error
> appears in the Outlook Send/Receive Progress.
>
> Task: 'SharePoint' reported error (0x80004005): 'An error occurred in this
> SharePoint List ( Name of Calendar)- Try updating the folder again. If the
> problem continues, contact the SharePoint site administrator - HTTP 500.
> The
> server returned the follow error message: Exception of type
> 'Microsoft.SharePoint.SoapServerExeception' was thrown.'
>
> Only a single user is experiencing this problem, while others have no
> issues. Any ideas of what's causing this?