We have one user who is on a Mac running Entourage, connecting to our local Exchange Server v6. We have the problem that when this user accepts a calendar appointment requests we see two errors in the Windows logs:. Even though we see these error messages at server level it appears that the calendar entries are still saving correctly onto Exchange. All information we can seem to find on this suggests that a software update should solve this problem but all is up to date here.
We do not believe desktop syncing to be an issue here as our user has an iPhone that talks directly to Exchange for its email, no syncing takes place on the desktop.
The iPhone has an iCloud account associated with it but we do not believe this to be a problem as it's a completely separate account which handles no mail from Exchange. We have another Mac user in our network who is also using Entourage and is causing no problem. This may be an issue with Activesync.
We have account and will be a problem if we can't migrate contacts automatically. At least with -SkipContacts we can moving on with migrations but of course, this can't be the final solution for us. Is there any alternate way like any third party tool by which we can migrate only contacts from Gsuite to O? Emanuele EM Mure. This thread is locked.
You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 5. Report abuse. Details required :. Cancel Submit. Previous Next. Best regards, Jennifer. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Feel free to contact us if you need further assistance. Regards, Jennifer. As you know, every job does not finish in a few minutes but also lasts hours, so even just one small change to a migration batch costs hours of time.
However, currently the problem persists. I created a new service account as explained in the guide. Only on an empty brand new mailbox , the batch went through. I tried the imap mode and those went well. But as you will understand, using "imap mode" is a problem if you have users. I tried powershell with -excludeFolder but nothing. Any ideas?? Hi All, Thank you for your reporting of the problem you encountered to us. Yeah, I also stumbled upon that article. However, I don't have any problem with services not starting and moreover, the article is for Exch, while I'm running It started this morning at 8am.
Whenever a user changes something in their calendar, it gives this error. So i since turned it off. Even when this error was fixed, the 0xffff still came up in the application event log. I have found that bouncing the box and restarting the transport service resolved it for about a month. This is a pretty new server, been online for about 8 months. I have had this problem on and off from the beginning, through all the rollups and SP1. Most users have migrated succesfully and OWA works.
Outlook is not a problem. OWA is not a problem with other users. Calendaring agent failed with error code 0xffff while expanding recurring appointments. Mail 62 6f 78 3a 49 6c 73 65 box:Ilse 20 56 61 6e 52 6f 79 VanRoy. I 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! 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 calendar problem equires rollup 1 or rollup 2 of Exchange SP1. I suspected it is the. NET 32 run on bit which made it fails. 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 bit. This fix work for me so good luck to you guy. It's a long day for me. Type the following command to install the version of ASP. NET 2. Make sure that the status of ASP. NET version 2. Note The build version of ASP. These steps are for build version 2. Update the roll up 1 or the newest, rollup 2, for Exchange SP1.
So I did what he said, although honestly I was a little skeptical. 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 I can't find one online, and all the forums say there is no official list. I'm officially baffled. 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:. I read elsewhere that reapplying the latest rollup should fix this issue. I will try that and write back. That hkcrscan. 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. In services. I upgraded from Exchange to Exchange about 2 weeks back.
I find a lot of technical information, and finally through the following methods to resolve problems. Note You must complete step 2 before you continue to this step. Click Start, click Run, type dcomcnfg, and then click OK. Expand Component Services, and then expand Computers. Note The Computers node may take several minutes to expand. Do you with to record it? Click Yes. Important Exoledb Session Factory does not appear if you do not remove the registry key that is described in step 2.
Additionally, when you click Properties, the Exoledb Session Factory Properties dialog box may take several minutes to appear. Click the Identity tab, click The launching user, and then click OK. Good luck! I've found this thread useful but i still havent bee able to resolved the issue.
Upgrading from sp1 ru 7 to ru 9 didnt help, upgrading PP from 6. I've also modifed the parameters as suggested in this thread to disable meeting request scanning and the kaspersky components. I've tried everything in this thread to no effect. I had openend a MS case on july 8 and it was finally solved on march 3 I must admit the engineers went very far to try to reproduce the issue and I don't think they eventually could reproduce it in their labs.
However, during that time they did some live debug sessions on my own server cool stuff, watching the store. Here's the instructions:. Note: The value should be case sensitive. Of course, you could also just change this using the GUI of services. After the reboot, I went to OWA and created 1 appointment using a 'test2' account. In the application event log, there was 1 message about this:. ID: 0x Named property GUID: 8cda1cae-afdbdc04faaa.
The following user is attempting to create the named property: "test2". Protocol: MAPI. Client type: OWA. Client version: Named property GUID: efff-b9ab-accaa Just for the record: I too had a server running policypatrol During the course of the case, I had removed it from the server relocating it to another server on premises and routing mail via that other server , but the issue remained.
Wish I had looked back at this blog posting before today, because between my original posting and now, there had been some entries about the LK. Auto key which, off course, is also still present at my server. Perhaps removing this key would have solved it too, don't know.
0コメント