Blackbaud AppFx Service Failing on Test Configuration Page

On the Blackbaud NetCommunity Configuration Test Page  one or more of the Blackbaud AppFx Services may be in a failed state and reflecting the following error: System.Net.WebException: The remote server returned an error: (400) Bad Request.

Note:
If NetCommunity is on version 7.0 and below, review [netcommunityURL]/testconfig.aspx.
If NetCommunity is on version 7.1 and above, refer to Knowledgebase
 
The error: The remote server returned an error: (400) Bad Request, is indicative of an issue that Microsoft IIS is having when trying to reach the endpoint of URLs configured in the system. This is normally not an issue which is related to functionality of the Blackbaud NetCommunity database or the installed software.  

Common causes of HTTP 400 Errors include:
  1. Restart the NetCommunity Web Services server
  2. DNS Resolution on the NetCommunity web server.  Consider flushing the DNS records on the server
  3. A problem with Application Pools in IIS.  Consider recycling the application pools or restarting the IIS service.
  4. Crashing Application Pools due to some other distress that the operating system is experiencing, such as RAM memory saturation.
  5. Missing Files or the storage volume is in distress
If the problem persists, you may need to engage your internal IT department or Microsoft Support.

Please contact the appropriate software vendor or IT professional for assistance with this process or issue which is beyond Blackbaud's scope of support. 



 

Environment

 Chrome;Firefox;Internet Explorer;Opera;Safari
 Windows Server 2003 (32-bit);Windows Server 2003 (64-bit);Windows Server 2008 (64-bit);Windows Server 2008 R2

Was this article helpful?