Troubleshooting: WebService Calls Between Servers Return a 404 Error (Missing HTTP Activation Feature) – SecureAuth Support

Version Affected: All

Overview

Configuring a WebService call between servers can result in a 404 (or 404.x) error. Browsing directly to the membership endpoint (https://%host%/%realm%/webservice/membershipws.svc) reproduces the failure directly.

On the originating server:

Generic IIS Server Error page reading "404 - File or directory not found", shown when the request from the originating server can't reach the membership endpoint.

On the target server:

Detailed IIS error page reading "HTTP Error 404.3 - Not Found" for the membershipws.svc request, listing StaticFileModule and ExecuteRequestHandler as the failing module and handler.

Cause

This can be caused by a missing Windows feature, primarily .NET Framework Features > WCF Services > HTTP Activation. SecureAuth's own OVAs (Open Virtualization Appliances) already have this feature enabled, but hardening steps performed by customers during setup can remove it.

Windows Server 'Select features' wizard with .NET Framework 4.7 Features expanded, showing the WCF Services > HTTP Activation checkbox unchecked.

Resolution:

Ensure HTTP Activation is enabled on the target WebService server, at minimum, via Server Manager > Add Roles and Features > Features > .NET Framework 4.7 Features > WCF Services > HTTP Activation.

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.