SQL Server Reporting Services SSRS Report Builder GUID Error – Item Not Found

Using Report Builder 3.0, SharePoint Integrated Mode and SQL Server 2008R2.

On creating a new report in Report Builder, I kept getting the error:

‘Failed to preview the report. The Item XXX can not be found’.

XXX being a meaningless GUID.

Turns out, the Report needed to be saved to a SharePoint library for the preview to render.

Lean something new every day:

My Error

The Fix, thank you Technet:

http://social.technet.microsoft.com/wiki/contents/articles/982.aspx

Save to a SharePoint Library!

 

 

4PSA – tbrestore from Total Backup for Plesk- phew

 

I bought the 4PSA Total Backup for Plesk some time ago for my Plesk server. Of course, 1 week before I was due to retire the server, it crashed. I had to reimage, and then came the nail biting task of restoring it.
But I had a few errors, I installed the correct version of Total Backup, but when I ran

/usr/local/tbackup/tbrestore

I got the error

 

Error! Cannot cd to directory

‘Crap!’ I thought to myself. Googling didn’t help, nor did the 4PSA forums. Turns out the fix was that I had to specify a local backup directory through the Plesk control panel, for tbrestore to work.

It’s running now, it’s a slow, nail biting experience …..

Migrating from MySQL 4.1 to MySQL 4.0, fixing the missing AUTO_INCREMENT field error

 

After buying a 1and1 managed server, and signing up for two years, I discovered that even in the days of MySQL 5.0, these managed servers are set to use MySQL 4.0,
This sucks for alot of reasons, the main one being the pain in the arse it is to migrate other MySQL databases back to 4.0

After stuffing around at the command line using options like
mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` -p –skip-opt –create-options –compatible=mysql40 –add-drop-table –default-character-set=latin1 mydb > db.sql

It turns out that a bug in mysql4.1 screws up the creation of auto_increment when exporting with compatible=mysql40

Basically this means that if I export from mysql4.1 to mysql4.0, I have to manually add the AUTO_INCREMENT field type to each of the primary keys in the table. And since I’ve had alot of databases to move, each with up to 100 tables, I didn’t really fancy the idea.

So, after stuffing around I found a work around.

Export as normal from phpmyAdmin,

Do a find and replace on the SQL
Find: DEFAULT CHARSET=latin1
And Replace With:

That is just delete all occurances of: DEFAULT CHARSET=latin1

Then find: timestamp NOT NULL default CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
And replace with: timestamp NOT NULL

This seems to do the trick

Worked for a Joomla on 4.1 to 4.0 database conversion
Worked for Zen Cart 1.2.6 to mysql 4.1 to 4.0
Worked for b2Evolution mysql 4.1 to 4.0 database conversion
Worked for Mambo 5 mysql 4.1 to 4.0 database conversion
 

MySQL in and around PLESK really useful commands

I’m always having to look up and figure out all this mysql stuff online. So I’m going to save my favourite commands here. I’ll try to include versions where I can…. Stay tuned.

 

OK, exporting ( dumping from a MySQL database ) in Plesk

mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` –add-drop-table –add-drop-database  –default-character-set=latin1 mydb > db.sql

This bit `cat /etc/psa/.psa.shadow` grabs your PLESK MySQL password.

Add –add-drop-table if you’ll be exporting over an existing database or tables

Add –add-drop-database if you’ll be exporting over an existing database

mydb is the database you want to export from.

db.sql is the file you want to export to.

 

To import the file in to a database, connect to MySQL on your server

Go to the directory that has your db.sql file that you’re going to be importing

mysql -uadmin -p`cat /etc/psa/.psa.shadow` -p

Then enter the password

If you’re importing in to a new database:
The type in USE mydatabasename
Where mydatabasename is the name of the database you’re writing over

now type source db.sql;

remember to put the semi colon in there,
You should see a whole lot of
Query OK, 1 row affected (0.01 sec)
Lines, which is fine. Just wait it out and your import should complete all by itself.

Falling in love again ….

Last weekend, I fired up SQL Server 2005. It was an upscale of an MS Access backend I was using. And my god, did it seriously help me get my app working!!

I used SQL Server for some projects a few years ago, and even trained up in it. And with it’s stored procedures, triggers, user definable functions, cursors, and calcualted columns it rocks! And it’s got a really neat IDE. I’ve also just discovered that Access 2007 can edit SQL Server object nicely. Sweeeeet.

So, oh so much better than mysql. And this is from someone who’s been using mysql for 3 years now.

Mysql’s great as a content store for sites, but if you ever want to RAD an Application, use SQL Server!