I use Redemption DLL to get Mails from a lot of Mailboxes from the local Exchange Servers. All Mailboxes are connected on the Default MAPI Profile, Outlook is open. Switching from one Mailbox to the other in Outlook does not give any error, Sending and Receiving Mails with Outlook also seems fine.
Since some weeks my VBS Scripts using Redemption DLL fail most of the time with the .Logon Statement for the RDO Session. The last Change on the Scripts was 27.07.2022, so I suspect, something in the timing with Exchange Server 2016 has been changed by Patches.
I ran 2 Scripts each every 5 Minutes on the Server. I disabled these tasks and tested the scripts manually every 10 to 20 Minutes, because I first suspected a throttling issue. But the same, Sometimes the RDOSession.Logon works, mostly it fails.
I checked the Eventlogs of the 3 Exchange 2016 Servers for related entries but did not find any.
How can I get the exact Error when calling RDOSession.Logon simply dies not hand back the control to my script?
I found the Problem: The Outlook Profile Settings on the affected computer were defect. Outlook itself did not care about this and opened fine everytime, also I was able to send and receive messages and lookup/change the connected calendars. Calling the Account settings from within Outlook also worked fine and fast, but: Calling the "E-Mail (32-bit)" from Control panel showed exactly the behaviour as did my scripts. After around 20 tries (every try added a task to Taskmanager), the Profile manager opened, I deleted the Outlook Profile, restarted the Computer, created a new Profile. Problem gone, the Scripts are running fine since then. Massive Thanks to @DmitryStreblechenko for helping in debugging this.