Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Maverick494
2017-11-06T17:40:08Z
When I execute 2 specific powershell scripts in VC I get

System.Management.Automation.CmdletInvocationException: The response content cannot be parsed because the Internet Explorer engine is not available, or Internet Explorer's first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again. ---> System.NotSupportedException: The response content cannot be parsed because the Internet Explorer engine is not available, or Internet Explorer's first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again.
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.VerifyInternetExplorerAvailable(Boolean checkComObject)
at Microsoft.PowerShell.Commands.InvokeWebRequestCommand.ProcessResponse(WebResponse response)
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at TaskPowerShell.PowerShellTaskClass.Run(ProcessPowerShellTaskInfoClass ti, StringBuilder& sbStandardOut, StringBuilder& sbStandardError, Boolean& bolResult)

But both scripts execute without issue in powershell and powershell ISE. I also run 7 other powershell scripts in VC without issues. Why would VC error out when the scripts execute without issue outside of VC?

Edit: It appears that the script isn't even executing long enough to get past the very first wget in the script because I added a start-sleep -s 10 right after it.
Sponsor
Forum information
Support
2017-11-07T10:03:57Z
Try the UseBasicParsing flag:

https://stackoverflow.co...et-explorer-engine-is-no 

There are differencies between the PowerShell host that VisualCron (.NET) uses and normal.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Maverick494
2017-11-07T14:16:28Z
Originally Posted by: Support 

Try the UseBasicParsing flag:

https://stackoverflow.co...et-explorer-engine-is-no 

There are differencies between the PowerShell host that VisualCron (.NET) uses and normal.



I initially tried UseBasicParsing; I probably should have stated that too. It didn't work the first few times I tried it, but I figured out why and I have put it in all the places it needs to be and it seems to be working now. The odd thing is there are only 2 out of like 10 scripts that need this flag and it has only been the case since I loaded 8.2.9

Thank you for the response, I appreciate the help.
Support
2017-11-08T13:25:40Z
Originally Posted by: Maverick494 

Originally Posted by: Support 

Try the UseBasicParsing flag:

https://stackoverflow.co...et-explorer-engine-is-no 

There are differencies between the PowerShell host that VisualCron (.NET) uses and normal.



I initially tried UseBasicParsing; I probably should have stated that too. It didn't work the first few times I tried it, but I figured out why and I have put it in all the places it needs to be and it seems to be working now. The odd thing is there are only 2 out of like 10 scripts that need this flag and it has only been the case since I loaded 8.2.9

Thank you for the response, I appreciate the help.



It is most likely because the IE dependency and that it is the first time it launches under that profile. The setting causes automatic compatiblity settings.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top