Forum Discussion
Solved
PowerShell - ActiveX Control Error
Greetings, We have a script that connects to Exchange Online. The first time we run the script, it kicks back this error: "ActiveX control '8856f961-340a-11d0-a96b-00c04fd705a2' cannot be instantiat...
ColeRiese Does your script utilize any forms? (e.g. $form1 = New-Object System.Windows.Forms.Form)
I just got done going through this and was finally able to work around it. It is my understanding that there is a bug in newer versions of the Exchange Online module. If you are using any sort of forms in your script and those forms are called before you connect to Exchange Online it generates the error. If you connect to Exchange Online first, then the form is called, there is no issue.
I had to tweak our script to connect to Exchange Online first, then add a prefix to our on-prem exchange session to prevent any conflicts. Here are a couple links I found during my search that helped me track down the issue.
https://twitter.com/DanielSjoegren/status/1406954671248396292
https://www.sapien.com/forums/viewtopic.php?t=15297
https://www.sapien.com/forums/viewtopic.php?t=16213&sid=b1fcd3f71b3ada945eeb75f4dbc4490f&start=10
Hope this helps!
I'm not sure which line is kicking out that error. We don't have 729 lines in the script.
The 729 line is in the ExchangeOnlineManagement module... If you open your script in ISE or VSCode and run a few lines at a time, you know what line or action causes the error to appear.
Can you reproduce this on every client in PowerShell 5? Does it work without errors in 7?
Can you reproduce this on every client in PowerShell 5? Does it work without errors in 7?
- If the script runs fine the second time, it could be a timing issue in initializing specific code. But again, without showing that part of the script... It's just guessing...
- Yes, other users running PowerShell 5 are getting the error message. The script seems to run fine in 7, however, we want to run the script in ISE because there are visual prompts
