Archive for the ‘Profitbase Studio’ Category

Error when refreshing list of online templates

December 5th, 2011 No comments

A customer ran into an issue today when trying to load the list of online templates while creating a new Solution.
When the customer hit the “Refresh” button to load the online template list in the New Solution wizard, he got an error saying “System.ServiceModel.Security.MessageSecurityException:An unsecured or incorrectly secured fault was received from the other party….”

Luckily, we were able to log on to the customer and trobleshoot the issue by enabling diagnostics for WCF and use the SvcTraceViewer tool to read the log and track down the following service error message;

Security processor was unable to find a security header in the message. This might be because the message is an unsecured fault or because there is a binding mismatch between the communicating parties.   This can occur if the service is configured for security and the client is not using security.

This is a pretty generic error message, and the error could be caused by a number of things, but after some investigation we started to suspect it had something to do with time stamps in the message headers, so we checked the computer clock at the client and it turned out that it was off by about 15 minutes.

Once we had set the correct time for the computer clock, everything worked as expected.

Categories: Profitbase Studio Tags:

Modifying the Profitbase Studio window title

October 19th, 2010 No comments


A probably unknown (and probably also a pretty much useless) feature is the ability to modify the text displayed in the Profitbase Studio application window (the application title). By default, the window title is “Profitbase Studio”, but this can be modified with a leading and trailing text.

To do this, you need to edit the ManagementStudio.config-file in the application user settings folder, which normally is something like C:\Users\[user]\AppData\Roaming\ProfitBase\PBMS\[version].
Open the file and insert a AppNamePrefix and / or AppNamePostfix XML element as shown below;

<?xml version="1.0" encoding="utf-8"?>
<Setting Name="AppNamePrefix"> <Value> <string>Demo - </string> </Value> </Setting> <Setting Name="AppNamePostfix"> <Value> <string> My Company</string> </Value> </Setting> </Settings>

Categories: Profitbase Studio Tags:

Profitbase Studio / Server and SQL Server dependencies

September 7th, 2010 No comments

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 the following components from the SQL Server 2005 Feature Pack.

  1. Microsoft SQL Server 2005 Management Objects Collection
  2. Microsoft SQL Server 2005 Analysis Services 9.0 OLEDB Provider

When PB Studio / Server is running on the SQL Server 2008 Platform
Install SSMS 2008 OR install the following components from the SQL Server 2008 Feature Pack.

  1. Microsoft SQL Server 2008 Management Objects (requires Microsoft Core XML Services 6.0, Microsoft SQL Server Native Client and Microsoft SQL Server System CLR Types)
  2. Microsoft Analysis Management Objects

Extracting MSI files from the installer .exe

March 4th, 2010 No comments

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

February 3rd, 2010 No comments

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

January 8th, 2010 No comments

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.

Categories: Profitbase Studio Tags:

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

December 22nd, 2009 No comments

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”

Categories: Profitbase Studio Tags: