WebService calls failing with a 404 or 404.x error

Version Affected:  All

Description:  
When attempting to configure a WebService call between Servers a 404 or 404..x error is displayed
Whilst troubleshooting the issue, browsing directly to the membership endpoint can present the below errors:
Membership Endpoint URL - https://%host%/%realm%/webservice/membershipws.svc
e.g. https://IdP_Server1.domain.local/SecureAuth12/webservice/membershipws.svc

On the originating server:

On the target server:

Cause:  
This can be down to a missing Windows Feature, primarily the below:
.NET Framework x.x Features - WCF Services - HTTP Activation




Our OVAs will already have the required features enabled although some 'hardening' practices may see these removed during installation of the Server by our Customers

Resolution:  
Ensure HTTP Activation is enabled on the target WebService Server at a minimum

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.