One user can't write to the SharePoint team calendar
This is a weird one. I have one user, member of a department with 7 other users in it. When this one user sends an email to the mail-enabled SharePoint Team Calendar, the event never gets written in the calendar. Everyone else in this department can send an email to the calendar and the event shows up. The user is a member of the same group everyone else is. It doesn't appear to be a permission issue, because he can drag events from his own calendar to the SharePoint Team Calendar within Outlook, and the event gets written there without issue.It doesn't seem to be an Exchange 2007 issue, because when I look at the message tracking log, a successfully sent email to the Shared Team Calendar and the email sent from the one user to the SharePoint Team Calendar that doesn't make it to the calendar looks exactly the same.Any ideas? I've also given Full Control explicitly on the calendar to this user, with no change.
February 13th, 2010 2:28am
Hi Donia,You can track this thing out using SharePoint Logs or your machine event log. You can check event viewer from Administrative Toolsyou can check logs from 12 hive. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LogsYou can turn on Event Throtlling feature of Incomming email to Verbose and then ask the person to send email again and then you can check the recent log to see the actual error. Once you see something you can post it here.I hope this helps.J:Jerry
February 13th, 2010 3:44pm
Thanks, had the user send two meeting requests to the support calendar, both were not written (as he still cannot write anything to it).Here is the verbose trace log with the only errors that showed up for email, both at the same time he sent the meeting requests: User sent meeting request to calendar at 8:51AM: 02/18/2010 08:51:27.34 OWSTIMER.EXE (0x0814) 0x1BF4 Windows SharePoint Services E-Mail 6873 Warning An error occurred while processing the incoming e-mail file C:\Inetpub\mailroot\Drop\86d3c93401cab0ba0000002b.eml. The error was: Value cannot be null. Parameter name: stream. 02/18/2010 08:51:27.34 OWSTIMER.EXE (0x0814) 0x1BF4 Windows SharePoint Services E-Mail 6871 Information The Incoming E-Mail service has completed a batch. The elapsed time was 00:00:00.1400952. The service processed 1 message(s) in total. Errors occurred processing 1 message(s): Message ID: <3035D3C0E0C8924EB8AC9207426A09580D08B71DE8@qhrmail01.QuadrantHR.com> User sent meeting request to calendar at 8:52AM: 02/18/2010 08:52:27.37 OWSTIMER.EXE (0x0814) 0x10EC Windows SharePoint Services E-Mail 6873 Warning An error occurred while processing the incoming e-mail file C:\Inetpub\mailroot\Drop\a2cd063c01cab0ba0000002c.eml. The error was: Value cannot be null. Parameter name: stream. 02/18/2010 08:52:27.37 OWSTIMER.EXE (0x0814) 0x10EC Windows SharePoint Services E-Mail 6871 Information The Incoming E-Mail service has completed a batch. The elapsed time was 00:00:00.1300884. The service processed 1 message(s) in total. Errors occurred processing 1 message(s): Message ID: <3035D3C0E0C8924EB8AC9207426A09580D08B71DEF@qhrmail01.QuadrantHR.com> No errors in the app or system logI appreciate the help--can't see anything different about this user, he has no computer/sharepoint issues otherwise and he needs to write to the support calendar as he is the manager. Thanks!
February 18th, 2010 9:00pm
Please take a look at these KB and thread:http://www.eggheadcafe.com/software/aspnet/29871966/incoming-email-problem-.aspxhttp://support.microsoft.com/kb/926891As mentioned in the thread: "If you're fast enough you can open the mesage in the drop box and you should see two attatchments. My problem was that the attachement was being stripped off before it hit the moss drop folder", you can check whether the KB will be useful for you by openning the eml file in C:\Inetpub\mailroot\Drop folder to check whether there is attachment in it. Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact firstname.lastname@example.org
February 19th, 2010 8:07am
Hi:Thanks for the info, but that did not help us out, no one else has this issue either: 02/19/2010 13:55:27.36 OWSTIMER.EXE (0x0814) 0x1D08 Windows SharePoint Services E-Mail 6873 Warning An error occurred while processing the incoming e-mail file C:\Inetpub\mailroot\Drop\3c18475a01cab1ae00000034.eml. The error was: Value cannot be null. Parameter name: stream. 02/19/2010 13:55:27.36 OWSTIMER.EXE (0x0814) 0x1D08 Windows SharePoint Services E-Mail 6871 Information The Incoming E-Mail service has completed a batch. The elapsed time was 00:00:00.2101428. The service processed 1 message(s) in total. Errors occurred processing 1 message(s): Message ID: <3035D3C0E0C8924EB8AC9207426A09580D08C15652@qhrmail01.QuadrantHR.com>
February 20th, 2010 1:07am
OK, this is really bizarre and I'm not sure how this is happening:I logged on to another computer with this same user's username and passwordI sent a meeting request to the Optimed Support calendarIt shows upSo this is either computer or perhaps the local computer profile related.I then deleted the Outlook profile on his computer that cannot write to the SharePoint calendar, and recreated it. Still cannot write. I can log into other computers with his username and password, let Outlook autoconfigure with his Outlook settings and he can send meeting requests to the SharePoint calendar.Back to his own computer, meeting requests are sent, but are never written to the SharePoint calendar.
February 20th, 2010 2:30am
Hi Donia,Check this out.http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/5c651812-8808-4214-b03f-40d62f3943daTo confirm that this works on one computer but not other read the thread below. Just read the last reply.http://www.eggheadcafe.com/software/aspnet/31723023/incoming-email-issue.aspxA possible solution can also be http://sharepointjoe.blogspot.com/2007/05/moss-2007-smtp-and-pop3.htmlSo many people are looking to fix it. J:Jerry
February 20th, 2010 11:32am
Hi,The first link you gave me in your answer doesn't seem to have anything to do with the issue I am having unless I missed something.http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/5c651812-8808-4214-b03f-40d62f3943daTo recap:9 other members of the team can write to the calendar, it is just this one user that can't. If I log on to another computer with this user's logon and password and send an email from there, the meeting gets written into the calendar. So, it wouldn't seem to have anything to do with SMTP/POP services, and the issue couldn't be server-side.
February 22nd, 2010 8:22pm
Another bit of info concerning this:If he types the SharePoint calendar address in the Meeting request rather than choosing it from the global address list, the Meeting request does show in the SharePoint calendar for all other members of the team that share this calendar--except on his computer.
February 22nd, 2010 8:39pm
Anyone have any idea what the process could be that is stopping this user from writing to a Shared SharePoint calendar ONLY on one particular computer? I would expect the process go from Exchange> Web Front End SMTP> SharePoint and I don't see how sending a message request from a particular computer would affect what gets written to the SharePoint calendar. (Same profile, other computers--user can write to the SharePoint calendar.)
February 23rd, 2010 11:02pm
I also deleted the SharePoint calendar from the user's Outlook and readded it again from SharePoint--no change. He can't write to the SharePoint calendar only from his own computer.
February 25th, 2010 6:44pm
I would really love to know the reasoning behind this, but here is the fix:I changed the calendar's name in SharePoint, from 'Support Calendar' to 'Client Services Calendar'This user can now write to the SharePoint calendar from his own computer when he sends an email to it.Outlook is involved somehow here, as he could send emails under his own profile from any other computer other than his own, the appts would show up in the calendar. I wonder if there was some sort of block or flag under his particular computer's Outlook to cause this.
March 1st, 2010 10:51pm
I know this is late in coming and I tried everything in this post. Here is some additional information for anyone else that is having the problem. We are running Exchange 2007 and Office 2007 on XP machines with a few exceptions. Using my ID I tried scheduling the calendar on the following machines: XP/Office 2007 - failed Windows 7/Office 2007 - failed Windows 7/Office 2010 - worked This told me that it was probably machine/application specific and not SharePoint and I really didn't want to have to change the name of the calendar so I kept digging. This is what worked: http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/3de28156-b62d-455d-810c-c52ff9cde7ef - Worked it out, when creating a mail contact in Exchange for a sharepoint calendar, you need to make sure that “Use MAPI rich text format” is set to NEVER. (This changes the mAPIRecipeint field to False) This setting is also in ADSI edit or the Attribute Editor tab in ADUC. Set the mAPIRecipient field to False. Hope this helps anyone else that has the problem.
June 30th, 2010 7:43pm
Hi Deb: Interestingly enough, we did already have that set--because there is a known issue we ran into where attachments sent to Document Libraries would disappear and never make it into libraries--with no error messages in logs or Exchange. Setting "use Mapi rich text", which is the default, to Never fixed our missing attachments issue. However, it did not fix the calendar for that user. We set all contacts to "never" when they are first created. Good find.
June 30th, 2010 8:21pm
From AD (ours run on R2 mode), right-click on the Contact of the affected SharePoint Calendar, select Properties, Attribute Editor, and change the mAPIRecipeint field to False (by default this value is set to 'not set').
February 18th, 2011 7:27am