Troubleshooting

This section describes some issues that may arise when installing the Web3 Platform and ways to address them.

Web3 Web Application Not Responding

The most likely reason for this is that IIS7.0 was installed or activated after .NET 4.0 was installed. The resolution is to re-register .NET with IIS. The utility to register .NET with IIS is called aspnet_regiis.exe and can be found in the .NET framework directory (%WindowsDir%/Microsoft.NET/Framework/v4.0.30319). Typically it is run with the -i parameter to register .NET 4.0 with IIS, but you should refer to the documentation for that command to determine the registration command that best suits your particular environment.

SQL Server Express fails to Install after download

Sometimes after downloading SQL Server Express over the internet it will fail to install correctly. The first thing to try is to rerun the Web3 installer. As the SQL Server install files have already been downloaded it will use those and should then install correctly.

SQL Server Express fails to Install after download and Retry

There are many checks that SQL Server Express will perform when installing. As this is a silent install a failure in one of these checks, such as free disk space, are not propagated up for the user to see. If SQL Server Express does not install correctly then download it from http://www.microsoft.com/express/Database/InstallOptions.aspx. Please ensure you download the version with Advanced Services. Running this installer will alert you to any other environment issues preventing SQL Server Express from installing. When prompted for the instance name enter 'Web3'. Once this process has completed re-run the Web3 installer.

Unable to create Message Queues due to insufficient privileges

Ensure that the machine name was provided as part of the Account name. Providing just the user name without the machine name will lead to an error when installing the Message Queues and services.

Javascript Error When Viewing Web3 Site

There is a known issue with the Javascript that loads the main Web3 portal Silverlight application. If you have installed Web3 at http://localhost/web3, browsing to this address (without a trailing slash) will display a Javascript error. To avoid this, always browse/link to the Web3 portal home page using a trailing slash on the URL (e.g. http://localhost/web3/).

Upgrade Process Requires a Reboot

This is an issue for users upgrading from the beta release of Web3 - although services are stopped and restarted by the installer, in some cases it appears that references to old versions of the Web3 libraries can be referenced by the services when they restart, causing service processing to fail. To avoid this we strongly recommend a machine reboot after performing an upgrade installation. This should not be necessary when performing a clean installation of Web3 for the first time on a machine.

Deleting Topics Causes a '405 Method not allowed' error with WebDAV installed

If WebDAV is installed as a module in the IIS site that is hosting the Web3 Platform then it is not possible to delete topics. WebDAV must be removed from the IIS site in order for the Web3 Platform to function correctly.

To remove WebDAV, open the site in the IIS Features panel and open the Modules feature. Select the WebDAV module if it is installed and choose the Remove action. Restart the site and check that topics can now be deleted.