Member Avatar for p17

When I deploy asp.net web application in one server it is working,but when it placed in NLB cluster (deployed in more than one server )
looking for webform1.aspx file not found error is coming.
Do I need to take any necessary actions during development of application if it has to place in NLB cluster.
we are using asp.net 1.0 (visual studio 2003)

  • 3 Contributors
  • 3 Replies
  • 123 Views
  • 6 Days Discussion Span
  • Latest Post Latest Post by vbLegend

Dani AI

Generated

As described, the app works on a single box but returns "WebForm1.aspx not found" behind the NLB. The suggestions from and (machineKey and IIS script support) are valid starting points, but a 404 for an .aspx usually means a deployment or IIS configuration difference on one or more nodes rather than a networking problem. Note: Visual Studio 2003 targets the .NET Framework 1.1 — make sure each cluster node has the same runtime and that ASP.NET is registered with IIS.

Try this focused troubleshooting workflow (fast to run and repeat on each node):

  1. Isolate the node that returns 404. Point a browser (or hosts file) to each server IP/FQDN to see which node fails.
  2. Verify the physical file on the failing node: confirm the exact path used by IIS contains WebForm1.aspx and that timestamps/checksums match the good node.
  3. Check IIS site settings on that node: site binding/host header, virtual directory physical path, application root, application pool and the mapped ASP.NET version/script mappings (ISAPI or extension mappings). In IIS6 also confirm the ASP.NET Web Service Extension is allowed.
  4. Check file/folder ACLs: the worker process identity (NETWORK SERVICE, ASPNET or AppPool identity) needs Read (+ Execute for bin).
  5. Inspect IIS logs and Event Viewer on the failing node for the request entry and the 404 substatus; logs show which server produced the error and the physical path IIS tried to open. Use the log hit to narrow the cause quickly.
  6. If deployment is automated, re-deploy or mirror the published build to the bad node (avoid manual copy mistakes). If the app uses encrypted ViewState or auth cookies, ensure consistent machineKey and shared session state for a web farm.

Useful quick commands (run on the node):

%windir%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

robocopy \\build-server\publish C:\inetpub\wwwroot\MyApp /MIR /COPY:DAT /R:2 /W:5

findstr /i "WebForm1.aspx" C:\Windows\System32\LogFiles\W3SVC*\*.log

Focus first on file presence, IIS bindings/mappings and logs — those almost always reveal why one node returns 404 while another works.

Recommended Answers

All 3 Replies

Member Avatar for kedar_challa

give same machine key in web.config file on both servers.

Member Avatar for p17

Thank you we are using same,I have to check with admin people is there any installation issues.

Thanks,
padma

Member Avatar for vbLegend

Follow kedar_challa steps and check whether the allow Asp.Net scripts are enabled in the IIS in the NLB clusters(or both the servers).

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.