Profitbase Studio on Terminal Server

  1. Create local folder, i.e. "c:\ProfitbaseLicense" on server where Profitbase Studio is going to run.
  2. Give "Users"-group rights to modify the contents (Allow Modify).
  3. Go to "Environment Variables" on the server.
  4. Create a new system environment variable called "Profitbase".
  5. Set it to "c:\ProfitbaseLicense\%USERNAME%"
  6. Open Profitbase Studio.
  7. Select Tools/Options from the menu. An "Options" window appears.
  8. Select "Configuration Manager Settings".
  9. In "Configuration path" choose "Use Environment Variable Scope": Machine
  10. Set "Environment variable" to "Profitbase".

The file CfgManager.config is created in step 7. This file can also be copied directly into the Client32 or the Client64 catalog, alternatively be set via the installer. 

CfgManager.config:

<?xml version="1.0" encoding="utf-8"?>
<CfgPathManager>
  <ConfigSetting ConfigType="EnvironmentVariable">
     <Config Variable="Profitbase" Target="Machine" />
  </ConfigSetting>
</CfgPathManager>

Pre-requirements and installation

Click here for requirements.

All SQL versions

Package

32 bit

64 bit

Microsoft® Core XML Services (MSXML) 6.0 SP 1

Link

Link

 

SQL Server 2008 R2 (v. 10.50)  

Package

32 bit

64 bit

Microsoft® SQL Server® 2008 R2 Native Client

Link

Link

Microsoft® System CLR Types for SQL Server® 2008 R2

Link

Link

Microsoft® SQL Server® 2008 R2 Analysis Management Objects

Link

Link

Microsoft® SQL Server® 2008 R2 Shared Management Objects

Link

Link

 

SQL Server 2012 (v. 11.0)

Package

32 bit

64 bit

Microsoft® SQL Server® 2012 Native Client

Link

Link

Microsoft® System CLR Types for SQL Server® 2012

Link

Link

Microsoft® SQL Server® 2012 Analysis Management Objects

Link

Link

Microsoft® SQL Server® 2012 Shared Management Objects

Link

Link

Note! SQL Server Native Client (SNAC) is not supported beyond SQL Server 2012. The Microsoft ODBC Driver for SQL Server provides native connectivity from Windows to Microsoft SQL Server and Microsoft Azure SQL Database.

SQL Server 2014 (v. 12.0)

These files must be selected for download for each package from the Microsoft SQL Server 2014 Feature Pack.

Package

Link

File name

Microsoft® ODBC Driver 11 for Microsoft SQL Server® - Windows

Link

msodbcsql.msi

Microsoft® System CLR Types for SQL Server® 2014

Link

SQLSysClrTypes.msi

 

Microsoft® SQL Server® 2014 Analysis Management Objects

Link

SQL_AS_AMO.msi

Microsoft® SQL Server® 2014 Shared Management Objects

Link

SharedManagementObjects.msi

 

SQL Server 2016 (v. 13.0)

These files must be selected for download for each package from the Microsoft SQL Server 2016 Feature Pack.

Package

File name

Microsoft® ODBC Driver 11 for Microsoft SQL Server® - Windows

msodbcsql.msi

Microsoft® System CLR Types for SQL Server® 2016

SQLSysClrTypes.msi

 

Microsoft® SQL Server® 2016 Analysis Management Objects

SQL_AS_AMO.msi

Microsoft® SQL Server® 2016 Shared Management Objects

SharedManagementObjects.msi

 

SQL Server 2017 (v.14.0)

Some of these files must be selected for download for each package from the Microsoft SQL Server 2017 Feature Pack.

Package

File name

Microsoft® ODBC Driver 11 for Microsoft SQL Server® - Windows

msodbcsql.msi

Microsoft® System CLR Types for SQL Server® 2017

SQLSysClrTypes.msi

 

NA (Microsoft® SQL Server® 2017 Analysis Management Objects - see Note 

SQL_AS_AMO.msi)

NA (Microsoft® SQL Server® 2017 Shared Management Objects - see Note

SharedManagementObjects.msi)

 

Microsoft Shared Management Objects (SMO) and Analysis Management Objects (AMO) is removed from Microsoft's SQL Server Feature Pack. 

It will be included in future PS64 builds.

Click here to download a set of 2017 dll's in a zip (SMO, AMO, SQLClrTypes). 

Extract the files and copy them to the install directory of both Profitbase Studio client and server. (e.g.  C:\Program Files\Profitbase\Profitbase Studio 6.3\Client64).