CODEWITHSUNDEEP
iisarrwindows-server-2019
user1477388
user1477388

Reputation: 21440

ARR Requests Not Properly Routing to Server Farm

I have installed ARR on my Windows 2019 server via the IIS Platform Installer and configured it by adding a server farm and adding a single server to it.

I can ping the server and ARR shows it is online. The issue is, when I submit a request from my local PC, it seems to hit the ARR server but it never hits the server farm. The browser returns 404 Not Found.

On the ARR server, if I create a request to "controlcenter.mydomain.com" and view the logs in C:\iislogs\www\HTTPERR I see this error:

2020-10-30 19:14:54 [my local computer IP address] 53391 [my ARR server IP address] 80 HTTP/1.1 GET / - 404 - NotFound -

The sites on my webfarm server are "controlcenter.mydomain.com" and "api.mydomain.com." Do I need to create special rewrite rules for these sub domains? I cannot seem to tell from the documentation.

How can I find out why the request is not being properly routed from the ARR server to the server I've added to my server farm (shown below)?

enter image description here

When I tried to reset runtime statistics on the Monitoring and Management page, it says, "The operation could not be completed because the worker process has stopped."

enter image description here

enter image description here

The health test with URL "http://controlcenter.mydomain.com" succeeds also.

Upvotes: 0

Views: 4276

Answers (1)

Bruce Zhang
Bruce Zhang

Reputation: 3042

Before you use ARR, you must first make sure to create a site bound to your domain, and then ARR can forward requests for that domain to the server farm.

In order to solve the problem of stopping the work process, there are the following methods.

  • Setting Ping Enabled to False stops IIS from checking whether the worker process is still running and keeps the worker process alive until you stop your debugged process. Setting Ping Maximum Response Time to a large value allows IIS to continue monitoring the worker process. You can refer to this document.
  • Run this command from the elevated command prompt on the controller machine.

net stop webfarmservice & cd /d "%programfiles%\iis\Microsoft Web Farm Framework" & mkdir extensions & move WFFExtension.dll extensions & net start webfarmservice

When I tested in my environment and killed the w3wp.exe, health test returned success but status of servers were unknow. This command solved the issue.

  • Delete the server farms and restart the IIS, then re-create server farms and add servers.

Upvotes: 1

Related Questions