• When I try to install the application, I get an error message that "IIS" is not installed.
    On Windows Server installations, IIS is usually installed as part of the factory configuration, whereas on Windows XP, Windows Vista, or Windows 7 installations, you typically need to manually add the components to the factory configuration. To check if you have IIS installed, click Start > Settings > Control Panel > Administrative Tools. Under the “Administrative Tools folder”, you should see an icon for “Internet Information Services”. If you don’t see this icon, then it means that you need to add IIS to your computer.
    > View the installation documentation for details of how to resolve
     
  • When I try to install the application, I get an error message that "MSDTC" is not installed.
    There is one common error that has been found with installations where Microsoft SQL Server was installed after IIS was installed. This typically affects only Windows XP Professional, but could occur in other situations. What happens is that the SQL Server installation inadvertently removes the Microsoft Distributed Transaction Coordinator (MSDTC) service from the system during the installation.
    > View the installation documentation for details of how to resolve
     
  • When I try to install the application, I get an error message that "ASP.NET" is not installed.

    If you installed the .NET Framework 4.0 after IIS then ASP.NET is typically configured for you, but if you installed IIS afterwards, then further manual steps may be necessary.

    To verify that ASP.NET has been correctly configured, click on Start > Settings > Control Panel > Administrative Tools > Internet Information Services to launch the IIS administrative console. Expand the name of the web-server (marked as local computer), expand the “Web Sites” folder, right-click on “Default Web Site” and choose the “Properties” link. This will bring up the IIS configuration dialog-box. Then click on the 'Configuration' button to bring up the “Application Configuration” window. If ASP.NET is correctly configured, you will see entries marked “.aspx”, “.asax” in the “Application Mappings” portion of the window. If you don’t see those entries, then ASP.NET needs to be configured for this web site.
    > View the installation documentation for details of how to resolve

    Also please check that you have the full .NET Framework 4.0 installed and not just the limited ".NET Framework 4.0 Client Profile". If you have just the .NET 4.0 Client Profile installed, you need to download and install the full .NET Framework 4.0 from Microsoft's website. This will ensure that you have all the necessary server components.

  • When I try to access the application, I get a “The underlying provider failed on Open. [System.Data.EntityException {0x80131501}]” message

    This error is most likely caused by a misconfiguration within IIS when setting up the application pool for Spira Team.
    1. First, go into IIS and make sure the "Identity" for the application pool is set to "NETWORK SERVICE". If it is not, this can be changed in the advanced settings for that application pool.

    2. Try to disable impersonation – it can be found in IIS: under Sites ->  Website containing SpiraTeam -> SpiraTeam. Then, click on SpiraTeam and find the "Authentication" settings under the IIS settings section for the SpiraTeam site. Once there, make sure ASP.NET Impersonation is disabled.

  • When I try to access the application, I get a "page cannot be displayed. HTTP 500 - Internal server error" message.
    If you receive the dreaded “IIS 500 Internal Error” webpage when you try and access an ASP or ASP.NET application on the server, there can be a myriad of causes. However a good first place to look for the cause is inside the Windows Event Viewer, which stores all errors raised in the system. For your peace of mind, we offer one year of FREE Support with all our products, so if you receive such errors, email the contents of the error log to support@inflectra.com and we will work with you to resolve the problem.

  • When I try to access the application, I get a “HTTP Error 500" or “Internal error 500” message with no record in Event Viewer

    Error 500 is very common for the first time on-premise installations and range of root causes can vary from security policies blocking required files to IIS configuration mismatch, including IIS, ASP.NET 4.x, and other supporting technologies.
    1. Recommendation is to load that URL and immediately check the server's event logs so to slim down the number of logged items.
    2. Verify you haven’t miss any details as it listed in documentation
    > View the IIS installation documentation
     
  • When I try to access the application, I get a "page cannot be displayed. HTTP 404 - Page Not Found" message.
    This error message can get displayed on a Windows 2003 Server application if ASP.NET is not installed or enabled. There are two common solutions to this error message: Ensure that ASP.NET is installed:
    1. Click Start, and then click Control Panel
    2. Click Add or Remove Programs
    3. Click Add/Remove Windows components
    4. Double-click Application Server, and then click Details
    5. If the ASP.NET check-box is not checked, click to select the ASP.NET check box, and then click OK
    6. Click Next
    7. Click Finish
    Ensure that ASP.NET is enabled:
    1. Open IIS Manager, expand the master server node (that is, the Servername node), and then select the Web service extensions node
    2. In the right pane of IIS Manager, right-click the ASP.NET 4.0 extension to enable it if it is not already enabled.
    3. Click to select the Allow check box
       
  • When I try to access the application, I get a Compiler Error Message: CS0016: Could not write to output file 'c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files...'
    There are many reasons for this error, however the following two links outlines the most common causes and solutions:
  • How do I setup the system administrator (SA) account in Microsoft SQL Server so that I can install the application?
    What you need to do is setup the built-in SA account on SQL Server. This also means that the SQL Server needs to be setup for mixed-mode authentication where it allows both SQL Server and Windows logins. To do this, follow these steps:
    1. In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.
    2. On the Security page, under Server authentication, select 'SQL Server and Windows Authentication Mode', and then click OK.
    3. In the SQL Server Management Studio dialog box, click OK, to acknowledge the need to restart SQL Server.
    4. In Object Explorer, right-click your server, and then click Restart. If SQL Server Agent is running, it must also be restarted.
    5. In Object Explorer, expand Security, expand Logins, right-click sa, and then click Properties.
    6. On the General page, you may have to create and confirm a password for the sa login.
    7. On the Status page, in the Login section, click Enabled, and then click OK.
       
  • When I try to access the application, I get the error message "Parser Error Message: Unrecognized attribute 'type'."
    This error means that your IIS web server is currently configured to run a version of ASP.NET earlier than v4.0 (which is required). To switch IIS to ASP.NET to version 4.0, please follow these steps:
    1. Open up the IIS Administration Console on the server
    2. Expand the Web Sites folder and right-click on Default Website
    3. Select the ASP.NET tab and change the ASP.NET version to v4.0
    4. Click OK and close the Administration Console. You should now be able to access the application.
       
  • When I try to access the application, I get the error message System.Security.SecurityException: Request for the permission of type 'System.Diagnostics.EventLogPermission, System, Version=XXXX' failed.
    There are two common reasons for this error:
    1. The web server is set to run in Medium-Trust mode, which does not allow the system to log to the Windows Event Log. You need to disable event logging by opening up C:\Program Files\SpiraTeam\Web.Config and changing:
      <setting name="EventLogSource" serializeAs="String">
<value>SpiraTeam</value>
</setting>
      to:
      <setting name="EventLogSource" serializeAs="String">
<value />
</setting>

       

    2. The IIS Web Site that the application is running on is configured to be managed by Microsoft SharePoint. In this case you need to either disable SharePoint from managing the web site (through the SharePoint Web Admin) or you need to create a new IIS Web Site to host the application and make sure that SharePoint is not managing that new site.
       
  • When I try to access the application, I get the error message "Parser Error Message: Unrecognized attribute 'targetFramework'."
    This error means that your IIS web server is currently configured to run a version of ASP.NET earlier than v4.0 (which is required). To switch IIS to ASP.NET to version 4.0, please follow these steps:
    1. Open up the IIS Administration Console on the server
    2. Expand the Web Sites folder and right-click on Default Website
    3. Select the ASP.NET tab and change the ASP.NET version to v4.0
    4. Click OK and close the Administration Console. You should now be able to access the application.