Warmup Service Applications generates Bad Request

Nov 23, 2015 at 1:07 PM
Edited Nov 23, 2015 at 1:08 PM
The warmup of some Service Applications generate a Bad Request:

https://spserver01:32844/f5e4cac0184d469db4a95a330b157cab/AppMng.svc/secure
System.Net.WebException: The remote server returned an error: (400) Bad Request.
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()
https://spserver02:32844/f5e4cac0184d469db4a95a330b157cab/AppMng.svc/secure
System.Net.WebException: The remote server returned an error: (400) Bad Request.
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()


In the script the following URLs are 'found' by the GetWebApplicationUrls function:
(e.g. for App Management)

Processing service application App Management Service Id: f5e4cac0-184d-469d-b4a9-5a330b157cab
http://spserver01:32843/f5e4cac0184d469db4a95a330b157cab/AppMng.svc
http://spserver02:32843/f5e4cac0184d469db4a95a330b157cab/AppMng.svc
https://spserver01:32844/f5e4cac0184d469db4a95a330b157cab/AppMng.svc/secure
https://spserver02:32844/f5e4cac0184d469db4a95a330b157cab/AppMng.svc/secure

The 3th and 4th url generate this warning.

There are more service applications with a suffix on the URL, on which a 400 Bad Request is generated. These warnings end up in my Event log.

Is this correct?
Developer
Nov 25, 2015 at 8:50 AM
Is the Search service started on those servers? Have a look at this article:
http://www.c-sharpcorner.com/UploadFile/anavijai/error-the-requested-service-appmng-svc-could-not-be-activa/
Nov 27, 2015 at 9:33 AM
Yes the Search Service is started.

The requests for the regular service endpoints do succeed. Only the httpS-variants fail.
Developer
Nov 27, 2015 at 12:29 PM
Have you opend the URLs in a browser then and looked if the certificates are vaild?
Nov 30, 2015 at 6:43 AM
Edited Nov 30, 2015 at 6:44 AM
I opened the urls (https-versions) in the browser, both generate a 400 Bad-Request.

I suspect the problem is in het '/secure/' part of the url.

Opening https://spserver01:32844/f5e4cac0184d469db4a95a330b157cab/AppMng.svc/secure in the browser gives me a 400 Bad Request.
Opening https://spserver01:32844/f5e4cac0184d469db4a95a330b157cab/AppMng.svc (without /secure) in the browser gives a normal WCF response (just like the http-variants).
Developer
Nov 30, 2015 at 10:37 PM
Ok, I'll have a look at this. Would you please add what SharePoint version you are using.
Developer
Jan 9, 2016 at 12:09 PM
Ok, after some digging, this happens because the script assumes a service (e.g. search) is runing on all farm node.
Mar 9, 2016 at 6:01 AM
Would it be possible to stop the error messages appearing the event log? It does tend to generate a lot of error message in there on a multi-server farm.