In the page header I wanted to display the page number in the following format:
page x(y)

Should be simple enough
="Sida "+CStr(Globals!PageNumber)+" ("+CStr(Globals!TotalPages)+")"
or
"page: " + Globals!PageNumber.ToString + " of " + Globals!TotalPages.ToString

But that didn’t work. In MS Word the header always said page 1(1). The solution is to use “Expression with Text Runs” as stated on technet. In the page number example that means
="Sida " & Globals!PageNumber & " (" & Globals!TotalPages & ")"

Quite often when you work with analyzing data you need to be able to see your KPI’s per day, week or some other time-frame. Both Sweden and Norway has a fairly unusual way to handle week numbers which might make it a bit difficult to find scripts that are ready to use. Here is my DimDate table and the procedure I have to populate the table.

This script is based on a post by Robin Langell.

The changes that I have made are:

1. Changed object names to English
2. Added dayInYear
3. Use ISO_WEEK instead of WEEK (gives Swedish/Norwegian week behavior)
4. Made it into a procedure
5. Set start and end date (instead of creating a certain number of days)
6. Made Sunday to be day number 7 (instead of day 0)

Ofcourse feel free to let me know if there are any errors in my code!

Creating the table:

use [YourDB]
go

declare @table as varchar(50)
SET @table = 'DimDate'

IF NOT EXISTS (
	select 'Y'
	from sys.tables
	where name = @table
	)

	BEGIN
		CREATE TABLE dbo.dimDate (
			ID	INT NOT NULL,
			[Day]	DATETIME NOT NULL,
			[Week]	INT NOT NULL,
			[Month]	INT NOT NULL,
			[Quarter]	INT NOT NULL,
			[Year]	INT NOT NULL,
			DayInYear INT NOT NULL,
			DayInMonth	INT NOT NULL,
			dayInWeek	INT NOT NULL,
			YearWeek	INT NOT NULL,
			MonthWithZero NVARCHAR(2) NOT NULL,
			[DayName]	NVARCHAR(10) NOT NULL,
			[MonthName]	NVARCHAR(20) NOT NULL
		CONSTRAINT PK_DimDatum_datumNyckel PRIMARY KEY (ID)
		);
		SELECT 'Table did not exist, table '+ @table +' created';
	END ELSE
		IF NOT (
			SELECT COUNT(*)
			FROM DimDate
			) > 0
		BEGIN
			Drop Table DimDate;

			CREATE TABLE dbo.dimDate (
				ID	INT NOT NULL,
				[Day]	DATETIME NOT NULL,
				[Week]	INT NOT NULL,
				[Month]	INT NOT NULL,
				[Quarter]	INT NOT NULL,
				[Year]	INT NOT NULL,
				DayInYear INT NOT NULL,
				DayInMonth	INT NOT NULL,
				dayInWeek	INT NOT NULL,
				YearWeek	INT NOT NULL,
				MonthWithZero NVARCHAR(2) NOT NULL,
				[DayName]	NVARCHAR(10) NOT NULL,
				[MonthName]	NVARCHAR(20) NOT NULL
			CONSTRAINT PK_DimDatum_datumNyckel PRIMARY KEY (ID)
			);
			SELECT 'Table '+ @table +' existed without data, table dropped and recreated';
		END ELSE
		SELECT 'Table '+ @table +' contains data, no action taken';

And then creating the procedure:

Use [YourDB]
go

IF EXISTS (
	SELECT 'Y'
	FROM sys.objects
	WHERE name = 'AddDates'
	)
	Drop proc AddDates
go

CREATE PROC AddDates
	(
	@StartDate as DateTime,
	@EndDate as DateTime
	)
AS 

  DECLARE @CurrentDate AS DATETIME
  SET @CurrentDate = @StartDate
  WHILE @CurrentDate <= @EndDate
	BEGIN
		INSERT INTO dbo.DimDate
		SELECT
		CAST(CONVERT(nvarchar(10), @CurrentDate, 112) as int) as ID,
		CAST(CONVERT(nvarchar(10), @CurrentDate, 112) as DATETIME) as [Day],
		DATEPART(ISO_WEEK,@CurrentDate) as [Week],
		MONTH(@CurrentDate) as [Month],
		DATEPART(Q,@CurrentDate) as [Quarter],
		YEAR(@CurrentDate) as [Year],
		DatePart(DayOfYear, @CurrentDate) AS DayInYear,
		DATEPART(DD,@CurrentDate) as DayInMonth,
		CASE WHEN DATEPART(WEEKDAY,@CurrentDate) -1 = 0 THEN 7
			ELSE DATEPART(WEEKDAY,@CurrentDate) -1
		END as dayInWeek,
		CASE WHEN DATEPART(WEEK,@CurrentDate) < 10 THEN CAST(YEAR(@CurrentDate) AS NVARCHAR(4)) + '0' +  CAST(DATEPART(WEEK,@CurrentDate) AS NVARCHAR(2))
			ELSE  CAST(YEAR(@CurrentDate) AS NVARCHAR(4)) + CAST(DATEPART(WEEK,@CurrentDate) AS NVARCHAR(2))
		END as YearWeek,
		CASE WHEN MONTH(@CurrentDate) < 10 THEN '0' + CAST(MONTH(@CurrentDate) AS NVARCHAR(2))
			ELSE CAST(MONTH(@CurrentDate) AS NVARCHAR(2))
		END as MonthWithZero,
		CASE
			WHEN DATEPART(WEEKDAY,@CurrentDate) -1 = 1 THEN 'Måndag'
			WHEN DATEPART(WEEKDAY,@CurrentDate) -1 = 2 THEN 'Tisdag'
			WHEN DATEPART(WEEKDAY,@CurrentDate) -1 = 3 THEN 'Onsdag'
			WHEN DATEPART(WEEKDAY,@CurrentDate) -1 = 4 THEN 'Torsdag'
			WHEN DATEPART(WEEKDAY,@CurrentDate) -1 = 5 THEN 'Fredag'
			WHEN DATEPART(WEEKDAY,@CurrentDate) -1 = 6 THEN 'Lördag'
			WHEN DATEPART(WEEKDAY,@CurrentDate) -1 = 0 THEN 'Söndag'
		END	as [DayName],
		CASE
			WHEN MONTH(@CurrentDate) = 1 THEN 'Januari'
			WHEN MONTH(@CurrentDate) = 2 THEN 'Februari'
			WHEN MONTH(@CurrentDate) = 3 THEN 'Mars'
			WHEN MONTH(@CurrentDate) = 4 THEN 'April'
			WHEN MONTH(@CurrentDate)= 5 THEN 'Maj'
			WHEN MONTH(@CurrentDate)= 6 THEN 'Juni'
			WHEN MONTH(@CurrentDate)= 7 THEN 'Juli'
			WHEN MONTH(@CurrentDate)= 8 THEN 'Augusti'
			WHEN MONTH(@CurrentDate)= 9 THEN 'September'
			WHEN MONTH(@CurrentDate)= 10 THEN 'Oktober'
			WHEN MONTH(@CurrentDate)= 11 THEN 'November'
			WHEN MONTH(@CurrentDate)= 12 THEN 'December'
		END	as [MonthName]
		SET @CurrentDate += 1
    END
go

And finally populating the table

exec AddDates '19700101','20201231';

Error at  []: Failed to decrypt protected XML node “DTS:Password” with error 0x8009000B “Key not valid for use in specified state.”. You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.

If you do then this blog post and this one will help you understand why and how you should handle it in the future.

In short: Before you start developing your packages you need to think about deploying the solution to the production environment. What you should do is set your package cariable called ProtectionLevel to DontSaveSensitive, why? Cause you should store your sensitive data in a database and keep your connection data to that table in one package variable. The first link above explains why and the second link above explains how.

http://consultingblogs.emc.com/jamiethomson/archive/2006/01/05/SSIS_3A00_-Suggested-Best-Practices-and-naming-conventions.aspx

The acronymns below should be used at the beginning of the names of tasks to identify what type of task it is.

These acronymns should be used at the beginning of the names of components to identify what type of component it is.

I got errors like

Ambiguity between Input0Buffer.x and Input0Buffer.x

or

The name ‘Output0Buffer’ does not exist in the current context

and while googling the errors I didn’t find much help on the subject.

The errors I had where not caused by the actual Visual C# code I was working on but some settings on hte script component task that I had overlooked.

In my case it was the “SynchronousInputID” that should have been set to “None”. When that was done the errors dissappeared.

Really nice =)

After setting up the basic things on the VPS such as Apache2m MySQL-server and the such I download modx revolution, crete a database for it and go to the setup page only to be greeted by this:

FATAL ERROR: MODx Setup cannot continue.
To use PHP 5.3.0+, you must set the date.timezone setting in your php.ini. Please do set it to a proper timezone before proceeding. A list can be found here.

Thanx for that curveball..
After a bit of googling you learn that you need to set up you date and timezones properly sure enough you type
dpkg-reconfigure tzdata
and set your timezone, but it still doesn’t work so you figure out that you need to edit your php.ini cause as of PHP5.3 the timezone isn’t set by default in php.ini anymore. Fine..

find / -name php.ini

/etc/php5/apache2/php.ini
/etc/php5/cgi/php.ini
/etc/php5/cli/php.ini

so you edit them all adding the line
ini_set('date.timezone', 'Europe/Stockholm');
under the Date section in your php.ini files and it still doesn’t work..?!?! WTF?!

Seems to work for a lot of other people but not for you?! I don’t know why but what you can do is to add the following
ini_set('date.timezone', 'Europe/Stockholm');
to
./core/config/config.inc.php
./setup/index.php
assuming that it is modx you’re working on..
(Thank you mvladk for helping me with this solution)
This issue is not a modx specific issue and unfortunatly I don’t know how to solve the real issue so I have had to accept this solution instead.

From your termnial type:
cat /etc/lsb-release
for me that returns the following

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION=”Ubuntu 10.04.1 LTS”

So, is it a 32-bit system or a 64 bit system?
Type
uname -m
in my case it says i686 which means it is a 32-bit system.
If it says x86_64 then you have a 64 bit system.