Profitbase Studio / Server and SQL Server dependencies

Profitbase Studio / Server is using parts of the SQL Server API directly, so it is required that these components are installed on the same computer as the Profitbase Studio and/or Profitbase Studio Server. Although these requirements are listed in the System Requirements document, they may from time to time (using clever ninja tactics) avoid attention from people setting up the system.

So a quick recap of the SQL Server dependencies for Profitbase Studio / Server;

When PB Studio / Server is running on the SQL Server 2005 Platform
Install SSMS 2005 OR install Microsoft SQL Server 2005 Management Objects Collection which is a part of the SQL Server 2005 Feature Pack.

When PB Studio / Server is running on the SQL Server 2008 Platform
Install SSMS 2008 OR install Microsoft SQL Server 2008 Management Objects whis is a part of the SQL Server 2008 Feature Pack.

Extracting MSI files from the installer .exe

Profitbase software is normally installed by running an installer .exe-file. The .exe-files act as bootstrappers for reading the content of the .MSI-file, checking if the required version of the Windows Installer is installed on the system, and then launches the .MSI that takes care of the actual installation of the product.

If for example you want to install the product using Group Policy deployment, you need to extract the .MSI from the .EXE. A way to do this is using the UniversalExtractor tool. This tool extracts the .MSI-file (along with other files as well) from the .EXE-file to a folder of your choice.
Once the .MSI-file is extracted, you can run it directly or use the Windows Installer tool (MSIEXEC.exe) from the command prompt to do additional actions. To get a list of your options with the Windows Installer tool, simply open a command prompt and type “MSIEXEC”

Activity Start Interval in the Parallel Activity

A Data Flow Parallel Activity has a setting called “Activity Start Interval”. Activity Start Interval specifies the time in seconds elapsed between the start of each activity. For example, if the value is 0.2, the activities will start at a 0.2 seconds interval. The reason you’d want to use this setting is that on some systems, you may experience connection pool problems when the activities are started to rapidly. As a result, the Data Flow activities will fail to start and you will get the following error message in the log.
Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.

Setting the Activity Start Interval to a higher value will fix this problem.

Getting a security error when importing or exporting templates

You may get the following error message when importing or exporting templates to the Profitbase Template Store.

“An error occurred when verifying the security for the message”
or a message similar to this
“The security timestamp is invalid because its creation time (‘8/262008 1:45:51 PM’) is in the future”

If you get this error message, please make sure that your Date and Time settings are correct. Your system clock cannot be more than 5 minutes off.
The reason for this is to prevent message replay attacks against the Profitbase Template Store web service.

Setting the Run As property to SQL Authentication gives “Object reference not set to an instance of an object” error message

When setting the Run As property to SQL Authentication, you may get the following error message when you click the User Name text box: “Object reference not set to an instance of an object”. 

This is caused by a bug in .NET Framework 3.5 (SP1), but is reported to be fixed in .NET 4.0.
To work around the issue, you need to disable “Advanced Text Services” found in Control Panel –> Regional and Language Options –> Languages Tab –> Details… Button –> Advanced Tab –> Check “Turn off advanced text services”