By Jessica Chiang


Step-by-Step Guide to Setup Tackle, the Web-Based SCRUM Tracking Site



1.    Log in as a Windows administrator. In our case, itís jessica.

2.    Stop the Apache Web Server if itís running, using Apache Monitor. If Apache Web Server is running, IIS Web Server can not start because


3.    Make sure that SQL Server 2005 Express is in mixed login mode (windows authentication and SQL authentication).

Install SQL Server 2005 Express and SQL Server Management Studio if not already installed. Login to SQL Server using SQL Server Management Studio, then right click on the server, JESSICA-EF96BBD\SQLEXPRESS (SQL Server 9.0..). Then select Property.



At the Server Property Prompt, select Security page, and select SQL Server and Windows Authentication mode (mixed mode). Then hit OK.



4.      Install AJAXASP.Net and Report Viewer.

You can obtain AJAXASPExtSetup.msi from the office Tackle website, and ReportViewer.exe from this Microsoft download page.

5.      Obtain system information required to install Tackle


Obtain SQL Server instance name using SQL Server Configuration Manager that came with SQL Server 2005 Express. As the screenshot below shows, the SQL Server instance name in this example is JESSICA-EF96BBD\SQLEXPRESS.







6.    Install Tackle


Double click Tackle v1[1].02.msi,



Click Browse button to find the SQLServer name but replace (local) with the machine name found in step 5.Enter the Windows Administrator account you wish to use for Tackle Administrator.



Open C:\Inetpub\wwwroot\Tackle\web.config and search for xmlns, and remove all strings starts with xmlns, as shown in red below.



To set IIS web site permission, use Computer Management utility. On Windows 2003 server, go to Start->Administrative Tools->Computer Management. On Windows XP, go to Control Panel ->Administrative Tools->Computer Management.


Go to System Tools->Service and Applications->Internet Information Services->Web Sites, and then start the Default Web Site if not already started. Make sure that Apache Web Server is stopped if itís running, because both Apache Web Server and IIS Web Server listen to port 80.



Then right click on Tackle, select Property, and select Directory Security tab. Click the Edit button. Then set the directory security as shown. Make sure that Anonymous access checkbox is checked, and Integrated Windows Authentication is checked.††



Next, set the directory permission for C:\Inetpub\wwwroot\Tackle directory. First, create a Group called IIS_WPG and then add Tackle users to this group. Go to Computer Management->System Tools->Local Users and Group. Right click on Groups and select New Group to add a new group named IIS_WPG. Then add user jessica to the group.



Enter IIS_WPG for Group name, and some simple description to describe this group. Then click Add to add the administrator member to this group.



Click the Advanced button.


Click the Find Now button to browse all Users and Groups. Select Jessica, which is the administrator account selected at Step 6. Click OK to confirm the selection.


User jessica is now added to IIS_WPG. Click OK to save.


Click Create to create this new group, IIS_WPG.



Right click on Tackle and select Property. Then click Directory Security tab.






7.    Trouble Shooting

        FireFox on IIS Problem




Enter ntlm as Filter.


Enter localhost as a trusted URI.


Then you should be able to go to http://localhost/Tackle without FireFox prompting for password and username.

        Reinstalling Tackle




When the install just did not work and you need to start from a clean slate, first uninstall Tackle by running the install MSI and select remove.


The uninstaller does not remove the Tackle database, therefore Tackle database must be deleted manually. Login as an administrator (in this case, jessica) to SQL Server 2005 Express using SQL Server Management Studio


Then select the Tackle database by selecting SQL Server name (JESSICA-EF96BBD\SQLEXPRESS in this case), Database, and then Tackle. Right click on Tackle and select Delete.





Back to Perceptual Complexity 1