Installation under Windows 7


1. IIS installation/configuration

2. SQL Server installation/configuration

3. Installation of Sprintometer Web Service

4. Testing the installation

5. Configuring the client

6. Troubleshooting



1. IIS installation/configuration


IIS is not installed on Windows 7 by default. The following steps will ensure required IIS components are installed.

  1. Open Control Panel.
  2. Select 'Programs'.




  1. Click 'Turn Windows features on or off'.


Windows Features


  1. Make sure 'Internet Information Services' is selected.
  2. Under 'Web Management Tools'/'IIS 6 Management Compatibility', make sure 'IIS Metabase and IIS 6 configuration compatibility' is selected.
  3. Under 'World Wide Web Services'/'Application Development Features', make sure 'ASP.NET' is selected.


Internet Information Services Settings




2. SQL Server installation/configuration


Sprintometer Web Service requires SQL Server 2005 SP3 or SQL Server 2008 SP1. Earlier versions are not supported.


If you don't have the required version of SQL Server installed you can download and install SQL Server 2008 Express SP1 from here:


When you install SQL Server, make sure you select Mixed (SQL Server and Windows) authentication mode. Other options can be left with default values.



Mixed Authentication Mode



If you already have SQL Server installed and it is using Windows authentication mode, you'll have to switch it to SQL Server and Windows authentication mode following instructions from this link:




3. Sprintometer Web Service installation


Unpack into a temporary directory and run setup.exe. Install all prerequisite software if prompted to by the installation wizard.



Welcome Screen



Follow the installation screens. When prompted, select the web site and application pool where you want Sprintometer Web Service to be installed.



IIS Configuration Screen



Sprintometer Web Service is an ASP.NET 2.0 application, and thus it should be put into an Application Pool which uses .NET Framework 2.0. In standard configuration 'Default App Pool' uses .NET Framework 2.0 so it will work fine.


When you get to the database configuration screen, select SQL Server where you want Sprintometer database to be created and enter database administrator's password. If your server is not listed type in the name manually. The installer will create the database with name 'sprintometer' and SQL Server login 'sprintometer'. You can later change the default password for login 'sprintometer' and update application's Web.config accordingly.



Database Configuration Screen



Email configuration screen is self explanatory. Note that TLS and SSL are not supported in the current version, so you should use SMTP server that does not require TLS or SSL.



Email Configuration Screen



When you press 'Send Test Message' button, the following email will be sent to the 'Email for test messages':



Test email message



Reboot the system to complete the installation.



Reboot Prompt



After reboot, proceed to chapter 4.




4. Testing the installation


Open your web browser and go to the following URL: http://localhost/SWS/SWS.asmx

You should see this screen:



Installation Check Screen 1



Click 'CheckConfiguration' method.



Installation Check Screen 2



Press 'Invoke' button. If everything is OK you should see this message:



Installation Check Screen 3




5. Configuring the client


Now you can enter the URL of your new web service into Server Settings screen of your Sprintometer client. Change server URL and press OK in the settings dialog.



Sprintometer Server Settings



If you have not configured SSL in IIS, you need to use http: instead of https: in the server URL. Sprintometer client supports both HTTP and HTTPS protocols. If you need additional security, you can configure IIS to use SSL and disable HTTP access.


You can transfer existing projects from a different server to your new server. Open the project from the old server, then change server settings to point to the new server, then save the project on the new server using 'Save As' command. Make sure that all users assigned to this project exist on the new server under the same logins (or just remove unneeded users from the project).




6. Troubleshooting


Problem: The setup fails with error message "The installer was interrupted before Sprintometer Web Service could be installed. You need to restart the installer to try again".

Possible reason: IIS Metabase and IIS 6 configuration compatibility is not installed.

Solution: Refer to chapter 1 for information on IIS installation requirements.


Problem: The installation was completed but when I open "http://localhost/SWS/SWS.asmx", I get "HTTP Error 404.3 - Not Found. The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map."

Possible reason: ASP.NET support in IIS is not installed.

Solution: Refer to chapter 1 for information on IIS installation requirements.


Problem: The installation was completed but when I invoke CheckConfiguration method, I get an error "System.Data.SqlClient.SqlException: Login failed for user 'sprintometer'. The user is not associated with a trusted SQL Server connection."

Possible reason: SQL Server is not using Mixed Authentication mode.

Solution: Refer to chapter 2 for information on SQL Server installation requirements.


Problem: When I open "http://localhost/SWS/SWS.asmx", I get the following error: "The specified module could not be found. (Exception from HRESULT: 0x8007007E)"

Possible reason: 'bin' subdirectory of Sprintometer Web Service is not included in system PATH.

Solution: Add Sprintometer Web Service 'bin' subdirectory (where SprintometerWS.dll is located) to the system PATH environment variable and reboot your system.


Problem: When I save my project on the new server, I get the following error: "Cannot connect to server. SOAP Error: Server was unable to process request. ---> The INSERT statement conflicted with the FOREIGN KEY constraint 'FK_ProjectUser_User'."

Possible reason: Some user logins assigned to this project are not registered on the new server.

Solution: Make sure that all assigned users exist on the new server or just remove unneeded users from the project.


Useful Services

Latest news