If you tried to browse to http://localhost/bnf on the machine where BNF 63 was installed, and you failed to get a response from the server, it is likely that IIS has not been started on the the server. Right-Click on My Computer on your Desktop and select the Manage option.
The Computer Management Console will appear, scroll down to the bottom of the left hand (tree) pane and expand Services and Applications -> Internet Information Server -> Web Sites -> Default Web Site. (If you have not used the default website select the site that you have installed BNF 63 into – Please see the section Installing to a non Default Website under the Post installation tasks section).
Click on the Play Icon in the toolbar to start the Web Site, after a short wait the Default web site should be running. Browse to http://localhost/ to confirm that the default web site is running, and then to http://localhost/bnf to confirm that BNF 63 is running.
If you are still having trouble accessing http://localhost/bnf, Right click on the website BNF 63 is installed under (Normally the Default Website) and select Properties.
Now select the ISAPI Filters tab from the top of the list, you should see a filter named redirect listed with a green arrow pointing up next to it.
If the Redirect Filter is not listed, Click on the Add button and enter the name Redirect and Browse to the installation path of the BNF 63 where you should see a file named redirect.dll.
Click Open to select the file.
Click OK. You will now see the filter priority status listed as Unknown.
Click Apply and then OK, Browse to http://localhost/ to confirm that the default web site is running, and then to http://localhost/bnf to confirm that BNF 63 is running.
If you can browse to http://localhost/ but you still get a "Page Not Found" it is possible that the the .NET Framework is not correctly registered with IIS. To confirm if this is the case open the Computer Management console as above.
Click on the Default Web Site in the tree pane to see the bnf and bnf toolkit web applications. Then Right-Click on the bnf web application and select Properties from the pop-up menu.
On the Site Properties dialogue select the Virtual Directory tab and click on the Configuration button.
On the Application Configuration Dialog that appears select the Mappings tab and scroll down to check that the .aspx extensions is registered for the executable C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\aspnet_isapi.dll for verbs including GET, HEAD and POST. If there are other verbs listed, these should be left as they are.
If you find that the .aspx extension is not registered you may use the following command to register the .NET Framework with IIS.
\WinNT\Microsoft.Net\Framework\v1.0.3705\aspnet_regiis.exe -i
BNF 63 server is normally accessable using the http protocol on port 80. You should check that any security precautions such as firewalls are letting you access web sites in general and the BNF 63 server in particular.
When using the local formulary editor on a machine other than the one on which the BNF 63 is installed, the file /bnf/lfe/web.config may need to be edited to suit the specific installation
The line:
<add key="deploy.root.url" value="http://localhost/bnf/"/>
should be changed to the external name or IP address of the server e.g.:
<add key="deploy.root.url" value="http://examplelfeserver.nhs.uk/bnf/"/>
or:
<add key="deploy.root.url" value="http://10.1.1.200/bnf/"/>
