If receive "page not found" or 404 error or 400 error testing WBI


#1

When first testing WBI using a web browser on the server itself , if results in web browser displaying “page not found”, or a 404 error or a 400 error - perform the following first:
reconfirm all configuration steps
confirmed the URL you are entering (test using the ip address as well as the localhost URL and double-check the port number used)
confirm IIS is running
confirm IIS is using .NET 2 [if using WBI 5 or 6- note this should be .NET 3.5, if using WBI 7 this should be .NET 4]
confirm the AyaNovaWBI app is using .NET 2 [if using WBI 5 or 6- note this should be .NET 3.5, if using WBI 7 this should be .NET 4]
If you continue to experience an issue, perform the suggestions below, testing again after each.

[FORUM NOTE: Each version of WBI requires a different version of .NET Framework - do make sure to refer to the specific requirements for the WBI version you are using.]

  1. Check that ASP.NET is enabled on Windows 2003 or Windows XP 64bit computers - for example Windows 2003 Server’s IIS is not enabled by default.

In IIS Manager, expand the local computer, and then click Web Service Extensions.
In the details pane, click ASP.NET, and then click Allow.
You can also check this by Computer Management as per the screenshot below

  1. Repair the Microsoft.NET Framework 2 installation

Open Control Panel -> Add/Remove Programs
Select Microsoft.NET Framework 2 and select Change/Remove
Select Repair
This will take at least 5 or more minutes
When finished, you must reboot the computer
Once loaded back up, confirm IIS is running, confirm IIS’s Default Web Site is using .NET 2, and the AyaNovaWBI 4 app is using .NET 2, enter in the URL and the login page for WBI will now come up
3. Repair the links between .NET 2 and IIS - as per the Microsoft topic http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3BQ306005

To fix IIS mappings for ASP.NET, run the Aspnet_regiis.exe utility:

Click Start, and then click Run.
In the Open text box, type cmd, and then press ENTER.
At the command prompt, type the following, and then press ENTER:
“%windir%\Microsoft.NET\Framework\version\aspnet_regiis.exe” -i
In this path, %winver% is the Windows directory for your operating system, and version represents the version number of the .NET Framework that you installed on your server. You must replace this placeholder with the actual version number when you type the command.

Refer to the Microsoft topics http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3BQ306005 and http://msdn2.microsoft.com/en-us/library/k6h9cz8h(vs.80).aspx for additional information on using aspnet_regiis.exe

[FORUM NOTE: Each version of WBI requires a different version of .NET Framework - do make sure to refer to the specific requirements for the WBI version you are using.]