Articles Tagged 'iis'

When using Spira or KronoDesk on a separate web and database server, the easiest configuration is to use SQL Server authentication to connect between the web server and database. However that means hard coding a password in the web server (in the Web.config file). So in this article we explain how to use Windows Integrated Authentication instead.

Spira (SpiraTest, SpiraTeam and SpiraPlan) and KronoDesk all use the Microsoft Internet Information Services (IIS) web server. A common need is to be able to change the IIS application name / virtual directory. For example, you may need to rename "SpiraTest" to "SpiraTeam" after you have upgraded your edition.

Most on-premise Spira and KronoDesk installations will be using the Microsoft Internet Information Services (IIS) Server to serve the application to users.  If you are experiencing performance problems or slow page load times (and you cannot move to our cloud version), this article will help you troubleshoot IIS worker process requests.

We had a customer that was using a VPN / Firewall to access our cloud instances of Spira. Most firewalls simply pass through the HTTPS traffic on port 443 unaltered. However some more stringent ones actually decrypt the HTTPS traffic, inspect the packets and then re-encrypt it for the user. In one case, this was causing an ERR_CONNECTION_CLOSED error.

Sometimes we get help desk tickets from on-premise customers regarding the performance of our web-based applications (SpiraTest, SpiraPlan, SpiraTeam and KronoDesk). Whilst every situation is different, this article provides some common best practices that should help having a high-performing system.

By default, IIS web server allows for limited file size to be uploaded to the web server. For IIS 6 and IIS 7, the default maximum file upload size is 4 MB and 28.6 MB respectively. IIS 7 returns a 404 error (HTTP Error 404.13 - CONTENT_LENGTH_TOO_LARGE) if someone uploads something larger than 30MB. In order to allow for larger file size uploads, a few server changes are required.

Our web-based products: SpiraTest, SpiraPlan, SpiraTeam and KronoDesk make use of the Microsoft IIS web-server and Microsoft SQL Server database platforms.

This KB article explains some of the more common error messages that can occur after installing one of our products and the steps to remedy them.

This article was written specifically for versions v3.0 - v4.2 of Spira and versions v1.x of KronoDesk.

If you install SpiraTeam or KronoDesk on Windows 8 or later, you need to make sure that the various IIS Roles and Features are installed. If not, you may find that various Menus don't display correctly or that the pages do not display any data. This article describes the features and roles that need to be included.

If you install SpiraTeam or KronoDesk on Windows Server 2012, you need to make sure that the various IIS Roles and Features are installed. If not, you may find that various Menus don't display correctly or that the pages do not display any data. This article describes the features and roles that need to be included.

This article describes how to resolve the following error message that can occur on new installations of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk when ASP.NET is not correctly configured. This message typically only occurs on Windows Vista, Windows7 or Windows 2008 Server.

HTTP Error 500.21 - Internal Server Error
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list.

If you face performance issues with Spira or KronoDesk when the users use Internet Explorer 9.0, there is a known issue in ASP.NET 4.5 that can cause the client to disconnect and all subsequent AJAX calls do not get processed. This article describes the symptoms and the solution.

When installing SpiraTest/Plan/Team or KronoDesk on a Windows 2008+ server, some of the controls or content in the application does not display correctly.