The remote server returned an error: (400) Bad Request

Problem

Timestamp: 17:06:43.378  
Message: Error when detecting/processing new command. Dropping message. Invalid argument:
System.ArgumentException: The remote server returned an error: (400) Bad Request. ---> System.Net.WebException:
The remote server returned an error: (400) Bad Request.  
    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)  
    at Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.GetAsyncResult`1.EndGetResponse(GetAsyncResult`1 thisPtr, IAsyncResult ar)  
    at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)  
--- End of inner exception stack trace ---

Server stack trace:

Exception rethrown at [0]:  
    at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)  
    at Microsoft.ServiceBus.NamespaceManager.OnEndQueueExists(IAsyncResult result)  
    at Zipper.ZervicePoint.ProcessSystem.Engine.Queues.ServiceBusQueue.EnsureQueue(String queueName)  
    at Zipper.ZervicePoint.ProcessSystem.Engine.Queues.ServiceBusQueue.get_Queue()  
    at Zipper.ZervicePoint.ProcessSystem.Engine.Queues.ServiceBusQueue.Peek(TimeSpan serverWaitTime)  
    at Zipper.ZervicePoint.ProcessSystem.Engine.Detectors.ActivityJobsDetector.StartActivityJobsDetection()  
Category: Process  
Priority: -1  
EventId: 37  
Severity: Error  
Title:  
Machine: LOCALHOST  
Application Domain:
Zipper.ZervicePoint.ProcessSystem.WorkflowService.exe  
Process Id: 1648  
Process Name: C:\Program Files\Zipper\ZervicePoint\ProcessSystem\Zipper.ZervicePoint.ProcessSystem.WorkflowService.exe  
Win32 Thread Id: 1796  
Thread Name:  
Extended Properties:

Solution

  1. Verify that the ZervicePoint service account is not a member of too many AD Groups. (The account that runs the provisioning and process services).
  2. See this article: https://blogs.msdn.microsoft.com/biztalknotes/2015/05/19/workflow-manager-configuration-fails-with-400-bad-request/