Unexpected error while installing

2 posts, 1 answers
  1. Mehmet
    Mehmet avatar
    1 posts
    Member since:
    Jul 2010

    Posted 29 Jul 2010 Link to this post

    I am trying to install standard edition of TeamPulse and getting an unexpected error. Using Windows Server 2008 R2 and SQL Server Express R2.



    Executing sql script DatabaseExtensions.TeamPulse_CreateSchema.sql on connection server=(local)\sqlexpress;Integrated Security=true;DATABASE=master
    MSI (s) (1C!04) [10:10:32:112]: Closing MSIHANDLE (118) of type 790531 for thread 5892
    MSI (s) (1C!04) [10:10:33:917]: Creating MSIHANDLE (119) of type 790531 for thread 5892
    Failed to execute sql, exception details: Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: Invalid column name 'projectid'.
    Invalid column name 'iterationid'.
       at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
       at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
       --- End of inner exception stack trace ---
       at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
       at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand)
       at DatabaseExtensions.CustomActions.ExecuteSQL(Session session, String connectionString, String sql)
       at DatabaseExtensions.CustomActions.ExecuteSqlContent(Session session, String contentName)
    MSI (s) (1C!04) [10:10:33:919]: Closing MSIHANDLE (119) of type 790531 for thread 5892
    MSI (s) (1C!04) [10:10:33:919]: PROPERTY CHANGE: Adding INSTALLERROR property. Its value is '**********'.

  2. Answer
    David Harris
    David Harris avatar
    1 posts

    Posted 29 Jul 2010 Link to this post

    Hi Mehmet,

    Unfortunately we appear to have a bug in our database creation script in that it is not specifying the database collation when creating the TeamPulse database. Without specifying the collation it appears to be inheriting the collation default of the server it is installed on, which I presume is Case-Sensitive in your scenario. The TeamPulse database needs to be Case-Insensitive for our scripts and queries to run, hence the error you are seeing.

    We will rectify this situation in an upcoming service pack, however the only workaround I can see at this time is for you to select a SQL Server instance that is configured to use a default Case-Insensitive (CI) collation value.

    Best wishes,
    David Harris
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top