Practice CS: Login Failed for User 'CreativeSolutionsPracticeCsDatabaseOwner'

Alerts and notices
Leave Feedback

Error when opening PracCS, System.Data.SqlClient.SqlException: Login failed for user 'CreativeSolutionsPracticeCsDatabaseOwner'. Reason: Not associated with a trusted SQL Server connection.

Practice CS requires SQL Server to be configured to allow both Windows and SQL Authentication. This setting can be changed by following one of the two procedures described below. It is recommended to perform procedure 1 first and then to use procedure 2 if the first procedure fails to resolve the error.

Procedure 1: Rerun step 2 of the installation

  1. Download and execute the latest installation file from cs.thomsonreuters.com.
  2. When you get to the screen showing the three steps, click on the Step 2 to start it.

  3. On the next screen, choose the option to Use the CREATIVESOLUTION instance of Microsoft SQL Server.

    Note: If you used a different instance name, choose Use an existing instance of Microsoft SQL Server and select the instance name.

  4. Complete the installation by following the prompts to the last screen, then click Finish.

Procedure 2: Change the security settings in SQL Server Management Studio

  1. Open SQL Server Management Studio (Express) on the SQL server.
  2. Right-click the server.
  3. Choose Properties.
  4. ClickSecurity.
  5. Change the Security settings to allow for both Windows & SQL Authentication.

Procedure 3: Check the size of the database files (mdf and ldf)

  1. On the SQL server browse out to the data directory for the SQL files (default would be C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.CreativeSolution\MSSQL\DATA or C:\Program Files\Microsoft SQL Server\MSSQL10_50.CreativeSolution\MSSQL\DATA
  2. If the combined size of these two files is causing the database to be at or over the limit for SQL express (10GB for SQL Express 2012), you could receive this error
  3. If the mdf is nearing the SQL express limit, the firm will need to upgrade SQL.
  4. If the log.ldf file is causing the database to near the SQL express limit, stop SQL on the SQL server, remove the log.ldf file from the data folder and then start SQL.  A new log.ldf file will be created and will be very minimal in size.
  5. Open Practice CS.