This page is maintained for older versions of Spira only. The latest documentation can be found at: https://spiradoc.inflectra.com

SpiraTest Administration Guide Help Viewer

1. Introduction
2. Installing SpiraTeam®
3. System Administration
4. Appendices
Search:
1. Introduction
2. Installing SpiraTeam®
3. System Administration
4. Appendices

4.1. Appendix A – Troubleshooting

If you receive the dreaded “IIS 500 Internal Error” or the “Server Application Not Available” webpage when you try and access SpiraTeam® for the first time, 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.

To open the Event Viewer, click Start > Settings > Control Panel > Administrative Tools > Event Viewer. This will open up the event viewer:

Click on the Application and System folders in turn and look for errors raised by “MSSQLSERVER”, “SpiraTest”, “SpiraTest DataSync Service”, “DCOM”, “ASPNET” or “IIS”. Click on the error message, and copy the text of the message into a text editor (e.g. Notepad).

Before contacting Inflectra® customer support with the specific error message, here are a couple of common causes for the above errors together with the appropriate resolutions:

  • The ASP.NET process account has been disabled (Windows XP only)Go to Start > Control Panel > Administrative Tools > Computer Management and launch the Windows computer management console. Expand Local Users and Groups > Users and then double-click on the 'ASPNET' account. Make sure that the ASPNET user is not disabled.This only applies to installing SpiraTeam on Windows XP. For other versions of Windows, the ASPNET user is set per-application pool and typically is set to the built-in NETWORKSERVICE account, so this won’t apply.
  • The ASP.NET process account does not have sufficient permissionsRight-click on the C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319 folder (and any other versions of .NET that are listed) and make sure that the ASPNET, NETWORKSERVICE and LOCALSERVICE accounts are all listed with Full Control. If that doesn’t fit the issue and you are using Windows Server, open up the IIS manager and right-click on the Application Pool that SpiraTeam® is running under and make sure that the identity listed has Full Control permissions on the same folders.
  • The Windows Event Log is fullOpen up the Application and System event logs, right-click on the log name and choose Properties. Make sure that both are set to “overwrite events as needed”. If they are not set to overwrite as needed, change the setting then manually clear both logs.

If the resolutions above were not able to resolve the issue, please send an email to and include the error message from both the web page and the Windows Event Logs.