1

Closed

The response content cannot be parsed because the Internet Explorer engine is not available

description

I'm starting the script as an ScriptService user (local admin, with SPShellAccess and fullread policy on all webapplications)

In the event log I have this warning:

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.

It seems it wants to use some part of IE, but won't start because IE has never run interactivly.
Closed Nov 24, 2015 at 1:08 PM by Samurai_ka
Will be added to the next release. Until then it can be downloaded from the code repository.

comments

Samurai_ka wrote Nov 21, 2015 at 2:25 PM

What version are you using?

Samurai_ka wrote Nov 22, 2015 at 8:19 PM

Could you also give more details on what Windows version and SharePoint version you are using.

MartijnBodewes wrote Nov 23, 2015 at 9:05 AM

I'm using
  • SharePoint 2013 (15.0.4551.1511)
  • SPBestWarmUp-2.0.9.ps1 (downloaded 19-nov-2015)
  • Windows Server 2008 R2 SP1
  • The account that runs the timer job is local admin, but: This account has never started IE as an Interactive User (eg. logged in with a GUI), so it has never answered the 'first run' questions of IE.
I've fixed the error by adding "-UseBasicParsing" on line 150 to the Invoke-WebRequest command.

(this may even speed up the warmup, since the command doesn't have to parse response.)

Samurai_ka wrote Nov 24, 2015 at 8:48 AM

OK. I've fixed the lines where the Invoke-WebRequest is used (Rows 156, 170 & 186). The patch is applied in build 115688. I will merge it into a new release later, after adding some other new features.

wrote Nov 24, 2015 at 1:08 PM