SQL Server, girlfriends and speed cameras

I went to work today, yes I know it”s a sunday…a day where god told us not to work. But anyways, I had to migrate a SQL Server Express Edition to an Enterprise Edition for a Sharepoint Server 2007 installation.

I should of stayed home!!! I got caught by a speed camera on my way back home and I still haven”t migrated the damn thing! I had no choice. It was either go to work or getting bad looks from my girlfriend whilst getting poked in the back with the vacuum cleaner. Me and the cat were sitting on the cauch watching tv and I was eating a banana for breakfast although it was already past noon. The cat had pied on a wet towel and the girlfriend went ballistic for it got mad at me so I knew it was time to leave the house leaving the cat behind, desperately looking for a quit spot being scared of the vacuum cleaner.

When I came back at home I yelled I got caught by a speed camera. Put the bloody shoes off!!! I just cleanded the bloody house!!

So far my sunday…it”s getting dark as I write this post, nothing on tv tonight, caught by a speed camera and still no migration.

To be continued with more on the migration…


Initialization failed after reinstalling Reporting Services 2005

My new SSRS failed after reinstalling it with error

“ReportServicesConfigUI.WMIProvider.WMIProviderException: The report server installation is not initialized.”

Even when I used the Reporting Services Configuration Manager to intialize it, it failed on me.
So how do you fix it? Easy peasy! Go to the Reporting Services Configuration Manager and delete encrypted content and restore the key you backup up and voila. Your SSRS will initialize again.

IIS Diagnostic Toolkit

Did you ever do some troubleshooting on authentication and authorization in Reporting Services 2000? You wish you had the Reporting Services 2005 Configuration Manager huh?

Check out the IIS Diagnostic Toolkirt from Microsoft. It helps you check permissions on the folders and authentication among other interesting features.

The tool can be downloaded from:


How to solve a rsInvalidReportServerDatabase error based on the wrong version of the database

The last couple of days I”ve been doing a standard deployment model of Reporting Services 2000.

I ended up with the following error:

The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is ”C.0.6.43”. The expected version is ”C.0.6.54”. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase) Get Online Help

Unfortunately I was using Reporting Services 2000 because in 2005, you can upgrade the database with one single click using the Reporting Services Configuration Manager.

But anyways, I was stuck with this error. I came accros some answers in groups that say you have to reinstall Reporting Services. Pfff, I must of reinstalled it like three times with no luck.

Apparently installing SP1, reboot, install SP2 and reboot did the trick. I performed this procedure twice on two different occasions with the same error so I guess that must be the way to do it.

I hope this information can be of help to someone because it took me a very long time.

My mind to your mind