[EXCH07] Calendaring agent failed with error code 0x8000ffff while saving appointment.
- I've been pulling my hair out over this error for days now and I don't seem to be any closer to a resolution or an answer. This is the error that is flooding the application logs on all of my mailbox servers:
Event Type: ErrorThe situation is that we are migrating/transistioning from Exchange 5.5 to Exchange 2007 using the Exchange Migration Wizard from Quest Software. The new Exchange 2007 environment is as follows: 2 Edge Transport servers in the DMZ, 2 servers with Hub and Client Access roles, and 2 clustered mailbox servers using CCR (4 nodes, 2 clusters).
Event Source: EXCDO
Event Category: General
Event ID: 8206
Date: 12/13/2007
Time: 11:47:49 AM
User: N/A
Computer: <servername>
Description:
Calendaring agent failed with error code 0x8000ffff while saving appointment.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 48 72 53 61 76 69 6e 67 HrSaving
0008: 41 70 70 74 3a 3a 48 72 Appt::Hr
0010: 43 68 65 63 6b 50 61 74 CheckPat
0018: 74 65 72 6e 20 66 61 69 tern fai
0020: 6c 65 64 2e 20 4d 61 69 led. Mai
0028: 6c 62 6f 78 3a 4d 61 72 lbox:Mar
0030: 6b 2e 44 61 6e 69 65 6c k.Daniel
0038: 73 40 6d 63 6c 65 6f 64 s@<domain
0040: 75 73 61 2e 63 6f 6d name>
I thought that I found an answer in this article: http://calendarservermigration.blogspot.com/2007/08/setting-permissions-for-migration-into.html
This thread also discusses some of the permissions for "impersination" mentioned in the above article.
http://forums.microsoft.com/technet/showpost.aspx?postid=1851510&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=1
Using the powershell add-adpermission bits described in that article to add the permissions it suggested I have seen no change in the amount of EXCDO errors.
All servers are running Exchange 2007 SP1 on Windows Server 2003 R2 SP2 64bit.
Any help or clues anyone could provide would be very helpful and thank you for taking the time to read this thread.
All Replies
- I'm having the same issue here, and it's releated to SP1. I have checked another installation of Exchange 2007, which isn't running SP1, and the issue doesn't occur there. Also, at the same time of the EXCDO errors, in the System Event log there is a DCOM error, event 10016:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{9DA0E106-86CE-11D1-8699-00C04FB98036}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18). This security permission can be modified using the Component Services administrative tool.
I've tried to change the security permission on the GUID mentioned. That is not easily done, I had to change the (Default) registry key of HKCR\AppId\{9DA0E0EA-86CE-11D1-8699-00C04FB98036}, since this is the one referenced in HKCR\CLSID\{9DA0E106-86CE-11D1-8699-00C04FB98036}\AppID. One you change the (Default) into something else than (value not set), such as Exchange Property Mapping Interface, which seems to be the name for this GUID, you can see the properties of it in the DCOMCNFG (Component Services MMC snap-in).
If I try to add the Local Launch permission on that GUID to SYSTEM, the DCOM errors go away. BUT: you can't access some mailboxes anymore. While I was troubleshooting this issue, I was checking with the administrator mailbox and that was no problem, but it seemed any other normal user could no longer get to its mailbox, via Outlook or via OWA. The net result was that the request hanged. Even stopping the Exchange Information Store no longer was possible: I had to kill it in taskmanager. And even then, the EXCDO errors remained.
Bad thing is: even with a brandnew mailbox, the issues of EXCDO and corresponding DCOM also occur. So I'm stumped, everything seems to work but these errors keep occuring. It looks like it has something todo with the calendar, but I think my users don't really use that so maybe the don't see the problem because they're just not using it.
So please help, I don't know what to do with it.
- Antivirus software?
No Antivirus software present during these issues. I have installed Redearth's PolicyPatrol for anti-spam and anti-virus filtering (using Kaspersky), but it makes no difference, the errors keep occuring.
Even with a complete new user, made through ADUC, given a mailbox in Exchange Console, open the mailbox in OWA, I get 2 of these messages (2 in each eventlog, EXCDO in Application, DCOM in System). Then when I go to the calendar and make an appointment in it, I get lots of those errors (didn't count, >5 at least). They stop when I stop browsing the calendar.
I have tried to make a meeting request and see the calendar of another new user, but there are just dashes and the calendar of the other user is not displayed (cannot find a free spot). So I'm sure it has got something to do with the Free/Busy stuff, but I was just using OWA, so it's not through a public folder, right?
Still, the public folder is present on the exchange 2007. And the test for outlook 2007 autodiscovery also shows no errors and works fine.
One thing: this is a migration from a EXCH2003 server. This server is still operational, even though all mailboxes have been moved to the new EXCH2007 server. This was done about a month ago. The EXCH2007 was installed and SP1 applied right after installation. The errors start showing since the day of the migration. So maybe it was related to the old server, but then I get these errors also with complete new user accounts & mailboxes, so I don't think it is something left over from the old server.
I have the same thing happening now:
Exchange server 2003 SP1 - 2 node active / passive cluster.
Approx. 26 hours ago started getting the 0x8000ffff error.
Once every minute I get 3 identical 0x8000fff messages.
All error messsages related to the same mail box.
No other error messages occur at the same time or are related that I can see.
There have been no changes to the system recently.
Any ideas????
- This MS article describes broblem and workaround:http://support.microsoft.com/kb/823159
Yeah, I also stumbled upon that article. However, I don't have any problem with services not starting and moreover, the article is for Exch2003, while I'm running 2007. Plus it's a brandnew server, I don't think there's anything in the HKCR with too many characters in it, unless perhaps it came with Exchange SP1....
Has anyone had success with that HKCRScan.exe tool with this problem in Exchange 2007?
I have had exactly the same problem.
It started this morning at 8am. Whenever a user changes something in their calendar, it gives this error.
I fixed the DCOM error by changing the permissions on the DCOM, but then any calendar activities went extremely slow... about 30 seconds for a change to take, and outlook starts responding again. So i since turned it off.
Even when this error was fixed, the 0x8000ffff still came up in the application event log.
Anyone else had any luck with fixing this?
I have the same problem.
I have found that bouncing the box and restarting the transport service resolved it for about a month.
Now it’s back - after NO changes were made to the system. This is a pretty new server, been online for about 8 months. It strictly runs our mail; I’m in a single server environment.
I have had this problem on and off from the beginning, through all the rollups and SP1.
If i give the DCOM object (Exchange Property Mapping Service) local launch, mail flow crawls to a halt.
I know SOMEONE has the answer!
Hook a brother up!
Hi - I have exactly the same problem.
I upgraded from SBS2003 to Exchange 2003 to Exchange 2007 about 6 weeks back. Most users have migrated succesfully and OWA works. I have one user, however, that floods the Event Viewer every time they load a page using OWA. Outlook 2007 is not a problem. OWA is not a problem with other users. At the client end, the user with the broken mailbox suffers very slow page loads/refreshes and we get 3 errors in the event log when the page eventually loads (so a time out of some kind).
Source: EXCDO
Event ID: 8208
Calendaring agent failed with error code 0x8000ffff while expanding recurring appointments.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 48 72 51 75 65 72 79 52 HrQueryR
0008: 6f 77 73 3a 3a 53 65 74 ows:
et
0010: 49 6d 70 6c 69 65 64 52 ImpliedR
0018: 65 73 74 72 69 63 74 69 estricti
0020: 6f 6e 73 20 66 61 69 6c ons fail
0028: 65 64 2e 20 4d 61 69 6c ed. Mail
0030: 62 6f 78 3a 49 6c 73 65 box:Ilse
0038: 20 56 61 6e 52 6f 79 VanRoyI have atttempted to rebuild the mailbox, repair the database, delete and repair rege keys Exoledb Session Factory and gone through AD to repropagate permissions for the user from the organisation container. It just won't go away.
I don't think it's the mailbox. I can't see any GPO rules that affect the user either. Somehow though there is a specific permission setting on calendar objects that I can't get to. It's driving me nuts!
Same Issue here: 2 Exchange 2007 servers running CAS/HT/MB....SP1 installed a month ago, last week we start getting the EXCDO errors.......Installed Rollup 2 for SP1....no help....Anybody get this sorted out yet?I have mostly same problem with you guys and I didn't even install the virus program, only anti spam-virus for Exchange.
I spent whole day researching this, everything from DCOM fixing to checking service pack, and rollup 2 for Exchange (regarding Calendar error). The calendar update issue happens for most user when they update, create new calendar. The Outlook client freeze and the email server record event for EXCDO 8206, 8209.
This all relates to all errors:
-W3SVC-WP event ID: 2268, 2274
-Exchange EXCDO Event ID 8206
-In system log, DCOM Event ID: 10016, W3SVC Event ID: 1002, 1039
all these related events cause Exchange calendar failed in some mailbox, IIS failed to function (even though it started) which include Sharepoint and Exchange OWA.The calendar problem equires rollup 1 or rollup 2 of Exchange 2007 SP1.
Fix DCOM:
I suspected it is the .NET Framework because that causes the IIS Web failed too. so I found an article about this .NET 32 run on 64-bit which made it fails.
http://technet.microsoft.com/en-us/library/cc179581(EXCHG.80).aspx?wt.svl=overview
then at it bottom there is a link how to fix this
http://support.microsoft.com/?kbid=894435#
Thank God the whole thing works again. I guess at some point there is a software upgrade or install which screwed up the ASP.NET configuration for 64-bit.
This fix work for me so good luck to you guy. try this. It's a long day for me.
ASP.NET 2.0, 64-bit version
To run the 64-bit version of ASP.NET 2.0, follow these steps:
1.
Click Start, click Run, type cmd, and then click OK.
2.
Type the following command to disable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
3.
Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
4.
Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the Web service extension list in Internet Information Services Manager.
Note The build version of ASP.NET 2.0 may differ depending on what the currently released build version is. These steps are for build version 2.0.50727.
Fix calendar:
Cause: http://support.microsoft.com/kb/943371/
Update the roll up 1 or the newest, rollup 2, for Exchange 2007 SP1.
Roll up 1
Roll up 2
- Gelfer said:
Yeah, I also stumbled upon that article. However, I don't have any problem with services not starting and moreover, the article is for Exch2003, while I'm running 2007. Plus it's a brandnew server, I don't think there's anything in the HKCR with too many characters in it, unless perhaps it came with Exchange SP1....
Has anyone had success with that HKCRScan.exe tool with this problem in Exchange 2007?
yes i did. i had the same problem as described in this post. now solved. - So I was getting 8206 and 8207 errors all weekend. I racked my brain all morning looking for a solution. Finally I gave in and asked the guy that installed this system. He said "After rebooting, shut down all Exchange services and start them back up in random order".
I had already rebooted the server, which I thought would have fixed the issue if it was a simple service stop/start issue. So I did what he said, although honestly I was a little skeptical. It took about 5 minutes to stop/start the services. But lo and behold, it actually worked.
I would love for somebody at Microsoft to tell me how in the flip that makes any sense. Shouldn't the reboot have accomplished the same thing as restarting the services?
That being said... Is there a recommended stop/start list for Exchange services? I can't find one online, and all the forums say there is no official list. I'm officially baffled.
- Proposed As Answer bynickadelman Monday, January 26, 2009 4:24 PM
I have the exact same errors. Everything seems to be fine, but our mac entourage users cannont connect.
I have done the above dcom fix with no luck, although I have not rebooted the machine as it is production. I was able to generate another dcom error by giving permissions to the system account. The new dcom error is:The server {9DA0E106-86CE-11D1-8699-00C04FB98036} did not register with DCOM within the required timeout.
I read elsewhere that reapplying the latest rollup should fix this issue. I will try that and write back. That hkcrscan.exe tool looks to not exsist on the web. If anyone has a link, that would be appreciated as i havent tried that. I also did not try randomly restarting services becuase that makes little sense at this tiem.
- Edited bysharepointisneedlesslycomplex Wednesday, April 22, 2009 10:11 PMincorrect info
- HKCR tool can be found at this kind fellows blog
http://abneru.wordpress.com/2009/01/28/hkcrscan-tool-microsoft/
Also i should note that this tool has completely fixed the problem for me.
If you want a copy and the ftp isnt working leave your email or reply to this thread. Hopefully m$ doesnt k-line me. It fixes a known issue in THEIR product. I do not see why anyone should pay 250$ for this, period.
- I was apparently a bit premature in saying that this was solved. The issue occurred on reboot this morning.
As no patches were installed, i decided to see if the "reset services in random order" would fix things. I got lucky. After restarting the "microsoft exchange information store" and NOTHING else, the problem disappeared! and mac users are able to connect again.
So it looks like the "random" restart fix mentioned above, merely started the information store in the proper order. - This is what I did to resolve this issue:
Open Component Services
Expand My Computer
Expand DCOM Config
Right click on {9DA0E0EA-86CE-11D1-8699-00C04FB98036} and go to properties and select the properties tab.
Under Launch Permission check if any groups or users are been listed.
Removed all users and groups, then clicked OK.
ORIGINAL USERS & GROUPS before I removed them:
Administrators (DOMAIN\Administrators) <- now removed
INTERACTIVE <- now removed
SYSTEM <- now removed
I was not able to reboot right away. When I finally rebooted there was a new Rollup Update, which I installed. I know that performing the above steps correct the issue, but I am not sure if it was a long term correction.
This error no longer occurs.
(i beleive when rollup 5 for exchange 2007 service pack 1 was installed is when i started having the same issue as others. i beleive it was rollup 7 for exchange 2007 service pack 1 that was installed before the reboot. it has been over 4 months since this issue occured, and i finally have a free second to post this info.) - I'm getting 8206,8207, and 8208 excdo errors in my event log and 10016 dcom errors in my system log after updating to Exchange sp1 rollup 9. Originally I was getting 10010 dcom errors and our calendars we're hanging in outlook. After changing the dcom permission as stated above we started getting the 10016 dcom errors and the calendars stopped hanging, only now when we dismiss appointments sometimes the reminder comes back. I've been working with MS support for 2 days now and after the 2nd night where they almost completed hosed the system itself and left me to fix it late into the night I'm reluctant to continue working with them until they can tell me they have a solution. They've told me that it is usually caused by an AV program but the only AV we are using is Forefront for exchange. I uninstalled it to no avail.
Has anyone run into this? - A few days ago my case got escalated and I got a very good tech. He gathered tons of info before he tried anything. He ended up removing a registry key (HKEY_CLASSES_ROOT\LK.Auto) and after a reboot no more dcom errors and no more 8206,8207,8208 errors. I'm getting a few excdo warnings in the event log but they all state detecting and inconsistency in the calendar and a repair is being performed. I'm not going to worry about these warnings unless they are still there a few days from today.
Here's my set up incase anyone else comes across this:
Exchange 2007 SP2 (originally SP1 with rollup 9, upgraded to SP2 to try to fix the problem)
Forefront for Exchange sp2
Policy Patrol for email signatures- Proposed As Answer byCasimir Couvillion Sunday, November 08, 2009 10:34 PM
A few days ago my case got escalated and I got a very good tech. He gathered tons of info before he tried anything. He ended up removing a registry key (HKEY_CLASSES_ROOT\LK.Auto) and after a reboot no more dcom errors and no more 8206,8207,8208 errors. I'm getting a few excdo warnings in the event log but they all state detecting and inconsistency in the calendar and a repair is being performed. I'm not going to worry about these warnings unless they are still there a few days from today.
Here's my set up incase anyone else comes across this:
Exchange 2007 SP2 (originally SP1 with rollup 9, upgraded to SP2 to try to fix the problem)
Forefront for Exchange sp2
Policy Patrol for email signatures
Thank you! Thank you! Thank you!
This has been driving me nuts for more than a month. It started for me right after I installed a demo of Policy Patrol. It continued after I removed the demo and updated Exchange 2007 to SP2.
Some investigation leads me to believe the LK.Auto key has something to do with the licensing for the Kapersky AV module in Policy Patrol.
I removed the key, rebooted and no more errors! It is surprising to me that that key causes the error when Policy Patrol and Kapersky are no longer installed on my server, but I'll take it.- Glad that was helped :-)
I also believe the LK.Auto key is related to Kasperkey which was one of the AV engines I had chosen for Forefront., I spent about 3 weeks on this problem, several late nights, and dealt with several grumpy end users and it was as simple as removing a key. Who knew - This also fixed my problem. I too was getting the 8206, 8207 and 10016 event id error messages. After deleting the LK.Auto key from the registry the problems disappeared. The original problem occured after the upgrade to version 6 of the Policy Patrol software from Redearth software. My enviroment is SBS 2008 with Exchange 2007 SP1.
Thanks so Much! - I think this thread has helped us a lot. Thanks to everyone who has posted here.Our Exchange 2007 server would not allow many people onto OWA services and no mailboxes could be moved between servers or mailbox stores. Many user also reported Outlook 2003 hanging problems...
Removing the lk.auto registry key works, followed by restarting the Information Store service. All EXCDO and in our case, DCOM errors too were resolved. However, the lk.auto key comes back after a server reboot and I think this must be down to Policy Patrol Disclaimers version 6 being installed.Strangely, the Exchange 2003 server does not exhibit any of these problems or errors.If I get anything from Red Earth Software who support Policy Patrol, I'll post my finds.-Nick
