This project has moved. For the latest updates, please go here.

Quick Setup

These instructions are for new installations using the default configuration. These instructions assume you are deploying the pre-compiled distribution of the application to a Windows server running IIS.

Quick Setup Requirments:

  • Windows Server with IIS 7 (or higher)
  • Microsoft .NET framework 4.5
  • Microsoft SQL Server 2012 LocalDB Edition with the default instance named "v11.0".

Web Site:

To deploy the web application, all you have to do is create an IIS virtual directory or web site and copy the application's files to the server.

In IIS you should configure your virtual directory or web site to use an application pool that is setup for .NET 4 and the integrated mode pipeline.

TicketDesk should not require any customization to the default IIS settings in most environments. If using Active Directory security, you must enable Windows Authentication in IIS (you can leave anonymous enabled too if you wish).


  • Once you have copied the application's files to the server, run the application. Login as as "admin" with the password "admin".
  • Change your admin user's password in the My Account section.
  • Navigate to the admin section, then go to Security Management, then Manage Users. Remove the default user accounts for "otherstaffer" and "toastman". Create any additional users you desire (you can have your users register themselves if you prefer).
  • Navigate to the admin section, then go to the "change application settings" page. Change settings to values that are appropriate for your organization and preferences. Pay particular attention to the following email related settings:
    • From Email Address
    • From Email Display Name
    • Site Root Url For Email
    • Enable Outlook Friendly Html Email
  • You will also need to edit web.config and setup the mailSettings section with values appropriate for your email environment. A typical setup for email using a locally installed SMTP agent would look like this:
<smtp deliveryMethod="Network">
<network host="localhost" port="25" defaultCredentials="true"/>

Cleanup (optional):

TicketDesk's default distribution contains some files that you can (optionally) remove from the application before deployment.
  • Within app_data: Only the TicketDesk.mdf and TicketDesk.ldf files are needed. The other folders contain scripts and alternate database versions that are NOT used at runtime.
  • In the root folder, you can remove SQLWeb.config and ADWeb.config. These are not used at runtime.

Last edited Nov 21, 2014 at 3:40 PM by StephenRedd, version 8


Odehabuzaid Nov 12, 2015 at 6:13 PM 
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

StephenRedd Jul 22, 2015 at 4:58 AM 
2.5 will not support SQL 2005. It lacks too many modern features, even some of the basic datatypes that Entity Framework takes for granted.

Honestly, I don't even know for 100% sure that TicketDesk 2.1 is still compatible with 2005 anymore. I stopped testing on SQL 2005 two or three of years ago; however; TD 2.1 was compatible with SQL 2005 when it was designed, and should continue to do unless Entity Framework itself has broken compatibility (which is a possibility).

jonatanmoleiro Jul 17, 2015 at 4:52 PM 
Using SQL Server 2005 and triying to install the version v2.5 i get this error:

There is no store type corresponding to the conceptual side type 'DateTimeOffset' of primitive type 'DateTimeOffset'.

Is still supported SQL Server 2005?

I'll try to install v2.1 instead :(

StephenRedd Jun 4, 2015 at 3:23 AM 
amedrano, localdb should be installed on the web server, it doesn't support remote connections. Also, if you installed SQL 2014 localdb, you will need to update the connection strings in web.config; 2012 uses the server name "(LocalDB)\v11.0" while 2014 uses "(LocalDB)\MSSQLLocalDB".

amedrano Jun 2, 2015 at 8:52 PM 
I followed steps but i have this error on firts run, i have installes sql localdb

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred. Cannot create an automatic instance. See the Windows Application event log for error details.


dibblm Jun 30, 2011 at 7:21 PM 
Correction on AJAX. Looks like MVC..

dibblm Jun 30, 2011 at 7:18 PM 
Following these instructions. The following errors are being provided. Seems the AJAX extensions also need loaded ? i will follow up and let you know the results.

Server Error in '/' Application.

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'System.Web.Mvc, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Source Error:

Line 71: <add assembly="System.Web.Abstractions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
Line 72: <add assembly="System.Web.Routing, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
Line 73: <add assembly="System.Web.Mvc, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
Line 74: <add assembly="System.Data.Entity, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
Line 75: </assemblies>

Source File: C:\inetpub\wwwroot\TicketDesk_2.0.1_Beta_-_Compiled\web.config Line: 73

Assembly Load Trace: The following information can be helpful to determine why the assembly 'System.Web.Mvc, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1