Metadata Corrupt in RTC | Experiences

Strange errors in RoleTailored Client RDLC reports

Navigate Into Success — Sat, 11 Sep 2010 22:37:56 GMT

We old dogs really have to learn new tricks with RTC (RoleTailored Client), as I found out couple of

re: Metadata Corrupt in RTC | Experiences

Marq — Fri, 10 Sep 2010 13:50:18 GMT

Hi Dean,

Thanks for reading this.

Deleting records in the metadata table were deleted by me hoping that recompiling would solve my issue.

The personalisation went corrupt at exactly the same moment. It started with customised views do be duplicated. (Actualy it showed it five times).

You know the structure way better than I will ever do. Next time I have this (hopefully never) I will call you. ;)

See you next time in Vedbaek.

/Mark

re: Metadata Corrupt in RTC | Experiences

Vjekoslav Babic — Fri, 10 Sep 2010 10:08:23 GMT

Something similar happened to me, regarding corrupt data in Object Metadata table with Report Layouts. For some reason, for two times already, an report stopped working in RTC, however compiling luckily sorted it out, and no errors with Object Metadata table. The problem is - this pops up just out of a blue, and I am sure the same report will stop working again.

Now having read your blog post, I'm starting losing hope :(

re: Metadata Corrupt in RTC | Experiences

Dean McCrae — Fri, 10 Sep 2010 09:42:09 GMT

Mark, without sitting down at the system and debugging it is hard to know what's going on here.

My only guess is that the versions in the Object Tracking table are out of sync with the database (there have been bugs on this in the past). But this will not cause entries to be deleted from the Object Metadata table!

The restore from another database will perhaps set versions that are less than the latest version in the database, thereby 'correcting' the problem.

I think the problem with the personalization causing a crash is a totaly separate problem actually.

re: Metadata Corrupt in RTC | Experiences

waldo — Fri, 10 Sep 2010 07:07:14 GMT

I agree with Marcel .. I experienced the same issues when I use wrong build-numbers.. .

But as you said, they were the same, so that's not the case, probably.

Anyway, it's a golden tip: ALWAYS KEEP YOU BUILDS THE SAME!! Classic, RTC, Server, NAS .. everything!

re: Metadata Corrupt in RTC | Experiences

Marq — Thu, 09 Sep 2010 07:54:32 GMT

@Marcel,

The buildnumbers are the same, only difference is that my local database was a native database, not SQL.

Maybe there is a difference between the fin.exe and finsql.exe.

The fin.exe does not have to compile .net off course.

Is there a stable build that MS recommends to use? From my SQL Perform times I can remember that not all hotfixes are improvements. ;-)

re: Metadata Corrupt in RTC | Experiences

Steve Knott — Wed, 08 Sep 2010 21:16:33 GMT

Welcome to RTC.. .

Happened a few times to me.. fortunately small clients where I could kick everyone off...

Ditto your comment re MS sorting out.... it is needed.

Thanks for the blog

re: Metadata Corrupt in RTC | Experiences

Marcel Lathouwers — Wed, 08 Sep 2010 20:45:34 GMT

Hi Marc,

My first guess would be to get to the latest platform hotfix.

Recently we bumped into strange behaviour, when a object was compiled from a hotfixed client, while the service tier was on the vanila build.

Regards,

Marcel