Sometimes, a relatively small table is split across 2 pages in the same report.

To avoid this from happening, you have to right click on that specific table in Report Builder, and choose Tablix Properties. After the properties window opens check the Keep together on one page if possible option.

Full story »

Problem

When executing an SSIS package, the following error appears:

0x80040E55 Column does not exists

Solution

I encountered this error when running a SSIS package that executes a stored procedure, inside an OLE DB Source component, on several remote servers. The result set obtained is saved into a local table.

The problem is that when using stored procedures as the source of data for the SSIS pipeline, even if you can preview the data returned from the stored procedure, when pressing the columns mapping tab of the OLE DB Source Adapter, the columns are not displayed.

Full story »

Problem

When executing an SSIS package, the following error appears:

SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. 

Solution

If the error messages are not a concern and you want to get rid of them, open the Properties window and, under Execution section, you will see the MaximumErrorCount property. You can change it?s value from 1 (the default) to whatever you want.

The Properties window should already be open in the bottom right of BIDS (Business Intelligence Development Studio). If you don?t see it, you can open it from the menu by going to View/Properties Window, or just hit the F4 key.

Full story »

Problem

When executing an SSIS package, the following error appears:

Error: component "OLE DB Source" (1) failed the pre-execute phase and returned error code 0xC0010001

Solution

I was using a parameterized procedure in an OLE DB Source component and I forgot to map the variable to the procedure?s parameter.

Full story »

Problem

When executing an SSIS package, the following error appears:

An error occurred while assigning a value to variable " User::Variable_Name": "The type of the value being assigned to variable "User:: Variable_Name " differs from the current variable type. Variables may not change type during execution. Variable types are strict, except for variables of type Object.

Solution

I encounter the above error while using an Int64 variable to store the result set from a SQL Task. The value returned by the query used in the SQL Task was stored in Bigint variable.

It seems that this is a normal behavior when trying to store Bigint results into Int64 data type SSIS variables.

Full story »