AUTOMATION ERROR:OLE IDsipatch exception code 4096 from MS Outlook when scheduling a meeting request

hi, i was wondering if anyone can help. We have a cleint that uses SPM & they schedule activities as meeting request internal & some are internal & extrenal. in the beginning they used to get this message & it became apparent that youd to elevate each users permissions on each others Outlok calendars. I.e Right click on it>permissions & make them editors.

They have just created a new SPM user. Hes using the Terminal server to log into Opera. Hes scheduling an activity for himself, e.g that he has a sales meeting next week. The activity type is "schedule this type of activity as a meeting request internal" & its purely for himself. He is getting the attached file. Ive therefore added him as an owner on his own calendar (which I wasn't convinced needed done), but this hasn't made any difference. If you change the activity type to "schedule these types of activity as appointments" - then it duly adds it to his MS Outlook Calendar.

Im just a little stuck with what else to suggest, so any help would be much appreciated.

Regards

James[View:/cfs-file/__key/communityserver-discussions-components-files/35/Doc1.docx:320:240]

Find more posts tagged with

Pegasus - Partner General Discussions

Comments

joe_cancglin

Hi James,

We have seen a instance of this where a user couldnt edit or save a specific activity they got he same error.

It turned out to be an issue with the mail profile which was resolved by creating a new one.

I hope this helps.

James

dEPM-629 - How to get data into Infor dEPM - S01E01 - Intro and Getting Data to the Data Lake.mp4

unknown

Cheers James. Ive asked their IT people if this is possible. Whats annoying is that he can send a meeting request to himself, manually through Outlook. Its just when hes trying to do it through Opera. He can also create an activity that updates his Outlook with an appointment (direct, as opposed to sending a meeting request). Pegasus say its an Outlook issue, their IT people are saying its a Pegasus issue etc, so a bit of an impasse is being reached....Once again thanks for the input

unknown

We got it fixed in the end. We tried all sorts & the solution doesn't really make any sense. They had a remote user called Ian, that could successfully run this. We tried using the Saul Opera user with Ian's Outllok account - still didnt work. We use Ians Opera account with Sauls mailbox - it worked, so we were happy it wasnt a TS/Oulook problem. So we literally copied the "IAN" opera user to a "SAUL2" Opera user - and this resolved it! Thanks for you input though

0812040327243779.pdf

Copyright © 2025 Infor. All rights reserved.